Marlier, Ian wrote
The trick, here, is that you're installing to /dev/sde, but it's going to be /dev/sda when the system boots. The bootloader section, at least, needs to be adjusted to handle that case.
That doesn't help, because then I must rely on my boot disk being always /dev/sde, because I must specify it in the profile. But in this case, /dev/sda - /dev/sdd are external disk on a fibre channel bus. I cannot rely on all of them always being online. So, sometimes my internal scsi disk could be /dev/sde, sometimes /dev/sdc or sth. To circumvent this, our solution has been to always load the module for the internal scsi disk as first module. So we can be sure we will be working on /dev/sda, because the internal disks are the only ones that will never vanish :-) -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *