From: David H. <dhi...@hi...> - 2005-05-19 04:30:24
|
I'm running Fedora core 3 using a 3ware Escalade 9500S-8 raid controller with 4 SATA drives. I get the following error at boot time: smartd[4195] Device: /dev/sda, opened kernel: 3w-9xxx: scsi4: ERROR: (0x03:0x0104): SGL entry has illegal length:address=0x7735C00, length=0x24, cmd=X. kernel: program smartd is using a deprecated SCSI ioctl, please convert it to SG_IO smartd[4195]: Device /dev/sda, please try '-d 3ware,N' smartd[4195]: Unable to register SCSI device /dev/sda at line 1 of file /etc/smard.conf smard[4195]: Unable to register device /dev/sda (no Directive -d removable). Exiting File /etc/smartd.conf: /dev/sda -H -m root@localhost.localdomain I ran the following command: smartctl -H -S on -o on -d 3ware,0 /dev/sda smartctl version 5.33 [x86_64-redhat-linux-gnu] Copyright.... WARNING - NO DEVICE FOUND ON.... smartctl -H -S on -o on -d 3ware,0 /dev/sda1 SMART support is: Ambiguous - ATA IDENTIFY DEVICE workds 82-83 don't show if SMART supported. A manadatory SMART command failed: exiting. .... So what's the proper smartd.conf file for this configuration? |
From: Andreas U. <un...@ne...> - 2005-05-19 04:40:40
|
Thats not right for 3ware controllers, you had to use a style like /dev/twe0 -d 3ware,0 -a -p -o on -S on -s (S/../.././02|L/../../6/03) -m root@localhost /dev/twe0 -d 3ware,1 -a -p -o on -S on -s (S/../.././03|L/../../7/03) -m root@localhost twe is the character device and with -d you specify which physical disk you want to monitor (for you 0,1,2 and 3) Andreas David Highley wrote: >I'm running Fedora core 3 using a 3ware Escalade 9500S-8 raid controller >with 4 SATA drives. I get the following error at boot time: >smartd[4195] Device: /dev/sda, opened >kernel: 3w-9xxx: scsi4: ERROR: (0x03:0x0104): SGL entry has illegal >length:address=0x7735C00, length=0x24, cmd=X. >kernel: program smartd is using a deprecated SCSI ioctl, please convert >it to SG_IO >smartd[4195]: Device /dev/sda, please try '-d 3ware,N' >smartd[4195]: Unable to register SCSI device /dev/sda at line 1 of file >/etc/smard.conf >smard[4195]: Unable to register device /dev/sda (no Directive -d >removable). Exiting > >File /etc/smartd.conf: >/dev/sda -H -m root@localhost.localdomain > >I ran the following command: >smartctl -H -S on -o on -d 3ware,0 /dev/sda >smartctl version 5.33 [x86_64-redhat-linux-gnu] Copyright.... >WARNING - NO DEVICE FOUND ON.... > >smartctl -H -S on -o on -d 3ware,0 /dev/sda1 >SMART support is: Ambiguous - ATA IDENTIFY DEVICE workds 82-83 don't >show if SMART supported. >A manadatory SMART command failed: exiting. .... > > >So what's the proper smartd.conf file for this configuration? > > > >------------------------------------------------------- >This SF.Net email is sponsored by Oracle Space Sweepstakes >Want to be the first software developer in space? >Enter now for the Oracle Space Sweepstakes! >http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >_______________________________________________ >Smartmontools-support mailing list >Sma...@li... >https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > > |
From: Samuel F. <sf...@ra...> - 2005-05-20 01:59:29
|
Andreas Unterkircher wrote: > Thats not right for 3ware controllers, you had to use a style like > > /dev/twe0 -d 3ware,0 -a -p -o on -S on -s (S/../.././02|L/../../6/03) -m > root@localhost > /dev/twe0 -d 3ware,1 -a -p -o on -S on -s (S/../.././03|L/../../7/03) -m > root@localhost > > twe is the character device and with -d you specify which physical disk > you want to > monitor (for you 0,1,2 and 3) Wouldn't a 9500 controller use twa not twe like the 750x/850x controllers. |
From: Andreas U. <un...@ne...> - 2005-05-20 04:14:37
|
Samuel Flory wrote: > Wouldn't a 9500 controller use twa not twe like the 750x/850x > controllers. In my server I have both - a old 6000er (ata) & 9500S-4LP (sata) controller. Using smartd v5.33 and kernel 2.6.11. For both controllers I can use the /dev/twe devices on my side. /dev/twe0 -o on -S on -d 3ware,0 -a -s L/../../7/01 -m un...@ne... /dev/twe0 -o on -S on -d 3ware,1 -a -s L/../../7/02 -m un...@ne... /dev/twe0 -o on -S on -d 3ware,2 -a -s L/../../7/03 -m un...@ne... /dev/twe0 -o on -S on -d 3ware,3 -a -s L/../../7/03 -m un...@ne... /dev/twe1 -o on -S on -d 3ware,0 -a -s L/../../7/01 -m un...@ne... /dev/twe1 -o on -S on -d 3ware,1 -a -s L/../../7/02 -m un...@ne... /dev/twe1 -o on -S on -d 3ware,2 -a -s L/../../7/03 -m un...@ne... May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], opened May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], found in smartd database. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], enabled SMART Attribute Autosave. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], enabled SMART Automatic Offline Testing. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], is SMART capable. Adding to "monitor" list. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], opened May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], found in smartd database. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], enabled SMART Attribute Autosave. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], enabled SMART Automatic Offline Testing. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], is SMART capable. Adding to "monitor" list. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], opened May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], found in smartd database. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], enabled SMART Attribute Autosave. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], enabled SMART Automatic Offline Testing. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], is SMART capable. Adding to "monitor" list. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], opened May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], found in smartd database. May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], enabled SMART Attribute Autosave. May 20 06:07:32 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], enabled SMART Automatic Offline Testing. May 20 06:07:32 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], is SMART capable. Adding to "monitor" list. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], opened May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], found in smartd database. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], enabled SMART Attribute Autosave. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], enabled SMART Automatic Offline Testing. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], is SMART capable. Adding to "monitor" list. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], opened May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], found in smartd database. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], enabled SMART Attribute Autosave. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], enabled SMART Automatic Offline Testing. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], is SMART capable. Adding to "monitor" list. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], opened May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], found in smartd database. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], enabled SMART Attribute Autosave. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], enabled SMART Automatic Offline Testing. May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], is SMART capable. Adding to "monitor" list. May 20 06:07:32 server smartd[1688]: Monitoring 8 ATA and 0 SCSI devices May 20 06:07:34 server smartd[1690]: smartd has fork()ed into background mode. New PID=1690. May 20 06:07:34 server smartd[1690]: file /var/run/smartd.pid written containing PID 1690 |
From: Bruce A. <ba...@gr...> - 2005-05-20 15:31:23
|
Andreas, Interesting. I had thought that you HAD to use /dev/twe for the 'escalade' cards (<=8000) and /dev/twa for the 'apache' cards (>=9000). Bruce On Fri, 20 May 2005, Andreas Unterkircher wrote: > Samuel Flory wrote: > > > Wouldn't a 9500 controller use twa not twe like the 750x/850x > > controllers. > > In my server I have both - a old 6000er (ata) & 9500S-4LP (sata) > controller. Using smartd > v5.33 and kernel 2.6.11. For both controllers I can use the /dev/twe > devices on my side. > > /dev/twe0 -o on -S on -d 3ware,0 -a -s L/../../7/01 -m un...@ne... > /dev/twe0 -o on -S on -d 3ware,1 -a -s L/../../7/02 -m un...@ne... > /dev/twe0 -o on -S on -d 3ware,2 -a -s L/../../7/03 -m un...@ne... > /dev/twe0 -o on -S on -d 3ware,3 -a -s L/../../7/03 -m un...@ne... > > /dev/twe1 -o on -S on -d 3ware,0 -a -s L/../../7/01 -m un...@ne... > /dev/twe1 -o on -S on -d 3ware,1 -a -s L/../../7/02 -m un...@ne... > /dev/twe1 -o on -S on -d 3ware,2 -a -s L/../../7/03 -m un...@ne... > > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > opened > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > found in smartd database. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > enabled SMART Attribute Autosave. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > enabled SMART Automatic Offline Testing. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > is SMART capable. Adding to "monitor" list. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > opened > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > found in smartd database. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > enabled SMART Attribute Autosave. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > enabled SMART Automatic Offline Testing. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > is SMART capable. Adding to "monitor" list. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > opened > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > found in smartd database. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > enabled SMART Attribute Autosave. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > enabled SMART Automatic Offline Testing. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > is SMART capable. Adding to "monitor" list. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > opened > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > found in smartd database. > May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > enabled SMART Attribute Autosave. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > enabled SMART Automatic Offline Testing. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > is SMART capable. Adding to "monitor" list. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > opened > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > found in smartd database. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > enabled SMART Attribute Autosave. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > enabled SMART Automatic Offline Testing. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > is SMART capable. Adding to "monitor" list. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > opened > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > found in smartd database. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > enabled SMART Attribute Autosave. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > enabled SMART Automatic Offline Testing. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > is SMART capable. Adding to "monitor" list. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > opened > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > found in smartd database. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > enabled SMART Attribute Autosave. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > enabled SMART Automatic Offline Testing. > May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > is SMART capable. Adding to "monitor" list. > May 20 06:07:32 server smartd[1688]: Monitoring 8 ATA and 0 SCSI devices > May 20 06:07:34 server smartd[1690]: smartd has fork()ed into background > mode. New PID=1690. > May 20 06:07:34 server smartd[1690]: file /var/run/smartd.pid written > containing PID 1690 > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > |
From: Andreas U. <un...@ne...> - 2005-05-20 15:43:08
|
Yes, you are write. I'm seeing some problem within my /dev filesystem - the twe and twa devices have the same major number (253) instead of 254 for the twe*. this explain why it works with the 900x controller. the ctime is somewhere in 2004, probably I got them from one of the 'in engineering phase' 3dmd versions... sorry for the confusion. but wondering why the 600x controller is still working with 253.... Andreas Bruce Allen wrote: >Andreas, > >Interesting. I had thought that you HAD to use /dev/twe for the >'escalade' cards (<=8000) and /dev/twa for the 'apache' cards (>=9000). > >Bruce > >On Fri, 20 May 2005, Andreas Unterkircher wrote: > > > >>Samuel Flory wrote: >> >> >> >>> Wouldn't a 9500 controller use twa not twe like the 750x/850x >>>controllers. >>> >>> >>In my server I have both - a old 6000er (ata) & 9500S-4LP (sata) >>controller. Using smartd >>v5.33 and kernel 2.6.11. For both controllers I can use the /dev/twe >>devices on my side. >> >>/dev/twe0 -o on -S on -d 3ware,0 -a -s L/../../7/01 -m un...@ne... >>/dev/twe0 -o on -S on -d 3ware,1 -a -s L/../../7/02 -m un...@ne... >>/dev/twe0 -o on -S on -d 3ware,2 -a -s L/../../7/03 -m un...@ne... >>/dev/twe0 -o on -S on -d 3ware,3 -a -s L/../../7/03 -m un...@ne... >> >>/dev/twe1 -o on -S on -d 3ware,0 -a -s L/../../7/01 -m un...@ne... >>/dev/twe1 -o on -S on -d 3ware,1 -a -s L/../../7/02 -m un...@ne... >>/dev/twe1 -o on -S on -d 3ware,2 -a -s L/../../7/03 -m un...@ne... >> >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], >>opened >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], >>found in smartd database. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], >>enabled SMART Attribute Autosave. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], >>enabled SMART Automatic Offline Testing. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], >>is SMART capable. Adding to "monitor" list. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], >>opened >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], >>found in smartd database. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], >>enabled SMART Attribute Autosave. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], >>enabled SMART Automatic Offline Testing. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], >>is SMART capable. Adding to "monitor" list. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], >>opened >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], >>found in smartd database. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], >>enabled SMART Attribute Autosave. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], >>enabled SMART Automatic Offline Testing. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], >>is SMART capable. Adding to "monitor" list. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], >>opened >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], >>found in smartd database. >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], >>enabled SMART Attribute Autosave. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], >>enabled SMART Automatic Offline Testing. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], >>is SMART capable. Adding to "monitor" list. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], >>opened >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], >>found in smartd database. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], >>enabled SMART Attribute Autosave. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], >>enabled SMART Automatic Offline Testing. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], >>is SMART capable. Adding to "monitor" list. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], >>opened >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], >>found in smartd database. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], >>enabled SMART Attribute Autosave. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], >>enabled SMART Automatic Offline Testing. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], >>is SMART capable. Adding to "monitor" list. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], >>opened >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], >>found in smartd database. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], >>enabled SMART Attribute Autosave. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], >>enabled SMART Automatic Offline Testing. >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], >>is SMART capable. Adding to "monitor" list. >>May 20 06:07:32 server smartd[1688]: Monitoring 8 ATA and 0 SCSI devices >>May 20 06:07:34 server smartd[1690]: smartd has fork()ed into background >>mode. New PID=1690. >>May 20 06:07:34 server smartd[1690]: file /var/run/smartd.pid written >>containing PID 1690 >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by Oracle Space Sweepstakes >>Want to be the first software developer in space? >>Enter now for the Oracle Space Sweepstakes! >>http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >>_______________________________________________ >>Smartmontools-support mailing list >>Sma...@li... >>https://lists.sourceforge.net/lists/listinfo/smartmontools-support >> >> >> >> > > > |
From: Bruce A. <ba...@gr...> - 2005-05-20 16:02:41
|
> Yes, you are write. I'm seeing some problem within my /dev filesystem - > the twe and twa devices > have the same major number (253) instead of 254 for the twe*. this > explain why it works with the > 900x controller. the ctime is somewhere in 2004, probably I got them > from one of the 'in engineering > phase' 3dmd versions... sorry for the confusion. but wondering why the > 600x controller is still working > with 253.... Ouch! The code in smartmontools scans /proc/devices to see if twa or twe are listed, and gets the major number from there. So everything depends upon the driver correctly registering an entry there. If smartmontools finds a sensible major number in /proc/devices, it will make the sixteen /dev/twa or /dev/twe entries if they don't exist already. Cheers, Bruce > Bruce Allen wrote: > > >Andreas, > > > >Interesting. I had thought that you HAD to use /dev/twe for the > >'escalade' cards (<=8000) and /dev/twa for the 'apache' cards (>=9000). > > > >Bruce > > > >On Fri, 20 May 2005, Andreas Unterkircher wrote: > > > > > > > >>Samuel Flory wrote: > >> > >> > >> > >>> Wouldn't a 9500 controller use twa not twe like the 750x/850x > >>>controllers. > >>> > >>> > >>In my server I have both - a old 6000er (ata) & 9500S-4LP (sata) > >>controller. Using smartd > >>v5.33 and kernel 2.6.11. For both controllers I can use the /dev/twe > >>devices on my side. > >> > >>/dev/twe0 -o on -S on -d 3ware,0 -a -s L/../../7/01 -m un...@ne... > >>/dev/twe0 -o on -S on -d 3ware,1 -a -s L/../../7/02 -m un...@ne... > >>/dev/twe0 -o on -S on -d 3ware,2 -a -s L/../../7/03 -m un...@ne... > >>/dev/twe0 -o on -S on -d 3ware,3 -a -s L/../../7/03 -m un...@ne... > >> > >>/dev/twe1 -o on -S on -d 3ware,0 -a -s L/../../7/01 -m un...@ne... > >>/dev/twe1 -o on -S on -d 3ware,1 -a -s L/../../7/02 -m un...@ne... > >>/dev/twe1 -o on -S on -d 3ware,2 -a -s L/../../7/03 -m un...@ne... > >> > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > >>opened > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > >>found in smartd database. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > >>enabled SMART Attribute Autosave. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > >>enabled SMART Automatic Offline Testing. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_00], > >>is SMART capable. Adding to "monitor" list. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > >>opened > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > >>found in smartd database. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > >>enabled SMART Attribute Autosave. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > >>enabled SMART Automatic Offline Testing. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_01], > >>is SMART capable. Adding to "monitor" list. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > >>opened > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > >>found in smartd database. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > >>enabled SMART Attribute Autosave. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > >>enabled SMART Automatic Offline Testing. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_02], > >>is SMART capable. Adding to "monitor" list. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > >>opened > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > >>found in smartd database. > >>May 20 06:07:31 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > >>enabled SMART Attribute Autosave. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > >>enabled SMART Automatic Offline Testing. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe0 [3ware_disk_03], > >>is SMART capable. Adding to "monitor" list. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > >>opened > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > >>found in smartd database. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > >>enabled SMART Attribute Autosave. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > >>enabled SMART Automatic Offline Testing. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_00], > >>is SMART capable. Adding to "monitor" list. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > >>opened > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > >>found in smartd database. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > >>enabled SMART Attribute Autosave. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > >>enabled SMART Automatic Offline Testing. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_01], > >>is SMART capable. Adding to "monitor" list. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > >>opened > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > >>found in smartd database. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > >>enabled SMART Attribute Autosave. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > >>enabled SMART Automatic Offline Testing. > >>May 20 06:07:32 server smartd[1688]: Device: /dev/twe1 [3ware_disk_02], > >>is SMART capable. Adding to "monitor" list. > >>May 20 06:07:32 server smartd[1688]: Monitoring 8 ATA and 0 SCSI devices > >>May 20 06:07:34 server smartd[1690]: smartd has fork()ed into background > >>mode. New PID=1690. > >>May 20 06:07:34 server smartd[1690]: file /var/run/smartd.pid written > >>containing PID 1690 > >> > >> > >> > >>------------------------------------------------------- > >>This SF.Net email is sponsored by Oracle Space Sweepstakes > >>Want to be the first software developer in space? > >>Enter now for the Oracle Space Sweepstakes! > >>http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click > >>_______________________________________________ > >>Smartmontools-support mailing list > >>Sma...@li... > >>https://lists.sourceforge.net/lists/listinfo/smartmontools-support > >> > >> > >> > >> > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > |
From: Samuel F. <sf...@ra...> - 2005-05-20 17:38:01
|
Bruce Allen wrote: > Andreas, > > Interesting. I had thought that you HAD to use /dev/twe for the > 'escalade' cards (<=8000) and /dev/twa for the 'apache' cards (>=9000). On my 9500 controllers I get. "Smartctl open device: /dev/twe0 failed: No such file or director" Maybe 3ware changed something in the 2,6,11 kernel as I'm still running Suse 9.2. |
From: Andreas U. <un...@ne...> - 2005-05-20 17:50:37
|
I have a machine here with SuSE 9.2 but only a 3ware 6000 controller. But it works. Could you post a "cat /proc/devices"? Samuel Flory wrote: > Bruce Allen wrote: > >> Andreas, >> >> Interesting. I had thought that you HAD to use /dev/twe for the >> 'escalade' cards (<=8000) and /dev/twa for the 'apache' cards (>=9000). > > > On my 9500 controllers I get. > "Smartctl open device: /dev/twe0 failed: No such file or director" > > Maybe 3ware changed something in the 2,6,11 kernel as I'm still > running Suse 9.2. > |
From: Samuel F. <sf...@ra...> - 2005-05-20 17:54:24
|
Andreas Unterkircher wrote: > I have a machine here with SuSE 9.2 but only a 3ware 6000 controller. > But it works. > Could you post a "cat /proc/devices"? It shows a twa device, and no no twe device. (Which I'd expect on a 9500.) tiamat:/vol0/nfs/images # cat /proc/devices Character devices: 1 mem 2 pty 3 ttyp 4 /dev/vc/0 4 tty 4 ttyS 5 /dev/tty 5 /dev/console 5 /dev/ptmx 6 lp 7 vcs 9 st 10 misc 13 input 21 sg 29 fb 128 ptm 136 pts 180 usb 188 ttyUSB 253 ipmidev 254 twa Block devices: 1 ramdisk 3 ide0 7 loop 8 sd 9 md 11 sr 22 ide1 65 sd 66 sd 67 sd 68 sd 69 sd 70 sd 71 sd 128 sd 129 sd 130 sd 131 sd 132 sd 133 sd 134 sd 135 sd 253 device-mapper 254 mdp |
From: Bruce A. <ba...@gr...> - 2005-05-20 18:11:00
|
Could you please do 'lsmod'. Bruce On Fri, 20 May 2005, Samuel Flory wrote: > Andreas Unterkircher wrote: > > I have a machine here with SuSE 9.2 but only a 3ware 6000 controller. > > But it works. > > Could you post a "cat /proc/devices"? > > It shows a twa device, and no no twe device. (Which I'd expect on a > 9500.) > > tiamat:/vol0/nfs/images # cat /proc/devices > Character devices: > 1 mem > 2 pty > 3 ttyp > 4 /dev/vc/0 > 4 tty > 4 ttyS > 5 /dev/tty > 5 /dev/console > 5 /dev/ptmx > 6 lp > 7 vcs > 9 st > 10 misc > 13 input > 21 sg > 29 fb > 128 ptm > 136 pts > 180 usb > 188 ttyUSB > 253 ipmidev > 254 twa > > Block devices: > 1 ramdisk > 3 ide0 > 7 loop > 8 sd > 9 md > 11 sr > 22 ide1 > 65 sd > 66 sd > 67 sd > 68 sd > 69 sd > 70 sd > 71 sd > 128 sd > 129 sd > 130 sd > 131 sd > 132 sd > 133 sd > 134 sd > 135 sd > 253 device-mapper > 254 mdp > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > |
From: Samuel F. <sf...@ra...> - 2005-05-20 18:14:51
|
Bruce Allen wrote: > Could you please do 'lsmod'. I've got the 3w_9xxx loaded, and the 3w_xxxx isn't loaded. Module Size Used by nls_utf8 18432 0 ipmi_devintf 23812 0 ipmi_msghandler 67936 1 ipmi_devintf nfsd 129736 17 exportfs 22656 1 nfsd usbserial 45288 0 parport_pc 56384 1 lp 27272 0 parport 57032 2 parport_pc,lp nvram 26120 0 speedstep_lib 20740 0 freq_table 21248 0 thermal 34184 0 processor 43456 1 thermal fan 21636 0 button 24720 0 battery 27780 0 ac 22660 0 edd 26908 0 ipv6 321280 82 bond0 82536 0 evdev 25472 0 joydev 26048 0 sg 54816 0 st 55580 0 sr_mod 33444 0 ide_cd 56608 0 cdrom 54940 2 sr_mod,ide_cd e100 52608 0 mii 21504 1 e100 hw_random 21908 0 uhci_hcd 48784 0 raid5 39296 1 xor 31624 1 raid5 dm_mod 75264 0 e1000 101892 0 usbcore 132708 4 usbserial,uhci_hcd raid1 33920 3 reiserfs 277840 3 3w_9xxx 50564 16 sd_mod 34304 32 scsi_mod 133700 5 sg,st,sr_mod,3w_9xxx,sd_mod |
From: Bruce A. <ba...@gr...> - 2005-05-20 18:13:20
|
What about /dev/twe1, /dev/twe2, etc? Bruce On Fri, 20 May 2005, Samuel Flory wrote: > Bruce Allen wrote: > > Andreas, > > > > Interesting. I had thought that you HAD to use /dev/twe for the > > 'escalade' cards (<=8000) and /dev/twa for the 'apache' cards (>=9000). > > On my 9500 controllers I get. > "Smartctl open device: /dev/twe0 failed: No such file or director" > > Maybe 3ware changed something in the 2,6,11 kernel as I'm still > running Suse 9.2. > > > ------------------------------------------------------- > This SF.Net email is sponsored by Oracle Space Sweepstakes > Want to be the first software developer in space? > Enter now for the Oracle Space Sweepstakes! > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > |
From: Samuel F. <sf...@ra...> - 2005-05-20 18:28:50
|
Bruce Allen wrote: > What about /dev/twe1, /dev/twe2, etc? > None of them work, but as I said twa0 works just fine. The the twe character device is a 3w-xxxx driver only thing. 3w-xxxx.c: register_reboot_notifier(&tw_notifier); if ((twe_major = register_chrdev (0, "twe", &tw_fops)) < 0) { printk(KERN_WARNING "3w-xxxx: Unable to register \"twe\" character device, error = %d.\n", twe_major); } Where as 3x-9xxx doesn't create a twe character device. Instead it creates a twa device. 3w-9xxx.c: if ((twa_major = register_chrdev (0, "twa", &twa_fops)) < 0) TW_PRINTK(host, TW_DRIVER, 0x29, "Failed to register character device"); } This why I'm puzzled by anyone claiming to access a 9500 controller via twe. Looking at the 3w-xxxx driver code it doesn't even attempt to create the character device unless it detects a controller. |
From: Bruce A. <ba...@gr...> - 2005-05-20 18:33:46
|
> This why I'm puzzled by anyone claiming to access a 9500 controller > via twe. Looking at the 3w-xxxx driver code it doesn't even attempt to > create the character device unless it detects a controller. I agree. I am also puzzled. Bruce |
From: Andreas U. <un...@ne...> - 2005-05-20 19:25:46
|
Could it be some conflict with udev? SuSE 9.2 is running udevd I believe. Andreas Bruce Allen wrote: >> This why I'm puzzled by anyone claiming to access a 9500 controller >>via twe. Looking at the 3w-xxxx driver code it doesn't even attempt to >>create the character device unless it detects a controller. >> >> > >I agree. I am also puzzled. > >Bruce > > > >------------------------------------------------------- >This SF.Net email is sponsored by Oracle Space Sweepstakes >Want to be the first software developer in space? >Enter now for the Oracle Space Sweepstakes! >http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click >_______________________________________________ >Smartmontools-support mailing list >Sma...@li... >https://lists.sourceforge.net/lists/listinfo/smartmontools-support > > > |
From: Bruce A. <ba...@gr...> - 2005-05-20 21:08:37
|
> Could it be some conflict with udev? SuSE 9.2 is running udevd I believe. This could explain it. If this is the reason, I would gratefully accept a patch for smartmontools that fixes it (:-)! Cheers, Bruce |
From: Andreas U. <un...@ne...> - 2005-05-20 21:50:30
|
Ok. I had given it a short try now. After installing udev under a Debian SID, it mounts it's tmpfs over the existing /dev structure and creates the new device nodes only for the existing physical devices in the server - but no twe or twa devices. Then, after starting 3dm2, there are now 16 twe devices for my 3ware controller. Also smartd is creating these devices if I made it the first step before starting 3dm2. Looks good from here. Andreas Bruce Allen wrote: >>Could it be some conflict with udev? SuSE 9.2 is running udevd I believe. >> >> > >This could explain it. If this is the reason, I would gratefully accept a >patch for smartmontools that fixes it (:-)! > >Cheers, > Bruce > > > |
From: Bruce A. <ba...@gr...> - 2005-05-21 02:37:51
|
> Ok. I had given it a short try now. After installing udev under a Debian > SID, it mounts it's tmpfs over the > existing /dev structure and creates the new device nodes only for the > existing physical devices in the server - > but no twe or twa devices. > > Then, after starting 3dm2, there are now 16 twe devices for my 3ware > controller. Also smartd is creating > these devices if I made it the first step before starting 3dm2. Looks > good from here. Andreas, do I understand you correctly, that udev is NOT the problem? Cheers, > Bruce Allen wrote: > > >>Could it be some conflict with udev? SuSE 9.2 is running udevd I believe. > >This could explain it. If this is the reason, I would gratefully accept a > >patch for smartmontools that fixes it (:-)! > > > >Cheers, > > Bruce > > > > > > > > |
From: Andreas U. <un...@ne...> - 2005-05-21 06:45:34
|
Bruce Allen wrote: >Andreas, do I understand you correctly, that udev is NOT the problem? > >Cheers, > > Yes - from my point of view I can say, that I havn't any problem with udev, because smartd or 3dm2 create the necessary devices as the should. No problem with the interaction of udev. Cya, Andreas |
From: Volker K. <lis...@pa...> - 2005-05-20 22:21:40
|
> Could it be some conflict with udev? SuSE 9.2 is running udevd I believe. Yes it does: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 2432 0.0 0.0 1360 256 ? S<s May13 0:00 udevd But I don't see anything mounted over /dev in /proc/mounts: > t /proc/mounts rootfs / rootfs rw 0 0 /dev/root / reiserfs rw 0 0 proc /proc proc rw,nodiratime 0 0 sysfs /sys sysfs rw 0 0 devpts /dev/pts devpts rw 0 0 none /lib/bootchart/mnt tmpfs rw 0 0 tmpfs /dev/shm tmpfs rw 0 0 usbfs /proc/bus/usb usbfs rw 0 0 [remaining data partitions omitted] Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. |
From: Andreas U. <un...@ne...> - 2005-05-21 06:54:02
|
Volker Kuhlmann wrote: >>Could it be some conflict with udev? SuSE 9.2 is running udevd I believe. >> >> > >Yes it does: > >USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND >root 2432 0.0 0.0 1360 256 ? S<s May13 0:00 udevd > >But I don't see anything mounted over /dev in /proc/mounts: > > > I also see no mounts over /dev with SuSE 9.2. But all the files in /dev have a new ctime (bootup). But with Debian I see a tmpfs: server:~# cat /proc/mounts .... none /dev tmpfs rw 0 0 devpts /dev/pts devpts rw 0 0 tmpfs /dev/shm tmpfs rw 0 0 .... Probably only Debian is doing this to speedup the initial creation time of the devices nodes during bootup. SuSE may leave it in normal root fs. Could also be an advantage, if udev isn't coming up correctly during boot and you still have the device nodes from the last time. Andreas |
From: Volker K. <lis...@pa...> - 2005-05-21 10:15:44
|
> I also see no mounts over /dev with SuSE 9.2. But all the files in /dev > have a new ctime (bootup). They're all (re-)created at boot time. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. |