Re: S.M.A.R.T. messages - what do they mean
On Thu, Sep 25, 2003 at 03:07:13PM +0200, Nicos Gollan wrote:
> On Wednesday 24 September 2003 22:42, René Seindal wrote:
> > I just got these messages from smartmontools on my laptop. I checked
> > the logs because the disk make a weird sound.
> >
> > Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
>
> This one might actually be harmless if you always got it and get it a lot. It
> probably just means that your drive doesn't provide that information.
Here's a series of the messages. I just noticed that the
Load_Cycle_Count messages come with 30 minutes intervals, so it might be
a lack of understanding between the drive and smartd. The Spin_Up_Time
messages are explainable, I think. Excessive variation in Spin_Up_Time
can be an indacator of a failing spindle motor, but the value is
consistently between 110-130, and usually around 115-120, so I take that
to be stable.
The drive, BTW, is
hda: IBM-DJSA-220, ATA DISK drive
hda: 39070080 sectors (20004 MB) w/1874KiB Cache, CHS=38760/16/63, UDMA(33)
The messages are:
Sep 24 22:55:15: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 24 23:25:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 24 23:55:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 00:25:15: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 00:55:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 01:25:15: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 01:55:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 02:25:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 02:55:16: Device: /dev/hda, SMART Prefailure Attribute: 3 Spin_Up_Time changed from 121 to 119
Sep 25 02:55:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 03:25:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 03:55:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 04:25:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 04:55:17: Device: /dev/hda, SMART Prefailure Attribute: 3 Spin_Up_Time changed from 119 to 115
Sep 25 04:55:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 05:25:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 05:55:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 06:25:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 06:55:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 07:25:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 07:55:19: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 08:25:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 08:55:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 09:25:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 09:55:15: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 10:25:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 10:55:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 11:25:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 11:55:17: Device: /dev/hda, SMART Prefailure Attribute: 3 Spin_Up_Time changed from 115 to 123
Sep 25 11:55:17: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 12:25:15: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 12:55:15: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
Sep 25 13:25:16: Device: /dev/hda, Failed SMART usage Attribute: 193 Load_Cycle_Count.
> > Device: /dev/hda, SMART Usage Attribute: 191 G-Sense_Error_Rate changed
> > from 99 to 98
>
> This one might be more serious. But from what I've seen at
> http://yusoft.kulichki.com/russian/doc/smartdoc.htm
> (translations anyone?), it has to do with G-forces (as in acceleration)
> exerted on the drive, and if you didn't drop it it shouldn't be of much
> importance.
I had it on my lap, and might have moved it a bit briskly. It did make
a weird sound, but there have been no other errors since.
Anyway, I'm quite a bit calmer now, but I will keep an eye on the drive
in the time to come.
As for backup, it is a development machine I use at home, and everything
I have there is mirrored on other computers or in CVS. I not too afraid
of losing data, rather about losing time.
>
> > What do these messages mean and do I need to buy a new harddisk?
>
> In any case, have a look at smartctl and its documentation. Get the logged
> information and see if any of the parameters is out of bounds. If so,
> double-check that your drive is not transmitting the data backwards (some
> Samsung drives do which lead to an error count >300,000 on one of my drives).
> Many manufacturers also offer proprietary tools that work from a bootfloppy
> and know what the drive is talking about.
>
> There's some more information at
> http://www.siguardian.com/products/siguardian/on_line_help/
> s_m_a_r_t_attribute_meaning.html
> but it's rather incomplete due to the industry's usual "don't tell" attitude.
>
> Most important: DON'T PANIC. There's a strong tendency on this list to send
> people shopping as soon as there's any message in the logs concerning
> harddrives; take those with a large grain of salt unless a proper explanation
> is offered.
>
--
René Seindal (rene@seindal.dk) http://sights.seindal.dk/
Reply to: