>>> When a few weeks ago the new auto-updated kernel would not boot,
>>> used an older kernel, waiting for the next update. This was today, and
>>> now the two latest kernels don't work. Booting stops after the Fedora
>>> logo fills up white, after which it says (copying manually from
>>> screen, whitespaces probably not correct):
>>> ERROR: asr: wrong # of devices in RAID set "asr_BOOT " [1/2] on /dev/sda
>>> No root device found
>>> Boot has failed, sleeping forever
>>> The third oldest kernel apparently boots fine. Interestingly, Google
>>> finds nothing for "ERROR: asr: wrong".
>> If you add the following entry to your grub.conf, can you boot from it?
>> title Fedora Test (22.214.171.124-174.2.3 with 126.96.36.199-162 initramfs)
>> root (hd0,0)
>> kernel /vmlinuz-188.8.131.52-174.2.3.fc12.i686 ro
>> root=UUID=7dc291fd-739e-4280-8196-c906e8b6ea00 rhgb quiet
>> SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
>> initrd /initramfs-184.108.40.206-162.fc12.i686.img
> Yes, that one actually booted! Does that provide any insight?
It means that the initramfs files of the new kernels are not loading
dmraid either because the dmraid module is not being loaded, "dmraid
-ay is not being run or both."
Do you have any dracut and/or dmraid errors in
Is there a dmraid directory or module in
You probably already know this but change in /etc/yum.conf
installonly_limit=3 to a higher value,
I have mine set to 5. This means the next kernel update you get won't erase your only
¡Encuentra las mejores recetas
con Yahoo! Cocina!
-- users mailing list [email protected] To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines