FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 03-08-2009, 09:11 AM
randall
 
Default smart

hi all,

my first mail to this list so apologies if this has been discussed recently.

i have a raid 10 array and 1 of the disks is acting up according to
SMART and i'm not sure how to interpret the logs and if i should ignore,
repair or replace.


smartd has been sending me several mails like this, they always come in
pairs.
(the dates mentioned in the mails are sometimes match the date of
sending and sometimes are a week or month off, but this might be another
problem, not sure. i think however it started after a power failure)


The following warning/error was logged by the smartd daemon:
Device: /dev/sde, 1 Currently unreadable (pending) sectors

AND

The following warning/error was logged by the smartd daemon:
Device: /dev/sde, 1 Offline uncorrectable sectors


smartctl --all /dev/sde
gives me the following, i've been trying to google this but some sources
say replace the disk at once or don't wory, its harmless. Anybody can
shed some light?



smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8
Bruce Allen

Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11
Device Model: ST3500320AS
Serial Number: 5QM056TH
Firmware Version: SD04
User Capacity: 500,107,862,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Sun Mar 8 11:00:53 2009 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 113) The previous self-test
completed having

the read element of the test failed.
Total time to complete Offline
data collection: ( 634) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 106) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x003b) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail
Always - 132023209
3 Spin_Up_Time 0x0003 093 092 000 Pre-fail
Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age
Always - 159
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
Always - 35
7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail
Always - 21613621419
9 Power_On_Hours 0x0032 089 089 000 Old_age
Always - 9858
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 100 037 020 Old_age
Always - 159
184 Unknown_Attribute 0x0032 100 100 099 Old_age
Always - 0
187 Reported_Uncorrect 0x0032 082 082 000 Old_age
Always - 18
188 Unknown_Attribute 0x0032 100 098 000 Old_age
Always - 4295032838
189 High_Fly_Writes 0x003a 001 001 000 Old_age
Always - 344
190 Airflow_Temperature_Cel 0x0022 071 048 045 Old_age
Always - 29 (Lifetime Min/Max 27/31)
194 Temperature_Celsius 0x0022 029 052 000 Old_age
Always - 29 (0 21 0 0)
195 Hardware_ECC_Recovered 0x001a 028 021 000 Old_age
Always - 132023209
197 Current_Pending_Sector 0x0012 100 100 000 Old_age
Always - 1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
Offline - 1
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age
Always - 0


