Hello,
I have a problem with this disk inside a NAS system with linux system
could you help me to fix this problem?

smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: WDC WD5000AAJS-22TKA0
Serial Number: WD-WCAPW4129429
Firmware Version: 12.01C01
User Capacity: 500,107,862,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jun 11 21:28:36 2012 CEST
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: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
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: (12600) 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 157) minutes.
Conveyance self-test routine
recommended polling time: ( 6) 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
1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0003 186 170 021 Pre-fail Always - 5675
4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5374
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0
9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5732
10 Spin_Retry_Count 0x0012 100 100 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0
12 Power_Cycle_Count 0x0032 096 096 000 Old_age Always - 4499
192 Power-Off_Retract_Count 0x0032 199 199 000 Old_age Always - 1221
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5377
194 Temperature_Celsius 0x0022 116 087 000 Old_age Always - 34
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 051 Old_age Offline - 0

SMART Error Log Version: 1
ATA Error Count: 34 (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 34 occurred at disk power-on lifetime: 5576 hours (232 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 08 d8 ea 5b e0 Error: UNC 8 sectors at LBA = 0x005bead8 = 6023896

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 d8 ea 5b 00 00 00:00:15.142 READ DMA EXT
25 00 08 d8 ea 5b 00 00 00:00:13.042 READ DMA EXT
25 00 08 c8 ea 5b 00 00 00:00:13.042 READ DMA EXT
25 00 08 c0 ea 5b 00 00 00:00:13.033 READ DMA EXT
25 00 08 20 08 00 00 00 00:00:13.032 READ DMA EXT

Error 33 occurred at disk power-on lifetime: 5576 hours (232 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 08 d8 ea 5b e0 Error: UNC 8 sectors at LBA = 0x005bead8 = 6023896

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 d8 ea 5b 00 00 00:00:13.042 READ DMA EXT
25 00 08 c8 ea 5b 00 00 00:00:13.042 READ DMA EXT
25 00 08 c0 ea 5b 00 00 00:00:13.033 READ DMA EXT
25 00 08 20 08 00 00 00 00:00:13.032 READ DMA EXT
25 00 08 00 08 60 00 00 00:00:13.025 READ DMA EXT

Error 32 occurred at disk power-on lifetime: 3710 hours (154 days + 14 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 40 3f 74 1f e0 Error: UNC 64 sectors at LBA = 0x001f743f = 2061375

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 40 3f 74 1f 00 00 00:01:38.491 READ DMA EXT
35 00 00 b7 61 1a 03 00 00:01:38.490 WRITE DMA EXT
35 00 08 ef 19 3e 02 00 00:01:38.490 WRITE DMA EXT
35 00 18 bf 19 3e 02 00 00:01:38.490 WRITE DMA EXT
35 00 00 af 5f a2 00 00 00:01:38.488 WRITE DMA EXT

Error 31 occurred at disk power-on lifetime: 3710 hours (154 days + 14 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 40 3f 74 1f e0 Error: UNC 64 sectors at LBA = 0x001f743f = 2061375

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 40 3f 74 1f 00 00 00:01:36.350 READ DMA EXT
35 00 08 2f 64 00 00 00 00:01:36.350 WRITE DMA EXT
35 00 08 ff 19 3e 02 00 00:01:36.350 WRITE DMA EXT
35 00 00 af 4f a2 00 00 00:01:36.348 WRITE DMA EXT
35 00 00 af 4e a2 00 00 00:01:36.347 WRITE DMA EXT

Error 30 occurred at disk power-on lifetime: 3710 hours (154 days + 14 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 40 3f 74 1f e0 Error: UNC 64 sectors at LBA = 0x001f743f = 2061375

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 40 3f 74 1f 00 00 00:01:34.384 READ DMA EXT
25 00 40 8f 43 17 00 00 00:01:34.377 READ DMA EXT
35 00 08 1f f4 0e 00 00 00:01:34.377 WRITE DMA EXT
25 00 48 4f a8 02 00 00 00:01:34.360 READ DMA EXT
35 00 08 f7 19 3e 02 00 00:01:34.359 WRITE DMA EXT

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% 3442 -
# 2 Conveyance offline Completed without error 00% 3347 -
# 3 Short offline Aborted by host 50% 3347 -

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.


Regards
Dario

Cambia disco . TU non puoi farci nulla se il disco e' degradato. Posso fare qualcosa ma me lo devi mandare (ricertificarlo completamente come se uscisse dalla fabbrica, a parte che ha lavorato il tempo che ha lavorato - ma con tutti gli errori azzerati e il resto perfetto).
Dimenticavo : scegli un altro tipo di disco...

Replace. there's nothing YOU can do if the disk is in degraded condition. I can fix it but need you to send the drive (complete recertify like brand new beside the working time, with perfect surface and zero errors).
P.S. choose another disk

ok grazie per le dritte, il disco non contiene dati in quanto era già stato dismesso da parecchio tempo, volevo solo capire perchè se utilizzato con Windows 7 funziona e anche check disk non da errori, mentre sul nas non viene nemmeno riconosciuto (Stasera provo a montarlo su una macchina Debian/linux e gli voglio fare un po' di diagnosi approfondita usanto smartmoontools, lo stesso del nas)

Invece come posso analizzare i codici esadecimali degli errori, dove posso trovare la tabella che mi dica il significato dei codice?
ER = Error register [HEX] = 40
ST = Status register [HEX] = 51
SC = Sector Count Register [HEX] = 08
SN = Sector Number Register [HEX] = d8
CL = Cylinder Low Register [HEX] = ea
CH = Cylinder High Register [HEX] = 5b
DH = Device/Head Register [HEX] = e0

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 d8 ea 5b e0 Error: UNC 8 sectors at LBA = 0x005bead8 = 6023896

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 d8 ea 5b 00 00 00:00:15.142 READ DMA EXT

Dario




ok thank you for hints, the hard disk doesn't have data, it was already put in retirement, I like to understand because on Windows 7 works fine, instead on nas linux machine it is not recognized (This evening I want to diagnose it with debian/linux distro, pheraps using smartmoontools, the same of nas tool )

I'd like to know how I can analyze the hexadecimal error code, where can I find the table to tell me the meaning of the code, as this example?
ER = Error register [HEX] = 40
ST = Status register [HEX] = 51
SC = Sector Count Register [HEX] = 08
SN = Sector Number Register [HEX] = d8
CL = Cylinder Low Register [HEX] = ea
CH = Cylinder High Register [HEX] = 5b
DH = Device/Head Register [HEX] = e0

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 d8 ea 5b e0 Error: UNC 8 sectors at LBA = 0x005bead8 = 6023896

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 08 d8 ea 5b 00 00 00:00:15.142 READ DMA EXT

Regards
Dario

Se il disco E' AZZERABILE con PERDITA DI DATI : lascia perdere i codici di errore, le interpretazioni e tutti i vari SMART monitors , alla fine sono solo cazzate che nulla dicono se non cosi' "alla buona" circa lo stato del disco. Per provare a riutilizzarlo, usa MHDD collegandolo su macchina pura DOS e azzeralo (comando ERASE) completamente. Occhio a selezionare il corretto disco (comando PORT) prima di fare qualsiasi cosa - meglio partire con SOLO il tuo disco collegato e boot da floppy ! A questo punto tra l'altro qualcosa nello SMART dovrebbe cambiare (in meglio o in peggio ma cambia) MA non e' la soluzione definitiva.
Dopo che ha finito (a occhio ci mettera' un bel po'...) usa il comando SCAN o F4 e controlla tutta la superficie.
Se e' tutto a posto dovresti avere "al massimo" qualche settore entro i 150 ms. (verde). Presenza di blocchi marrone, contigui o peggio rossi o "Warning : xxxxxxx" sono indice di sicuro degrado.
Dopo che il disco e' stato azzerato completamente puoi farlo riconoscere a 7 o a Linux e ti apparira' come completamente "unallocated" e "non inizializzato".
E' l'ultima spiaggia del fai da te, oltre quello se e' proprio degradato non c'e' nient'altro da fare se non usare i nostri strumenti ahime' complicati e costosi (e il know how....). Comunque confermo che sono dischi del .... specie se usati in NAS o in applicazioni intensive.
P.S. probabilmente il NAS richiede di inizializzare il disco se nuovo in maniera diversa.... oppure effettivamente c'e' ben altro problema .
Fammi sapere.

If the disk CAN BE ZEROFILLED (with loss of data!) : forget error codes and smart monitors that give only "at a glance" indication of health and often all that stuff is of no practical use : try using MHDD on a pure DOS PC , erasing the disk (ERASE command). Be careful selecting the correct disk (PORT command), better connecting ONLY your disk and booting from FDD. At this point, also, SMART can show some change, but it's not the definitive solution. After finishing (will take a while) SCAN surface (also F4) : you should only have "some" green blocks (best : zero). Presence of brown , red or -worst case : WARNING : xxxxxx means degradation.
After erasing, the disk will be seen as completely unallocated and NOT inited by 7 and linux.
This is the last resort for DIY, otherwise there's no alternative to our complicated and expensive equipments (and don't forget the know how....) - anyway I still say these are not good disks for that application, especially on NAS or intensive.
P.S. maybe the NAS require a different procedure for initing the disk ... or there's REALLY something wrong with the disk. Let me know.

@darioit,

As BlackST says (with lots of good detail), your only DIY repair attempt would be to zero-fill the disk, scan it, and then re-check the SMART attributes and SMART error log again, and then make an educated judgement about the state of the disk. However, as always you cannot rely on SMART to show you every problem - it was not designed to be that detailed. I don't want to interrupt your discussion with BlackST, but I'll make a few comments and reply to your question.

FYI, you are using an old version of smartmontools (or is this the version installed on the NAS?). There is an interesting inconsistency between the SMART attributes (no pending sectors), and the SMART error log (UNCs occurred). If it was my disk, I would use the current smartmontools version and see if attributes 197 or 198 show different values, and then scan the disk and do the same again. I would also see if there is any difference when using the extended data collection (I guess this was the output from smartctl -a, although you don't mention the exact command that was used).

However, in any case, from the SMART error log entries, the disk has problems. IMHO this is a good example of the value of the SMART error log, as collected by smartmontools but not collected by many other tools, as the error log shows that there are problems - this is not obvious from the (currently reported) SMART attributes.


What exactly do you mean by "works fine"? How did you decide this?


What exactly do you mean by "not recognized"? Were you referring to the disk itself or the filesystem? Where exactly were you looking for "recognition"? Personally I would check using a plain Linux system, in case you are being misled by the NAS software.


smartctl (smartmontools) has already decoded the meaning for you, in the section which I made bold above. If you want to read more about these registers, you need to spend (lots of) time researching the ATA specification.

hello everyone,

first thanks for support, the solution of my problem is "the nas work bad" I try to change this disk with another sata 80GB and the problem still remain, the smart attribute of new disk was fine, but the Nas won't recognize the disk. (The model model of nas is this one http://mrt.nas-central.org/wiki/Category:35HD-QUAD-NAS)

Anyway I want to follow BlackST suggestion to ERASE and SCAN 500gb hard drive, and the result is that this disk is perfect
here attach the detail of test http://img189.imageshack.us/img189/4196/dsc17802.jpg

Disregard 3 >500ms because is caused by plug and unplug usb keyboard.

From my point of view now I open a call to Nas support to understand what's wrong, pheraps is only a firmware problem.

Thanks to all

Regards
Dario

yesterday I try a simple operation, change hard disk position on nas slot, and I discover that 2 of 4 bay are damaged.

So I confirm the problem is was on Nas Sata controller.

Thanks anyway for support

Regards
Dario

Thanks for the update. I can only think of one type of NAS fault which could perhaps explain the SMART error log entries. The results so far don't explain the exact fault which you have found - it seems that you have found a NAS problem, but personally I'm not yet sure that you've found the only problem. As I mentioned earlier, there were other steps which I suggested to look deeper for any latent disk issues, but of course it is your choice how much troubleshooting you do.