locking down scsi device id's in 6.2

Robert Marella rmarella at gmail.com
Fri Apr 13 01:32:35 UTC 2007

On Thu, 12 Apr 2007 21:15:22 -0400
"Dave" <dmehler26 at woh.rr.com> wrote:

> Hello,
>     My thanks to everyone who has helped thus far with this
> situation. I've gone over scsi(4) and have added the below to
> device.hints:
> hint.sa.0.at="scbus0"
> hint.sa.0.target="5"
> hint.sa.0.unit="0"
> hint.cd.0.at="scbus0"
> hint.cd.0.target="0"
> hint.cd.0.unit="0"
> hint.cd.1.at="scbus0"
> hint.cd.1.target="1"
> hint.cd.1.unit="0"
> camcontrol devlist shows:
> <Quantum DLT4000 D996>             at scbus0 target 5 lun 0
> (sa0,pass0) <LITE-ON LTR-48246S SS06>          at scbus2 target 0 lun
> 0 (cd2,pass1) <LITE-ON DVDRW SOHW-1633S BS0K>    at scbus2 target 1
> lun 0 (cd3,pass2)
> I used the wired example, but my device didn't wire. Any suggestions
> as to what i missed?
> Thanks.
> Dave.


I still think you are missing the scsi controller.

I used to use a scsi hard drive in one of my computers and here is what
I had

hint.scbus.0.at="ahc0"   #find this with dmesg

I do not think you have to do anything with the Cd devices. At least I
never did. At this time I have an external hard drive on firewire that
I have wired down with the following.

### Wire down external hd to da0###
hint.scbus.0.at="sbp0"    #find this with dmesg

I hope this helps


More information about the freebsd-questions mailing list