Public bug reported:
When I upgraded from Feisty to Gutsy, I noticed that my NTFS partition
was no longer being mounted at startup. The NTFS partition is on a
striped array using DMRAID, along with several ext3 partitions (all of
which mounted ok). The NTFS partition (/dev/mapper/nvidia_effeccbe1) is
listed in my fstab (see attached) using the UUID (B080F3DA80F3A54E).
This worked okay in Feisty.
If I remove the UUID entry for this partition and use
'/dev/mapper/nvidia_effeccbe1' instead, the partition mounts fine.
The output of blkid gives:
/dev/mapper/nvidia_effeccbe7: TYPE="swap"
UUID="92995c4b-7205-47a5-96a4-3da870607792"
/dev/mapper/nvidia_effeccbe6: LABEL="root"
UUID="4a810ba8-bfc5-4a54-b9f3-e7588805b872" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/nvidia_effeccbe5: LABEL="tmp"
UUID="4d2dbdd4-b441-4c3b-b3b1-63598b5091f4" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/nvidia_effeccbe3: LABEL="boot"
UUID="450a14e7-7e17-41e1-9c0a-5c576aaade73" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/nvidia_effeccbe1: TYPE="ntfs" UUID="B080F3DA80F3A54E"
/dev/mapper/nvidia_effeccbe9: UUID="dfa88fa9-e0e7-4a3f-bc76-08c2e087d431"
SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/nvidia_effeccbe8: LABEL="var"
UUID="7568e5ba-bc0a-4773-98dd-051aabdd9430" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb1: LABEL="home" UUID="7cfd1f74-70d1-412e-8dfd-1c1ed4dd9526"
SEC_TYPE="ext2" TYPE="ext3"
This clearly shows that the UUID that I am using in my fstab is correct.
However, if I do a ls -l on /dev/disk/by-uuid, I get the following results:
total 0
lrwxrwxrwx 1 root root 29 2007-10-20 11:56 450a14e7-7e17-41e1-9c0a-5c576aaade73
-> ../../mapper/nvidia_effeccbe3
lrwxrwxrwx 1 root root 29 2007-10-20 11:56 4a810ba8-bfc5-4a54-b9f3-e7588805b872
-> ../../mapper/nvidia_effeccbe6
lrwxrwxrwx 1 root root 29 2007-10-20 11:56 4d2dbdd4-b441-4c3b-b3b1-63598b5091f4
-> ../../mapper/nvidia_effeccbe5
lrwxrwxrwx 1 root root 29 2007-10-20 11:56 7568e5ba-bc0a-4773-98dd-051aabdd9430
-> ../../mapper/nvidia_effeccbe8
lrwxrwxrwx 1 root root 10 2007-10-20 11:56 7cfd1f74-70d1-412e-8dfd-1c1ed4dd9526
-> ../../sdb1
lrwxrwxrwx 1 root root 29 2007-10-20 11:56 92995c4b-7205-47a5-96a4-3da870607792
-> ../../mapper/nvidia_effeccbe7
lrwxrwxrwx 1 root root 10 2007-10-20 11:56 B080F3DA80F3A54E -> ../../sda1
lrwxrwxrwx 1 root root 29 2007-10-20 11:56 dfa88fa9-e0e7-4a3f-bc76-08c2e087d431
-> ../../mapper/nvidia_effeccbe9
This shows that the UUID I am using in my fstab is linked to the wrong
device. It is in-fact linked to a 'partition' on one of the disks which
make up the striped array, which is different to the output of blkid.
Note, I am not sure which package to file this bug against. I've filed
it against dmraid for now, but please change as appropriate.
** Affects: dmraid (Ubuntu)
Importance: Undecided
Status: New
--
UUID's not correctly allocated for DMRAID devices in Gutsy
https://bugs.launchpad.net/bugs/154834
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
