Comment 2 for bug 224171

Thanks for the link - its the first time I heard about this having come to Ubuntu after Edgy and from SuSe 9.2. I long as I have known Linux, IDE disk devices have always been entirely predictable from the cabling. It's the SCSI, SATA and USB drives that have a predictability problem - so I am not sure that messing with them was worth the effort. BTW, the bug also affects tapes. My IDE attached tape changed from /dev/ht0 to /dev/st0 at the same time!

Going back to an earlier backup, this is what my fstab looked like before the upgrade to 8.04:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda6
UUID=9d716e44-0a7f-4abb-abd1-6f7cf8dc0173 / ext3 defaults,errors=remount-ro 0 1
# /dev/hda5
UUID=03826fd9-2e03-4510-b630-f1e849c87f1d none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/md0 /raiddisk reiserfs rw,acl,user_xattr 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

Note that the /dev/hda entries had been commented out. I assume this is by the Ubuntu installer as I don't remember doing this. I am not surprised to see this as hard linking a system disk to a UUID seems to be a good way of making it difficult to recover from a broken system disk. The RAID 1 arrar has a reiserfs file system for the simple reason that the system was upgraded from Suse 9.2 by replacing the system disk and then adding the RAID array from the original system.

I have been scanning the literature to see how to build a RAID array by UUID, but can't seen to find anything on this. Looks like you have to know the device names before you can assemble a RAID array - so UUIDs don't help much here.