After using ntfs-config, upon restart, boot halts: Unable to access resume device

[davidfreeman]

This was Fedora x86_64 using ntfs-config-1.0.1-2.fc10.noarch. I am excerpting my comment #7 from the Redhat bug at https://bugzilla.redhat.com/show_bug.cgi?id=475266 .

In my case, this seems to have proceeded from the utility ntfs-config
substituting the dm-n/dmsetup filesystem names for the LVM lv names in
/etc/fstab. I was able to work around my version of this problem by modifying
/etc/fstab with a reversal of that substitution and then running mkinitrd.

I experienced this:

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

after

  1. using the GUI 'ntfs-config', which had generated a new /etc/fstab file
(and thankfully left a useful turd at '/etc/fstab-ntfs-config-save'), and then
before rebooting
  2. updating from 2.6.27.21-170.2.56.fc10.x86_64 to
2.6.27.24-170.2.68.fc10.x86_64 :

with kernel 2.6.27.24-170.2.68.fc10.x86_64 with three LVM volumes, when the
following relevant entries in fstab continued to boot just fine for the
preceding kernel's (2.6.27.21-170.2.56.fc10.x86_64) image:

#############################
# <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
/dev/dm-1 /storage ext3 defaults 1 2
/dev/dm-2 swap swap defaults 0 0
#############################

...and after reading the helpful blog post of someone who experienced the same
syndrome at
http://ratnadeepdebnath.wordpress.com/2009/03/11/resolved-kernel-boot-problem-d/
, I edited my /etc/fstab to use the LVM filesystem names instead of the 'dm-n'
dmsetup filesystem names and contain the following relevant entries:

#############################
# <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
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
/dev/VolGroup00/LogVol01 /storage ext3 defaults 1
2
/dev/VolGroup00/LogVol02 swap swap defaults 0 0
#############################

...then ran:

  mkinitrd -f -v /boot/initrd-2.6.27.24-170.2.68.fc10.x86_64.img
2.6.27.24-170.2.68.fc10.x86_64

...and was able to boot to both the new kernel and the preceding kernel.

[Florent Mertens (givre)]

Interesting issue, but there is several things that I don't understand:
- Which device path worked for you, /dev/dm-0 or /dev/VolGroup00/LogVol00 ?
- Which device path did ntfs-config wrote in fstab ?