SAMSUNG SP1614C LBA Errors

[cavefish]

This SAMSUNG SP1614C was running on a failing thermaltake power supply unit with bad caps.

Tested it with:

Hard Disk Sentinel

MHDD 4.6

HDAT2 v4.5.3

SMARTUDM - HDD S.M.A.R.T. Viewer 2.0

Hard Disk Sentinel reported health decreased from 90% to 70 %
MHDD shows 10 lba unc errors
HDAT2 sees 9

What else can I do, it's recoverable ?
Can I use it and partition around that area?

Attachments

SMARTUDM.RPT.TXT

(4.43 KiB) Downloaded 622 times

HDAT2_0Y127423.LOG

(1.96 KiB) Downloaded 627 times

MHDD.LOG

(3.82 KiB) Downloaded 593 times

Hard_Disk_Sentinel-REPORT.XML

(10.68 KiB) Downloaded 565 times

[N.C.]

This SAMSUNG SP1614C was running on a failing thermaltake power supply unit with bad caps.

Tested it with:

Hard Disk Sentinel

MHDD 4.6

HDAT2 v4.5.3

SMARTUDM - HDD S.M.A.R.T. Viewer 2.0

Hard Disk Sentinel reported health decreased from 90% to 70 %
MHDD shows 10 lba unc errors
HDAT2 sees 9

What else can I do, it's recoverable ?
Can I use it and partition around that area?

It is recoverable, i am sure, but if you wants to use it, you need to re-assing all pending sectors.
You can do that with linux's badblocks command (in write mode). (THIS WILL ERASE YOUR DRIVE!)
You should run it twice and in the second attempt, there should be no error.
if you still have errors, than forget this drive, and live without this.

Janos

[cavefish]

I've done samsung ES-Tool low format
and "zero fill" more then one time with other tools.

You can do that with linux's badblocks command (in write mode).

Badblocks
Important note: If the output of badblocks is going to be fed to the e2fsck or mke2fs programs, it is important that the block size is properly specified, since the block numbers which are generated is very dependent on the block size in use. For this reason, it is strongly recommended that users not run badblocks directly, but rather use the -c option of the e2fsck and mke2fs programs.

What this note means?

[N.C.]

I've done samsung ES-Tool low format
and "zero fill" more then one time with other tools.

You can do that with linux's badblocks command (in write mode).

Badblocks
Important note: If the output of badblocks is going to be fed to the e2fsck or mke2fs programs, it is important that the block size is properly specified, since the block numbers which are generated is very dependent on the block size in use. For this reason, it is strongly recommended that users not run badblocks directly, but rather use the -c option of the e2fsck and mke2fs programs.

What this note means?

in short:
Because you don't want to use/create/fix any EXT2/3 FS, in your case it is not important.
You need to know exactly the drive still have pending sectors or not.
If you force the drive to repeat the patter test with badblocks, you can have only 3 result:
1. the drive can't / don't want to reallocate, and nothing will happens
2. the drive gets fixed
3. the drive will die completely, but in this case you can prevent your data from lost.

Janos

[cavefish]

Have done 2 passes with badblocks -w read-write mode, the results:

First Pass completed, 48 bad blocks found.

Second Pass completed (11h! twice the first pass elapsed time), 49 bad blocks found.

Also ran smartctl -a after each completed passes.

Should I run smartctl self-test or it is just a waste of time ?

Attachments

smartctl_info_after_2.txt

(8.13 KiB) Downloaded 600 times

smartctl_info_after_1.txt

(8.15 KiB) Downloaded 614 times