No UUID's for DMRAID block devices

[Chris Coulson]

Binary package hint: dmraid

I have just done a fresh install of Intrepid beta using the alternate CD, so I can test the functionality of the new out-of-the-box DMRAID support. The is on a system that I've been using DMRAID on quite successfully for some time (albeit, with no support from the installer).

The installation went ok, but when I rebooted I found that only one of my filesystems was mounted. When I typed 'sudo mount -a', I got a bunch of error about filesystems not being found.

The fstab (which was created by the installer) identifies each block device by UUID (my fstab is attached). However, 'ls -l /dev/disk/by-uuid' yields the following:

chr1s@chris-desktop:~$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 2008-10-04 12:29 7cfd1f74-70d1-412e-8dfd-1c1ed4dd9526 -> ../../sdb1

There is only a UUID for the one non-DMRAID block device. There are no UUID's for any of the DMRAID block devices identified in my fstab. However, if I type in 'sudo blkid', I get completely different results:

chr1s@chris-desktop:~$ sudo blkid
[sudo] password for chr1s:
/dev/mapper/nvidia_effeccbe7: TYPE="swap" UUID="b79ca3cd-cafd-48b4-b3dd-231698d4b7df"
/dev/mapper/nvidia_effeccbe6: LABEL="root" UUID="79267606-351d-4255-b0d4-d64ce80b42fc" TYPE="ext3"
/dev/mapper/nvidia_effeccbe5: LABEL="tmp" UUID="6750a25d-7a06-403b-8804-f72f63c6b47a" TYPE="ext3" SEC_TYPE="ext2"
/dev/mapper/nvidia_effeccbe3: LABEL="boot" UUID="ca038584-024c-41d6-8096-e257f7b2ef93" TYPE="ext3" SEC_TYPE="ext2"
/dev/mapper/nvidia_effeccbe1: UUID="B080F3DA80F3A54E" TYPE="ntfs"
/dev/mapper/nvidia_effeccbe9: LABEL="misc" UUID="a46008f5-5902-4539-918c-a5a49843bf3d" TYPE="ext3" SEC_TYPE="ext2"
/dev/mapper/nvidia_effeccbe8: LABEL="var" UUID="0634d668-0563-4236-b3f3-9257b76ad2d2" TYPE="ext3" SEC_TYPE="ext2"
/dev/sdb1: LABEL="home" UUID="7cfd1f74-70d1-412e-8dfd-1c1ed4dd9526" TYPE="ext3" SEC_TYPE="ext2"

All of them except for the swap partition look correct. This all worked ok in Hardy.

I was going to open this bug report against UDEV initially, as I thought it may just be an issue with the UDEV rules, but I ran 'sudo udevadm monitor --environment' and then 'echo add > /sys/block/dm-3/uevent', and I got the following:

chr1s@chris-desktop:~$ sudo udevadm monitor --environment
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent

UEVENT[1223117827.145600] add /block/dm-3 (block)
ACTION=add
DEVPATH=/block/dm-3
SUBSYSTEM=block
MAJOR=254
MINOR=3
DEVTYPE=disk
SEQNUM=3012

UDEV [1223117827.149000] add /block/dm-3 (block)
UDEV_LOG=3
ACTION=add
DEVPATH=/block/dm-3
SUBSYSTEM=block
MAJOR=254
MINOR=3
DEVTYPE=disk
SEQNUM=3012
UDEVD_EVENT=1
DEVNAME=/dev/dm-3

I was expecting to see a 'ID_FS_UUID' field in this output.

[Luke Yelavich (themuso)]

Dmraid needs to depend on dmsetup for the UUIDs to be set correctly. For now, please install the dmsetup package, and let me know how things go.

I will be addressing this in a dmraid update this week.

Luke

[Chris Coulson (chrisccoulson)]

Thanks for the quick response lUke.

Installing dmsetup has worked fine.

[Chris Coulson (chrisccoulson)]

The bug number isn't in the changelog, so this wasn't closed automatically.

This bug was fixed in the package dmraid - 1.0.0.rc14-2ubuntu9

---------------
dmraid (1.0.0.rc14-2ubuntu9) intrepid; urgency=low

 * debian/control: dmraid and dmraid-udeb should depend on dmsetup and
   dmsetup-udeb respecitvely, to ensure UUID symlinks are correctly
   created.
 * debian/patches/07_isw-raid10-nested.dpatch: Re-add this patch as a user
   is not able to make use of his RAID array without it. Yes its known
   to break other RAID configurations, however there have been no Ubuntu
   bugs filed about this issue. (LP: #276095)

 -- Luke Yelavich <email address hidden> Wed, 08 Oct 2008 11:46:19 +1100