problems with 10.04 upgrade to 12.04 (procps)

[NoOp]

On 09/07/2012 11:43 AM, Liviu Andronic wrote:
> On Fri, Sep 7, 2012 at 7:04 PM, NoOp ...
>> I see you got this sorted out:
>> <https://bugs.launchpad.net/ubuntu/+source/procps/+bug/602896/comments/18>
>>
> Almost.. I indeed managed to complete the upgrade by following the
> suggestion in comment 17 in the bug above: There are no more packages
> to configure/update/install.
> 
> However, I'm still unable to boot Precise. Using default kernel
> parameters (for 3.2.0) I get the following messages:
> [..]
> Begin: Running /scripts/init-bottom ... done.
> could not log bootup: Address already in use
> [ 10.1 ] init: plymouth main process (327) terminated with status 69
> mount: Too many levels of symbolic links
> mountall: mount /run [349] terminated with status 32
> mountall: Filesystem could not be mounted: /run
> An error occurred while mounting /run.

Are you able to boot to recovery mode? If so, can you try the dpkg option?

> 
> 
> Then I press S to skip mounting and I get the following:
> The disk drive for / is not ready yet or not present.
> Skipping /run at user request
> udevd[359]: error: runtime dir '/run/dev/' not writable, for now
> falling back to '/dev/.udev'
> 
> 
> Next I press M for manual recovery and get this:
> Root filesystem check failed.
> A maintenance shell will now be started.

That sounds like the cryptswap issue:
<https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/874774>
if so, then generally it will time out after a moment or two.

> 
> 
> All this looks strange to me, as I force checked / (and all other FS)
> and they're all clean. I'm wondering though if after installing all
> the packages there were some Precise-specific scripts that didn't get
> executed to prepare the new OS. Among other things, perhaps /etc/fstab
> didn't get updated? (Here's my current /etc/fstab:
> http://paste.ubuntu.com/1191361/ )

Do the UUID's match against:

$ sudo blkid

And  does
$ sudo fdisk -l
show the cryptswap?

> 
> Should I run 'do-release-upgrade' again?

Try the recovery dpkg option first.

> 
> Regards
> Liviu
>