martin

Q1. Can anyone advise me from the messages below whether my HDD is dying?

Q2. Is it possible to tell FreeBSD 6.1 to scan the disk surface for bad
sectors and map around them, or are all modern hard disks expected to
do bad-sector remapping transparently?

The disk is a Maxtor 300 GB IDE device in my home server, about 2 years old.
It only started showing errors today, always with the same block number.
The system itself is still working OK but if the disk is about to fail
then I need to order a new disk and swap it out ASAP.

The /var/log/messages output is here:-

Jul 16 13:00:03 server kernel: ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=231963267
Jul 16 13:00:03 server kernel: g_vfs_done():ad0s1f[READ(offset=84405422080, length=2048)]error = 5
Jul 16 13:29:54 server smartd[589]: Device: /dev/ad0, 1 Currently unreadable (pending) sectors
Jul 16 13:29:54 server smartd[589]: Device: /dev/ad0, 1 Offline uncorrectable sectors
Jul 16 13:29:54 server smartd[589]: Device: /dev/ad0, ATA error count increased from 11 to 13

The smartctl -a output follows.

Thanks for your time.

- Martin.
--------------------


# smartctl -a /dev/ad0
smartctl version 5.36 [i386-portbld-freebsd6.1] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family: Maxtor MaXLine II family
Device Model: Maxtor 5A300J0
Serial Number: A814BJ6E
Firmware Version: RAMB1TV0
User Capacity: 300,001,443,840 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Sun Jul 16 16:55:59 2006 BST
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: (0x02) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 115) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 30) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 158) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
3 Spin_Up_Time 0x0027 202 202 063 Pre-fail Always - 11927
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 407
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 8
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0
8 Seek_Time_Performance 0x0027 250 246 187 Pre-fail Always - 55654
9 Power_On_Minutes 0x0032 217 217 000 Old_age Always - 777h+08m
10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 253 253 000 Old_age Always - 68
192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age Always - 0
193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always - 0
194 Temperature_Celsius 0x0032 253 253 000 Old_age Always - 52
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always - 44574
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 1
198 Offline_Uncorrectable 0x0008 252 252 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 22
202 TA_Increase_Count 0x000a 253 252 000 Old_age Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 12
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0
207 Spin_High_Current 0x002a 253 252 000 Old_age Always - 0
208 Spin_Buzz 0x002a 253 252 000 Old_age Always - 0
209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 13 inconsistent with error log pointer 5

