Option to use /dev values instead of UUID values

[Lou Katz]

AHA!!! See below ---

On Thu, Mar 25, 2010 at 04:10:00PM -0400, Tom H wrote:
> >> > ? ? ? ?$ sudo blkid
> >> > ? ? ? ?[sudo] password for lou:
> >> > ? ? ? ?/dev/sda2: UUID="4E0C083C0C082197" LABEL="W2K" TYPE="ntfs"
> >> > ? ? ? ?/dev/sda3: UUID="B2DCD2EADCD2A83D" LABEL="XP-Root" TYPE="ntfs"
> >> > ? ? ? ?/dev/sda5: UUID="3bdf3983-9d86-4adb-85df-257942a33e5b" TYPE="swap"
> >> > ? ? ? ?/dev/sda7: UUID="19299e03-366c-4c76-b8fc-f650bd77f790" SEC_TYPE="ext2" TYPE="ext3"
> >> > ? ? ? ?/dev/sda8: UUID="d1e3679d-1a16-4154-95ad-e04edcedb271" TYPE="ext3"
> >> > ? ? ? ?/dev/sda9: UUID="300425e2-2fce-4421-a7a9-a956118b2c18" TYPE="ext2"
> >> > ? ? ? ?/dev/sda10: UUID="354d6e92-99f3-427f-867e-f02183bf0454" TYPE="ext3" SEC_TYPE="ext2"
> >> > ? ? ? ?/dev/sda11: UUID="48a4bc15-b0f9-4a46-a563-114a45477534" TYPE="ext3" SEC_TYPE="ext2"
> >> > ? ? ? ?/dev/sdb1: LABEL="WORK" UUID="631F-D2FD" TYPE="vfat"
> >> > ? ? ? ?/dev/sdb2: UUID="e704b2dd-3253-4c00-8025-b11eaa25ae33" TYPE="ext3"
> >> > ? ? ? ?/dev/sdb3: UUID="9b27509d-5528-4df6-a7b9-b7748cc19c17" TYPE="ext3"
> >> > ? ? ? ?/dev/sdb4: UUID="cebf1c58-8ccb-43f6-a6b4-f23e15a39211" TYPE="ext3"
> >> > ? ? ? ?/dev/sdg1: UUID="893dc90f-e09d-4aae-857f-28102c692518" TYPE="ext3" SEC_TYPE="ext2"
> >> > ? ? ? ?/dev/sdg2: UUID="46c6e755-f867-4653-a9a4-066c9869e5f0" TYPE="swap"
> 
> >> > I've tried
> >> > ? ? ? ?tune2fs -U time /dev/sda1
> >> > ? ? ? ?and
> >> > ? ? ? ?tune2fs -L boot /dev/sda1
> 
> >> How about
> >> tune2fs -U clear /dev/sda1
> >> tune2fs -U random /dev/sda1
> 
> > No joy.
> 
> 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


I tried using the Force, Luke!




> 
> And what does
> grep -i boot /etc/fstab
> return?
> 
> -- 
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

-- 

-=[L]=-

Let me put it to you this way: computers are my business.