Description of problem: Kernel halts with message complaining about the resume device. Version-Release number of selected component (if applicable): kernel-2.6.27.5-117.fc10.i686 How reproducible: Always Steps to Reproduce: 1. boot kernel 2. 3. Actual results: Unable to access resume device (/dev/dm-2) mount: error mounting /dev/root on /sysroot as ext3: No such file or directory Expected results: bootable kernel Additional info: I have uninstalled this kernel and reinstalled to to rebuild the initrd and that did not help. I do not use suspend/resume on this system. Previous kernel 2.6.27.5.109 does not exhibit this problem.
Same problem in kernel-2.6.27.7-134.fc10.
Same problem in kernel-2.6.27.9-159.fc10.
Same problem in kernel-2.6.27.12-170.2.5.fc10
Same problem in kernel-2.6.27.15-170.2.24.fc10
Same problem in kernel-2.6.27.21-170.2.56.fc10 If someone could tell he how I should attempt to debug this, I'd be happy to give it a try. I'm not quite sure where to start looking.
Same problem in the PAE model: kernel-PAE-2.6.27.21-170.2.56.fc10 (i686) I boot with previous kernel-PAE-2.6.27.19-170.2.35.fc10 (i686), that goes sill oke, but mount already does not show the real logical volume names, but the internal names. Relevant lines from the output are: /dev/dm-0 on / type ext3 (rw) /dev/sda1 on /boot type ext3 (rw) /dev/dm-2 on /home type ext3 (rw) /dev/dm-1 on /var type ext3 (rw) So maybe it is not directly a kernel problem, but more something from the logical volume manager.
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.
(In reply to comment #7) > 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 : > Did you file a bug against ntfs-config?
Thanks to the comment in #7, I straightened out my /etc/fstab (from the backup) and rebuild initrd. Now everything is back to normal. Looks like a ntfs-config bug - any objections to moving this bug to ntfs-config?
Created bug against ntfs-config at https://bugs.launchpad.net/bugs/383816 .
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.