[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Marking as fixed since this is now working in Intrepid. ** Changed in: udev (Ubuntu) Status: Incomplete => Fix Released ** Changed in: dmraid (Ubuntu) Status: New => Fix Released -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
I'm having same issue on hardy on two different computers, one 32bit, one 64bit. I am using ubuntu on a mdraid system, and additionally use part of the dmraid for ubuntu two. I can not use UUID because it is not unique. Output of blkid: (64bit system hardy 2.6.24-19-generic kernel) /dev/sda1: UUID="AE787AAF787A75C5" TYPE="ntfs" /dev/sdb1: UUID="AE787AAF787A75C5" TYPE="ntfs" /dev/sdc1: UUID="d505cea8-619c-d7e8-3cbc-1de6f0265fbc" TYPE="mdraid" /dev/sdd1: UUID="d505cea8-619c-d7e8-3cbc-1de6f0265fbc" TYPE="mdraid" /dev/md0: UUID="61662c4b-fafc-47a8-82f3-688f932c0e09" TYPE="ext3" /dev/md1: UUID="304412cd-d2a6-41e3-ae54-9214eac90a03" TYPE="ext3" /dev/md3: TYPE="swap" UUID="df6e002b-926a-4953-be85-effb9dc43300" /dev/mapper/pdc_dghdgccfge1: UUID="AE787AAF787A75C5" TYPE="ntfs" /dev/sdc5: UUID="82f5271b-f34b-8199-bcb1-b15f53338d70" TYPE="mdraid" /dev/sdc6: UUID="5684b35f-2c9a-4067-0e1d-96c5294c52fa" TYPE="mdraid" /dev/sdd5: UUID="82f5271b-f34b-8199-bcb1-b15f53338d70" TYPE="mdraid" /dev/sdd6: UUID="5684b35f-2c9a-4067-0e1d-96c5294c52fa" TYPE="mdraid" /dev/sde: SEC_TYPE="msdos" UUID="2A87-6CE1" TYPE="vfat" Disks sda and sdb share uuid with /dev/mapper/pdc_dghdgccfge1. I see the same behavior on my 32 bit system. I can provide additional info on request and I be willing to test patches. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Kay, I see the above linked patch from the ataraid list is still not in rc14. I might give it some testing in the next few weeks, but is it something that we might want? I can see how it would clearly help distinguish the UUIDs from standard disk UUIDs, in terms of mounting partitions. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Luke: In current Hardy Beta, my original issue (not being able to mount dmraid partition using UUID / conflicting outputs from blkid and ls -l on /dev/disk/by-uuid) seems to be fixed. I can mount the NTFS partition using UUID in my fstab now. FYI: [EMAIL PROTECTED]:~$ sudo blkid [sudo] password for chr1s: /dev/mapper/nvidia_effeccbe7: TYPE="swap" UUID="c7f0b160-7189-480b-8184-6aa575ae275a" /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" LABEL="misc" /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" [EMAIL PROTECTED]:~$ ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 29 2008-04-10 19:04 450a14e7-7e17-41e1-9c0a-5c576aaade73 -> ../../mapper/nvidia_effeccbe3 lrwxrwxrwx 1 root root 29 2008-04-10 19:04 4a810ba8-bfc5-4a54-b9f3-e7588805b872 -> ../../mapper/nvidia_effeccbe6 lrwxrwxrwx 1 root root 29 2008-04-10 19:04 4d2dbdd4-b441-4c3b-b3b1-63598b5091f4 -> ../../mapper/nvidia_effeccbe5 lrwxrwxrwx 1 root root 29 2008-04-10 19:04 7568e5ba-bc0a-4773-98dd-051aabdd9430 -> ../../mapper/nvidia_effeccbe8 lrwxrwxrwx 1 root root 10 2008-04-10 19:04 7cfd1f74-70d1-412e-8dfd-1c1ed4dd9526 -> ../../sdb1 lrwxrwxrwx 1 root root 29 2008-04-10 19:04 B080F3DA80F3A54E -> ../../mapper/nvidia_effeccbe1 lrwxrwxrwx 1 root root 29 2008-04-10 19:04 c7f0b160-7189-480b-8184-6aa575ae275a -> ../../mapper/nvidia_effeccbe7 lrwxrwxrwx 1 root root 29 2008-04-10 19:04 dfa88fa9-e0e7-4a3f-bc76-08c2e087d431 -> ../../mapper/nvidia_effeccbe9 >From my point of view, this bug is fixed, although the kernel still creates invalid partitions for my RAID device, so I'll leave it up to you as to whether you want to keep this bug report open. Kay might want to make this decision. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Has there been any progress on the bits required to make UUIDs and dmraid devices work properly? -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Sure, what you really want is the kernel not to create the (invalid) partitions at all for a raid device. We are working to get media change events for the disk, and we can start probing for raid setups (currently media changes are not reported, and probing a main device would store wrong information at media changes). Then we will see the "raid tag" at the disk database entry, which is imported into the partition event, and we can entirely ignore the partitions. -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
The problem is that dmraid needs to claim the entire disk, and disallow all other access to it. In the case of a raid1, you potentially will see 3 volumes with the same data: the two underlying mirrors and the mirror dm device. Any access to the underlying disks will be a problem. In the case of a raid0, often the kernel will see the partition table and create the devices for each partition, but they are not valid and must not be accessed. Bear in mind that dmraid rules activate on the raw disk device, not the partitions. Something then needs to be done to prevent udev from doing anything at all with the partition devices on the disk that dmraid has claimed. -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Oh, we have a patch in dmraid, we thought that would be already merged. The plain version of dmraid misses the uuids in the dm tables: http://www.redhat.com/archives/ataraid-list/2006-September/msg1.html Scott, we may give dm-* volumes by default a higher priority than plain disks? What do you think? Now that EVMS, which did silly things here, is dead. :) -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
This is what I get now, with the extra rule added: UEVENT[1193163711.005542] add /block/dm-1 (block) ACTION=add DEVPATH=/block/dm-1 SUBSYSTEM=block SEQNUM=2837 MINOR=1 MAJOR=254 UDEV [1193163711.016679] add /block/dm-1 (block) UDEV_LOG=3 ACTION=add DEVPATH=/block/dm-1 SUBSYSTEM=block SEQNUM=2837 MINOR=1 MAJOR=254 UDEVD_EVENT=1 DM_NAME=nvidia_effeccbe1 DM_STATE=ACTIVE DM_TABLE_STATE=LIVE DM_OPENCOUNT=2 DM_LAST_EVENT_NR=0 DM_MAJOR=254 DM_MINOR=1 DM_TARGET_COUNT=1 DM_TARGET_TYPES=linear ID_FS_USAGE=filesystem ID_FS_TYPE=ntfs ID_FS_VERSION=3.1 ID_FS_UUID=B080F3DA80F3A54E ID_FS_UUID_ENC=B080F3DA80F3A54E ID_FS_LABEL= ID_FS_LABEL_ENC= ID_FS_LABEL_SAFE= DEVNAME=/dev/mapper/nvidia_effeccbe1 DEVLINKS=/dev/disk/by-id/dm-name-nvidia_effeccbe1 /dev/disk/by-uuid/B080F3DA80F3A54E -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Oops, sorry, please add "--env" :) udevmonitor --env -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
One second actually, I've just realised I've rebooted since removing that extra rule. I'll try it again in a sec -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
This is the output I get from udevmonitor: UEVENT[1193162136.861547] add /block/dm-1 (block) UDEV [1193162136.872177] add /block/dm-1 (block) -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
What does: udevmonitor print, when you do: echo add > /sys/block/dm-1/uevent Does the environment contain DM_UUID? Prefixed with "dmraid-"? -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
I added ENV{DM_UUID}=="dmraid-*", OPTIONS="link_priority=50" to the file
65-dmsetup.rules, just underneath the line ENV{DM_UUID}=="?*",
SYMLINK+="disk/by-id/dm-uuid-$env{DM_UUID}", and it didn't make any
difference. Not sure if this is the correct place to add it.
--
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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Kay: [EMAIL PROTECTED]:~$ ls -l /dev/.udev/names/*B080F3DA80F3A54E* total 0 -rw-r--r-- 1 root root 0 2007-10-23 17:57 \x2fblock\x2fdm-1 -rw-r--r-- 1 root root 0 2007-10-23 17:57 \x2fblock\x2fsda\x2fsda1 So, it does seem there are two devices competing for the same name. I'll try adding that rule in a moment and see what difference it makes. -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Thanks, that's looks like the same data offered by two different kernel devices.
The fix will probably prevent the wrong detection, because the striping of
volumes
make the data we check for unreachable by the scsi device. But there might still
be setups where we can get exactly the same data from both devices.
We need to bump the symlink priority of dmraid symlinks. Let's see what:
ls -l /dev/.udev/names/*B080F3DA80F3A54E*
prints?
Are there the two devices competing about the same name? Then we need to
add something like: ENV{DM_UUID}=="dmraid-*", OPTIONS="link_priority=50"
to the device-mapper rules.
--
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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Kay, As requested: [EMAIL PROTECTED]:~$ sudo dd if=/dev/sda1 count=2 | hexdump -C 2+0 records in 2+0 records out 1024 bytes (1.0 kB) copied, 0.00038136 seconds, 2.7 MB/s eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS.| 0010 00 00 00 00 00 f8 00 00 3f 00 ff 00 3f 00 00 00 |?...?...| 0020 00 00 00 00 80 00 80 00 fd ef bf 12 00 00 00 00 || 0030 00 00 0c 00 00 00 00 00 ff fe 2b 01 00 00 00 00 |..+.| 0040 f6 00 00 00 01 00 00 00 4e a5 f3 80 da f3 80 b0 |N...| 0050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb b8 c0 07 |.3.|| 0060 8e d8 e8 16 00 b8 00 0d 8e c0 33 db c6 06 0e 00 |..3.| 0070 10 e8 53 00 68 00 0d 68 6a 02 cb 8a 16 24 00 b4 |..S.h..hj$..| 0080 08 cd 13 73 05 b9 ff ff 8a f1 66 0f b6 c6 40 66 |[EMAIL PROTECTED]| 0090 0f b6 d1 80 e2 3f f7 e2 86 cd c0 ed 06 41 66 0f |.?...Af.| 00a0 b7 c9 66 f7 e1 66 a3 20 00 c3 b4 41 bb aa 55 8a |..f..f. ...A..U.| 00b0 16 24 00 cd 13 72 0f 81 fb 55 aa 75 09 f6 c1 01 |.$...r...U.u| 00c0 74 04 fe 06 14 00 c3 66 60 1e 06 66 a1 10 00 66 |t..f`..f...f| 00d0 03 06 1c 00 66 3b 06 20 00 0f 82 3a 00 1e 66 6a |f;. ...:..fj| 00e0 00 66 50 06 53 66 68 10 00 01 00 80 3e 14 00 00 |.fP.Sfh.>...| 00f0 0f 85 0c 00 e8 b3 ff 80 3e 14 00 00 0f 84 61 00 |>.a.| 0100 b4 42 8a 16 24 00 16 1f 8b f4 cd 13 66 58 5b 07 |.B..$...fX[.| 0110 66 58 66 58 1f eb 2d 66 33 d2 66 0f b7 0e 18 00 |fXfX..-f3.f.| 0120 66 f7 f1 fe c2 8a ca 66 8b d0 66 c1 ea 10 f7 36 |f..f..f6| 0130 1a 00 86 d6 8a 16 24 00 8a e8 c0 e4 06 0a cc b8 |..$.| 0140 01 02 cd 13 0f 82 19 00 8c c0 05 20 00 8e c0 66 |... ...f| 0150 ff 06 10 00 ff 0e 0e 00 0f 85 6f ff 07 1f 66 61 |..o...fa| 0160 c3 a0 f8 01 e8 09 00 a0 fb 01 e8 03 00 fb eb fe || 0170 b4 01 8b f0 ac 3c 00 74 09 b4 0e bb 07 00 cd 10 |.<.t| 0180 eb f2 c3 0d 0a 41 20 64 69 73 6b 20 72 65 61 64 |.A disk read| 0190 20 65 72 72 6f 72 20 6f 63 63 75 72 72 65 64 00 | error occurred.| 01a0 0d 0a 4e 54 4c 44 52 20 69 73 20 6d 69 73 73 69 |..NTLDR is missi| 01b0 6e 67 00 0d 0a 4e 54 4c 44 52 20 69 73 20 63 6f |ng...NTLDR is co| 01c0 6d 70 72 65 73 73 65 64 00 0d 0a 50 72 65 73 73 |mpressed...Press| 01d0 20 43 74 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f | Ctrl+Alt+Del to| 01e0 20 72 65 73 74 61 72 74 0d 0a 00 00 00 00 00 00 | restart| 01f0 00 00 00 00 00 00 00 00 83 a0 b3 c9 00 00 55 aa |..U.| 0200 05 00 4e 00 54 00 4c 00 44 00 52 00 04 00 24 00 |..N.T.L.D.R...$.| 0210 49 00 33 00 30 00 00 e0 00 00 00 30 00 00 00 00 |I.3.0..0| 0220 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0250 00 00 00 00 00 00 eb 12 90 90 00 00 00 00 00 00 || 0260 00 00 00 00 00 00 00 00 00 00 8c c8 8e d8 c1 e0 || 0270 04 fa 8b e0 fb e8 03 fe 66 0f b7 06 0b 00 66 0f |f.f.| 0280 b6 1e 0d 00 66 f7 e3 66 a3 4e 02 66 8b 0e 40 00 |[EMAIL PROTECTED]| 0290 80 f9 00 0f 8f 0e 00 f6 d9 66 b8 01 00 00 00 66 |.f.f| 02a0 d3 e0 eb 08 90 66 a1 4e 02 66 f7 e1 66 a3 52 02 |.f.N.f..f.R.| 02b0 66 0f b7 1e 0b 00 66 33 d2 66 f7 f3 66 a3 56 02 |f.f3.f..f.V.| 02c0 e8 71 04 66 8b 0e 4a 02 66 89 0e 22 02 66 03 0e |.q.f..J.f..".f..| 02d0 52 02 66 89 0e 26 02 66 03 0e 52 02 66 89 0e 2a |R.f..&.f..R.f..*| 02e0 02 66 03 0e 52 02 66 89 0e 3a 02 66 03 0e 52 02 |.f..R.f..:.f..R.| 02f0 66 89 0e 42 02 66 b8 90 00 00 00 66 8b 0e 22 02 |f..B.f.f..".| 0300 e8 5f 09 66 0b c0 0f 84 57 fe 66 a3 2e 02 66 b8 |._.fW.f...f.| 0310 a0 00 00 00 66 8b 0e 26 02 e8 46 09 66 a3 32 02 |f..&..F.f.2.| 0320 66 b8 b0 00 00 00 66 8b 0e 2a 02 e8 34 09 66 a3 |f.f..*..4.f.| 0330 36 02 66 a1 2e 02 66 0b c0 0f 84 24 fe 67 80 78 |6.f...f$.g.x| 0340 08 00 0f 85 1b fe 67 66 8d 50 10 67 03 42 04 67 |..gf.P.g.B.g| 0350 66 0f b6 48 0c 66 89 0e 62 02 67 66 8b 48 08 66 |f..H.f..b.gf.H.f| 0360 89 0e 5e 02 66 a1 5e 02 66 0f b7 0e 0b 00 66 33 |..^.f.^.f.f3| 0370 d2 66 f7 f1 66 a3 66 02 66 a1 42 02 66 03 06 5e |.f..f.f.f.B.f..^| 0380 02 66 a3 46 02 66 83 3e 32 02 00 0f 84 1d 00 66 |.f.F.f.>2..f| 0390 83 3e 36 02 00 0f 84 c8 fd 66 8b 1e 36 02 1e 07 |.>6..f..6...| 03a0 66 8b 3e 46 02 66 a1 2a 02 e8 bc 01 66 0f b7 0e |f.>F.f.*f...| 03b0 00 02 66 b8 02 02 00 00 e8 fe 07 66 0b c0 0f 84 |..ff| 03c0 a8 09 67 66 8b 00 1e 07 66 8b 3e 3a 02 e8 31 06 |..gff.>:..1.| 03d0 66 a1 3a 02 66 bb 20 00 00 00 66 b9 00 00 00 00 |f.:.f. ...f.| 03e0 66 ba 00 00 00 00 e8 d6 00 66 85 c0 0f 85 23 00 |ff#.|
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
I've added a fix to the git tree, which may prevent the wrong NTFS recognition. Please still provide the hexdump, so we can be sure to have the right fix. I also wonder if the nvidia dmraid metadata is recognized. What does: sudo vol_id /dev/sda print? Thanks! -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Maybe a left-over signature again, we seem to miss the version information. We should add more consistency checks to NTFS then. What does: dd if=/dev/sda1 count=2 | hexdump -C and dd if=/dev/mapper/nvidia_effeccbe1 count=2 | hexdump -C print? -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
Kay: any idea why vol_id is picking up a UUID for the dmraid partition but blkid doesn't? -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
As requested: [EMAIL PROTECTED]:~$ sudo vol_id /dev/sda1 [sudo] password for chr1s: ID_FS_USAGE=filesystem ID_FS_TYPE=ntfs ID_FS_VERSION= ID_FS_UUID=B080F3DA80F3A54E ID_FS_UUID_ENC=B080F3DA80F3A54E ID_FS_LABEL= ID_FS_LABEL_ENC= ID_FS_LABEL_SAFE= [EMAIL PROTECTED]:~$ sudo vol_id /dev/mapper/nvidia_effeccbe1 ID_FS_USAGE=filesystem ID_FS_TYPE=ntfs ID_FS_VERSION=3.1 ID_FS_UUID=B080F3DA80F3A54E ID_FS_UUID_ENC=B080F3DA80F3A54E ID_FS_LABEL= ID_FS_LABEL_ENC= ID_FS_LABEL_SAFE= [EMAIL PROTECTED]:~$ blkid /dev/sda1 [EMAIL PROTECTED]:~$ sudo blkid /dev/sda1 [EMAIL PROTECTED]:~$ -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
What is the output of the following: vol_id /dev/sda1 vol_id /dev/mapper/nvidia_effeccbe1 Also provide: blkid /dev/sda1 for comparison. Thanks ** Changed in: udev (Ubuntu) Importance: Undecided => Medium Status: New => Incomplete -- 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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
I think this has more to do with udev so I'm adding it as well. ** Also affects: udev (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
[Bug 154834] Re: UUID's not correctly allocated for DMRAID devices in Gutsy
** Attachment added: "fstab" http://launchpadlibrarian.net/10080275/fstab -- 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
