I had a slight problem with upgrading from RH8.0 to RH9 because the installer was smart enough to load firewire drivers, but the device assignment went to them before my root,boot, and swap scsi devices. I got an error messages after my existing RH8.0 was detected on sdd2, saying that swap device on sda2 was having an error. I disconnected the firewire devices, which I used to always load with a script in rc.local, and it now seems to be progressing OK.
Will I have a problem with RH9 when I try to set up the firewire devices and leave them attached during a reboot? I was picturing that RH9 may load the firewire drivers ahead of my root, boot, and swap system scsi drives in the same way during a normal bootup and cause confusion with the swap device in a similar way. If so, what can I do to force the devices to be assigned to /dev/s[abcd][1234] in a consistent order, particularly to avoid the boot and swap device confusion that seems to have appeared above?
I finished the upgrade and thought there was a problem, as my scripts that use procfs to rescan the scsi bus, which is what worked before to detect the drives, were hanging on detecting the second drive no matter what I did w/cards, power reset, plugin/out disks, and so on.
However, it turns out that now the devices are detected normally during bootup and nicely assigned to sdc[123] and sdd[123], allowing me to put them in /etc/fstab. So, it actually works much better than before when the scsi bus rescan scripts were necessary to detect the drives. Thanks to those who added the improvements...
Would be curious to know why the rescan function no longer works, if anyone has insight into this, although I don't need it for what I'm doing, now that the drives are detected and mounted during the reboot process.
Bill Wraith
