Register a domain and help support LQ
Go Back > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Fedora This forum is for the discussion of the Fedora Project.


  Search this Thread
Old 05-30-2009, 08:47 PM   #1
LQ Newbie
Registered: Jun 2005
Posts: 19

Rep: Reputation: 0
"unable to access resume device (/dev/dm-1)" after fc10 kernal update

kernal was updated via "software update"

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
title Fedora (
root (hd0,0)
kernel /vmlinuz- ro root=/dev/dm-0 rhgb quiet
initrd /initrd-
title Fedora (
root (hd0,0)
kernel /vmlinuz- ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-
title Fedora (
root (hd0,0)
kernel /vmlinuz- ro root=UUID=bf0dd8cd-ee71-4021-a2ad-f09a532265d0 rhgb quiet
initrd /initrd-
title Other
rootnoverify (hd1,0)
chainloader +1


Last edited by ben201; 05-30-2009 at 08:50 PM.
Old 05-31-2009, 12:50 PM   #2
LQ Newbie
Registered: Jun 2005
Posts: 19

Original Poster
Rep: Reputation: 0
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.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
"internal system error" during fc10 openoffice update LloydM Fedora 0 02-17-2009 11:18 PM
How can I "keep" yum'ed RPMs so I can setup a new FC10 pc WITHOUT internet access? rylan76 Fedora 15 01-09-2009 03:54 PM
lilo says, "L 01 01 01" and fdisk says, "Unable to seek on /dev/hda1" clausawits Linux - General 3 12-31-2007 10:33 PM
Unable to access resume device jdege Linux - General 9 12-20-2007 11:32 PM
"unable to find device node for /dev/x in /dev!" during install zombiedeth *BSD 0 02-02-2004 03:38 AM

All times are GMT -5. The time now is 09:56 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration