Dreadfully slow WD15EADS - 00P8B0 1.5TB

[masbass]

Hello all,
I have a Western Digital WD15EADS-00P8B0 1.5TB (32MB CACHE) (with NTFS uncompressed) that runs at excruciatingly slow speeds as less and less space is left on the drive. To use it (kinda) efficiently I need to leave more than 100GB free, and even then, copying speeds are quite low. As I fill it up and reach the 30GB free space, any file copy takes hours and even errors out. These green drives are dreadful and what I'd like to know is whether there is some kind of format procedure or factory settings tweaking that I could do to make it a usable drive. Any tip would be appreciated.

[Vulcan]

As I fill it up and reach the 30GB free space, any file copy takes hours and even errors out. These green drives are dreadful and what I'd like to know is whether there is some kind of format procedure or factory settings tweaking that I could do to make it a usable drive. Any tip would be appreciated.

What you are describing is abnormal and suggests the drive is probably faulty. More details are needed in order to try to better understand the problem, including:

What is the history of the drive - any mechanical shocks or other unusual events?

Collect the full raw SMART data, for review (do NOT perform any SMART or other disk tests).

What are the exact errors that you mention during file copying?

Do you need the data from this disk or are you just looking to make the disk reliable and the data is already backed-up elsewhere?

[masbass]

This drive is used as a backup drive, just storing files that aren't accessed frequently anymore, and never leaves the house. It's almost always turned off in its USB enclosure and I use it only when I want to copy files there, not as a live, always connected to PC drive. No falls or shocks up to now. When I go home I'll look at the SMART data and post them here.

File copying starts normally, and then after a short while data transfer speed drops and drops and drops and if you leave it copying it even disconnects and you get a device not found from Windows. From what I read around it seems many WD green drives like mine had a bug in their firmware and were practically useless (imagine trying to run an OS on top of that mess) but I haven't found any solution to that no matter how much I googled.

I need the data from this disk and will try to empty it before executing any changes (that will take a while...)

[einstein9]

This drive is used as a backup drive, just storing files that aren't accessed frequently anymore, and never leaves the house. It's almost always turned off in its USB enclosure and I use it only when I want to copy files there, not as a live, always connected to PC drive. No falls or shocks up to now. When I go home I'll look at the SMART data and post them here.

File copying starts normally, and then after a short while data transfer speed drops and drops and drops and if you leave it copying it even disconnects and you get a device not found from Windows. From what I read around it seems many WD green drives like mine had a bug in their firmware and were practically useless (imagine trying to run an OS on top of that mess) but I haven't found any solution to that no matter how much I googled.

I need the data from this disk and will try to empty it before executing any changes (that will take a while...)

connect it via USB and check the events viewer , sure you will see bad sectors, if that is the case, you will need to seek a pro to help you
good luck

[Vulcan]

@masbass,

Thanks for the info so far. Here are my comments (all IMHO) based on what you've said. Other people may have different views.

This drive is used as a backup drive

Without wanting to be pedantic, since you say that you need files which only exist on the drive, that isn't what most people would call a backup (i.e. it isn't another copy of data which exists elsewhere also). The point is that this news changes the whole risk/reward ratio, if the data on this drive is important to you. Any DIY recovery attempts may cause further / faster deterioration of what is likely to be an already-failing drive. If you are lucky, you might recover most or all of what you need; if you're unlucky or make mistakes, then you won't and your attempts may make any later professional recover harder and/or more expensive or, in the worst case, impossible.

just storing files that aren't accessed frequently anymore, and never leaves the house. It's almost always turned off in its USB enclosure and I use it only when I want to copy files there, not as a live, always connected to PC drive. No falls or shocks up to now.

OK, so no hints there what may have triggered the problem.

When I go home I'll look at the SMART data and post them here.

Thanks - remember, the full, raw SMART values are needed, in addition to the usual "value, worst, threshold" SMART values for each attribute. As einstein9 mentioned, some unreadable sectors are very likely - I'm interested to see that info (SMART attribute #5) and other attribute values, to see how severe the drive thinks the current situation is.

File copying starts normally, and then after a short while data transfer speed drops and drops and drops and if you leave it copying it even disconnects and you get a device not found from Windows.

OK, that still fits with a possible drive fault.

From what I read around it seems many WD green drives like mine had a bug in their firmware and were practically useless (imagine trying to run an OS on top of that mess) but I haven't found any solution to that no matter how much I googled.

