<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Ok, I understand that cheers, but I'm not having a problem with the ordering of the devices it's the ordering of the controllers. I have two controllers. The first, and LSI ( the internal ), and my newly added Adaptec. The LSI is detected first by the Bios and the Adaptec second ( which is what I want ). So why would the adaptec be assigned sda and my internal disks get sdb ? That's what's breaking things for me. Because my internal disks are no longer sda1/2/3 my kickstart build fails (or installs onto the external array which I really don't want). Anything I could do here, I think it's the hardware being funny and presenting itself to the kernel in the wrong order perhaps? -n. Jeff Vian wrote: <blockquote cite="mid1089602769.3792.96.camel@goliath.lab.net" type="cite"> <pre wrap="">On Sun, 2004-07-11 at 21:56, Naoki wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi all, I have a problem, when I install my OS ( FC2 ) on my nice machine with an internal scsi controller my two disks are sda and sdb, which is all nice and expected. But then when I add a new scsi card and hook up the external disk array the new array now becomes sda which has a very negative effect, can't boot.. Any helpful hints? I could label the disks sure but then swap is still on sda2 and that's a problem. </pre> </blockquote> <pre wrap=""> The order of the scsi adapters being configured at boot time causes that.... first adapter --> first device ==> sda. AFAIK the easiest way to fix that is to swap the positions on the mobo so the original adapter is seen first. BTW, by the time you labeled the partitions you could also change fstab for swap as well as the filesystem partitions. The real problem I would see is the location of the grub boot image. HTH Jeff </pre> </blockquote> </body> </html>