> This sounds like the same situation I ran into with Fedora 7. > > Rebuilding the initrd for the new kernel fixed the problem. > > Kenny Thanks for the thought Kenny! Hadn't even ocurred to me that might be necessary. :) Well, and that's because it shouldn't be. Anyway, this whole situation is odd to me. If you edit your fstab to remove "relatime" and recompile your initial rd, then change your fstab back to include relatime again... THEN you can get the new kernel to boot properly. Just recompiling initrd without removing relatime from your fstab isn't gonna make a difference. To give more detail, it throws up an "Unrecognized mount option 'relatime' or missing value" error. Then of course everything else fails (setting up dev, proc, sys, and passing ctl to init). So the question is, why is this happening? Obviously, it shouldn't be happening. Gary: I didn't look at the link Kenny gave, but fyi it's trivial to rebuild an initrd img after you remove relatime from your fstab. In your case I believe you'd just be running as root: mkinitrd /path/to/initrd-to-create.img kernel-version or, explicitly: # mkinitrd -f /boot/initrd-2.6.26.6-79.fc9.x86_64.img 2.6.26.6-79.fc9.x86_64 (which would replace your current /boot/initrd-$brokenkernel.img file with a new one.) -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
