Distribution upgrade from K12.04 to K12.10 64bit stopped at 68%.

[Shabakthanai]

I am at 68% of installing the distribution upgrade in Kubuntu. The last line of install is: Starting RoarAudio: | . Can this upgrade be salvaged? Final 32% of the install, cleanup and restart and a very long process is finished. Thanks in advance for your wisdom. Current version of KDE is 4.9.4, if important.

[pauly]

at grub select advanced options, select recovery, select repair broken and continue the upgrade.

[Shabakthanai]

I paused again with this at the last:

fsck from util-linux 2.20.1
fsck from util-linux 2.20.1
/dev/sda6: Superblock last write time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set.) FIXED.
/dev/sda6: clean, 19016/12025856 files, 4076597/48095488 blocks

The cursor '_' is blinking as though perhaps the computer may still be working, but it is not moving at all. Is there anything else I should do? If not, what is my next step, fresh install? Nice seeing you again Pauly. Thanks!

at grub select advanced options, select recovery, select repair broken and continue the upgrade.

[pauly]

If you restart can you login or just a blinking cursor?

[pauly]

you could go to root konsol in recovery and try.

sudo apt-get -f dist-upgrade

or try this

https://help.ubuntu.com/community/LiveCdRecovery

[Shabakthanai]

Dear pauly,

Here is the command reply:

root@Yeshuah2:~# apt-get -f dist-upgrade
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: dpak was interrupted. you must manually run 'dpkg --configure -a' to correct the problem.
root@Yeshuah2~# dpkg --configure -a
dpkg: error: unable to access dpkg status area: Read-only file system
root@Yeshuah2:~# _

When I attempt to open regularly, the computer boots to a black screen with Kubuntu centered on the desktop and 5 dots below the OS name, with a blinking cursor following the 5th dot. I have never seen this before; that is the reason I described the appearance. The upgrade that I am attempting is in my laptop, which is a dual-boot with Windows Vista, and I am able to boot to the Vista OS. Do you have any further ideas, my friend. If and when I appear to be at a point of 'time to reinstall K12.10 from a DVD', I am ready, however, if you think we can still solve my problem, I would prefer it. I am learning quite a bit in the process. Thank you for your patience.

you could go to root konsol in recovery and try.

sudo apt-get -f dist-upgrade

or try this

https://help.ubuntu.com/community/LiveCdRecovery

[SteveRiley]

black screen with Kubuntu centered on the desktop and 5 dots below the OS name, with a blinking cursor following the 5th dot

Ubuntu incorporates a subsystem called Plymouth, which really does nothing more than put up the pretty splash screen you see during boot. Normally, the Plymouth splash is graphical; but for some reason, your incomplete upgrade has resulted in the text-mode Plymouth splash screen appearing instead. (Personally, I loathe Plymouth, because it conceals useful boot-time status messages.)

Here is the command reply:

root@Yeshuah2:~# apt-get -f dist-upgrade
W:  Not using locking for read only lock file /var/lib/dpkg/lock
E:   dpak was interrupted.  you must manually run 'dpkg --configure -a' to correct the problem.
root@Yeshuah2~# dpkg --configure -a
dpkg:  error:  unable to access dpkg status area:  Read-only file system
root@Yeshuah2:~# _

Something is causing Kubuntu to think there's a problem with your filesystem, and is therefore mounting it as read-only for protection. The usual troubleshooting step is to boot into recovery mode and run a filesystem check on each partition:

fsck /dev/sda1

fsck /dev/sda2

...

And take corrective action based on what you see. I'd like you to do this before I suggest additional steps.

[Shabakthanai]

The boot continues to a screen that just shows the word Kubuntu in the center with 5 dots below it. At the end of the dots is a blinking cursor.

If you restart can you login or just a blinking cursor?

[Shabakthanai]

steven@Yeshuah:~$ fsck /dev/sda1
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
/dev/sda1 is mounted.



WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.


Do you really want to continue<n>? no
check aborted.
steven@Yeshuah:~$ fsck /dev/sda2
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext2: No such file or directory while trying to open /dev/sda2
Possibly non-existent device?
steven@Yeshuah:~$

Ubuntu incorporates a subsystem called Plymouth, which really does nothing more than put up the pretty splash screen you see during boot. Normally, the Plymouth splash is graphical; but for some reason, your incomplete upgrade has resulted in the text-mode Plymouth splash screen appearing instead. (Personally, I loathe Plymouth, because it conceals useful boot-time status messages.)


Something is causing Kubuntu to think there's a problem with your filesystem, and is therefore mounting it as read-only for protection. The usual troubleshooting step is to boot into recovery mode and run a filesystem check on each partition:

fsck /dev/sda1

fsck /dev/sda2

...

And take corrective action based on what you see. I'd like you to do this before I suggest additional steps.

[SteveRiley]

You missed a bit:

The usual troubleshooting step is to boot into recovery mode and run a filesystem check

[Shabakthanai]

I tried again, this time:

fsck from util-linux 2.20.1
fsch from util-linux 2.20.1
/dev/sda6: 19016files (0.4%) non-contiguous), 4076597/48095488 blocks
/dev/sda3: 4076597/942858 files (0.2% non-contiguous), 3438685/3771392 blocks.

I have no idea what any of this means.

[/QUOTE]

[sithlord48]

now ur susposted to try to boot again. if you can boot then you should naturally run dpkg --configure -a to let dpkg finish what it was doing.i once wrote a how to for fixing these kinds of problems it might mention ppa's but its advice also applys to distro upgrades

[Shabakthanai]

I restarted and booted in recovery mode chose root for a konsole, and got the following:

dpkg: error: unable to access dpkg status area: read only file system. I then entered "restart". Instead of restarting, the computer opened at the point in the installation procedure that it stalled at at the beginning of this post. It was stalled again, so I shutdown and booted into the other OS. Do you see anything else I can do to try to fix this problem? Thanks for your part in trying to help, sithlord.

now ur susposted to try to boot again. if you can boot then you should naturally run dpkg --configure -a to let dpkg finish what it was doing.i once wrote a how to for fixing these kinds of problems it might mention ppa's but its advice also applys to distro upgrades

[vinnywright]

I see where you posted fsck output from sda6 and sda3 ,,,, what about the rest of your partitions ? especially the / one whatever it may be (sda1?)

and that recovery mode root konsole is where you should be running the fsck from.

VINNY

[Shabakthanai]

Hi vinnywright, I made the fsck from the konsole from within the recovery mode, as you say I should. That was the total report! Do you want me to try again? I suspect if I do it will provide the same data.

I see where you posted fsck output from sda6 and sda3 ,,,, what about the rest of your partitions ? especially the / one whatever it may be (sda1?)

and that recovery mode root konsole is where you should be running the fsck from.

VINNY