Option to use /dev values instead of UUID values

[Tom H]

>> Since blkid does not return the uuid of sda1, the following will most
>> probably not either, but you never know...

>> $ sudo -i
>> # file -s /dev/sda1
>> # tune2fs -l /dev/sda1 | grep -i uuid
>> # ls -l /dev/disk/by-uuid/ | grep -i sda1
>> # grep -i uuid /dev/.udev/db/block\:sda1
>> # udevadm info -q all -n /dev/sda1 | grep -i uuid

> WEIRD!!

> root at puce:~# file -s /dev/sda1
> /dev/sda1: Linux rev 1.0 ext2 filesystem data (mounted or unclean), UUID=acb92e5f-f14a-4205-b67a-f5852919796a, volume name "BootDrive"
> root at puce:~#
> root at puce:~# tune2fs -l /dev/sda1 | grep -i uuid
> Filesystem UUID:          acb92e5f-f14a-4205-b67a-f5852919796a
> root at puce:~#
> root at puce:~# ls -l /dev/disk/by-uuid/ | grep -i sda1
> lrwxrwxrwx 1 root root 11 2010-03-25 07:09 354d6e92-99f3-427f-867e-f02183bf0454 -> ../../sda10
> lrwxrwxrwx 1 root root 11 2010-03-25 07:09 48a4bc15-b0f9-4a46-a563-114a45477534 -> ../../sda11
> root at puce:~#
> root at puce:~# grep -i uuid /dev/.udev/db/block\:sda1
> root at puce:~# udevadm info -q all -n /dev/sda1 | grep -i uuid

> So - it is in there and tune2fs sees it but the other stuff doesn't. My fstab was edited by hand (this whole system,
> which resulted in a upgrade from 9.04) has been exceedingly flaky since the upgrade, by the way. It is still running
> Grub1, not Grub2 (the upgrade did not seem to remove Grub1), perhaps because there is more than one partition with
> a root file system??? Doing an fsck doesn't make any difference.

> Putting the right UUID into fstab and trying to do a mount gives me:

> root at puce:~# mount /boot
> mount: special device UUID=acb92e5f-f14a-4205-b67a-f5852919796a does not exist

So udev does not recognize sda1 but sda1's superblock does have a uuid
(that "file..." and "tune2fs..." display).

Check
/var/log/udev
to see how sda1 is being handled or mishandled.