Your problem description is so severe that I don't believe you have a f/w fault. However if that is the only path you want to persue, just say so and I'll leave you to it and wish you good luck.

I need the data from this disk and will try to empty it before executing any changes (that will take a while...)

As I mentioned above, DIY recovery attempts have risks, which you need to consider and accept before you continue.

You have 2 basic options to try to get the data off the drive - either try to copy the files (if you only need a very small number of files, you might be lucky doing this although you've explained that your drive won't successfully copy for long), or cloning the whole drive to another empty, working, 1.5TB or larger drive, using software which can cope with (and has some error recovery control regarding) unreadable sectors. There are a few choices for cloning software depending on your budget (some are commercial, some are free), your expectations regarding features (GUI or CLI, supported or not, degree of control etc.), your skills with other OS (some are Linux/Unix, some are Windows, some are DOS etc.). In my (non-DR) work, if I need to do this, I use GNU ddrescue on *nix, but that is unlikely to be suitable for you unless you have some *nix experience, and even then, it is not a "one click" utility. Other previous recommendations from other members include DMDE, Media Tools Pro, HDClone etc. Do not try to use Ghost, Acronis, XXLClone etc. as they are not designed specifically to cope with failing disks. You must get the direction of the clone (source vs. target) correct, otherwise you irreversibly erase your data!

Unless your USB enclosure (which I guess was one you bought and fitted the drive into) does encryption, then in general it is usually more successful to clone when the failing drive is removed from the USB enclosure & attached via (S)ATA instead of USB. The (empty, working) 1.5TB or larger target drive of the clone can be USB-attached, since we don't expect it'll need error recovery to occur during the clone. If your enclosure does do encryption then this needs to be investigated further to decide on your options.

Overall, unless you need only a few files, then cloning the whole drive (or at least the partitions containing data, is that is much less than the whole drive) with suitable software is generally recommended - but you're still taking a risk whatever you do. (I believe that DMDE has some features in this area to minimise what needs to be cloned, assuming that the MFT is readable, but that isn't software I've investigated myself, as I can't use it at work.)

If the data has more than minimal value to you, you may want to consider using the services of a DR company, if they have dedicated cloning devices (many companies do), as those devices will typically do a better (more successful & less risky) job of cloning a failing disk. Your data, your risk, your choice!

[masbass]

