|
[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[NMLUG] smartd errors??
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tim Emerick wrote:
> Has anybody ever experienced smartd errors? If so, what did you do?
>
> I have a new 200GB hard drive that seems to be throwing errors. Probably
> under warranty. I don't understand them though. Two lines keep showing up
> in /var/log/syslog. I've put the pertinent syslog lines and the smartctl
> output at the end of this email.
>
> Any help would be appreciated.
>
> Thanks!
>
> Tim Emerick
>
> debian:/var/log# tail syslog | grep smartd
> Apr 7 01:00:14 localhost smartd[1744]: Device: /dev/hde, 131 Currently
> unreadable (pending) sectors
> Apr 7 01:00:14 localhost smartd[1744]: Device: /dev/hde, 133 Offline
> uncorrectable sectors
>
> And a smartctl returns this:
>
> debian:/var/log# smartctl -l error /dev/hde
> smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
> === START OF READ SMART DATA SECTION ===
> SMART Error Log Version: 1
> Warning: ATA error count 94 inconsistent with error log pointer 5
>
> ATA Error Count: 94 (device log contains only the most recent five errors)
> CR = Command Register [HEX]
> FR = Features Register [HEX]
> SC = Sector Count Register [HEX]
> SN = Sector Number Register [HEX]
> CL = Cylinder Low Register [HEX]
> CH = Cylinder High Register [HEX]
> DH = Device/Head Register [HEX]
> DC = Device Command Register [HEX]
> ER = Error register [HEX]
> ST = Status register [HEX]
> Powered_Up_Time is measured from power on, and printed as
> DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
> SS=sec, and sss=millisec. It "wraps" after 49.710 days.
>
> Error 94 occurred at disk power-on lifetime: 969 hours (40 days + 9 hours)
> When the command that caused the error occurred, the device was in an
> unknown state.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 59 80 af 7d 78 e0 Error: UNC at LBA = 0x00787daf = 7896495
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 24 00 80 af 7d 78 e0 08 1d+08:08:50.736 READ SECTOR(S) EXT
> 24 00 08 a7 7d 78 e0 08 1d+08:08:49.952 READ SECTOR(S) EXT
> 24 00 10 9f 7d 78 e0 08 1d+08:08:49.088 READ SECTOR(S) EXT
> 24 00 18 97 7d 78 e0 08 1d+08:08:48.304 READ SECTOR(S) EXT
> 24 00 80 2f 7d 78 e0 08 1d+08:08:45.712 READ SECTOR(S) EXT
>
> Error 93 occurred at disk power-on lifetime: 969 hours (40 days + 9 hours)
> When the command that caused the error occurred, the device was in an
> unknown state.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 59 08 a7 7d 78 e0 Error: UNC at LBA = 0x00787da7 = 7896487
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 24 00 08 a7 7d 78 e0 08 1d+08:08:49.952 READ SECTOR(S) EXT
> 24 00 10 9f 7d 78 e0 08 1d+08:08:49.088 READ SECTOR(S) EXT
> 24 00 18 97 7d 78 e0 08 1d+08:08:48.304 READ SECTOR(S) EXT
> 24 00 80 2f 7d 78 e0 08 1d+08:08:45.712 READ SECTOR(S) EXT
> 24 00 80 af 7c 78 e0 08 1d+08:08:45.696 READ SECTOR(S) EXT
>
> Error 92 occurred at disk power-on lifetime: 969 hours (40 days + 9 hours)
> When the command that caused the error occurred, the device was in an
> unknown state.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 59 10 9f 7d 78 e0 Error: UNC at LBA = 0x00787d9f = 7896479
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 24 00 10 9f 7d 78 e0 08 1d+08:08:49.088 READ SECTOR(S) EXT
> 24 00 18 97 7d 78 e0 08 1d+08:08:48.304 READ SECTOR(S) EXT
> 24 00 80 2f 7d 78 e0 08 1d+08:08:45.712 READ SECTOR(S) EXT
> 24 00 80 af 7c 78 e0 08 1d+08:08:45.696 READ SECTOR(S) EXT
> 24 00 80 2f 7c 78 e0 08 1d+08:08:45.680 READ SECTOR(S) EXT
>
> Error 91 occurred at disk power-on lifetime: 969 hours (40 days + 9 hours)
> When the command that caused the error occurred, the device was in an
> unknown state.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 59 18 97 7d 78 e0 Error: UNC at LBA = 0x00787d97 = 7896471
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 24 00 18 97 7d 78 e0 08 1d+08:08:48.304 READ SECTOR(S) EXT
> 24 00 80 2f 7d 78 e0 08 1d+08:08:45.712 READ SECTOR(S) EXT
> 24 00 80 af 7c 78 e0 08 1d+08:08:45.696 READ SECTOR(S) EXT
> 24 00 80 2f 7c 78 e0 08 1d+08:08:45.680 READ SECTOR(S) EXT
> 24 00 80 af 7b 78 e0 08 1d+08:08:45.088 READ SECTOR(S) EXT
>
> Error 90 occurred at disk power-on lifetime: 969 hours (40 days + 9 hours)
> When the command that caused the error occurred, the device was in an
> unknown state.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 59 19 95 7d 78 e0 Error: UNC at LBA = 0x00787d95 = 7896469
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 24 00 80 2f 7d 78 e0 08 1d+08:08:45.712 READ SECTOR(S) EXT
> 24 00 80 af 7c 78 e0 08 1d+08:08:45.696 READ SECTOR(S) EXT
> 24 00 80 2f 7c 78 e0 08 1d+08:08:45.680 READ SECTOR(S) EXT
> 24 00 80 af 7b 78 e0 08 1d+08:08:45.088 READ SECTOR(S) EXT
> 24 00 80 2f 7b 78 e0 08 1d+08:08:45.072 READ SECTOR(S) EXT
>
> debian:/var/log#
>
>
>
>
> __________________________________
> Yahoo! Messenger
> Show us what our next emoticon should look like. Join the fun.
> http://www.advision.webevents.yahoo.com/emoticontest
> _______________________________________________
> NMLUG mailing list
> NMLUG@nmlug.org
> http://www.nmlug.org/mailman/listinfo/nmlug
I've used smartd on several boxes for quite a while. Sometime last July
my desktop rig emailed me with some similar errors (unreadable sectors).
I had another drive laying around and I immediately made a backup of my
system, and am I glad I did...My HD failed about 2 days later. It was
under warranty, too. I RMA'd it and got another one and it has worked
fine since.
smartd can be pretty verbose. It'll constantly mention temperature
changes in the logs, but you don't have to worry about those. If you
set smartd up to email you, then usually by default it only emails you
for the really critical stuff. logwatch on the other hand might send
you hoards of smartd lines, most of which can be ignored.
The smartctl lines show that you had a bunch of errors in a short
timeframe. Since the smart stuff only stores the last x errors (usually
5), you don't have much of a history to go by. However, when you get a
bunch of errors like you did (all at power on lifetime 40days 9hours),
that's not commonly a sign of health. ;-)
I'd advise a full backup just in case...It can't hurt and if that drive
dies, then you've got a backup. Be prepared for that drive to fail.
Set up something to monitor it and if/when it dies, have it page you or
text your cell phone or something. ;-)
- -Dan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCVqhanURHNoE9YE4RAoCqAJ466DUdo7kngIl+jr/AaE86SdwYTQCglv/6
JAiF0iVgWZdIYJ1vzY+Luo4=
=r0jf
-----END PGP SIGNATURE-----
|
|
