Seagate Barracuda ES.2 0MB size w/ Error 1008 DETSEC

[Murtazah]

Hello Everyone,

I Have Seagate Barracuda ES.2 HP oem with Firmware HPG1.

Its showing in BIOS, but in windows disk management showing uninitialized and 0mb size.

Tried 0LBA method but getting following error.

F3 T>m0,2,2,0,0,0,0,22

Error 1008 DETSEC 0000500E Process Defect List Error
R/W Sense 00000002, R/W Error 841C0087, List Offset 00000000, File Error 00000001

I really need this drive data as this is 2nd failed drive out of RAID 5.

Anyone please help! Thanks in advance.

[hddguy]

Error 1008 DETSEC 0000500E Process Defect List Error
R/W Sense 00000002, R/W Error 841C0087, List Offset 00000000, File Error 00000001

I had a case similar to this, Primary defect table was damaged, Translator repair does not allow DRDY or good ID. After I solve error with defect list I could still only reach data through ESLIP mode in terminal.

[Murtazah]

Thanks for reply hddguy,

is there any possible solution to this?

what is ESLIP mode ( I am not so technical but surely can follow instructions ) , could you please post step by step instructions to follow to solve this issue.

Can i use data in ESLIP mode , means can i use it to create the image of the disk? so that i can regenerate the RAID5.

Any help is much appreciated.

[dmarques]

In terminal mode make an image is a very very very delayed task. Don't know if you have the time for it.

[hddguy]

Yes, is very slow process.

What is problem with other failed member? Maybe possibility to repair other disk will be simpler task

[Murtazah]

Other failed drive has got bad sectors. I made image of this drive and regenerated RAID 5 with missing drive option but the volume does not give correct directory listing and files are all scattered every where.

Any idea to get better image of drive affected with bad sectors?

Please also let me know how to get the image out of terminal mode and approx time it would take to make image of 750GB drive.

[dmarques]

First of all, on the the other drive, how much bad sectors do you have? Where are they located?

[hddguy]

I guess disk with bad sectors already failed and RAID run in degraded mode. I guess lots of data still would be good, but depending how old stale disk is could be lots of corrupt data.

To reach ESLIP translator command should complete successfully, in this case it does not. Make sure you have backup of all SA then identify which defect list is giving problem, bearing in mind if Primary list is replaced, modified or erased it will have affect on translator, also to remember that the secondary defect list also has influence on translator.

Can you check SA for errors?

[Murtazah]

dmarques thanks for quick reply.

Can you please let me know how can i show you where the bad sectors are located, is there any automated program which will capture all bad sectors? which I can post here for your reference.

[dmarques]

I don't know, you made the image, so what did you used for it?

[Murtazah]

How to check SA for Errors? Any terminal commands to follow?

Please forgive for these silly questions, but I really need help.

[Murtazah]

I have used r-studio for making and there were bad sectors on the top , just few minutes i will put list of errors found there.

[hddguy]

I made image of this drive and regenerated RAID 5 with missing drive option but the volume does not give correct directory listing and files are all scattered every where.

Are you sure RAID was built right?

Probably (I am certain) your RAID uses parity delay. Not supported in R-Studio (without custom blocks layout) which I assume you are using as this is what you used for creation of your image

[Murtazah]

No I used Zero Assumption Recovery for building raid by instructions provided by Reclaime.

Could you please give list of commands to follow for entering SA mode and checking it for errors. Do i need other program to use Service Area (SA) checking or it can be done in terminal mode.

[hddguy]

Can you write here XML data given to you by Reclaime?

It is not always correct.

You are checking your HDD with terminal only, or you have some other hardware utility for it?

[Murtazah]

ZAR 9.0

These instructions are provided for Zero Assumption Recovery starting with version 9 build 38
1. Launch Zero Assumption Recovery
2. Click "Data Recovery for Windows and Linux. This is OK because we've already done the RAID reconstruction.

3. Right click anywhere in the disk list, select "Load image file". Enter "E:\[IBI-B] GB0750EAFJKHPG1.dsk" as the file name, click "Open"
4. Right click anywhere in the disk list, select "Load image file". Enter "E:\[IBI-A] GB0750EAFJKHPG1.dsk" as the file name, click "Open"

5. Right click anywhere in the disk list, select "Define RAID manually".

6. From the "Available drives" list, select the image file with ID 0200, then click "Add".
7. From the "Available drives" list, select "Disk 3 - GB0750EAFJK", then click "Add".
8. From the "Available drives" list, select "Disk 0 - GB0750EAFJK", then click "Add".
9. From the "Available drives" list, select the image file with ID 0201, then click "Add".
10. From the "Available drives" list, select "Disk 4 - ATA GB0750EAFJK", then click "Add".
11. Next to the "Array members" table, click "Add parity".
12. From the "Array members" table, select the last entry (ID 0500). Click "Move up" 5 times. Verify that the parity drive (ID 0500) is at the row 1 (the top row is number 1).
13. On the right side under "Array configuration", set "RAID type" to "RAID5 (Checkerboard)".
14. Below that, set "Stripe size" to "128 sectors".
15. Below that, set "Parity start/rotation" to 5/5.
16. In the "Array members" table, enter "0,1465149168" as "Start, Size" in all rows.

17. Set "Parity delay, stripes" to 16.
18. Set "Stripes in first delayed block" to 16.

19. Click "OK". The warning message may appear stating that "Starting sectors and sizes are incorrect". Click "OK" to dismiss the message box, then click "OK" on the manual RAID setup form again to close the form. This is the expected behavior.
20. In the device list, "Virtual RAID #0" is the newly created RAID. Double click it to start recovery.

[hddguy]

OK, results look good.

If you get poor results with this then I must assume stale member has data that is too old.

Unfortunately I do not know what hardware you use, if anything. If access is through Terminal only then workings will be much more difficult and image through terminal not possible (as far as I know) without third party tool like Data Extractor

[Murtazah]

Data extractor ? where i can buy ? Is this hardware tool or software?

How can we check drive with bad sectors, to confirm that its data is stale and should not be used for recovery? Any specific terminal commands?

[dmarques]

It might be that one of the drives was out of the array for some time already.

[Murtazah]

May i Know how to repair this drive with "Error 1008 DETSEC 0000500E Process Defect List Error", because I see that is the only option i have.