Howdy all
Guys I know may be this is irrelevant question but I don’t have somewhere else to go so please bear with me.
My question is how I can get trained by WD professionals "how to repair HD?"
I am computer guy; working as an assistant IT Manager in big company. My habit is to learn all the time very keen to gain more knowledge all the time.
I hope some one should help me in this. After all you all are professionals.
Thanks in advance.
Best regards
Xaroom 
"Tariq Zarrar"
- last edited on by
Bill_S
oh, here's my part of this sad, pathethic story:
my MB is GA-MA78G-DS3H (revision 1.001, bios F9d), UPS is APC Back-UPS ES 525.
i have^Whad 5 WD drives:
- WD15EARS-00Z5B1, 80.00A80 (about 0.5-0.75 year old, system is here) 3742 Power_On_Hours, 105319 Load_Cycle_Count
- WD3000JS-00PDB0, 21.00M21 (~4-6 years old **bleep**) 28623 Power_On_Hours, no LCC counter, 1 realocation (event) of 20 sectors some years ago
- WD10EADS-65L5B1, 01.01A01 (~1.5 year old) 9963 Power_On_Hours, 421 Load_Cycle_Count, 1 uncorrectable, 1 pending
- WD10EADS-00M2B0, 01.00A01 (~1 year old) 7316 Power_On_Hours, 54863 Load_Cycle_Count, 2 pending
- and 3 year old WD2500AAJS-00VTA0 (i know, it doesn't have that "feature". it was used extensively all 3 years with no rest 24/7 in contrary to other ones which just sit there with occasional read), which decided to die few days ago in same fashion as next candidate for garbage bin.
i will tell now about this candidate and the rest but for now - try and guess which of those drives is also on edge of dying.
which one says:
[ 699.152271] XFS mounting filesystem sdb1
[ 701.903832] ata2.00: exception Emask 0x0 SAct 0x9 SErr 0x80000 action 0x0
[ 701.903836] ata2.00: irq_stat 0x40000008
[ 701.903838] ata2: SError: { 10B8B }
[ 701.903842] ata2.00: failed command: READ FPDMA QUEUED
[ 701.903847] ata2.00: cmd 60/00:18:8a:46:38/04:00:3a:00:00/40 tag 3 ncq 524288 in
[ 701.903848] res 41/40:00:ec:47:38/00:00:3a:00:00/40 Emask 0x409 (media error) <F>
[ 701.903851] ata2.00: status: { DRDY ERR }
[ 701.903853] ata2.00: error: { UNC }
[ 701.903860] ata2: hard resetting link
[ 702.361027] ata2: softreset failed (device not ready)
[ 702.361031] ata2: applying SB600 PMP SRST workaround and retrying
[ 702.514037] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 702.526095] ata2.00: configured for UDMA/133
[ 702.526107] ata2: EH complete
[ 705.151245] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[ 705.151248] ata2.00: irq_stat 0x40000008
[ 705.151252] ata2.00: failed command: READ FPDMA QUEUED
[ 705.151258] ata2.00: cmd 60/00:00:8a:46:38/04:00:3a:00:00/40 tag 0 ncq 524288 in
[ 705.151259] res 41/40:00:ec:47:38/00:00:3a:00:00/40 Emask 0x409 (media error) <F>
[ 705.151261] ata2.00: status: { DRDY ERR }
[ 705.151263] ata2.00: error: { UNC }
[ 705.155871] ata2.00: configured for UDMA/133
[ 705.155880] ata2: EH complete
[ 707.766908] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[ 707.766911] ata2.00: irq_stat 0x40000008
[ 707.766915] ata2.00: failed command: READ FPDMA QUEUED
[ 707.766921] ata2.00: cmd 60/00:00:8a:46:38/04:00:3a:00:00/40 tag 0 ncq 524288 in
[ 707.766922] res 41/40:00:ec:47:38/00:00:3a:00:00/40 Emask 0x409 (media error) <F>
[ 707.766924] ata2.00: status: { DRDY ERR }
[ 707.766926] ata2.00: error: { UNC }
[ 707.771945] ata2.00: configured for UDMA/133
[ 707.771958] ata2: EH complete
[ 710.382561] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[ 710.382564] ata2.00: irq_stat 0x40000008
[ 710.382568] ata2.00: failed command: READ FPDMA QUEUED
[ 710.382574] ata2.00: cmd 60/00:00:8a:46:38/04:00:3a:00:00/40 tag 0 ncq 524288 in
[ 710.382575] res 41/40:00:ec:47:38/00:00:3a:00:00/40 Emask 0x409 (media error) <F>
[ 710.382577] ata2.00: status: { DRDY ERR }
[ 710.382579] ata2.00: error: { UNC }
[ 710.387019] ata2.00: configured for UDMA/133
[ 710.387027] ata2: EH complete
[ 712.998224] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[ 712.998228] ata2.00: irq_stat 0x40000008
[ 712.998231] ata2.00: failed command: READ FPDMA QUEUED
[ 712.998237] ata2.00: cmd 60/00:00:8a:46:38/04:00:3a:00:00/40 tag 0 ncq 524288 in
[ 712.998238] res 41/40:00:ec:47:38/00:00:3a:00:00/40 Emask 0x409 (media error) <F>
[ 712.998241] ata2.00: status: { DRDY ERR }
[ 712.998242] ata2.00: error: { UNC }
[ 713.003094] ata2.00: configured for UDMA/133
[ 713.003102] ata2: EH complete
[ 715.613926] ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[ 715.613930] ata2.00: irq_stat 0x40000008
[ 715.613933] ata2.00: failed command: READ FPDMA QUEUED
[ 715.613939] ata2.00: cmd 60/00:00:8a:46:38/04:00:3a:00:00/40 tag 0 ncq 524288 in
[ 715.613941] res 41/40:00:ec:47:38/00:00:3a:00:00/40 Emask 0x409 (media error) <F>
[ 715.613943] ata2.00: status: { DRDY ERR }
[ 715.613945] ata2.00: error: { UNC }
[ 715.619139] ata2.00: configured for UDMA/133
[ 715.619153] sd 1:0:0:0: [sdb] Unhandled sense code
[ 715.619155] sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
[ 715.619158] sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
[ 715.619162] Descriptor sense data with sense descriptors (in hex):
[ 715.619163] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 715.619169] 3a 38 47 ec
[ 715.619172] sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4
[ 715.619175] sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 3a 38 46 8a 00 04 00 00
[ 715.619181] end_request: I/O error, dev sdb, sector 976766956
[ 715.619206] I/O error in filesystem ("sdb1") meta-data dev sdb1 block 0x3a383a4b ("xlog_bread") error 5 buf count 209715
?
~5 years old WD3000, you think ? WRONG !
~1.5 year old WD10EADS ? wrong again.
it's ~1 year old WD10EADS with magnificent "advanced extended power saving feature" bull**bleep**.
saw LCC difference on same model ? or is it almost "same" ?
actually, some time ago those two were "falling out" synchronly, sometimes brought back by drive auto hard reset via kernel or something, sometimes don't. after playing with wdidle 2 month ago (which was a bummer to find, as you may know) they (two 10EADSs) stopped to "fall out"... until today when WD10EADS-00M2B0 even stopped being detected by BIOS from time to time :\
i don't know if it will "calm down" again nor i have space to back up data, nor i have shop's 10 month warranty anymore (which would not helped since i don't have space). thank you, WD's "engineers"-creators of such wonderfull feature.
no doubt the next will be other 10EADS, then 15EARS, and only then - the oldest son of the b^Hfactory...
as always - you going with the lowest bidder and this is what you get. even if hardware itself is ok at first.
by the way - after playing with wdidle, LCC stopped rising on them at any time other than per each power cycle.
what sould i do now ?
"shoot" them out of their missery and drop them in a garbage bin ? beg for indulgence of local WD representation and ask them for replacement of both 10EADS, forgetting about data, and hoping that new ones will not fail same way ?
i believe its about ~100km from my place and drive there (twice at least) will cost 1/3 of new drive (a pun !) and i was collecting that data for long [delete] time 
not cool, WD, not cool at all.
PS: i also "evaluated" and "appreciated" other WD15EARS (which was not "falling out" yet) feature - LYING about its physical sector size. oh, guys, i cannot express with words even in my native language how it was "enjoyable" to manually correctly allign 4 partitions on it and to calculate all this crap. finding tools with option to ignore DOS resctrictions was just a beggining.. and all in a sake of even more alienated WinXP users. but it's a different story.
PPS: it would be a good idea to fix your forum's "spoiler" tag not to fail with "Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed." obscure message.
it also ugly and hurts eyes, every letter written here is painfull, litteraly, not counting cut open finger (while detaching drive's cords, so drive would not injure itself further). so much pain... for my own money >:{
Great SCOTT,
This situation has gotten out of hand, at least for WD20EARS owners! Look I've done over two weeks of research prior to updating my hard drive with "Wdidle3". I actually bought my 2TB hard drive knowing that the LCC problem existed... Call me a risk taker... Actually smarter than you think, I bought the drive, formatted, partitioned, threw some data on it to see if it worked quick, and put the thing away until I found a solid solution. So as I mentioned before I did some serious research and found a simple yet effective way of fixing the 8 second idle time, to 5 mins which could potentially expand the life of your hard drive.
Here are my findings with absolute instructions on how you can create a USB DOS bootable stick, with "Wdidle3" on it. It's fairly simple with pictures and all. I've read many way's on how to create a DOS cd, USB DOS stick, etc. But they were all too complicated, and contained links to expired pages. My method is by far the EASIEST you will ever encounter. 5 mins idle time is recommended by Synology, and also the max idle time on the "Wdidle3" 30-300 second setting info. I wouldn't disable head parking indefinitely because head parking can STILL protect the drive. For those of you wondering the data I had on the hard drive did survive after the "Wdidle3" update [hehehe of course it would, it's just a firmware update]. In any case here's a link to my well thought out instructions:
HOW TO CREATE A DOS BOOTABLE USB STICK CONTAINING WDIDLE3
I'm an 11 year computer technician with A+ Certification knowledge...
P.s.
WD you totally suck for this, sure I bought my massive 2TB WD20EARS for $109. But at the cost of two weeks research... & for Pete's sake update your "Wdidle3" download page with information about other supported hard drives. From my experience the drive is quiet, fast in my Nexstar MX USB hdd enclosure, and really heavy! Oh did I forget to mention the fact that I also had to REALIGN the darn thing after formatting/partitioning the hard drive when I first purchased it for use under Win XP? Geez...
 Copyright © 2001 - 2010 Western Digital Corporation, All rights reserved. | Trademarks | Privacy | Terms of Service | Terms of Use | Copyright | Contact WD |
 |