ATA Error Count: 13 (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 13 occurred at disk power-on lifetime: 11988 hours (499 days + 12 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 51 03 83 7a d3 ed Error: UNC 3 sectors at LBA = 0x0dd37a83 = 231963267

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 04 83 7a d3 ed 08 23d+19:57:51.504 READ DMA
c8 00 04 83 7a d3 ed 08 23d+19:57:50.000 READ DMA
c8 00 04 ff 8e df ed 08 23d+19:57:50.000 READ DMA
c8 00 20 ff 4c d3 ed 08 23d+19:57:49.984 READ DMA
c8 00 04 87 7a d3 ed 08 23d+19:57:49.952 READ DMA

Error 12 occurred at disk power-on lifetime: 11988 hours (499 days + 12 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 51 03 83 7a d3 ed Error: UNC 3 sectors at LBA = 0x0dd37a83 = 231963267

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 04 83 7a d3 ed 08 23d+19:57:50.000 READ DMA
c8 00 04 ff 8e df ed 08 23d+19:57:50.000 READ DMA
c8 00 20 ff 4c d3 ed 08 23d+19:57:49.984 READ DMA
c8 00 04 87 7a d3 ed 08 23d+19:57:49.952 READ DMA
c8 00 04 9b 86 d3 ed 08 23d+19:57:49.952 READ DMA

Error 11 occurred at disk power-on lifetime: 11979 hours (499 days + 3 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 51 03 83 7a d3 ed Error: UNC 3 sectors at LBA = 0x0dd37a83 = 231963267

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 04 83 7a d3 ed 08 23d+09:08:52.144 READ DMA
c8 00 04 9b 86 d3 ed 08 23d+09:08:52.144 READ DMA
c8 00 04 7f 7a d3 ed 08 23d+09:08:52.144 READ DMA
c8 00 04 7b 7a d3 ed 08 23d+09:08:52.144 READ DMA
c8 00 04 bf 86 d3 ed 08 23d+09:08:52.144 READ DMA

Error 10 occurred at disk power-on lifetime: 9253 hours (385 days + 13 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 51 10 4f 00 00 e1 Error: UNC at LBA = 0x0100004f = 16777295

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c4 00 10 4f 00 00 e1 08 00:09:10.160 READ MULTIPLE
ef 03 0c 00 00 00 e0 08 00:09:10.144 SET FEATURES [Set transfer mode]
c8 00 10 4f 00 00 e1 08 00:09:07.648 READ DMA
ca 00 04 4f 00 c0 e0 08 00:09:07.648 WRITE DMA
ca 00 04 bf 15 c0 e0 08 00:09:07.648 WRITE DMA

Error 9 occurred at disk power-on lifetime: 9253 hours (385 days + 13 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 51 0d 4f 00 00 e1 Error: UNC 13 sectors at LBA = 0x0100004f = 16777295

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 10 4f 00 00 e1 08 00:09:07.648 READ DMA
ca 00 04 4f 00 c0 e0 08 00:09:07.648 WRITE DMA
ca 00 04 bf 15 c0 e0 08 00:09:07.648 WRITE DMA
c8 00 04 bf 15 c0 e0 08 00:09:07.648 READ DMA
c8 00 10 4f 00 c0 e0 08 00:09:07.632 READ DMA

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 30% 11987 231963268
# 2 Short offline Completed: read failure 60% 11986 231963268
# 3 Extended offline Interrupted (host reset) 40% 11985 -
# 4 Short offline Completed without error 00% 11978 -
# 5 Extended offline Completed without error 00% 11960 -
# 6 Short offline Completed without error 00% 11956 -
# 7 Short offline Completed without error 00% 11934 -
# 8 Short offline Completed without error 00% 11911 -
# 9 Short offline Completed without error 00% 11889 -
#10 Short offline Completed without error 00% 11867 -
#11 Short offline Completed without error 00% 11844 -
#12 Short offline Completed without error 00% 11822 -
#13 Extended offline Completed without error 00% 11803 -
#14 Short offline Completed without error 00% 11800 -
#15 Short offline Completed without error 00% 11777 -
#16 Short offline Completed without error 00% 11755 -
#17 Short offline Completed without error 00% 11732 -
#18 Short offline Completed without error 00% 11710 -
#19 Short offline Completed without error 00% 11688 -
#20 Short offline Completed without error 00% 11665 -
#21 Extended offline Completed without error 00% 11646 -

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.

chronos

After replacing Martin with a small shell script on Sunday 16 Jul 2006
17:05, the following appeared on stdout:


It has run out of sectors to assign to replace bad sectors (attribute 5
on Maxtors only starts counting up once it has run out of reserved
sectors to reallocate). Yes, I would think about replacing this drive
ASAP, especially if it is holding data you would not want to lose.


And this is why. That drive is running far too hot. Absolute maximum
active temperature for a Maxtor is 60 degrees, 55 degrees for any other
manufacturer. Maxtors are well known for thermal death. You may want to
consider a WD RAID Edition drive for 24X7 use, and install a bit of
forced air cooling in the front of the drive bay. A single decent 80mm
fan (Panaflo or similar) should suffice. Ensure your airflow is moving
in one direction (usually front to back) on all fans.
--
Chronos

martin

Thanks for the info - that's very useful.

Unusually for the UK, it's about 32 degrees centigrade here today. I was
already a bit concerned that this may cause problems!

I will look at more cooling, and at WD Raid Edition drives. More
recently I have bought Seagate Barracuda drives - so far, so good.

Cheers

- Martin.

chronos

After replacing Martin with a small shell script on Sunday 16 Jul 2006
18:10, the following appeared on stdout:


Yep, those are good, too. If you're in the UK, have a word with Odie
Ferrous on uk.comp.homebuilt. He's a data recovery expert who knows the
current trends for reliable drives. He'll probably pooh-pooh my
suggestion of WD REs and tell you to go with your Seagates. As long as
it's reliable information I don't mind being wrong, although my REs
(WD1600YD) as a gmirror array have never missed a beat and they are
rated by the manufacturer for 24X7 use. They also have five year
warranties, as do the Seagate Barracudas.
--
Chronos