I think, I've encountered this bug in Debian squeeze too, but in a safe way. I have 9 partitions on my desktop computer (P5QC) and only the UUID of sda9 isn't detected. Fortunately, it isn't the root partition.
I've never installed Windows on this computer but formatted its hard with etx3 from the start. My udev's version is 150-2. I also have an old Ubuntu Hardy, in which the UUID of sda9 is correctly detected. On Debian, this behavior happened since a few weeks ago, perhaps after udev was updated.
"sudo blkid -o udev -p /dev/sda9" gives:
/dev/sda9: ambivalent result (probably more filesystems on the device)
Is this problem related to partitioning with an older version of parted (GParted)? Or it's udev's fault?
I think, I've encountered this bug in Debian squeeze too, but in a safe way. I have 9 partitions on my desktop computer (P5QC) and only the UUID of sda9 isn't detected. Fortunately, it isn't the root partition.
I've never installed Windows on this computer but formatted its hard with etx3 from the start. My udev's version is 150-2. I also have an old Ubuntu Hardy, in which the UUID of sda9 is correctly detected. On Debian, this behavior happened since a few weeks ago, perhaps after udev was updated.
"sudo blkid -o udev -p /dev/sda9" gives:
/dev/sda9: ambivalent result (probably more filesystems on the device)
Is this problem related to partitioning with an older version of parted (GParted)? Or it's udev's fault?