System broken after upgrade to kernel-3.3.2-1.fc16.i686

I have just upgraded two systems to kernel-3.3.2-1. One system (x86_64
hardware) upgraded flawlessly. The other (i686 hardware) now won't
boot. The grub menu comes up allowing me to choose between:
kernel-3.3.2-1.f16.i686 -- which fails (see below)
kernel-3.3.0-0.f16.i686 -- which works
When I choose kernel-3.3.2-1, there is what seems like an exceptionally
long pause, the system briefly displays some garbage, and then these
messages appear:


dracut warning no root device "block:/dev/disk/by-uuid/2d...af"
found

dracut warning no root device "block:/dev/disk/by-uuid/2d...af"
found

dropping to debug shell

sh: 0 can't access tty: job control turned off

dracut:/#


In fact, as blkid shows the device (partition) that the system appears
to be looking for is not there. However all the partitions that should
be on the system are there, including the partition that is normally
mounted on /boot. Which must be so, since the previous kernel starts
OK.

Questions:

1. What's going on here?
2. How can I fix it?
3. How can I prevent this in the future?


Many thanks - jon


--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Relevant Pages

  • fixing grub : mbr fix when windows install after linux
    ... "There is not a boot manager screen at all, ... windows but GRUB boot window does not appear. ... "I forgot to install GRUB, I didn't install GRUB in the MBR, I chose ... Fedora but that was not an active primary partition". ...
    (comp.os.linux.misc)
  • Re: Fedora Core 2/Windows XP dual boot: selecting Linux doesnt work
    ... grub is installed on the /root partition, which is the first partition on hdc: hdc1, or in grub notation. ... Stage1 is the unpatched 512-byte file, that is patched and copied to the boot record during setup. ... This byte is initialized to 0xff in the stage1 file, but patched to 0x81 in your setup, to say "we are booting from disk." ...
    (comp.os.linux.setup)
  • Re: [opensuse] Yast & Grub bootloader different.
    ... My Grub bootup menu is different than the bootloader ... that shows up on the logon screen aat boot time. ... any boot loader for that matter, can only operate on one /boot partition at ... Grub doesn't scour the all hard drives on each install ...
    (SuSE)
  • Re: [Fwd: Re: [opensuse] Boot magic]
    ... Since I installed some milestones I can no longer boot the partition I want. ... I installed on part3 milestone 6 with its own boot directory in the rootdir. ... I only use the milestone 6 grub environment against my will. ...
    (SuSE)
  • Re: Boot manager for Windows only
    ... And also is GRUB capable of booting any ... > Windows partition or will it always hand over to the XP boot loader? ...
    (comp.os.linux.setup)