Recovery Force® Data Recovery Forum

Hello,

A piece of advice if you could, folks!

I have a WDC WD2002FAEX-007BA0 and ran MHDD twice over it. Both times I got:

------------------------------------------------------------------------------------------------------------------------------------------
16.04.2015 10:51:01 MHDD>MAKELOG
16.04.2015 10:51:01 WDC WD2002FAEX-007BA0 LBA: 3,907,029,168
16.04.2015 10:51:01 SN: WD-WCAY00545812 FW: 05.01D05
16.04.2015 10:51:01 Scan started
16.04.2015 10:51:01 MODE: IDE
16.04.2015 10:51:01 Making advanced log.
16.04.2015 10:51:01 Device: WDC WD2002FAEX-007BA0
16.04.2015 10:51:01 F/W: 05.01D05
16.04.2015 10:51:01 SN: WD-WCAY00545812
16.04.2015 10:51:01 -------------------------------
16.04.2015 10:51:01 Lap : 1
16.04.2015 10:51:01 LBA scan: 0 to 3907029167
16.04.2015 12:45:50 þ LBA Warning: 1889627775
16.04.2015 15:32:16 Time spent: 04:41:13
16.04.2015 15:32:16 Blocks < 3ms = 15308576
16.04.2015 15:32:16 Blocks < 10ms = 12974
16.04.2015 15:32:16 Blocks < 50ms = 133
16.04.2015 15:32:16 Blocks < 150ms = 0
16.04.2015 15:32:16 Blocks < 500ms = 1
16.04.2015 15:32:16 Blocks > 500ms = 0
16.04.2015 15:32:16 Errors: 0, Warnings: 1
16.04.2015 15:32:16 Done
16.04.2015 15:41:11
16.04.2015 15:41:11 MHDD>MAN LOG
16.04.2015 15:41:22
16.04.2015 15:41:22 MHDD>MAN EN LOG
16.04.2015 15:41:29
16.04.2015 15:41:29 MHDD>EXIT
16.04.2015 15:41:29 MHDD: Exit
18.04.2015 3:29:49
18.04.2015 3:29:49
18.04.2015 3:29:49 | MHDD 4.6 (c) Dmitry Postrigan | FREEWARE
18.04.2015 3:29:49 Changing mode to: IDE
18.04.2015 3:29:59
18.04.2015 3:29:59 MHDD>EID
18.04.2015 3:29:59 WDC WD2002FAEX-007BA0 LBA: 3,907,029,168
18.04.2015 3:29:59 SN: WD-WCAY00545812 FW: 05.01D05
18.04.2015 3:30:14
18.04.2015 3:30:14 MHDD>PORT
18.04.2015 3:30:16 Changing mode to: IDE
18.04.2015 3:30:16 Device selected: 8
18.04.2015 3:30:21
18.04.2015 3:30:21 MHDD>MAKELOG
18.04.2015 3:30:22 WDC WD2002FAEX-007BA0 LBA: 3,907,029,168
18.04.2015 3:30:22 SN: WD-WCAY00545812 FW: 05.01D05
18.04.2015 3:30:22 Scan started
18.04.2015 3:30:22 MODE: IDE
18.04.2015 3:30:22 Making advanced log.
18.04.2015 3:30:22 Device: WDC WD2002FAEX-007BA0
18.04.2015 3:30:22 F/W: 05.01D05
18.04.2015 3:30:22 SN: WD-WCAY00545812
18.04.2015 3:30:22 -------------------------------
18.04.2015 3:30:22 Lap : 1
18.04.2015 3:30:22 LBA scan: 0 to 3907029167
18.04.2015 5:25:14 þ LBA Warning: 1889627775
18.04.2015 8:11:36 Time spent: 04:41:12
18.04.2015 8:11:36 Blocks < 3ms = 15308546
18.04.2015 8:11:36 Blocks < 10ms = 13001
18.04.2015 8:11:36 Blocks < 50ms = 136
18.04.2015 8:11:36 Blocks < 150ms = 0
18.04.2015 8:11:36 Blocks < 500ms = 1
18.04.2015 8:11:36 Blocks > 500ms = 0
18.04.2015 8:11:36 Errors: 0, Warnings: 1
18.04.2015 8:11:36 Done
------------------------------------------------------------------------------------------------------------------------------------------

1) What is LBA Warning? Couldn't find this on FAQ, documentation neither on internet.

2) I have one block < 500ms. How can I check which block is that for each run, so I can see if the slow block is the same. Is it enough for a remap? Can I remap just this single block? Is it worth? This is an online backup drive, I need stable, good drives! Please advise.

Thank you!

The warning is for this:

18.04.2015 5:25:14 þ LBA Warning: 1889627775

As it was the same sector each time, it could be a weak spot on the drive.

Is there data on the drive that isn't 100% backed up?

Hello, Luke!

Thanks for your reply!

It isn't, but I''ll arrange it. What about other questions? Also, can/should I mark this block (or set of blocks) as bad? What you recommend?

Thank you!

After you get the data backed up, you can try the remap or the write slow reads.

A full erase may correct it too. Drive is still good, but you should be sure to keep a good backup and check the drive every now and then.

Yes I agree with Luke, the drive may still work for a long time with just an area of slow reading sectors. However I wouldn't trust it with any data that's not backed up as drives like that can quickly degrade even fail completely in some cases. Also in the future before running drive intensive tasks like MHDD it's best to have a current backup. Sometimes even a scan like that can kill a drive.

I see. Now a following question. I''ve scanned a next HDD (Seagate - Enterprise tie), and got a more worrying result:

________________________________________________________________________________________________
MHDD>MAKELOG
18.04.2015 17:54:20 Scan started
18.04.2015 17:54:20 MODE: IDE
18.04.2015 17:54:20 Making advanced log.
18.04.2015 17:54:20 Device: ST4000NM0033-9ZM170
18.04.2015 17:54:20 F/W: SN03
18.04.2015 17:54:20 SN: Z1Z0YGLS
18.04.2015 17:54:20 -------------------------------
18.04.2015 17:54:20 Lap : 1
18.04.2015 17:54:20 LBA scan: 0 to 3519069871
18.04.2015 17:56:23 þ LBA Warning: 45662850
18.04.2015 17:57:47 þ LBA Warning: 76642035
18.04.2015 17:58:19 þ LBA Warning: 88923855
18.04.2015 17:58:28 þ LBA Warning: 92173065
18.04.2015 18:01:14 þ LBA Warning: 153954720
18.04.2015 18:02:02 þ LBA Warning: 172196655
18.04.2015 18:02:11 þ LBA Warning: 175452750
18.04.2015 18:03:18 þ LBA Warning: 200422605
18.04.2015 18:03:35 þ LBA Warning: 206934285
18.04.2015 18:03:49 þ LBA Warning: 212361450
18.04.2015 18:04:15 þ LBA Warning: 222117495
18.04.2015 18:04:33 þ LBA Warning: 228600105
18.04.2015 18:04:47 þ LBA Warning: 233781705
18.04.2015 18:05:13 þ LBA Warning: 243516330
18.04.2015 18:06:02 þ LBA Warning: 261966345
18.04.2015 18:06:51 þ LBA Warning: 280390350
18.04.2015 18:07:09 þ LBA Warning: 286878060
18.04.2015 18:08:16 þ LBA Warning: 312134025
18.04.2015 18:08:49 þ LBA Warning: 324303900
18.04.2015 18:09:15 þ LBA Warning: 334084425
18.04.2015 18:10:55 þ LBA Warning: 371410815
18.04.2015 18:11:03 þ LBA Warning: 374672265
18.04.2015 18:12:44 þ LBA Warning: 412094025
18.04.2015 18:13:10 þ LBA Warning: 421851090
18.04.2015 18:14:41 þ LBA Warning: 456095805
18.04.2015 18:15:07 þ LBA Warning: 465762345
18.04.2015 18:15:47 þ LBA Warning: 481208970
18.04.2015 18:17:25 þ LBA Warning: 518694735
18.04.2015 18:18:15 þ LBA Warning: 537209520
18.04.2015 18:18:24 þ LBA Warning: 540663240
18.04.2015 18:18:51 þ LBA Warning: 550415715
18.04.2015 18:19:41 þ LBA Warning: 569015670
18.04.2015 18:21:49 þ LBA Warning: 617122185
18.04.2015 18:22:20 þ LBA Warning: 628504875
18.04.2015 18:23:44 þ LBA Warning: 660103965
18.04.2015 18:23:53 þ LBA Warning: 663307785
18.04.2015 18:28:20 þ LBA Warning: 761736255
18.04.2015 18:31:27 þ LBA Warning: 830719875
18.04.2015 18:32:06 þ LBA Warning: 844905525
18.04.2015 18:33:30 þ LBA Warning: 876177705
18.04.2015 18:33:53 þ LBA Warning: 884606985
18.04.2015 18:35:19 þ LBA Warning: 916241265
18.04.2015 18:35:37 þ LBA Warning: 922637430
18.04.2015 18:36:01 þ LBA Warning: 931486185
18.04.2015 18:37:08 þ LBA Warning: 956316810
18.04.2015 18:38:43 þ LBA Warning: 991236765
18.04.2015 18:41:38 þ LBA Warning: 1055240745
18.04.2015 18:42:02 þ LBA Warning: 1064028045
18.04.2015 18:51:21 þ LBA Warning: 1270516335
19.04.2015 0:24:16 þ LBA Warning: 2773700279
19.04.2015 1:25:34 þ LBA Warning: 3476104664
19.04.2015 1:29:43 Time spent: 07:35:21
19.04.2015 1:29:43 Blocks < 3ms = 30609734
19.04.2015 1:29:43 Blocks < 10ms = 30301
19.04.2015 1:29:43 Blocks < 50ms = 417
19.04.2015 1:29:43 Blocks < 150ms = 2781
19.04.2015 1:29:43 Blocks < 500ms = 51
19.04.2015 1:29:43 Blocks > 500ms = 0
19.04.2015 1:29:43 Errors: 0, Warnings: 51
19.04.2015 1:29:43 Done
________________________________________________________________________________________________

There are no bad blocks, but 51 < 500ms. So, my question is: what is the usual procedure? I am not asking a rule of thumb, but just parameters from your experience, folks. For example:

If no problems showing during routine activities, just < 50ms: do nothing and be happy;
If any < 500ms: backup and scan + remap. (or full erase first then scan + remap?)
If any > 500ms: what?
*assuming constant online backup for all cases ever.

From which point RMA usually qualifies?

Luke, Jared, thank you very much for answering on a sunday!!

Although most drives read a sector within a few ms, it is not uncommon to get some sectors that may require more time. With MHDD, a sector that takes 151ms is lumped in the same group as a sector that takes 499ms to respond. So, again, good backups and regular maintenance is a good way to prevent unnecessary data loss.

At the same time, you can regularly check the SMART to see the number of bad sectors it has logged. If you notice a significant number or a frequent incline, it is a good time to just retire the drive.

To answer your question about RMA, I don't believe most manufacturers will accept returns unless it at least has some actual bad/remapped sectors accd. to the S.M.A.R.T. data. So that's usually a good place to check. If you get SMART errors, you can generally RMA.

And is a remap from MHDD accd. to SMART? I mean, if I scan+remap and one or some blocks are effectively remapped, is this data accd. to SMART and hence RMA'able?

If your goal is to RMA the drive, download the Seagate diagnostic tools from Seagate and run their tests. If it passes, no RMA. If it fails, RMA.