Solaris device node, and NetBSD info.

Took me a while to work out what device path to use under Solaris, but this 
appears to work:

smartmontools-5.26# smartctl -a "/devices/pci <at> 1,0/pci15d9,9005 <at> 3/sd <at> 1,0:a"
smartctl version 5.26 Copyright (C) 2002-3 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Standard Inquiry failed [Inappropriate ioctl for device]
A mandatory SMART command failed: exiting. To continue, add one or more '-T 
permissive' options.
ddnsweb03:~/smartmontools-5.26# smartctl -a 
/devices/pci\ <at> 1,0/pci15d9,9005\ <at> 3/sd\ <at> 1,0\:a,raw
smartctl version 5.26 Copyright (C) 2002-3 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Device: MAXTOR   ATLAS10K4_36SCA  Version: DFV0
Serial number: B2G24X6M
Device type: disk
Transport protocol: Parallel SCSI (SPI-4)
Local Time is: Mon Dec  1 12:26:15 2003 JST
Device supports SMART and is Enabled
Temperature Warning Enabled
SMART Health Status: OK

Current Drive Temperature:     26 C
Manufactured in week 35 of year 2002
Current start stop count:      56 times
Recommended maximum start stop count:  4294967295 times

Re: Solaris device node, and NetBSD info.

Hi Jorgen,

> Took me a while to work out what device path to use under Solaris

My apologies. The solaris support is new, and the person who added it is
not able to act as a developer.  And he didn't update the documentation.
The examples are also non-solaris:

After reading the code a bit, I've added the following:

       On  startup,  in  the  absence  of  the configuration file
       /etc/smartd.conf, the smartd daemon first  scans  for  all
       devices  that support SMART.  The scanning is done as fol-
       lows:

       LINUX:   Using "/dev/hd[a-t]"  for  IDE/ATA  devices,  and
                "/dev/sd[a-z]" for SCSI devices under Linux.

       FREEBSD: Exmaine  all  entries "/dev/ad[0-9]+" for IDE/ATA
                devices and "/dev/da[0-9]+" SCSI devices.

       SOLARIS: Examine all entries "/dev/rdsk/c?t?d?s?" for SCSI
                disk  devices,  and entries "/dev/rmt/*" for SCSI
                tape devices.

This should at least be a hint!  Try /dev/rdsk/c0t0d0s0 for a start.

(By the way, I'm still looking for a solaris maintainer/developer/tester.  
If you're interested, please send me a non-public note).

Re: Patch for Hitachi DK23xx drives

There's a couple of odd things in the output.  Are you using an x86
machine or something that's big-endian?

Bruce

On Sun, 30 Nov 2003, Serguei Miridonov wrote:

> Hi,
> 
> First of all, thank you for your great program. I would like 
> to submit a patch which I had to apply to make the package 
> to work with my Hitachi DK23DA-30 drive. 
> 
> Please, note, that I have just made the options for already 
> included support for DK23EA-30 working for entire series of 
> Hitachi DK23xx drives. Of course, I'm not sure that it is 
> right and it will work with all these drives with any 
> firmware... So, please, since you have more experience, 
> consider this patch as experimental.
> 
> The patch and the output from my drive are included as 
> attachmets.
> 
> Thank you and best regards.
> Serguei.
> 

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it

Re: Patch for Hitachi DK23xx drives

> On Sunday 30 November 2003 20:38, Bruce Allen wrote:
> >  There's a couple of odd things in the output.  Are you
> > using an x86 machine or something that's big-endian?
> 
> This is Compaq Presario 900Z with Athlon 2000+, so this is 
> quite normal x86...

It's OK -- Hitachi has their maximum/minimum temperature reversed in their
SMART data.  I don't think it matters much...

Bruce

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

Re: Solaris device node, and NetBSD info. (fwd)

For the record, I'm copying parts of this to the mailing list.

> >        SOLARIS: Examine all entries "/dev/rdsk/c?t?d?s?" for SCSI
> >                 disk  devices,  and entries "/dev/rmt/*" for SCSI
> >                 tape devices.
> 
> I thought so at first, but they don't work.
> 
> Smartctl open device: /dev/dsk/c0t0d0s0 failed: Device busy
> Smartctl open device: /dev/rdsk/c0t0d0s0 failed: Device busy
> Smartctl open device: /dev/dsk/c0t0d0p0 failed: Device busy
> Smartctl open device: /dev/rdsk/c0t0d0p2 failed: Device busy

> Crap! :) Thats the damned IDE cd-rom thats first. Ok I see my foobar here :)

> ddnsweb04:~# smartctl -a /dev/rdsk/c1t0d0s0
> Device: MAXTOR   ATLAS10K4_36SCA  Version: DFV0
> 
> Sigh :) Ok sorry for the spam :)

No problem -- glad it does work more or less as advertised.

By the way, there is (not yet) any 'official' ATA support for solaris.  
You can find an 'unofficial' patched version of the smartmontools 5.1-18
release here: http://card-captor.dyndns.org/pub/solaris-smart/ We're
trying to get this support into the smartmontools source but it's being
held up as we try and sort out some licensing issues.

