I have 4 hard drive subsystems (not counting nfs, usb or cifs).
When I use /dev/sda etc. in /etc/fstab, any one of the 4 random drives gets assigned to /dev/sda. At boot time, it often crashes because it can't find the partitions.
I have to login in single user mode as root, look at gparted to find out where my devices wound up today and then edit /etc/fstab with the current device letters.
Then, I discovered vol_id which returns something like:
Since I got rid of the /dev/sd?? convention in favor of the UUID scheme, the booting partitions and mounts have worked flawlessly.
However, I am trying to get suspend/hibernate to work and it complains that I don't have any valid swap devices. Swapon sees them.
Is it my BIOS, firmware, Ubuntu or gremlins which are monkeying with my device assignments? Is there a way to get s2both/s2disk to understand the weird UUID method of swap assignment?
# swapon -s
Filename Type Size Used Priority
/dev/sda3 partition 8393952 2811980 -1
/dev/sdb3 partition 8193140 0 -2
/dev/sdc3 partition 9084748 0 -3
# grep swap /etc/fstab
UUID=7356e42c-2aa3-46ca-aacf-6efdd1cfec18 none swap sw 0 0
UUID=8e4a7444-6e14-49f7-81ee-190534eeacb5 none swap sw 0 0
UUID=9152f370-051a-497f-a4bf-3f5a679acb7e none swap sw 0 0
# alias df; df
alias df='df -h | grep dev/sd | sort'
/dev/sda1 2.0G 128M 1.8G 7% /boot
/dev/sda2 40G 8.9G 29G 24% /
/dev/sda4 228G 65G 152G 31% /home
/dev/sdb1 20G 66M 20G 1% /mnt/ntsys
/dev/sdb2 293G 3.6G 290G 2% /mnt/ntdat
/dev/sdb4 274G 20G 241G 8% /home2
/dev/sdc1 39G 3.7G 34G 11% /sys3
/dev/sdc2 877G 166G 668G 20% /tera
/dev/sdd1 2.6T 487G 2.0T 20% /r5