From owner-freebsd-questions@FreeBSD.ORG Sun Apr 15 01:53:26 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F3A6416A400 for ; Sun, 15 Apr 2007 01:53:25 +0000 (UTC) (envelope-from dmehler26@woh.rr.com) Received: from ms-smtp-04.ohiordc.rr.com (ms-smtp-04.ohiordc.rr.com [65.24.5.138]) by mx1.freebsd.org (Postfix) with ESMTP id CB9D013C480 for ; Sun, 15 Apr 2007 01:53:25 +0000 (UTC) (envelope-from dmehler26@woh.rr.com) Received: from satellite (cpe-71-64-129-15.woh.res.rr.com [71.64.129.15]) by ms-smtp-04.ohiordc.rr.com (8.13.6/8.13.6) with SMTP id l3F1rOs5018496; Sat, 14 Apr 2007 21:53:24 -0400 (EDT) Message-ID: <001f01c77f00$e1b3e820$0200a8c0@satellite> From: "Dave" To: "Robert Marella" , References: <000501c778a1$769989b0$0200a8c0@satellite> <20070407124555.3243bbcb@p4> <000501c7797b$961a9010$0200a8c0@satellite> <20070409072701.0687c6cd@p4> <001701c77d69$360a20e0$0200a8c0@satellite> <20070412153231.6cdc124e@p4> <000501c77df4$1f0ee2f0$0200a8c0@satellite> <20070413150600.77fca4eb@p4> <000701c77e35$c6d6f090$0200a8c0@satellite> <20070413191517.43b0905e@p4> <000d01c77e58$e896b080$0200a8c0@satellite> <20070414144231.464ee40e@p4> Date: Sat, 14 Apr 2007 21:53:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Subject: Re: locking down scsi device id's in 6.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dave List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2007 01:53:26 -0000 Hi, Thanks. That did it! I now have the tape drive right where it's suppose to be and the burners on 1,0,0 and 1,1,0 cd0 and cd1 which is what i originally wanted. For reference here is my modifications to /boot/device.hints: # custom devices hint.scbus.0.at="ahc0" #find this with dmesg hint.sa.0.at="scbus0" hint.sa.0.target="5" hint.sa.0.unit="0" hint.scbus.1.at="ata1" #find this with dmesg hint.cd.0.at="scbus1" hint.cd.0.target="0" hint.cd.0.unit="0" hint.cd.1.at="scbus1" hint.cd.1.target="1" hint.cd.1.unit="0" Thanks a lot. Dave. ----- Original Message ----- From: "Robert Marella" To: "Dave" ; Sent: Saturday, April 14, 2007 8:42 PM Subject: Re: locking down scsi device id's in 6.2 > On Sat, 14 Apr 2007 01:51:12 -0400 > "Dave" wrote: > >> Hi, >> Thanks. Still no good, basically it just brought me back to where >> i was. Do you know anyone else who might have an idea on this? >> Thanks for all your help. >> Dave. > > Perhaps I have been leading you on a wild goose chase. I have re-read > all of your posts and I now understand that you want to wire down bus, > target and unit. > > It is my understanding that the device.hints will wire down the device > (i.e. /dev/sa# or in my case /dev/da#). I played around with my system > with the external firewire drive and as long as I have the lines in > device.hints the 0-0-0 is reserved for the drive whether it is plugged > in or not. The optical drives remained at 2-0-0 and 2-1-0. > > I then plugged in a USB thumb drive and rebooted. This forced the > optical drives from 2-0-0 and 2-1-0 to 3-0-0 3-1-0 respectively. > > I then plugged in a USD card reader and rebooted. This forced the > optical drives to 4-0-0 and 4-1-0. > > I thought about this for awhile and looked at dmesg again. I then > edited /boot/device.hints as follows > > ### Wire down external hd to da0### > hint.scbus.0.at="sbp0" > hint.da.0.at="scbus0" > hint.da.0.target="0" > hint.da.0.unit="0" > > hint.scbus.1.at="ata1" #optical drives on the second ata cable. > hint.cd.0.at="scbus1" > hint.cd.0.target="0" > hint.cd.0.unit="0" > > hint.cd.1.at="scbus1" > hint.cd.1.target="1" > hint.cd.1.unit="0" > > this forced the optical drives back to 1-0-0 and 1-1-0 no matter what > other devices are plugged in. > > > [robert@asus64] ~> camcontrol devlist > at scbus0 target 0 lun 0 (da0,pass0) > at scbus1 target 0 lun 0 (cd0,pass1) > at scbus1 target 1 lun 0 (cd1,pass2) > at scbus2 target 0 lun 0 (da1,pass3) > at scbus2 target 0 lun 1 (da2,pass4) > at scbus2 target 0 lun 2 (da3,pass5) > at scbus2 target 0 lun 3 (da4,pass6) > at scbus3 target 0 lun 0 (da5,pass7) > > This may be what you want. > > I hope this helps. > > Robert > > P.S. I am adding the list back in. > > >> > On Fri, 13 Apr 2007 21:39:42 -0400 >> > "Dave" wrote: >> > >> >> Hello, >> >> Thanks for your reply. Please see below for responses. >> >> >> > >> >> Here is my add-ons to /boot/device.hints: >> >> >> >> # custom devices >> >> hint.scbus.0.at="ahc0" #find this with dmesg >> >> 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" >> >> int.cd.1.unit="0" >> >> >> > >> > Dave >> > >> > I would try commenting out or removing the hints referencing the >> > cd's so that you are only wiring down the scsi tape. >> > >> > The only other thing that comes to mind is the options master/slave >> > on the optical drives themselves. Both drives should be on the same >> > ATA cable and I always set "master" on the drive at the far end of >> > the cable and "slave" on the other. >> > >> > If this does not help I am afraid that I can be of no further help. >> > perhaps someone else on the list can give some additional advice. >> > >> > Robert >>