S.M.A.R.T. Monitoring Tools

Shaya Potter wrote:
> according to the documentation, smartctl should work with the newest
> version of 3ware's drivers.  However, it doesn't seem to play nice
> with my old 7000 series or my 9550SX-8.  In both cases, when I try to
> do 
> smartctl -a /dev/hdb,# or smartctl -a /dev/hdc,# it returns an error 
> Smartctl open device: /dev/hdc,0 failed: Function not implemented 
> as opposed to
> 
> smartctl -a /dev/hdd where it says "Cannot open device...."
> 
> how does one get it to work?
> 

What is the version of the 3ware 9000 Windows driver (3wareDrv.sys) ?

smartctl 5.37 has been tested on a 9500S-8 with 3wareDrv.sys 3.00.02.070
(from 9.4.0 driver package) and 3.00.02.090 (9.4.1).
This should also work with a 95XX Series controller, but I don't have
access to such controller for testing.
(The info about SMART support in the windows driver never
made it into the release notes or KB.)

Please send output from "smartctl -r ioctl,2 -i /dev/hdX,N" for further
diagnostics.


AFIAK, 7000 and 8000 series controllers do not work with the 9000 series
driver, therefore there is no native SMART support for these and likely
never will be. But if tw_cli.exe is able to output the hex dump of SMART
data for these controllers, you may use smartctl with the /dev/tw_cli
pseudo device to convert this output into a more reasonable form:

smartctl -i -c -A /dev/tw_cli/c0/p1

with tw_cli.exe in PATH. Or use /dev/tw_cli/{stdin,clip} to read tw_cli
or 3DM output from stdin or clipboard.

Cheers,

Christian

Re: [smartmontools-support] 3ware controller under windows? From: Shaya Potter <spotter@cs...> - 2007-07-10 14:04 Christian.Franke@... wrote: > Shaya Potter wrote: >> according to the documentation, smartctl should work with the newest >> version of 3ware's drivers. However, it doesn't seem to play nice >> with my old 7000 series or my 9550SX-8. In both cases, when I try to >> do >> smartctl -a /dev/hdb,# or smartctl -a /dev/hdc,# it returns an error >> Smartctl open device: /dev/hdc,0 failed: Function not implemented >> as opposed to >> >> smartctl -a /dev/hdd where it says "Cannot open device...." >> >> how does one get it to work? >> > > What is the version of the 3ware 9000 Windows driver (3wareDrv.sys) ? according to device manager it's dated 12/4/2006 and is version 3.0.2.90 > smartctl 5.37 has been tested on a 9500S-8 with 3wareDrv.sys 3.00.02.070 > (from 9.4.0 driver package) and 3.00.02.090 (9.4.1). > This should also work with a 95XX Series controller, but I don't have > access to such controller for testing. > (The info about SMART support in the windows driver never > made it into the release notes or KB.) > > Please send output from "smartctl -r ioctl,2 -i /dev/hdX,N" for further > diagnostics. C:\Documents and Settings\spotter>smartctl -r ioctl,2 -i /dev/hdc,0 smartctl version 5.37 [i686-mingw32-2003-sp2] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ \\.\PhysicalDrive2: successfully opened SMART_GET_VERSION failed, Error=1 To continue, add one or more '-T permissive' options. Smartctl open device: /dev/hdc,0 failed: Function not implemented C:\Documents and Settings\spotter>smartctl -r ioctl,2 -i /dev/hdc,0 smartctl version 5.37 [i686-mingw32-2003-sp2] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ \\.\PhysicalDrive2: successfully opened SMART_GET_VERSION failed, Error=1 To continue, add one or more '-T permissive' options. Smartctl open device: /dev/hdc,0 failed: Function not implemented > AFIAK, 7000 and 8000 series controllers do not work with the 9000 series > driver, therefore there is no native SMART support for these and likely > never will be. But if tw_cli.exe is able to output the hex dump of SMART > data for these controllers, you may use smartctl with the /dev/tw_cli > pseudo device to convert this output into a more reasonable form: > > smartctl -i -c -A /dev/tw_cli/c0/p1 > > with tw_cli.exe in PATH. Or use /dev/tw_cli/{stdin,clip} to read tw_cli > or 3DM output from stdin or clipboard. this works for both devices.

