[HARDY] Kernel will not Boot after upgrade

Bug #201684 reported by Sam Williams
22
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

just upgrade a second ago and now Hardy will not complete its boot. Turning off "noquiet" in grub we can see that it gets to a point where it is waiting for the root filesystem. Eventually it seems to time-out then default to a character based display with the following message tail on it:

udevd-event[2377]: run_program: ' /lib/udev/vol_id' abnormal exit
udevd-event[2379]: run_program: ' /lib/udev/vol_id' abnormal exit
udevd-event[2384]: run_program: ' /lib/udev/vol_id' abnormal exit
udevd-event[2387]: run_program: ' /lib/udev/vol_id' abnormal exit

we are then dropped into a busibox prompt labeled (initramfs). Not sure what to do at this point. Any help would be appreciated. Really surprised at this type of error so near the formal release of Hardy though.

Thanks

Revision history for this message
KF7EGD (drbrady) wrote :

I can confirm this. Just happened to me.

Revision history for this message
turox (tuxturox) wrote :

confirm this

Revision history for this message
Parthan SR (parth-technofreak) wrote :

Confirming this bug as there as hobodan and turox confirmed, as well as getting duplicates of the same bug.

Changed in linux:
status: New → Confirmed
Revision history for this message
mikeday (mikeday) wrote :

This just happened to me too. However, booting with the 386 kernel (2.6.24-12-386) rather than the generic kernel (2.6.24-12-generic) fixes the problem, at the cost of losing three cpu cores. No other config changes were necessary to make it work. Haven't found any method of making the generic kernel work yet, tried changing bios AHCI/RAID settings to no effect.

Revision history for this message
Rene Hennig (shifty) wrote :

First fix:
Boot Live-CD, mount linux partition an type in terminal:
sudo cp --parent `dpkg -L libc | xargs` /path/to/disk
Now, check the system @ chroot

Revision history for this message
mikeday (mikeday) wrote :

shifty, you mean "libc6", right? What is the fix meant to accomplish?

Revision history for this message
Rene Hennig (shifty) wrote :

Mhh ... Sorry. No more time for any description. I'm still at work. Look here for more information:

http://ubuntuforums.org/showthread.php?t=722886

Revision history for this message
mikeday (mikeday) wrote :

Ah, then perhaps I am having a different bug, as I have libc 2.7-5ubuntu2 and it appears to be working fine. Perhaps I have this bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/33269

A number of other people seem to have fixed the missing root file system by booting 386 instead of generic. Sorry for the noise!

Revision history for this message
iomicifikko (iomicifikko) wrote :

Same problem here, working on Virtualbox.

Revision history for this message
GianlucaDAndrea (acid-burn-x-privat) wrote :

i've solved the libc6 upgrade problem, but this problem still remains, booting the generic kernel image. only selecting the 386 kernel image from the boot loader, i'm able to boot. i think this bug is not a duplicate

Revision history for this message
Colin Watson (cjwatson) wrote :

Gianluca: the reason this happens for one kernel and not the other is due to a difference in when their respective initramfses were last updated. Booting the 386 kernel image and then running 'update-initramfs -u' should clear it up.

Revision history for this message
Martin (martin-zdila) wrote :

i had the same problem; update-initramfs -u fixed the issue :-)

Revision history for this message
Jan-Marc (jmvdb) wrote :

Hi,

I did boot the system with an older kernel, you can choose from GRUB. After logging in I installed "live-initramfs" using the package manager. It seems that it has reconfigured initramfs. Rebooting again and the systems boots well.

Revision history for this message
NoOp (glgxg) wrote :

"first reported on 2008-03-13'

Must have something to do with the 13th... Just did today's upgrades (April 13th) and the linux-restricted 386 kernel drops to initramfs busybox shell. Booting into -generic works fine.

Oddly enough, installing live-initramfs in the working (generic) kernel did not resolve the problem. But then removing (sudo apt-get remove live-initramfs) did, as the removal regenerated new boot initrd.img's for all the installed kernels.

$ sudo apt-get remove live-initramfs
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  user-setup busybox
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  live-initramfs
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 373kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 150602 files and directories currently installed.)
Removing live-initramfs ...
update-initramfs: Generating /boot/initrd.img-2.6.24-16-generic
update-initramfs: Generating /boot/initrd.img-2.6.24-16-386
update-initramfs: Generating /boot/initrd.img-2.6.24-15-generic
update-initramfs: Generating /boot/initrd.img-2.6.24-15-386
update-initramfs: Generating /boot/initrd.img-2.6.24-14-generic
update-initramfs: Generating /boot/initrd.img-2.6.24-14-386

Revision history for this message
Jim-Moroski (jmlm1977) wrote :

I'm brand new to this and it's my first install of ubuntu 8.04.1 x86_64 (Hardy). Are the commands listed above entered at the (initramfs)> prompt???

The libc references above don't mean anything to me at this point because I'm unfamiliar with the architecture.

Is the update-initramfs command entered from the initramfs prompt?

How do you install live-initramfs with the package manager? How do you run the package manager?

Should I try the x386 version of Hardy ? If so, will the install put it in its own partition or will it overwrite the x64 version? Will it prompt me to put it in its own partition?

Sorry for all the questions, but I'm REALLY new at installing.
Thanks for any help in advance.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.