> >>Anyone know how Western Digital "WDC WD2500JB-00EVA0" temperature raw
> >>values work? I get values around 104-114. Couldn't be celcius I hope,

Re: Patch for Hitachi DK23xx drives

> Well, that may be OK but after I ran a couple of tests with 
> smartctl and badblocks utility, things changed dramatically 
> and this troubles me... Seems I need to ask for another 
> drive...

The drive itself may be "OK" BUT you have a number of unreadable sectors:

197 Current_Pending_Sector  0x0032   083   081   000    Old_age   Always
-       17
198 Offline_Uncorrectable   0x0010   081   081   000    Old_age   Offline
-       19

You can run the IBM/Hitachi drive fitness utility to force these to
reallocate, but data will be lost unless the drive suceeeds in reading
those sectors.

Bruce

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

Re: Patch for Hitachi DK23xx drives

On Sunday 30 November 2003 20:38, Bruce Allen wrote:
>  There's a couple of odd things in the output.  Are you
> using an x86 machine or something that's big-endian?

This is Compaq Presario 900Z with Athlon 2000+, so this is 
quite normal x86...

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

Re: Patch for Hitachi DK23xx drives

On Sunday 30 November 2003 22:35, Bruce Allen wrote:
>  > On Sunday 30 November 2003 20:38, Bruce Allen wrote:
>  > >  There's a couple of odd things in the output.  Are
>  > > you using an x86 machine or something that's
>  > > big-endian?
>  >
>  > This is Compaq Presario 900Z with Athlon 2000+, so
>  > this is quite normal x86...
>
>  It's OK -- Hitachi has their maximum/minimum temperature
> reversed in their SMART data.  I don't think it matters
> much...

Well, that may be OK but after I ran a couple of tests with 
smartctl and badblocks utility, things changed dramatically 
and this troubles me... Seems I need to ask for another 
drive...

smartctl version 5.26 Copyright (C) 2002-3 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     HITACHI_DK23DA-30
Serial Number:    14TJCV
Firmware Version: 00J1A0A3
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   5
ATA Standard is:  ATA/ATAPI-5 T13 1321D revision 3

Re: Solaris device node, and NetBSD info. (fwd)

Hi all,

> For the record, I'm copying parts of this to the mailing list.
> 
> > >        SOLARIS: Examine all entries "/dev/rdsk/c?t?d?s?" for SCSI
> > >                 disk  devices,  and entries "/dev/rmt/*" for SCSI
> > >                 tape devices.
> > 
> > I thought so at first, but they don't work.
> > 
> > Smartctl open device: /dev/dsk/c0t0d0s0 failed: Device busy
> > Smartctl open device: /dev/rdsk/c0t0d0s0 failed: Device busy
> > Smartctl open device: /dev/dsk/c0t0d0p0 failed: Device busy
> > Smartctl open device: /dev/rdsk/c0t0d0p2 failed: Device busy
> 
> > Crap! :) Thats the damned IDE cd-rom thats first. Ok I see my foobar here :)
> 
> > ddnsweb04:~# smartctl -a /dev/rdsk/c1t0d0s0
> > Device: MAXTOR   ATLAS10K4_36SCA  Version: DFV0
> > 
> > Sigh :) Ok sorry for the spam :)
> 
> No problem -- glad it does work more or less as advertised.

As far as I experimented, this naming rule is applicable to ATA hard
drive behind ATA(PI)-to-USB converter.  It is recognized as SCSI
drive, but smartmontools reports that it has no SMART functionality.
Actually drive has SMART, so the converter is unable to handle SMART
correctly.

Re: Maxtor 15G disk age

Hi Volker,

You've rediscovered a know Maxtor firmware bug. See the FAQ section of the
smartmontools web page, where it says:

# The power-on timer (Attribute 9 raw value) on my Maxtor disk acts
strange.

There are three related problems with Maxtor's SMART firmware:

1 - On some disks from 2001/2002, the raw value of Attribute 9 (Power On
Time) is supposed to be minutes. But it advances at an unpredictable rate,
always more slowly than one count per minute. One (unconfirmed) theory is
that when the disk is in idle mode, the counter stops advancing. This is
only supposed to happen in standby mode.

2 - In Maxtor disks that use the raw value of Attribute 9 as a minutes
counter, only two bytes (of the six available) are used to store the raw
value. So it resets to zero once every 65536=2^16 minutes, or about once
every 1092 hours. This is fixed in all Maxtor disks manufactured after
July 2003, where the raw value was extended to four bytes.

3 - In Maxtor disks that use the raw value of Attribute 9 as a minutes
counter, the hour time-stamps in the self-test and ATA error logs are
calculated by right shifting 6 bits. This is equivalent to dividing by 64
rather than by 60. As a result, the hour time stamps in these logs advance
7% more slowly than they should. Thus, if you do self-tests once per week
at the same time, instead of the time-stamps being 168 hours apart, they
are 157 hours apart. This is also fixed in all Maxtor disks manufactured
after July 2003.