On Sun, 2005-10-02 at 21:51 -0700, Pete Lancashire wrote: > Jeff, > > Part II :) > > What looks confusing to me is during boot and the initial > device driver loading the Adapter and drive is found, > scsi1, and the one drive attached is assigned the /dev device sda. > but once the boot sequence is done, there is no /dev/sda > or a device reported by /proc/scsi/scsi. > The dmesg output showed that it was not configured. It did not see any partitions so did not assign sda1 for you. What is the partition type? I see one solaris partition type in fdisk table types. So theoretically, even if it is a solaris partition Linux FC4 should see it. I still would look at driver for the adapter to verify it loads, and look at termination. I have seen devices that work fine as long as they are the only thing on the bus, but they fall down when another is added. Also have seen cases where on one OS they would work and on another they would not with the exact same hardware. Sometimes that is driver and other times hardware/termination etc. If the driver does not work properly you can get the device (/dev/sda) reported, but the partition is never recognized (and other weird things) Try booting from Knoppix to see if you can see the drive there. > -pete "wait till i attach all 14 devices" > > > > On Sun, 2005-10-02 at 20:18, Jeff Vian wrote: > > On Sun, 2005-10-02 at 19:01 -0700, Pete Lancashire wrote: > > > (will update to FC3 soon) > > > > > > FC1 x86 > > > > > > I just added an Adaptec 29160 and for now one old hard drive > > > > > > a snip of dmesg gives me > > > > > > Attached scsi disk sda at scsi1, channel 0, id 0, lun 0 > > > SCSI device sda: 17755614 512-byte hdwr sectors (9091 MB) > > > sda: unknown partition table > > > > > > but no matter what I do, where I look cant find my disk > > > like fdisk /dev/sda give unable to open device. > > > > > > > > > /proc/scsi/scsi only has my two pseudo scsi devices in it > > > > > > Attached devices: > > > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > > > Vendor: ATAPI Model: CD-RW 52X24X Rev: MB53 > > > Type: CD-ROM ANSI SCSI revision: 02 > > > Host: scsi0 Channel: 00 Id: 01 Lun: 00 > > > Vendor: TOSHIBA Model: CD/DVDW SD-R5372 Rev: TU53 > > > Type: CD-ROM ANSI SCSI revision: 02 > > > > > > > > > You may want to check/confirm the actual scsi cable is properly > > connected and terminated. Unlike IDE devices, there MUST be exactly 2 > > terminators on a scsi bus and the cable must be connected properly. > > Less than 2 termination points, more than 2 termination points, or > > terminators not at the ends of the cable can cause problems. > > > > Connections MUST be made to both ends of the cable *at the end*. Any > > connectors between may or may not be used. Termination is usually done > > by the adapter at one end of the cable, and by either a physical > > terminator or the device connected to the other end of the cable. > > > > If the drive can be jumpered to enable termination on the drive it can > > be connected to the end of the cable. No other termination is allowed at > > this end of the cable when this is used. Termination must also be > > compatible with the bus speed. Your adapter is ultra 160 so the > > termination must be at least that quality. > > > > The last thing that is critical with scsi is addressing. No two devices > > on the same bus can have the same address. I don't think that is your > > issue since by default the adapter is set to ID 7 and the dmesg output > > shows the drive is at ID 0. > > > > > doing echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi > > > > > > only adds an entry do /log/messges, does not change /proc/scsi/scsi > > > s output > > > > > > > > > > > > also /proc/scsi seems to be a bit shy of things > > > > > > Am I missing something really simple ? > > > > > > TIA, > > > > > > -PETE > > > > > > in /proc/scsi > > > > > > >find /proc/scsi > > > /proc/scsi > > > /proc/scsi/sg > > > /proc/scsi/sg/version > > > /proc/scsi/sg/host_strs > > > /proc/scsi/sg/host_hdr > > > /proc/scsi/sg/hosts > > > /proc/scsi/sg/device_strs > > > /proc/scsi/sg/device_hdr > > > /proc/scsi/sg/devices > > > /proc/scsi/sg/debug > > > /proc/scsi/sg/def_reserved_size > > > /proc/scsi/sg/allow_dio > > > /proc/scsi/ide-scsi > > > /proc/scsi/ide-scsi/0 > > > /proc/scsi/scsi > > > > > > > > > > > > the SCSI part of dmesg ... > > > > > > SCSI subsystem driver Revision: 1.00 > > > hdc: attached ide-scsi driver. > > > hdd: attached ide-scsi driver. > > > scsi0 : SCSI host adapter emulation for IDE ATAPI devices > > > Vendor: ATAPI Model: CD-RW 52X24X Rev: MB53 > > > Type: CD-ROM ANSI SCSI revision: 02 > > > Vendor: TOSHIBA Model: CD/DVDW SD-R5372 Rev: TU53 > > > Type: CD-ROM ANSI SCSI revision: 02 > > > parport0: PC-style at 0x378 [PCSPP,TRISTATE] > > > parport0: Printer, HEWLETT-PACKARD DESKJET 895C > > > scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 > > > <Adaptec 29160N Ultra160 SCSI adapter> > > > aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs > > > > > > blk: queue f6fbde14, I/O limit 4095Mb (mask 0xffffffff) > > > (scsi1:A:0): 10.000MB/s transfers (10.000MHz, offset 15) > > > Vendor: SEAGATE Model: ST410800N Rev: 0016 > > > Type: Direct-Access ANSI SCSI revision: 02 > > > blk: queue f6fbdc14, I/O limit 4095Mb (mask 0xffffffff) > > > scsi1:A:0:0: Tagged Queuing enabled. Depth 32 > > > Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0 > > > Attached scsi CD-ROM sr1 at scsi0, channel 0, id 1, lun 0 > > > sr0: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray > > > Uniform CD-ROM driver Revision: 3.12 > > > sr1: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray > > > sr1: Hmm, seems the drive doesn't support multisession CD's > > > Attached scsi disk sda at scsi1, channel 0, id 0, lun 0 > > > SCSI device sda: 17755614 512-byte hdwr sectors (9091 MB) > > > sda: unknown partition table > > > scsi : 1 host left. > > > > > > The key being > > > >
