F14: after kernel update, can't boot (from software RAID)

[Alain Spineux]

On Wed, May 11, 2011 at 11:25 AM, Neil Bird <neil at fnxweb.com> wrote:
>
>   I did a belated update of my Fedora 14 box last night, which included a
> new kernel (2.6.35.13-91.fc14.i686.PAE, previous was
> 2.6.35.11-83.fc14.i686.PAE).  However, upon trying to boot, it slept for a
> little bit, then said something like:

Be sure to have your  mkinitrd  package up2date

# yum update mkinitrd

Then try to rebuild your initramfs file for your NEW kernel (DON'T
touch your old and working initramfs) using something like :

# mkinitrd -f  /boot/initramfs-2.6.35.11-83.fc14.i686.img 2.6.35.11-83.fc14.i686

some version of mkinitrd in the past where not handling raid very well.

Good luck

>
> Fatal: no boot partition found, sleeping forever
>
>   (paraphrasing, I neglected to write the exact message).
>
>
>   I can boot fine if I select the older kernel.
>
> title Fedora (2.6.35.13-91.fc14.i686.PAE)
>         root (hd0,0)
>         kernel /boot/vmlinuz-2.6.35.13-91.fc14.i686.PAE ro root=/dev/md0
> apm=power-off rdblacklist=nouveau vga=0x318 quiet rhgb LANG=en_GB.UTF-8
> KEYTABLE=uk
>         initrd /boot/initramfs-2.6.35.13-91.fc14.i686.PAE.img
>
> title Fedora (2.6.35.11-83.fc14.i686.PAE)
>         root (hd0,0)
>         kernel /boot/vmlinuz-2.6.35.11-83.fc14.i686.PAE ro root=/dev/md0
> apm=power-off rdblacklist=nouveau vga=0x318 quiet rhgb LANG=en_GB.UTF-8
> KEYTABLE=en-gb
>         initrd /boot/initramfs-2.6.35.11-83.fc14.i686.PAE.img
>
>
>
>   The complication is that I'm using partition-mirrored RAID (2x drives,
> identically partitioned, then /dev/mdX mirror-RAID devices applied to those
> partitions, so /dev/sda0 & /dev/sdb0 -> /dev/md0 (my root/boot partition).
>
>   It kind of feels like the initramfs has been mis-created without RAID
> support, but I'm not sure how to check.
>
>   I think there's been something iffy with my initramfs creation for a
> while, as I always get errors about not being able to find the listed
> KEYTABLE and SYSFONT (when present) files, although they're on my HD,
> nomatter what values I give.
>
>   In fact, I get SYSFONT errors even with the above (nothing specified).
> As it happend, those two errors (in quiet mode) are all I get when trying to
> boot the new kernel, before a ~10s. sleep and then the fatal error.
>
>   Non-quiet mode didn't show me anything in particular;  I'll try it again
> later with the kernel's 'slow-boot-output' enabled (boot_delay=n).
>
> --
> [neil at fnx ~]# rm -f .signature
> [neil at fnx ~]# ls -l .signature
> ls: .signature: No such file or directory
> [neil at fnx ~]# exit
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>



-- 
Alain Spineux                   |  aspineux gmail com
Monitor your iT & Backups |  http://www.magikmon.com
Free Backup front-end       | http://www.magikmon.com/mksbackup
Your email 100% available |  http://www.emailgency.com