
I'll try that later and post how it's done. to see drives by UUID, type ls -l /dev/disk/by-uuid/- to see drives by name (for sata only) type ls -l /dev/sd*. Got a tip from a guy to fix this by mounting partitions using UUID or label ( tune2fs -l):

It might happen that, if the installation drive (primary) has a name such as /dev/sde, when I remove a drive (let's say /dev/hdb), the installation drive gets a different name upon reboot and no more boot. My mobo has 2 SATA controllers: Intel ("built-in") and Silicon Image ("card"), as per description in the above link.

It seems that GRUB maps the drives differently (in different OS's) when more that one SATA controller is used. I see strange behavior when installing different distributions: some time I have my installation drive mapped as /dev/sda (Debian), sometimes it's mapped as /dev/sde (Ubuntu). Hardware and preparation | OS installation | Console and web monitoring | Network & services | Multimedia | Security Do not link to this page, it might change!
