device-mapper fails after upgrade to hardy

[Stephen Hill]

device mapper fails when using hardy kernels, after upgrade to hardy from gutsy.
If I use one of my pre-built 2.6.24.6 kernels (built from kernel.org source) it woks fine.
I am beginning to suspect evms as I know it has been deprecated, and which I do have installed, but I'm not sure how to rectify the situation.

On boot I get:
 device-mapper: table: 254:5: linear: dm-linear: device lookup failed

 fsck.ext3: No such file or directory while trying to open /dev/mapper/hda5

Info:

sudo blkid
 /dev/mapper/Ubuntu-swap_1: TYPE="swap"
 /dev/evms/lvm2/Ubuntu/swap_1: TYPE="swap"
 /dev/evms/lvm2/Ubuntu/root: UUID="d5944973-ea27-4fe4-a133-9eb07ddcc8a8" SEC_TYPE="ext2" TYPE="ext3"
 /dev/hda5: UUID="8f1629c2-be2f-402f-9c5c-9ab2b4f42218" SEC_TYPE="ext2" TYPE="ext3"
 /dev/mapper/Ubuntu-root: UUID="d5944973-ea27-4fe4-a133-9eb07ddcc8a8" SEC_TYPE="ext2" TYPE="ext3"
 /dev/mapper/lvm2|Ubuntu|swap_1: TYPE="swap"
 /dev/mapper/hda5: UUID="8f1629c2-be2f-402f-9c5c-9ab2b4f42218" TYPE="ext3"
 /dev/hda6: UUID="Te8N4E-iBOH-Ou75-IvMA-vRKW-zhXf-edN6K9" TYPE="lvm2pv"
 /dev/hda7: UUID="6KypRZ-l129-cf6T-RaXk-QCTH-9Arq-C1cIDB" TYPE="lvm2pv"
 /dev/mapper/hda6: UUID="Te8N4E-iBOH-Ou75-IvMA-vRKW-zhXf-edN6K9" TYPE="lvm2pv"
 /dev/mapper/hda7: UUID="6KypRZ-l129-cf6T-RaXk-QCTH-9Arq-C1cIDB" TYPE="lvm2pv"

cat /etc/fstab
 # /etc/fstab: static file system information.
 #
 # <file system> <mount point> <type> <options> <dump> <pass>
 proc /proc proc defaults 0 0
 /dev/mapper/Ubuntu-root / ext3 defaults,noatime,errors=remount-ro,commit=43200 0 1
 /dev/mapper/hda5 /boot ext3 defaults,noatime 0 2
 /dev/mapper/Ubuntu-swap_1 none swap sw 0 0
 /dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0
 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

[wolfger (wolfger)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in devmapper.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

[Stephen Hill (steve-d-hill)]

I manually changed my /boot/grub/menu.lst and /etc/fstab files to use UUIDs, and the problem has gone.

[wolfger (wolfger)]

I'm setting to "invalid" since you have fixed your problem, and UUID (which you manually implemented) is the default for Ubuntu. If you feel this bug still needs to be fixed, please reopen it by setting the status back to new, and explaining what you believe the problem to be.