JD wrote:
The pertinent failure message in both of these kernels is:
[ 29.653980] dracut Warning: No root device
"block:/dev/disk/by-uuid/03f82b3c-5163-465b-a4c3-3bcb349a1cc4" found
[ 29.654857] dracut: + emergency_shell No root device
"block:/dev/disk/by-uuid/03f82b3c-5163-465b-a4c3-3bcb349a1cc4" found
[ 29.654966] dracut: + set +e
[ 29.655231] dracut: + [ No root device
"block:/dev/disk/by-uuid/03f82b3c-5163-465b-a4c3-3bcb349a1cc4" found = -n ]
[ 29.655359] dracut: + _rdshell_name=dracut
[ 29.655443] dracut: + echo
[ 29.655512] dracut:
[ 29.655593] dracut: + echo
[ 29.655661] dracut:
[ 29.655880] dracut: + warn No root device
"block:/dev/disk/by-uuid/03f82b3c-5163-465b-a4c3-3bcb349a1cc4" found
[ 29.655984] dracut: + check_quiet
[ 29.656096] dracut: + [ -z yes ]
[ 29.656353] dracut: + echo <28>dracut Warning: No root device
"block:/dev/disk/by-uuid/03f82b3c-5163-465b-a4c3-3bcb349a1cc4" found
[ 29.656613] dracut: + echo dracut Warning: No root device
"block:/dev/disk/by-uuid/03f82b3c-5163-465b-a4c3-3bcb349a1cc4" found
[ 29.656860] dracut: dracut Warning: No root device
"block:/dev/disk/by-uuid/03f82b3c-5163-465b-a4c3-3bcb349a1cc4" found
[ 29.656981] dracut: + source_hook emergency
[ 29.657169] dracut: + source_all /lib/dracut/hooks/emergency
[ 29.657278] dracut: + local f
[ 29.657426] dracut: + [ /lib/dracut/hooks/emergency ]
[ 29.657590] dracut: + [ -d //lib/dracut/hooks/emergency ]
[ 29.657794] dracut: + [ -e //lib/dracut/hooks/emergency/50plymouth-emergency.sh ]
[ 29.660236] dracut: + . //lib/dracut/hooks/emergency/50plymouth-emergency.sh
The system then drops into the shell.
Bug ID 822792 at bugzilla.redhat.com is about this problem.
However, I am stuck booting kernel-3.3.4-3.fc16.i686 which does not have this
problem.
I have received no further updates on this problem, which might be unique to my
laptop???
I have also uploaded to the bug the full log of dracut and a file output of rpm
-qa in order
for the devs to see which package might be the culprit.
Don't think it's you, although it doesn't seem to be universal. Some hardware
seems to trigger a different output from the blkid calc, while most work. That's
only based on three upgrades, two worked fine, one did as you say, haven't
gotten to building a 3.4 kernel yet, on my to-do list for the weekend.
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
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
Have a question? Ask away: http://ask.fedoraproject.org
