"unable to access resume device (/dev/dm-1)" after fc10 kernal update
FedoraThis forum is for the discussion of the Fedora Project.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
title Fedora (126.96.36.199-170.2.68.fc10.x86_64)
kernel /vmlinuz-188.8.131.52-170.2.68.fc10.x86_64 ro root=/dev/dm-0 rhgb quiet
title Fedora (184.108.40.206-170.2.56.fc10.x86_64)
kernel /vmlinuz-220.127.116.11-170.2.56.fc10.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
title Fedora (18.104.22.168-117.fc10.x86_64)
kernel /vmlinuz-22.214.171.124-117.fc10.x86_64 ro root=UUID=bf0dd8cd-ee71-4021-a2ad-f09a532265d0 rhgb quiet
I fixed the problem. Looks like this is what happened.
When ntfs-3g was installed, the /dev/VolGroup00/LogVolnn entries in fstab were replaced with /dev/dm-n
Later when the kernal was updated, /dev/dm-0 ended up in grub.conf as root for the new kernal. This caused the problem finding the root at boot time.
What I did was replace the /dev/dm-n entries with /dev/VolGroup00/LogVolnn in both fstab and grub.conf. Then used mkinitrd to rebuild the boot image. No problems so far on the new kernal.