On Thu, 11 Jan 2001, Maurice Volaski wrote: Hi,
Got an IBM Netfinitiy 4500R box which started out with just a ServeRAID 3LS adapter. Configured it for RAID one on two of three internal hard disks and left the third disk untouched. Installed SuSe 7.0 Linux. At that point, it was a working system where the RAID one pair is /dev/sda and where Linux lives on both /boot and /. (zip) But with the external hardware RAID attached to the PCI SCSI card, it insists on calling the external hardware RAID /dev/hda and the internal RAID one disk /dev/hdb. (zip) Why does SUSE insist that the external RAID disk is /dev/sda? (How does it even manage to find it before it finds the internal disks?)
Interestingly, booting from the SUSE CD ROM correctly sees the internal RAID one disk as /dev/sda and the external RAID as /dev/sdc (the untouched internal disk is /dev/sdb).
Any ideas?
yes... at boot-up the kernel seeks for scsi controllers, and after that, it seeks for disks, starting at scsi0 (first controller found), scsi1, until scsin (n-th controller) for some reason, your second controller is being found before your original controller. If they two use the same chipset, it may have some way of inverting the order of the scan (normally it follows the pci bus numbering order) if they use different chipsets, and if their drivers are loaded as modules, you could see the order they're being loaded during boot, if your new controller's driver is being loaded before, you may try changing the modules name's order on the line INITRD_MODULES on /etc/rc.config, exec'ing mkinitrd, and lilo, and try rebooting. Hope to have helped rather thar creating more confusion :) Regards Adilson Ribeiro