Marc Champagne wrote:
It's true that higher SCSI IDs have higher bus priority. I'm not sure> I have been trying to fresh install 5.0.7 lately on a system
> that has a Adaptec 2940U2w card.
> I have read that the higher the SCSI ID the higher is the priority
> (At least with adaptec), so I have been trying to do a fresh install
> with my HD being at ID 6 (ID 7 is reserved for the controller itself).
it has a noticable effect in actual system performance. If it makes
your installation not work, that's a bit more of a negative than the
small theoretical performance gain you're trying for...
The driver for 2940U2W is built into OSR507, why are you using a BTLD?> Now, this controller has 2 hosts of which:
> channel A (host 0)
> Is used for legacy devices
> (wide ultra, Wide Fast, Ultra SCSI, Fast SCSI, SCSI-1)
> channel B (host 1)
> Is use for Ultra2 devices (which is my case)
> So I have my HD on Host 1, SCSI ID 6 and would like to know the
> right sequences of boot commandes to get this going.
> I was able to install the whole OS using this boot command:
> boot: defbootstr Sdsk=ad160(1,0,6,0) link="blad325"
And why are you mentioning "ad160"? "ad160" and "blad" are drivers for
two different generations of Adaptec card. "blad" is the driver for the
2940U2 family. (My guess: you meant to type "Sdsk=blad(1,0,6,0)" above,
that's what you actually typed during install.)
Try booting the hard disk with:> but, when I reboot after installion, the system is able to
> boot by pressing enter at the boot: prompt.
> Both adapters (controllers) show up during the boot up sequence
> with type=ad160.
> Then I get the following...
> hd: no root disk controller was found
> hd: a Boot-Time loadable driver my be required
: defbootstr Sdsk=blad(0,0,6,0)
(or "ad160", if that's really what you're using). That is, direct it to
the _other_ adapter number. There's an issue with the "blad" and
possibly later Adaptec drivers, that they sometimes order the adapter
numbers one way during ISL and the other way when booting from the hard
If that bootstring works, then what you'll want to do is edit
/etc/conf/cf.d/mscsi and toggle the adapter numbers of all "blad" (or
"ad160") lines, which should include at least your root disk, possibly
other devices. When editing mscsi, do not change anything other than
the adapter numbers; in particular, do _not_ change the order of the
lines within the file. Just change 0 to 1 and 1 to 0 in the 3rd column
of any "blad" (or "ad160") lines.
Then relink, reboot without a bootstring.