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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/11/2011 12:25 PM, Neil Bird 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:
did you, by any chance, patched your mkinitrd to support md_dX? (partitionable raid1)? if so, if your mkinitrd was updated you have to re-apply the patch and mkinitrd an new initrd
HTH,
Adrian


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).



--
Best regards,
Adrian

-------------------------------------------------------
Adrian Sevcenco - Institute of Space Sciences, Romania
-------------------------------------------------------

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

-- 
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
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux