kernel panic after upgrade ubuntu server from 10.04 to 12.04

[Laurent B.]

After an upgrade from Ubuntu Server 10.04 to 12.04, the system didn't restart.

Just after (silent) grub I have:
The disk drive for / is not ready yet or not present.
Continue to wait, or Press S to skip mounting or M for manual recovery.

Nothing can be done at this stage (S or M doesn't work)

Then I followed http://ubuntuforums.org/showthread.php?t=1507558 (at the bottom of the thread), just a bit more complicated as my system is using LVM(found a nice tuto on how to mount LVM), but finally was able to follow the procedure:

- I mounted my root partition, chrooted to it
- I fixed all the issues regarding apt dependencies (there was a lot).
- Re-installed linux-image-3.2-29-generic
- update-grub
- grub-install /dev/sda (maybe there I should have used sda1...)

FYI my system is as follow:
sda1 linux partition (small) that seems to contain only grub stuff
sda4 logical
sda5 LVM, my real / partition in my original install

After all of this I get a:
Kernel panic - not syncing: Attemped to kill init!
Pid: 1, comm: run-init Not tainted 3.2.0-29-generic #46-Ubuntu

Then I retried the procedure but before re-installing the kernel, I mounted /dev/sda1 (the one that seems containing grub stuff) on /boot (of my chrooted partition) wondering if it was not needed by grub...
No success.

This server was running the 10.04 for years...

Please any help welcome as this server is the center piece of my home network.

Thank you in advance,

- Laurent -

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1044749

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Laurent B. (lbnetid+lp)]

This problem occurs much before I can type anything in a console... It's a kernel panic, so not boot, at all even in "safe" mode.
following you advise I will then change the status to confirmed.
Thanks

[Laurent B. (lbnetid+lp)]

Problem is now fixed.

I actually found the solution in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/613273
It was really the problem of /run pointing to /var/run pointing to /run ...

The only thing I had to add compared to the solution described was to create /run/lock/lvm directory. Creating /run was not sufficient when trying to update-grub. My system is using LVM, thus...

A big thank you to http://www.linux-azur.org/ that helped me a lot on the issue.

Nevertheless I think there is a problem with the installer. It was the very first time I upgraded from an LTS to an LTS, all my other machines follow the normal cycle. I thought it would be a bit more... how to say... polished. I never had issue upgrading from one version to another on any machine except standard stuff like config file format changed etc, but having a machine stuck at early stage of boot was definitely not what I expected. So -1 to the LTS... Normally you would stay on an LTS because you care of the machine stability.Hopefully not the same story for 14.04.

Regards,
- Laurent -

[Laurent B. (lbnetid+lp)]

Assigning to update-manager as the issue is really related to the upgrade process itself even though my personal problem is now fixed.