LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   "unable to access resume device (/dev/dm-1)" after fc10 kernal update (https://www.linuxquestions.org/questions/fedora-35/unable-to-access-resume-device-dev-dm-1-after-fc10-kernal-update-729582/)

ben201 05-30-2009 07:47 PM

"unable to access resume device (/dev/dm-1)" after fc10 kernal update
 
kernal was updated via "software update"
from 2.6.27.21-170.2.56.fc10.x86_64
to 2.6.27.24-170.2.68.fc10.x86_64

Now system won't boot, getting the following error:

unable to access resume device (/dev/dm-1)
mount: could not find filesystem '/dev/root'

My /etc/fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>

tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/dm-0 / ext3 defaults 1 1
#Entry for /dev/sda1 :
UUID=29487531-ac9c-41bf-8c11-e383011f6c94 /boot ext3 defaults 12
#Entry for /dev/sdc2 :
UUID=E4DC56B7DC568428 /media/RAID_DATA ntfs-3g defaults,nosuid,nodev,locale=en_US.UTF-8 0 0
#Entry for /dev/sdb1 :
UUID=5078C75878C73B8A /media/disk ntfs-3g defaults,nosuid,nodev,locale=en_US.UTF-8 0 0
/dev/dm-1 swap swap defaults 0 0

My /boot/grub/grub.conf

# 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
#boot=/dev/sda
default=0
timeout=2
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.27.24-170.2.68.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.24-170.2.68.fc10.x86_64 ro root=/dev/dm-0 rhgb quiet
initrd /initrd-2.6.27.24-170.2.68.fc10.x86_64.img
title Fedora (2.6.27.21-170.2.56.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.21-170.2.56.fc10.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.27.21-170.2.56.fc10.x86_64.img
title Fedora (2.6.27.5-117.fc10.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=UUID=bf0dd8cd-ee71-4021-a2ad-f09a532265d0 rhgb quiet
initrd /initrd-2.6.27.5-117.fc10.x86_64.img
title Other
rootnoverify (hd1,0)
chainloader +1


Thanks

ben201 05-31-2009 11:50 AM

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.


All times are GMT -5. The time now is 09:00 AM.