You are not logged in.
Pages: 1
Topic closed
Hi All,
this morning my linux server sent me this 2 emails:
SMART error (CurrentPendingSector) detected on host: artemide
This message was generated by the smartd daemon running on:
host name: artemide
DNS domain: knossos
The following warning/error was logged by the smartd daemon:
Device: /dev/sdc [SAT], 56 Currently unreadable (pending) sectors
Device info:
ST3000DM001-9YN166, S/N:S1F01CJW, WWN:5-000c50-04a10cc7c, FW:CC4C, 3.00 TB
For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.
SMART error (OfflineUncorrectableSector) detected on host: artemide
This message was generated by the smartd daemon running on:
host name: artemide
DNS domain: knossos
The following warning/error was logged by the smartd daemon:
Device: /dev/sdc [SAT], 56 Offline uncorrectable sectors
Device info:
ST3000DM001-9YN166, S/N:S1F01CJW, WWN:5-000c50-04a10cc7c, FW:CC4C, 3.00 TB
For details see host's SYSLOG.
You can also use the smartctl utility for further investigation.
Another message will be sent in 24 hours if the problem persists.
this disk is part of a RAID5 array with 3 disks, is there a way to fix the problem, or the only thing I can do is to throw it away and change it?
here the result of "smartctl -a /dev/sdc"
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.12-1-amd64] (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: S1F01CJW
LU WWN Device Id: 5 000c50 04a10cc7c
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: 3.0 Gb/s)
Local Time is: Thu Sep 11 08:08:41 2014 CEST
==> 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
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
See vendor-specific Attribute list for marginal Attributes.
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: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 584) 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: ( 344) 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 112 099 006 Pre-fail Always - 48683880
3 Spin_Up_Time 0x0003 094 092 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 193
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1240
7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 36368561
9 Power_On_Hours 0x0032 082 082 000 Old_age Always - 16170
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 191
183 Runtime_Bad_Block 0x0032 087 087 000 Old_age Always - 13
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 099 000 Old_age Always - 0 0 7
189 High_Fly_Writes 0x003a 089 089 000 Old_age Always - 11
190 Airflow_Temperature_Cel 0x0022 052 045 045 Old_age Always In_the_past 48 (Min/Max 45/54)
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 - 151
193 Load_Cycle_Count 0x0032 021 021 000 Old_age Always - 159833
194 Temperature_Celsius 0x0022 048 055 000 Old_age Always - 48 (0 16 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 56
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 56
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 64
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 10210h+22m+12.763s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 45684523263768
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 89193678751496
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 Short offline Completed without error 00% 16170 -
# 2 Extended offline Completed without error 00% 16151 -
# 3 Short offline Completed without error 00% 16113 -
# 4 Short offline Completed without error 00% 16089 -
# 5 Extended offline Completed without error 00% 16070 -
# 6 Short offline Completed without error 00% 16041 -
# 7 Short offline Completed without error 00% 16017 -
# 8 Short offline Completed without error 00% 15993 -
# 9 Short offline Completed without error 00% 15969 -
#10 Short offline Completed without error 00% 15945 -
#11 Short offline Completed without error 00% 15921 -
#12 Extended offline Completed without error 00% 15902 -
#13 Short offline Completed without error 00% 15873 -
#14 Short offline Completed without error 00% 15849 -
#15 Short offline Completed without error 00% 15825 -
#16 Short offline Completed without error 00% 15801 -
#17 Short offline Completed without error 00% 15777 -
#18 Short offline Completed without error 00% 15753 -
#19 Extended offline Completed without error 00% 15734 -
#20 Short offline Completed without error 00% 15705 -
#21 Short offline Completed without error 00% 15681 -
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.
Last edited by miky76 (2014-09-11 08:38:11)
Offline
I'd say that disk is bad and will only cause you trouble, you should really consider changing it. Note that you already have 1240 reallocated sectors, that's never a good thing.
You better have good backups, 3TB are going to take a good while to resync, and with raid5 if any other disk throws a fit you can say goodbye to your data.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
==> WARNING: A firmware update for this drive is available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/e … Q/207931en
http://knowledge.seagate.com/articles/e … Q/223651en
Do so quickly!
No Errors Logged
Not all is lost
First update firmware -- maybe reformat drive.
Offline
I had the same problem. I could only find "get a new drive" solutions on the net. But then I have found another possible solution, along with some explanation. Check the docs that come with smart (this is the debian location, your distro may have another place for it):
/usr/share/doc/smartmontools/badblockhowto.html
Before doing anything, read this doc!
Normally the disk has some spare sectors to remap bad sectors, so that the user never notices that anything was ever wrong. In this case, however, the sector was good -> data was written to it /was ever wrong. In this case, however, the sector was good -> data was written on it -> now we cannot read it! It is still marked, however, as used. Since the system has no idea, what was on this sector AND it is used, it has no way to transparently copy it over to a good sector -> thus it delegates the problem to the user (you). The gist of the solution is (READ THE DOCS for full explanation!!!):
1) find the corrupted file (the file that has allocated the unreadable sector)
2) delete that file
3) possibly write 0-s over it
4) let the system do its magic, and reallocate the bad sector to a spare one (if there is any spare left!!!)
In my situation, I have LVM2 over raid2. I decided that finding the corrupted file over the LVM2 is too timeconsuming, and I have a perfectly good version in the other leg of the raid array,
so I simply kicked the faulty drive out of the array:
mdadm /dev/md0 --fail /dev/sda1 --remove /dev/sda1
Then wrote the whole drive over with 0-s (it took quite a long time, but it was not my time!):
dd if=/dev/zero of=/dev/sda1 bs=1M
re-run smart long test:
smartctl -t long /dev/sda
et voila, the error is gone, check with:
smartclt -l selftest /dev/sda
smartclt -a /dev/sda
Then I just repartitioned, and readded the drive to the raid array.
I had another drive with the same problem, I did the exact same thing, but it did not help, the long test still fail at the exact same sector. I am running now a
badblocks /dev/sda
on it. And hope for the best.
Of course, if you do this, keep in mind a few things:
- I have been a badblocks expert for like 24 hours, so use your own brain, as well
- even if everything works and back to normal, in the next few months you should keep an eye on the badblocks/reallocate counters, if they start to creep up, change the drive, or bad things w
ill happen very soon (like corrupted files)
- unless you are ok with suddenly losing all your data on that drive, or have plenty of backups (besides the raid2 on this machine, I have a the whole thing on a separate backup machine, so I was not afraid of doing something really stupid), or it is a live-or-die situation, don't try this, just buy a new drive. I am telling this, because even though it worked for me, I don't have any longterm experience with this solution!
Offline
Thanks for your input kzoltan. We have a policy against bumping old thread, as such I'll go ahead and close this thread:
Offline
Pages: 1
Topic closed