Thanks for your replies, it seems the hard drive is performing better when there's more empty space left. So, it would take some hours to unload the first 50-100GB, clear some space by deleting the salvaged files and then the next copy will be faster etc. I just need to do the first files in small 5GB chunks (no problem there as most are already large files) and they will hopefully be transferred at a reasonable rate. I can access the drive normally and open / view all files I randomly try, it's just excruciatingly slow and from what I read on the internet ( http://bit.ly/HO03Z0 or http://bit.ly/HO0liI or http://bit.ly/HYIhAY ) it seems this is a known issue among many WD Green drives (no solution found though). Here is the SMART data

Code:

    Model: WDC WD15EADS-00P8B0                 
Firmware: 01.00A01                           
   Serial: WD-WCAVU0122010                     
Disk size: 2930277168 LBAs            1430799 Mb
      CHS: 16383/16/63                8063 Mb 
    SMART: Enabled, Errlog, Selftest           
    CACHE: 32767k; L/A=ON; Wr=ON;     ok       
  Support: LBA, AAM, DLM, DMA         UDMA-6   
  AAM val: 254                        Maximum 
    Erase: ~344 minutes                       
Security: OFF, Frozen                         
    ATA-8: SCT, SFDLM, WrUnk                   

-------------------------------------------------------------------------
  ID      Name                   Value  Worst  Tresh       Raw    Health
-------------------------------------------------------------------------
  1 Raw read error rate           200    200     51            0   •••••
  3 Spin-up time                  180    180     21         5975   •••••
  4 Number of spin-up times       100    100      0           69   •••••
  5 Reallocated sector count      200    200    140            0   •••••
  7 Seek error rate               100    253      0            0   •••••
  9 Power-on time                  99     99      0         1282   •••• 
10 Spin-up retries               100    253      0            0   •••••
11 Recalibration retries         100    253      0            0   •••••
12 Start/stop count              100    100      0           23   •••••
192 Power-off retract count       200    200      0            8   •••••
193 Load/unload cycle count       200    200      0          166   •••••
194 HDA Temperature               121    107      0    29°C/84°F   •••• 
196 Reallocated event count       200    200      0            0   •••••
197 Current pending sectors       200    200      0            0   •••••
198 Offline scan UNC sectors      200    200      0            0   •••••
199 Ultra DMA CRC errors          200    200      0            0   •••••
200 Multi zone error rate         200    200      0            0   •••••


[Vulcan]

from what I read on the internet ( http://bit.ly/HO03Z0 or http://bit.ly/HO0liI or http://bit.ly/HYIhAY ) it seems this is a known issue among many WD Green drives (no solution found though).

Oh yes, it's known all right - just not shown to be a f/w problem, which was what you said earlier on. We're agreed there are similar problems (with varying degress of severity, and varying results to "workaround" attempts) being reported by many users

Here is the SMART data

Thanks for that. Disappointingly, I see nothing abnormal, but as always - lack of problem seen in the SMART data does not prove that no problem exists.

There are other diagnostic tests which could be run, but getting that data off the disk should be the priority IMHO, and I've already given suggestions about that (which didn't include doing file copies for large amounts of data, as you've decided to do). Good luck

[masbass]

hmmm... problem with cloning is that I have no 1.5 TB disk available. My brother can lend me a 1TB he has and if I delete around 600GB duplicate files (files I have already stored elsewhere as well) I might be able to free enough space and make it work. The files inside this HD are not unique / personal / work related, they're mostly stuff like documentaries, tv series etc that I can find again, so it's not a high importance file operation. I'll look on those windows/dos utilities you mentioned above and ask around for a 1.5TB disk (the way it works -if I remember well- in order to clone a disk one needs to have another disk with same size, even if the files to be salvaged take a lot less space ). Prices for new HDDs are way too expensive still so as the files are of minimal importance I'll try the cheap way. Will come back when disk is empty, thanks for your tips!

[masbass]

Ok, copied all data off the disk successfully, same pattern: at first, as the disk had about 30GB free it was copying at horrendously slow speeds, but as I was deleting the files that were copied away it went on it real fast. It is empty now, what checks do you want me to perform on it? I have downloaded Victoria and WD Data Lifeguard Diagnostics

[laptokowiec]

Scan it with MHDD.

[Keatah]

To me, this sounds like a logical or file layout problem as opposed to any impending doom with the mechanicals or electronics.

[Vulcan]

@Keatah,

To me, this sounds like a logical or file layout problem

Based on my experience, that hypothesis does not fit with this statement from the OP, which was in answer to one of my earlier questions:

if you leave it copying it even disconnects and you get a device not found from Windows

but I'm interested to hear your explanation for how a logical (filesystem) problem causes that behaviour.

IMHO the results of the MHDD scan, suggested above, will be interesting although I'm not prejudging how conclusive they will be.

[Keatah]

Apologies for not reading the details in the thread completely. I spoke before I thought it out completely too. I had the immediate idea the drive is thrashing all over the place, like being badly fragmented. Imagining the $MFT was in 200 pieces and each file triple that.. And so on and so forth.

But that's not likely being a "data-only" non-boot drive, isn't it..?

[Vulcan]

Understood - however as you now see, we have the OP's answer to my question providing evidence against it being that type of problem. Hopefully the results of benchmarking the drive itself (e.g. with MHDD Scan or similar) will give some food for thought.

[masbass]

Thanks for your answers, I'm trying to run MHDD on a small HDD in order to check the problematic drive as I need to somehow save the LOG files somewhere. The PC has no floppy and running MHDD from cd is read only. Is there a way to install MHDD on an HDD? I only find cd / floppy images and a copy of MHDD I installed on a FreeDOS partition doesn't see the disk at all (only two other SATAs plugged in next to it). Will try and switch cables (although the hdd I m running MHDD from is IDE and rightfully blocked from scanning).

Edit: something I noticed on the surface test MHDD was performing, there were distinct strong diagonal patterns all over the drive as the drive map was scrolling down. I did some tests on my other drives (and one was found to be in really bad shape and will be replaced) and I hadn't seen those stripes as evident as on the one I'm discussing above. Could this be a clue of some sort? Strong fragmentation maybe? Wouldn't that be fixed by formatting the drive and recopying all there or are file fragments copied along from HD to HD?

[Vulcan]

Since the suggestion to use MHDD was given by laptokowiec and not me, I don't want to "step on his toes" with whatever he will reply, now that you are following his suggestion so I'll just make a couple of brief comments:

Edit: something I noticed on the surface test MHDD was performing, there were distinct strong diagonal patterns all over the drive as the drive map was scrolling down. I did some tests on my other drives (and one was found to be in really bad shape and will be replaced) and I hadn't seen those stripes as evident as on the one I'm discussing above.

It is normal for those patterns to vary between different drive families.

Could this be a clue of some sort? Strong fragmentation maybe?

Fragmentation is a filesystem concept. MHDD accesses the raw drive, bypassing (i.e. ignoring) any filesystem, and so filesystem fragmentation (if it exists) would be irrelevant.

Wouldn't that be fixed by formatting the drive and recopying all there or are file fragments copied along from HD to HD?

I don't understand your exact suggestion, but "file fragments" (if any) have no effect on MHDD results, as I explained before.

I don't know exactly how laptokowiec will suggest you to use MHDD & to report its results (there are at least a couple of different techniques), but I hope my comments avoid you spending further time guessing about "file fragmentation" causing the diagonal patterns.

[masbass]

I see, thanks. I managed to load MHDD on a bootable USB stick with FreeDOS and here is the LOG saved there. I did this scan using the default MHDD settings, is there some other set of options you want me to run MHDD with? I saw in the MHDD manual that the procedure is: scan -> erase -> scan again. Any tips are welcome.

Code:

4.05.2012   1:47:17   MHDD>PORT
4.05.2012   1:47:38   Changing mode to: IDE
4.05.2012   1:47:38   Device selected: 4
4.05.2012   1:47:40   
4.05.2012   1:47:40   MHDD>SCAN
4.05.2012   1:47:40   WDC WD15EADS-00P8B0  LBA: 2,930,277,168
4.05.2012   1:47:40   SN: WD-WCAVU0122010  FW: 01.00A01
4.05.2012   1:47:54   Scan started
4.05.2012   1:47:54   MODE: IDE
4.05.2012   1:47:55   Device: WDC WD15EADS-00P8B0
4.05.2012   1:47:55   F/W: 01.00A01
4.05.2012   1:47:55   SN: WD-WCAVU0122010
4.05.2012   1:47:55   -------------------------------
4.05.2012   1:47:55   Lap : 1
4.05.2012   1:47:55   LBA scan: 0 to 2930277167
4.05.2012   1:52:47   ώ LBA warning: 57082515
4.05.2012   1:56:10   ώ LBA warning: 96670500
4.05.2012   2:03:39   ώ LBA warning: 184779375
4.05.2012   2:03:42   ώ LBA warning: 184932885
4.05.2012   2:04:23   ώ LBA warning: 192613230
4.05.2012   2:09:55   ώ LBA warning: 257695095
4.05.2012   3:09:02   ώ LBA warning: 918712470
4.05.2012   3:12:40   ώ LBA warning: 957505875
4.05.2012   3:13:14   ώ LBA warning: 963135765
4.05.2012   3:14:46   ώ LBA warning: 979368555
4.05.2012   3:22:55   ώ LBA warning: 1064233320
4.05.2012   3:33:31   ώ LBA warning: 1174331865
4.05.2012   3:40:00   ώ LBA warning: 1240067550
4.05.2012   6:25:24   ώ LBA warning: 2649379365
4.05.2012   7:12:03   Time spent: 05:24:06
4.05.2012   7:12:03    Blocks <   3ms = 11070240
4.05.2012   7:12:03    Blocks <  10ms = 420570
4.05.2012   7:12:03    Blocks <  50ms = 460
4.05.2012   7:12:03    Blocks < 150ms = 0
4.05.2012   7:12:03    Blocks < 500ms = 0
4.05.2012   7:12:03    Blocks > 500ms = 14
4.05.2012   7:12:03   Errors: 0, Warnings: 14
4.05.2012   7:12:03   Done
4.05.2012   7:12:05   WDC WD15EADS-00P8B0  LBA: 2,930,277,168
4.05.2012   7:12:05   SN: WD-WCAVU0122010  FW: 01.00A01


[masbass]

so, I erased the disk and reran scan and here is the log:

Code:

12.05.2012  10:25:26   MHDD>ERASE
12.05.2012  10:25:26   WDC WD15EADS-00P8B0  LBA: 2,930,277,168
12.05.2012  10:25:26   SN: WD-WCAVU0122010  FW: 01.00A01
12.05.2012  18:09:06   
12.05.2012  18:09:06   MHDD>EXIT
12.05.2012  18:09:06   MHDD: Exit
12.05.2012  21:46:59   
12.05.2012  21:46:59   
12.05.2012  21:46:59    | MHDD 4.6 (c) Dmitry Postrigan | FREEWARE
12.05.2012  21:46:59   Changing mode to: IDE
12.05.2012  21:47:01   
12.05.2012  21:47:01   MHDD>EID
12.05.2012  21:47:02   WDC WD15EADS-00P8B0  LBA: 2,930,277,168
12.05.2012  21:47:02   SN: WD-WCAVU0122010  FW: 01.00A01
12.05.2012  21:47:04   WDC WD15EADS-00P8B0  LBA: 2,930,277,168
12.05.2012  21:47:04   SN: WD-WCAVU0122010  FW: 01.00A01
12.05.2012  21:47:11   
12.05.2012  21:47:11   MHDD>PORT
12.05.2012  21:47:15   Changing mode to: IDE
12.05.2012  21:47:15   Device selected: 4
12.05.2012  21:47:17   
12.05.2012  21:47:17   MHDD>I
12.05.2012  21:47:18   WDC WD15EADS-00P8B0  LBA: 2,930,277,168
12.05.2012  21:47:18   SN: WD-WCAVU0122010  FW: 01.00A01
12.05.2012  21:47:22   
12.05.2012  21:47:22   MHDD>SCAN
12.05.2012  21:47:39   Scan started
12.05.2012  21:47:39   MODE: IDE
12.05.2012  21:47:39   REMAP: ON
12.05.2012  21:47:39   Device: WDC WD15EADS-00P8B0
12.05.2012  21:47:39   F/W: 01.00A01
12.05.2012  21:47:39   SN: WD-WCAVU0122010
12.05.2012  21:47:39   -------------------------------
12.05.2012  21:47:39   Lap : 1
12.05.2012  21:47:39   LBA scan: 0 to 2930277167
12.05.2012  21:49:11   ώ LBA warning: 17544765
12.05.2012  21:49:22   ώ LBA warning: 19332825
12.05.2012  21:52:07   ώ LBA warning: 51441405
12.05.2012  21:57:56   ώ LBA warning: 119748255
12.05.2012  22:03:18   ώ LBA warning: 182967855
12.05.2012  22:05:06   ώ LBA warning: 203865615
12.05.2012  22:15:05   ώ LBA warning: 320253225
12.05.2012  22:15:07   ώ LBA warning: 320255265
12.05.2012  22:47:19   ώ LBA warning: 684728295
12.05.2012  23:10:46   ώ LBA warning: 939023475
12.05.2012  23:11:40   ώ LBA warning: 948409260
12.05.2012  23:14:25   ώ LBA warning: 977581770
12.05.2012  23:15:08   ώ LBA warning: 984877575
12.05.2012  23:15:40   ώ LBA warning: 990288675
12.05.2012  23:17:46   ώ LBA warning: 1011947610
12.05.2012  23:18:20   ώ LBA warning: 1017611160
12.05.2012  23:22:50   ώ LBA warning: 1064233320
12.05.2012  23:24:05   ώ LBA warning: 1076830320
12.05.2012  23:29:39   ώ LBA warning: 1134514125
12.05.2012  23:35:56   ώ LBA warning: 1199387145
13.05.2012   0:46:39   ώ LBA warning: 1876949175
13.05.2012   3:12:00   Time spent: 05:24:18
13.05.2012   3:12:00    Blocks <   3ms = 11076054
13.05.2012   3:12:00    Blocks <  10ms = 414743
13.05.2012   3:12:00    Blocks <  50ms = 465
13.05.2012   3:12:00    Blocks < 150ms = 1
13.05.2012   3:12:00    Blocks < 500ms = 0
13.05.2012   3:12:00    Blocks > 500ms = 21
13.05.2012   3:12:00   Errors: 0, Warnings: 21
13.05.2012   3:12:00   Done
13.05.2012   6:58:06   


[BlackST]

Each time you do something, bad blocks increase.
The solution do exist but unfortunately you can't do on your own.
Replace drive, RMA it if possible or live with it. Or refer to someone who can professionally refurbish it.
Final note : yoiu bought a cheap drive and what you pay is what you get.

[masbass]

Ah, it came inside a USB enclosure and I had no idea it would be so bad. Wouldn't it be better if I run MHDD again and delete those delaying blocks marking them as bad? I guess some more would appear soon though... At least no system is running from this HD and it's there just to store away stuff with minimal use.