Missing /proc/scsi files...?
Does anyone know what is going on with /proc/scsi/* in 2.6.8...? I'm trying to run the 3ware disc management daemon on my 9500 (3dm2), which fails because it can't find /proc/scsi/3w-9xxx. In /proc/scsi I only have scsi and device_info... zaphod:~# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: 3wareModel: Logical Disk 00 Rev: 1.00 Type: Direct-AccessANSI SCSI revision: Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: 3wareModel: Logical Disk 01 Rev: 1.00 Type: Direct-AccessANSI SCSI revision: zaphod:~# cat /proc/scsi/device_info 'Aashima' 'IMAGERY 2400SP' 0x1 'CHINON' 'CD-ROM CDS-431' 0x1 'CHINON' 'CD-ROM CDS-535' 0x1 'DENON' 'DRD-25X' 0x1 'HITACHI' 'DK312C' 0x1 'HITACHI' 'DK314C' 0x1 'IMS' 'CDD521/10' 0x1 'MAXTOR' 'XT-3280' 0x1 'MAXTOR' 'XT-4380S' 0x1 'MAXTOR' 'MXT-1240S' 0x1 'MAXTOR' 'XT-4170S' 0x1 'MAXTOR' 'XT-8760S' 0x1 'MEDIAVIS' 'RENO CD-ROMX2A' 0x1 'NEC' 'CD-ROM DRIVE:841' 0x1 'PHILIPS' 'PCA80SC' 0x1 'RODIME' 'RO3000S' 0x1 'SUN' 'SENA' 0x1 'SANYO' 'CRD-250S' 0x1 'SEAGATE' 'ST157N' 0x1 'SEAGATE' 'ST296' 0x1 'SEAGATE' 'ST1581' 0x1 'SONY' 'CD-ROM CDU-541' 0x1 'SONY' 'CD-ROM CDU-55S' 0x1 'SONY' 'CD-ROM CDU-561' 0x1 'SONY' 'CD-ROM CDU-8012' 0x1 'TANDBERG' 'TDC 3600' 0x1 'TEAC' 'CD-R55S' 0x1 'TEAC' 'CD-ROM' 0x1 'TEAC' 'MT-2ST/45S2-27' 0x1 'HP' 'C1750A' 0x1 'HP' 'C1790A' 0x1 'HP' 'C2500A' 0x1 'MEDIAVIS' 'CDR-H93MV' 0x1 'MICROTEK' 'ScanMaker II' 0x1 'MITSUMI' 'CD-R CR-2201CS' 0x1 'NEC' 'D3856' 0x1 'QUANTUM' 'LPS525S' 0x1 'QUANTUM' 'PD1225S' 0x1 'QUANTUM' 'FIREBALL ST4.3S' 0x1 'RELISYS' 'Scorpio' 0x1 'SANKYO' 'CP525' 0x1 'TEXEL' 'CD-ROM' 0x1 'YAMAHA' 'CDR100' 0x1 'YAMAHA' 'CDR102' 0x1 'YAMAHA' 'CRW8424S' 0x1 'YAMAHA' 'CRW6416S' 0x1 'ADAPTEC' 'AACRAID' 0x2 'ADAPTEC' 'Adaptec 5400S' 0x2 'CANON' 'IPUBJD' 0x40 'CMD' 'CRA-7280' 0x40 'CNSI' 'G7324' 0x40 'CNSi' 'G8324' 0x40 'COMPAQ' 'LOGICAL VOLUME' 0x2 'COMPAQ' 'CR3500' 0x2 'COMPAQ' 'MSA1000' 0x1040 'COMPAQ' 'MSA1000 VOLUME' 0x1040 'COMPAQ' 'HSV110' 0x21000 'DDN' 'SAN DataDirector' 0x40 'DEC' 'HSG80' 0x1040 'DELL' 'PV660F' 0x40 'DELL' 'PV660F PSEUDO' 0x40 'DELL' 'PSEUDO DEVICE .' 0x40 'DELL' 'PV530F' 0x40 'DELL' 'PERCRAID' 0x2 'DGC' 'RAID' 0x40 'DGC' 'DISK' 0x40 'EMC' 'SYMMETRIX' 0x242 'EMULEX' 'MD21/S2 ESDI' 0x10 'FSC' 'CentricStor' 0x240 'HITACHI' 'DF400' 0x40 'HITACHI' 'DF500' 0x40 'HITACHI' 'DF600' 0x40 'HP' 'A6189A' 0x240 'HP' 'OPEN-' 0x240 'HP' 'NetRAID-4M' 0x2 'HP' 'HSV100' 0x21000 'HP' 'C1557A' 0x2 'IBM' 'AuSaV1S2' 0x2 'IBM' 'ProFibre 4000R' 0x240 'iomega' 'jaz 1GB' 0x21 'IOMEGA' 'Io20S *F' 0x8 'INSITE' 'Floptical F*8I' 0x8 'INSITE' 'I325VM' 0x8 'iRiver' 'iFP Mass Driver' 0x80400 'LASOUND' 'CDX7405' 0x90 'MATSHITA' 'PD-1' 0x12 'MATSHITA' 'DMC-LC5' 0x80400 'MATSHITA' 'DMC-LC40' 0x80400 'MegaRAID' 'LD' 0x2 'MICROP' '4110' 0x20 'MYLEX' 'DACARMRB' 0x2 'nCipher' 'Fastness Crypto' 0x2 'NAKAMICH' 'MJ-4.8S' 0x12 'NAKAMICH' 'MJ-5.16S' 0x12 'NEC' 'PD-1 ODX654P' 0x12 'NRC' 'MBR-7' 0x12 'NRC' 'MBR-7.4' 0x12 'PIONEER' 'CD-ROM DRM-600' 0x12 'PIONEER' 'CD-ROM DRM-602X' 0x12 'PIONEER' 'CD-ROM DRM-604X' 0x12 'REGAL' 'CDC-4X' 0x90 'SGI' 'RAID3' 0x40 'SGI' 'RAID5' 0x40 'SGI' 'TP9100' 0x2 'SONY' 'CD-ROM CDU-8001' 0x4 'SONY' 'TSL' 0x2 'SUN' 'T300' 0x40 'SUN' 'T4' 0x40 'TEXEL' 'CD-ROM' 0x4 'TOSHIBA' 'CDROM' 0x100 'TOSHIBA' 'CD-ROM' 0x100 'XYRATEX' 'RS' 0x240 'Zzyzx' 'RocketStor 500S' 0x40 'Zzyzx' 'RocketStor 2000' 0x40 However, under my 8500 card with a 2.4 kernel on my home debian server, I can see the 3ware driver does indeed have files under /proc/scsi/3w- [EMAIL PROTECTED]:~$ cat /proc/scsi/3w-/0 scsi0: 3ware Storage Controller Driver version: 1.02.00.037 Current commands posted: 0 Max commands posted: 254 Current pending commands:0 Max pending commands:4 Last sgl length: 2 Max sgl length: 62 Last sector count: 12 Max sector count: 256 Resets: 0 Aborts: 0 AEN's: 0 I'm currently running the 2.6.8-5 from testing. I've had a gander through the changelog, but can't see very much related to possible errors in /proc/scsi. Does anyone know why the new 3ware driver doesn't get the files created in /proc under 2.6.8? Legacy /proc/scsi support is enabled (built into) in the 2.6 kernel config. Lots of googling has revealed naff-all information (since the 9500's are brand new cards, and few people seem interested in using 3dm anyway), and obviously 3ware are rather reticent to give me the time of day since I'm running an unsupported platform. Also, the 3dm tools for Linux are closed source (grr) so I can't do much haXx0ring about in there either. If anyone has any ideas what is going on and whether or not it's fixable, I'd love to hear it! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Missing /proc/scsi files...?
At 13:50 28/09/2004, you wrote: Does anyone know what is going on with /proc/scsi/* in 2.6.8...? I'm trying to run the 3ware disc management daemon on my 9500 (3dm2), which fails because it can't find /proc/scsi/3w-9xxx. In /proc/scsi I only have scsi and device_info... I'm currently running the 2.6.8-5 from testing. I've had a gander through the changelog, but can't see very much related to possible errors in /proc/scsi. Does anyone know why the new 3ware driver doesn't get the files created in /proc under 2.6.8? Legacy /proc/scsi support is enabled (built into) in the 2.6 kernel config. Lots of googling has revealed naff-all information (since the 9500's are brand new cards, and few people seem interested in using 3dm anyway), and obviously 3ware are rather reticent to give me the time of day since I'm running an unsupported platform. Also, the 3dm tools for Linux are closed source (grr) so I can't do much haXx0ring about in there either. If anyone has any ideas what is going on and whether or not it's fixable, I'd love to hear it! snip Solved, sorta. 3ware have put up a beta version of 3dm2 which works with the inbuilt driver of 2.6.8.1. I used the install script to create the config file, ran 3dm2 from the CLI, and bingo I could connect via an SSH tunnel and actually do stuff this time. One of those rare occurrences where the drivers works well before the application ;) Although I can't get the email notification to work ([EMAIL PROTECTED]). Will post back with more info as and when, and I'll see if I can hack an init script or something together. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