SMART Error Log Version: 1
ATA Error Count: 18 (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 18 occurred at disk power-on lifetime: 9008 hours (375 days + 8 hours)
When the command that caused the error occurred, the device was active
or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 4b 10 95 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 9f 0e 95 40 00 17d+17:02:58.471 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:58.471 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 17d+17:02:58.348 READ LOG EXT
60 00 80 9f 0e 95 40 00 17d+17:02:56.547 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:56.546 IDENTIFY DEVICE

Error 17 occurred at disk power-on lifetime: 9008 hours (375 days + 8 hours)
When the command that caused the error occurred, the device was active
or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 4b 10 95 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 9f 0e 95 40 00 17d+17:02:56.547 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:56.546 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 17d+17:02:56.441 READ LOG EXT
60 00 80 9f 0e 95 40 00 17d+17:02:54.640 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:54.639 IDENTIFY DEVICE

Error 16 occurred at disk power-on lifetime: 9008 hours (375 days + 8 hours)
When the command that caused the error occurred, the device was active
or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 4b 10 95 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 9f 0e 95 40 00 17d+17:02:54.640 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:54.639 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 17d+17:02:54.534 READ LOG EXT
60 00 80 9f 0e 95 40 00 17d+17:02:52.707 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:52.707 IDENTIFY DEVICE

Error 15 occurred at disk power-on lifetime: 9008 hours (375 days + 8 hours)
When the command that caused the error occurred, the device was active
or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 4b 10 95 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 9f 0e 95 40 00 17d+17:02:52.707 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:52.707 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 17d+17:02:52.585 READ LOG EXT
60 00 80 9f 0e 95 40 00 17d+17:02:50.792 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:50.791 IDENTIFY DEVICE

Error 14 occurred at disk power-on lifetime: 9008 hours (375 days + 8 hours)
When the command that caused the error occurred, the device was active
or idle.


After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 4b 10 95 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 80 9f 0e 95 40 00 17d+17:02:50.792 READ FPDMA QUEUED
ec 00 00 00 00 00 a0 00 17d+17:02:50.791 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 17d+17:02:50.677 READ LOG EXT
60 00 80 9f 0e 95 40 00 17d+17:02:48.845 READ FPDMA QUEUED
60 00 00 9f 0a 95 40 00 17d+17:02:48.845 READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 10%
9849 917923767
# 2 Extended offline Completed without error 00%
9685 -
# 3 Extended offline Completed without error 00%
9594 -
# 4 Extended offline Completed: read failure 90%
9512 9769035
# 5 Extended offline Completed: read failure 90%
9344 9769035
# 6 Extended offline Completed: read failure 90%
9176 9769035
# 7 Extended offline Completed: read failure 90%
9008 9769035
# 8 Extended offline Completed without error 00%
8842 -
# 9 Extended offline Completed without error 00%
8674 -
#10 Extended offline Completed: read failure 40%
8505 675183097
#11 Extended offline Completed: read failure 40%
8342 675183097
#12 Extended offline Completed: read failure 40%
8170 675183097
#13 Extended offline Completed: read failure 40%
8002 675183097
#14 Extended offline Completed without error 00%
7835 -
#15 Extended offline Completed without error 00%
7673 -
#16 Extended offline Completed without error 00%
7503 -
#17 Extended offline Completed without error 00%
7333 -
#18 Extended offline Completed without error 00%
7165 -
#19 Extended offline Completed without error 00%
6997 -
#20 Extended offline Completed without error 00%
6833 -
#21 Extended offline Completed without error 00%
6660 -


SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


--

www.songshu.org
Just another collection of nuts


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-08-2009, 10:08 AM
Adrian Levi
 
Default smart

2009/3/8 randall <randall@songshu.org>:
> hi all,

G'Day.

> smartctl --all /dev/sde
> gives me the following, i've been trying to google this but some sources say
> replace the disk at once or don't wory, its harmless. Anybody can shed some
> light?

> *5 Reallocated_Sector_Ct * 0x0033 * 100 * 100 * 036 * *Pre-fail *Always
> * - * * * 35

This one above indicates that you drive is developing bad sectors. All
drives come with 'spare' sectors that can be remapped to the usable
space if ine or more becomes bad. Your drive has reallocated 35 bad
sectors and is most likely out of spares. Regardless the drive is
failing and must be replaced. In addition to that the data that was
stored on those 35 previously bad sectors is most likely irretrievably
lost. I hope that your raid setup has saved you from this data
corruption.

> Num *Test_Description * *Status * * * * * * * * *Remaining *LifeTime(hours)
> *LBA_of_first_error
> # 1 *Extended offline * *Completed: read failure * * * 10% * * *9849
> 917923767

...

> #13 *Extended offline * *Completed: read failure * * * 40% * * *8002
> 675183097

Your disc has been steadily failing for the last ~1800 hours.
Buy a replacement and swap it out asap.

Adrian

--
24x7x365 != 24x7x52 Stupid or bad maths?
<erno> hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-08-2009, 01:15 PM
randall
 
Default smart

Adrian Levi wrote:


Your disc has been steadily failing for the last ~1800 hours.
Buy a replacement and swap it out asap.

Adrian


Already had a spare lying around so i took the advice, the new disk is
actually syncing with the array at this moment.

http://www.songshu.org/index.php/replacing-a-failing-disk

thanks.

--

www.songshu.org
Just another collection of nuts


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-09-2009, 12:32 PM
"Stackpole, Chris"
 
Default smart

> From: randall [mailto:randall@songshu.org]
> Sent: Sunday, March 08, 2009 9:15 AM
> Subject: Re: smart
>
> Adrian Levi wrote:
> >
> > Your disc has been steadily failing for the last ~1800 hours.
> > Buy a replacement and swap it out asap.
> >
> > Adrian
> >
> >
> Already had a spare lying around so i took the advice, the new disk is
> actually syncing with the array at this moment.
> http://www.songshu.org/index.php/replacing-a-failing-disk

Randall,
I have had drives that had bad sectors like yours. My suggestion would
be to format the drive ext3 with the badblocks option.
`man mkfs.ext3`
You are going to want to read up on the -c option. I usually use the -cc
option when formatting the drive. If all goes well, physically mark the
drive so you know it has had issues then use it as a secondary/tertiary
backup.

I have a 500GB hard drive that has had problems for a while. It only
gives me like 380GB to use after a format. I wouldn't trust that drive
with my primary data period. However, if I am going on a road trip or
something I will toss a few recordings off of MythTV onto it, toss it
into an external drive enclosure, and I am good to go. Who cares if I
lose it, drop it, or otherwise cause it to fail?

What I am saying is, the badblocks option (mkfs.ext3 -cc) should find
the bad spots and allocate around them. Don't trust the drive, but you
might still be able to put it to use.

Have fun!
~Stack~


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 12:45 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org