Re: locking down scsi device id's in 6.2
On Sat, 14 Apr 2007 01:51:12 -0400 Dave [EMAIL PROTECTED] 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. [EMAIL PROTECTED] ~ camcontrol devlist WD External HDD Dev 0100 at scbus0 target 0 lun 0 (da0,pass0) SONY DVD RW DW-Q120A PYS1at scbus1 target 0 lun 0 (cd0,pass1) TOSHIBA ODD-DVD SD-M1802 1030at scbus1 target 1 lun 0 (cd1,pass2) USB2.0 CardReader CF RW 0814 at scbus2 target 0 lun 0 (da1,pass3) USB2.0 CardReader SD RW 0814 at scbus2 target 0 lun 1 (da2,pass4) USB2.0 CardReader SM RW 0814 at scbus2 target 0 lun 2 (da3,pass5) USB2.0 CardReader MS RW 0814 at scbus2 target 0 lun 3 (da4,pass6) SanDisk Cruzer Mini 0.1 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 [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locking down scsi device id's in 6.2
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 [EMAIL PROTECTED] To: Dave [EMAIL PROTECTED]; [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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. [EMAIL PROTECTED] ~ camcontrol devlist WD External HDD Dev 0100 at scbus0 target 0 lun 0 (da0,pass0) SONY DVD RW DW-Q120A PYS1at scbus1 target 0 lun 0 (cd0,pass1) TOSHIBA ODD-DVD SD-M1802 1030at scbus1 target 1 lun 0 (cd1,pass2) USB2.0 CardReader CF RW 0814 at scbus2 target 0 lun 0 (da1,pass3) USB2.0 CardReader SD RW 0814 at scbus2 target 0 lun 1 (da2,pass4) USB2.0 CardReader SM RW 0814 at scbus2 target 0 lun 2 (da3,pass5) USB2.0 CardReader MS RW 0814 at scbus2 target 0 lun 3 (da4,pass6) SanDisk Cruzer Mini 0.1 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 [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locking down scsi device id's in 6.2
On Fri, 13 Apr 2007 13:49:43 -0400 Dave [EMAIL PROTECTED] wrote: Hi, Either i've got a syntax error or my devices aren't wiring obeying /boot/device.hints. I've added: hint.scbus.0.at=ahc0 to my config. The tape drive is consistent on scbus0, target5, lun0, if i change it's target to say 3 it still shows up as scbus0, target5, lun0, but the sa driver is now at sa1 vs. sa0 and pass2 i think instead of pass0 not sure if this is important. The burner and the rom device never moved, they're still on scbus 2 and 3. Thanks. Dave. Please keep freebsd-questions included in your responses by replying to all. I have added the list back in to this message. Please copy and paste what you now have edited in /boot/device.hints to your next reply. Also, the ahc0 id for an adaptec scsi controller. Is that what you have. What I mean is, does ahc0 show up in dmesg or did you just include it from my previous email? Oh yeah, show me again what you have in camcontrol devlist Thanks Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locking down scsi device id's in 6.2
Hello, Thanks for your reply. Please see below for responses. - Original Message - From: Robert Marella [EMAIL PROTECTED] To: Dave [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, April 13, 2007 9:06 PM Subject: Re: locking down scsi device id's in 6.2 On Fri, 13 Apr 2007 13:49:43 -0400 Dave [EMAIL PROTECTED] wrote: Hi, Either i've got a syntax error or my devices aren't wiring obeying /boot/device.hints. I've added: hint.scbus.0.at=ahc0 to my config. The tape drive is consistent on scbus0, target5, lun0, if i change it's target to say 3 it still shows up as scbus0, target5, lun0, but the sa driver is now at sa1 vs. sa0 and pass2 i think instead of pass0 not sure if this is important. The burner and the rom device never moved, they're still on scbus 2 and 3. Thanks. Dave. Please keep freebsd-questions included in your responses by replying to all. I have added the list back in to this message. Please copy and paste what you now have edited in /boot/device.hints to your next reply. 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 Also, the ahc0 id for an adaptec scsi controller. Is that what you have. What I mean is, does ahc0 show up in dmesg or did you just include it from my previous email? I do have an adaptec scsi controller. Here's the dmesg output: ahc0: Adaptec 2940 Ultra SCSI adapter port 0xd000-0xd0ff mem 0xe8116000-0xe8116fff irq 16 at device 5.0 on pci0 ahc0: [GIANT-LOCKED] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs sa0 at ahc0 bus 0 target 5 lun 0 sa0: Quantum DLT4000 D996 Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) cd1 at ata1 bus 0 target 0 lun 0 cd1: LITE-ON LTR-48246S SS06 Removable CD-ROM SCSI-0 device cd1: 33.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present cd2 at ata1 bus 0 target 1 lun 0 cd2: LITE-ON DVDRW SOHW-1633S BS0K Removable CD-ROM SCSI-0 device cd2: 33.000MB/s transfers cd2: cd present [2295104 x 2048 byte records] Oh yeah, show me again what you have in camcontrol devlist This is what the devices are now, whenever i alter /boot/device.hints and reboot this box the cd's go all over the place, sometimes they're cd2 and 3, other times 0 and 3 this is what camcontrol devlist shows now: Quantum DLT4000 D996 at scbus0 target 5 lun 0 (sa0,pass0) LITE-ON LTR-48246S SS06 at scbus3 target 0 lun 0 (cd1,pass1) LITE-ON DVDRW SOHW-1633S BS0Kat scbus3 target 1 lun 0 (cd2,pass2) Thanks Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks. Dave. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locking down scsi device id's in 6.2
On Fri, 13 Apr 2007 21:39:42 -0400 Dave [EMAIL PROTECTED] 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locking down scsi device id's in 6.2
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 BS0Kat 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locking down scsi device id's in 6.2
On Thu, 12 Apr 2007 21:15:22 -0400 Dave [EMAIL PROTECTED] 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 BS0Kat 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. 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 hint.da.0.at=scbus0 hint.da.0.target=0 hint.da.0.unit=0 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 hint.da.0.at=scbus0 hint.da.0.target=0 hint.da.0.unit=0 I hope this helps Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locking down scsi device id's in 6.2
On Sat, 7 Apr 2007 21:16:50 -0400 Dave [EMAIL PROTECTED] wrote: (Format recovered: Please do not top post) On Fri, 6 Apr 2007 19:15:27 -0400 Dave [EMAIL PROTECTED] wrote: Hello, I've got a situation where three devices, one a scsi tape drive and the other two ide burners under scsi emulation with atapicam are fighting for scsi id's and i'd like to lock them down to specific id's. When the tape drive isn't plugged in the burners get 000 and 010 scsi ids, but when the tape goes in it takes 050 and the burners are on bus2 200 and 210 respectively. I hope this makes sense. I've been over loader and device.hints as well and i'm lost. I'd appreciate any info on this. Thanks. Dave. Hello Dave Have you looked at man scsi (4) for the correct way to edit /boot/device.hints to wire down devices? HTH Robert Hello, Yes i have. I am confused as to bus, target, and the values i'm suppose to use. Dave. Dave, Not only is top posting frowned upon on the FreeBSD lists you also removed -questions from your reply. I didn't even check my email over the weekend. Had you kept -questions in the loop you might have received an answer a lot sooner. Also, since I am wrong about as often as I am right you would probably received a better answer. That said, I will try to help. IMHO the easiest way to find the values is to boot with your SCSI tape drive connected. When you are up you can run camcontrol devlist without the quotes. This will show you the values. Example: SONY DVD RW DW-Q120A PYS1at scbus1 target 0 lun 0 (cd1,pass1) SONY DVD-ROM DDU1612 DYS1at scbus1 target 1 lun 0 (cd0,pass0) You should use dmesg to find the controller for the SCSI. It will be something like AHC0. you can then use all of these values in /boot/device.hints as shown in man scsi. I hope this helps. Remember to keep the list in the email. The archives will then have the final solution for the next person who needs it or when I forget :-) Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: locking down scsi device id's in 6.2
On Fri, 6 Apr 2007 19:15:27 -0400 Dave [EMAIL PROTECTED] wrote: Hello, I've got a situation where three devices, one a scsi tape drive and the other two ide burners under scsi emulation with atapicam are fighting for scsi id's and i'd like to lock them down to specific id's. When the tape drive isn't plugged in the burners get 000 and 010 scsi ids, but when the tape goes in it takes 050 and the burners are on bus2 200 and 210 respectively. I hope this makes sense. I've been over loader and device.hints as well and i'm lost. I'd appreciate any info on this. Thanks. Dave. Hello Dave Have you looked at man scsi (4) for the correct way to edit /boot/device.hints to wire down devices? HTH Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
locking down scsi device id's in 6.2
Hello, I've got a situation where three devices, one a scsi tape drive and the other two ide burners under scsi emulation with atapicam are fighting for scsi id's and i'd like to lock them down to specific id's. When the tape drive isn't plugged in the burners get 000 and 010 scsi ids, but when the tape goes in it takes 050 and the burners are on bus2 200 and 210 respectively. I hope this makes sense. I've been over loader and device.hints as well and i'm lost. I'd appreciate any info on this. Thanks. Dave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
