From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] smartctrl drive error @60%
Date: Wed, 25 Jun 2014 08:15:57 -0500 [thread overview]
Message-ID: <53AACB8D.6010300@gmail.com> (raw)
In-Reply-To: <53AAA791.4050506@thegeezer.net>
thegeezer wrote:
> On 06/25/2014 08:49 AM, Dale wrote:
>> thegeezer wrote:
>>> this is pretty bad.
>> Here is the output:
>>
>> root@fireball / # smartctl -a /dev/sdc
>> smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.14.0-gentoo] (local build)
>> Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
>>
>> === START OF INFORMATION SECTION ===
>> Model Family: Seagate Barracuda 7200.14 (AF)
>> Device Model: ST3000DM001-9YN166
>> Serial Number: Z1F0PKT5
>> LU WWN Device Id: 5 000c50 04d79e15c
>> Firmware Version: CC4C
>> User Capacity: 3,000,592,982,016 bytes [3.00 TB]
>> Sector Sizes: 512 bytes logical, 4096 bytes physical
>> Rotation Rate: 7200 rpm
>> Device is: In smartctl database [for details use: -P show]
>> ATA Version is: ATA8-ACS T13/1699-D revision 4
>> SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
>> Local Time is: Wed Jun 25 02:46:39 2014 CDT
>>
>> ==> WARNING: A firmware update for this drive is available,
>> see the following Seagate web pages:
>> http://knowledge.seagate.com/articles/en_US/FAQ/207931en
>> http://knowledge.seagate.com/articles/en_US/FAQ/223651en
> interesting - not seen that before might be worth a nose
I was thinking the same thing myself. How does it know there is a
update was another question I had.
>> 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: (0x00) Offline data collection activity
>> was never started.
>> Auto Offline Data Collection:
>> Disabled.
>> Self-test execution status: ( 118) The previous self-test completed
>> having
>> the read element of the test failed.
>> Total time to complete Offline
>> data collection: ( 584) seconds.
>> Offline data collection
>> capabilities: (0x73) SMART execute Offline immediate.
>> Auto Offline data collection
>> on/off support.
>> Suspend Offline collection upon new
>> command.
>> No 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: ( 340) minutes.
>> Conveyance self-test routine
>> recommended polling time: ( 2) minutes.
>> SCT capabilities: (0x3085) SCT Status 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 119 099 006 Pre-fail
>> Always - 234421760
> you can happily ignore this error rate, it is usual for it to be high
> and htere is hardware correction for it
>
>> 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail
>> Always - 0
>> 4 Start_Stop_Count 0x0032 100 100 020 Old_age
>> Always - 33
> 33 power cycles seem very low but further down we see the power on time
> is just under two years which is also erring towards the lighter side of
> the mtbf
About the only time I shutdown is when the power fails. My puter only
pulls about 150 watts so I just leave it running 24/7.
>
>> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
>> Always - 0
> zero reallocated sectors suggests there is space to do reallocation
>
>> 7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail
>> Always - 99909120
>> 9 Power_On_Hours 0x0032 082 082 000 Old_age
>> Always - 16379
> almost two years of power on time
>
>> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
>> Always - 0
>> 12 Power_Cycle_Count 0x0032 100 100 020 Old_age
>> Always - 34
>> 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age
>> Always - 0
>> 184 End-to-End_Error 0x0032 100 100 099 Old_age
>> Always - 0
>> 187 Reported_Uncorrect 0x0032 100 100 000 Old_age
>> Always - 0
>> 188 Command_Timeout 0x0032 100 100 000 Old_age
>> Always - 0 0 0
>> 189 High_Fly_Writes 0x003a 100 100 000 Old_age
>> Always - 0
>> 190 Airflow_Temperature_Cel 0x0022 069 063 045 Old_age
>> Always - 31 (Min/Max 26/33)
>> 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age
>> Always - 0
>> 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age
>> Always - 9
>> 193 Load_Cycle_Count 0x0032 093 093 000 Old_age
>> Always - 14284
>> 194 Temperature_Celsius 0x0022 031 040 000 Old_age
>> Always - 31 (0 17 0 0 0)
>> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age
>> Always - 104
> 197
> this says there are 104 pending sectors i.e. bad blocks on the drive
> that have not been reallocatd yet
Wonder why it hasn't? Isn't it supposed to do that sort of thing itself?
>
>> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age
>> Offline - 104
> this says it was not able to reallocate. which is odd because of the
> entry 5 being zero
Uh oh.
>
>> 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age
>> Always - 0
>> 240 Head_Flying_Hours 0x0000 100 253 000 Old_age
>> Offline - 15955h+37m+28.932s
>> 241 Total_LBAs_Written 0x0000 100 253 000 Old_age
>> Offline - 52221690631887
>> 242 Total_LBAs_Read 0x0000 100 253 000 Old_age
>> Offline - 74848968465606
>>
>> SMART Error Log Version: 1
>> No Errors Logged
>>
>> 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 60%
>> 16365 2905482560
>> # 2 Extended offline Completed: read failure 60%
>> 16352 2905482560
>> # 3 Extended offline Completed without error 00%
>> 8044 -
>> # 4 Extended offline Completed without error 00%
>> 3121 -
>> # 5 Extended offline Completed without error 00%
>> 1548 -
>> # 6 Short offline Completed without error 00%
>> 1141 -
>> # 7 Extended offline Completed without error 00%
>> 719 -
>> # 8 Extended offline Completed without error 00%
>> 525 -
>> # 9 Short offline Completed without error 00%
>> 516 -
>> #10 Extended offline Completed without error 00%
>> 18 -
>> #11 Extended offline Completed without error 00%
>> 5 -
>> #12 Short offline Completed without error 00%
>> 0 -
>>
>> 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.
>>
>> root@fireball / #
>>
>> Does that help shed any light on this situation? If you need more
>> info, just let me know. Off to newegg. BRB
>>
>> Dale
>>
>> :-) :-)
>>
> 104 bad blocks is not a sign of a happy disk.
> i would replace urgently
>
> also consider running smartd or a smartmonitor plugin for munin as the
> test log suggests you last ran a test after the first year of usage
>
>
I usually just run the test manually but I sort of had family stuff
going on for the past year, almost a year anyway. Sort of behind on
things although I have been doing my normal updates.
I ordered a drive. It should be here tomorrow. In the meantime, I
shutdown and re-seated all the cables, power too. I got the test running
again but results is a few hours off yet. It did pass the short test
tho. I'm not sure that it means much.
Thanks much.
Dale
:-) :-)
next prev parent reply other threads:[~2014-06-25 13:16 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 23:09 [gentoo-user] smartctrl drive error @60% Dale
2014-06-25 4:20 ` J. Roeleveld
2014-06-25 5:05 ` Dale
2014-06-25 7:26 ` J. Roeleveld
2014-06-25 7:43 ` Dale
2014-06-25 7:41 ` thegeezer
2014-06-25 7:49 ` Dale
2014-06-25 10:42 ` thegeezer
2014-06-25 13:15 ` Dale [this message]
2014-06-25 14:03 ` Rich Freeman
2014-06-25 15:54 ` Dale
2014-06-25 16:09 ` Neil Bothwick
2014-06-25 16:44 ` Mick
2014-06-25 17:29 ` Neil Bothwick
2014-06-25 22:16 ` Dale
2014-06-25 22:32 ` Rich Freeman
2014-06-26 2:07 ` Dale
2014-06-26 2:15 ` Rich Freeman
2014-06-26 4:57 ` Dale
2014-06-29 15:17 ` Frank Steinmetzger
2014-07-01 8:30 ` Dale
2014-07-01 8:46 ` Helmut Jarausch
2014-07-01 8:58 ` Dale
2014-07-01 9:06 ` Helmut Jarausch
2014-07-01 9:11 ` J. Roeleveld
2014-07-01 9:21 ` Dale
2014-07-01 10:19 ` J. Roeleveld
2014-07-01 12:36 ` Dale
2014-07-01 8:49 ` J. Roeleveld
2014-06-25 22:50 ` Neil Bothwick
2014-06-26 2:15 ` Dale
2014-06-26 5:56 ` Mick
2014-06-26 5:59 ` Mick
2014-06-26 14:14 ` Dale
2014-06-26 15:08 ` Neil Bothwick
2014-06-26 15:31 ` Dale
2014-06-27 13:22 ` Mick
2014-06-27 20:54 ` Neil Bothwick
2014-06-27 21:26 ` [gentoo-user] " Grant Edwards
2014-06-27 21:41 ` Rich Freeman
2014-06-28 7:48 ` [gentoo-user] " Mick
2014-06-28 8:37 ` Neil Bothwick
2014-06-28 11:54 ` Dale
2014-06-26 7:22 ` [gentoo-user] " Alberto Luaces
2014-06-26 10:11 ` [gentoo-user] " Neil Bothwick
2014-06-26 11:03 ` Dale
2014-06-26 11:24 ` Rich Freeman
2014-06-26 11:40 ` Dale
2014-06-26 0:38 ` Bill Kenworthy
2014-06-26 2:31 ` Dale
2014-06-26 17:39 ` [gentoo-user] " Grant Edwards
2014-06-28 11:55 ` Dale
2014-06-28 12:40 ` Neil Bothwick
2014-06-28 13:05 ` Dale
2014-06-28 13:08 ` Alan McKinnon
2014-06-28 13:58 ` Dale
2014-06-28 14:15 ` Dale
2014-06-28 14:50 ` Peter Humphrey
2014-06-28 16:00 ` Mick
2014-06-28 17:30 ` Dale
2014-06-25 16:38 ` [gentoo-user] " Rich Freeman
2014-06-26 2:13 ` Dale
2014-06-25 18:44 ` Douglas J Hunley
2014-06-25 18:50 ` Rich Freeman
2014-06-26 16:05 ` Dale
2014-06-26 0:00 ` David Haller
2014-06-26 2:40 ` Dale
2014-06-26 6:05 ` David Haller
2014-06-26 16:19 ` [gentoo-user] OT: power requirement (WAS: smartctrl drive error @60%) Frank Steinmetzger
2014-06-26 17:05 ` Daniel Frey
2014-06-26 23:01 ` Bill Kenworthy
2014-06-26 17:31 ` Dale
2014-06-25 16:55 ` [gentoo-user] smartctrl drive error @60% Volker Armin Hemmann
2014-06-25 17:06 ` Rich Freeman
2014-06-25 17:15 ` Volker Armin Hemmann
2014-06-25 17:44 ` Rich Freeman
2014-06-25 21:19 ` J. Roeleveld
2014-06-26 3:45 ` Dale
2014-06-26 1:16 ` Daniel Frey
2014-06-26 3:54 ` Dale
2014-06-26 10:05 ` Neil Bothwick
2014-06-26 10:54 ` Dale
2014-06-26 10:52 ` Alan McKinnon
2014-06-26 11:20 ` Dale
2014-06-26 12:57 ` Alan McKinnon
2014-06-26 13:58 ` Dale
2014-06-26 17:14 ` Daniel Frey
2014-06-26 17:21 ` Daniel Frey
2014-06-25 21:11 ` Dale
2014-06-25 9:46 ` Neil Bothwick
2014-06-25 10:05 ` Dale
2014-06-25 10:55 ` thegeezer
2014-06-25 11:02 ` Helmut Jarausch
2014-06-25 13:21 ` covici
2014-06-25 12:33 ` Rich Freeman
2014-06-25 14:23 ` Neil Bothwick
2014-06-25 14:29 ` Rich Freeman
2014-06-25 16:00 ` Dale
2014-06-25 15:30 ` covici
2014-06-25 16:34 ` Rich Freeman
2014-06-25 17:58 ` Alan McKinnon
2014-06-25 12:30 ` Dale
2014-06-25 7:35 ` Marc Joliet
2014-06-29 3:27 ` Dale
2014-06-29 3:34 ` Rich Freeman
2014-06-29 4:44 ` Dale
2014-06-29 7:38 ` Mick
2014-06-29 8:42 ` Dale
2014-06-29 9:40 ` Mick
2014-06-29 12:05 ` Rich Freeman
2014-06-29 12:30 ` Dale
2014-07-01 5:52 ` Mick
2014-07-01 6:09 ` J. Roeleveld
2014-07-01 7:21 ` Dale
2014-07-01 10:48 ` Rich Freeman
2014-07-01 10:55 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53AACB8D.6010300@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox