jrickman@xxxxxxxxxxx writes:
The only common thread I can find in all three systems is the following filesystem format setups: /boot runs EXT3 / runs EXT4 /home runs EXT4 /var runs EXT4 /tmp runs EXT4
Given that EXT4 is a relative newcomer, and you claim that your boot progress halts at the point where you expect the kernel to issue some EXT4 status messages, this strongly suggests EXT4 borkage in this kernel build.
These kinds of things happen, from time to time. Your only realistic option is to wait for the next kernel update, and hope that it gets fixed. You may consider opening a bug in Bugzilla; that might help things. If there are multiple reports in Bugzilla pointing the finger at ext4, this should catch someone's attention.
You may also consider booting the most recent working kernel with the "forcefsck" option, to force a fsck on all your ext4 partitions, in the event that your fubarage got triggered by minor filesystem corruption, but that's a long shot.
Attachment:
pgp1i0ZnA3f5E.pgp
Description: PGP signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