Re: [smartmontools-support] 3ware controller under windows? From: Christian Franke <Christian.Franke@t-...> - 2007-07-10 18:56 Shaya Potter wrote: > >> ... >> What is the version of the 3ware 9000 Windows driver (3wareDrv.sys) ? > > according to device manager it's dated 12/4/2006 and is version 3.0.2.90 > Same version works for my 9500S on XP SP2. >> ... >> Please send output from "smartctl -r ioctl,2 -i /dev/hdX,N" for further >> diagnostics. > > C:\Documents and Settings\spotter>smartctl -r ioctl,2 -i /dev/hdc,0 > smartctl version 5.37 [i686-mingw32-2003-sp2] Copyright (C) 2002-6 > Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > \\.\PhysicalDrive2: successfully opened > SMART_GET_VERSION failed, Error=1 > To continue, add one or more '-T permissive' options. > Smartctl open device: /dev/hdc,0 failed: Function not implemented > > Is this Win2003 x64? AFAIK, the 64bit driver has no (32bit variant of the) SMART ioctl. (You may want to open a 3ware support ticket to request this :-) Correct drive number? Try SCSI variant to get SCSI inquiry result: $ smartctl -i /dev/sdc ... Device: AMCC 9550SX- ..... Version: ... please try changing device to /dev/hdX,N or use smartd to scan for devices: $ echo DEVICESCAN | smartd -c - -q onecheck ... Device: /dev/hdc,1, opened Device: /dev/hdc,1, found in smartd database. Device: /dev/hdc,1, is SMART capable. Adding to "monitor" list. ... >> AFIAK, 7000 and 8000 series controllers do not work with the 9000 series >> driver, therefore there is no native SMART support for these and likely >> never will be. But if tw_cli.exe is able to output the hex dump of SMART >> data for these controllers, you may use smartctl with the /dev/tw_cli >> pseudo device to convert this output into a more reasonable form: >> >> smartctl -i -c -A /dev/tw_cli/c0/p1 >> >> with tw_cli.exe in PATH. Or use /dev/tw_cli/{stdin,clip} to read tw_cli >> or 3DM output from stdin or clipboard. > > this works for both devices. > The device name /dev/tw_cli/cX/pY may also be specified in smartd.conf. This provides at least temperature and other attribute monitoring. Cheers, Christian

Re: [smartmontools-support] 3ware controller under windows? From: Shaya Potter <spotter@cs...> - 2007-07-10 19:20 Christian Franke wrote: > Shaya Potter wrote: >> >>> ... >>> What is the version of the 3ware 9000 Windows driver (3wareDrv.sys) ? >> >> according to device manager it's dated 12/4/2006 and is version 3.0.2.90 >> > > Same version works for my 9500S on XP SP2. > > >>> ... >>> Please send output from "smartctl -r ioctl,2 -i /dev/hdX,N" for further >>> diagnostics. >> >> C:\Documents and Settings\spotter>smartctl -r ioctl,2 -i /dev/hdc,0 >> smartctl version 5.37 [i686-mingw32-2003-sp2] Copyright (C) 2002-6 >> Bruce Allen >> Home page is http://smartmontools.sourceforge.net/ >> >> \\.\PhysicalDrive2: successfully opened >> SMART_GET_VERSION failed, Error=1 >> To continue, add one or more '-T permissive' options. >> Smartctl open device: /dev/hdc,0 failed: Function not implemented >> >> > > Is this Win2003 x64? AFAIK, the 64bit driver has no (32bit variant of > the) SMART ioctl. > (You may want to open a 3ware support ticket to request this :-) no, it's 32 bit (smp athlon mp) Server 2003 Enterprise (overkill for my needs, but whats available via MSDN-AA). > Correct drive number? Try SCSI variant to get SCSI inquiry result: > > $ smartctl -i /dev/sdc > ... > Device: AMCC 9550SX- ..... Version: ... > please try changing device to /dev/hdX,N > > > or use smartd to scan for devices: > > $ echo DEVICESCAN | smartd -c - -q onecheck > ... > Device: /dev/hdc,1, opened > Device: /dev/hdc,1, found in smartd database. > Device: /dev/hdc,1, is SMART capable. Adding to "monitor" list. > ... not at the machine now, so can't test.

8 messages have been excluded from this view by a project administrator.