BIOS does not detect - ST32000542AS

[purenoise]

Actually, already have space prepared, and gonna backup it, but
i first check HDD surface to be sure that no damage was done during revive.
And when is backup is done - i'm gonna use it as test drive for temp data.

[ Learned from that]
To ewheryone:

- keep backup of important data in three different places [ better encrypted]
- make backup at least once a weak

Thanks.

[LarrySabo]

Actually, already have space prepared, and gonna backup it, but
i first check HDD surface to be sure that no damage was done during revive.

If during the surface test it dies completely and you haven't yet backed-up your data, you will have recovered no data and might not get a second chance to do so. If you start the backup and it dies part way through, at least you will have some of your data.

[purenoise]

I understan that, but:

- before i start backup [ working filesystem] i
need to know that surface of the plates not damaged, and
drive does not stuck during backup when Win10 does not know how to
deal with the read problem
- light blind surface test under Dos with direct HDD access is safer even
tere is surface damage - HDD should run until sca complete.

And as i suspect problem happened after
chkdsk /f which i had to run after noticing some issues with HDD.

My plan is to:

1. Complete MHDD basic scan
2. and then backup copying data [ not deletering/removing/moving] - just copying

and then i will keep using as a test subject hoping to
catch a reason of this problem - hope it's not me.

But still have a question:

- that problem was due to PCB, FW, Heads or Platters ?

[LarrySabo]

I would suggest using ddrescue to clone/image the drive--don't connect it to a Windows computer, don't run any scans with MHDD or other program. Once you have the image/clone, recover your data from that. chkdsk is the worst thing you can do to a corrupted filesystem when you don't have a sector-by-sector clone/image.

[purenoise]

I would suggest using ddrescue to clone/image the drive--don't connect it to a Windows computer, don't run any scans with MHDD or other program. Once you have the image/clone, recover your data from that. chkdsk is the worst thing you can do to a corrupted filesystem when you don't have a sector-by-sector clone/image.

I know what suggest and i'm considering that option:

- since it's 2TB - i need to do mirror clone [ i have 2TB waiting already]

, but:

- i have that feeling that i need to know that it's not just 2TB is real like it shows in BIOS, but
also whole data is accessible, and
will hate when cloning Halt and then i need to do surface scan anyway.

From my Experience never had MHDD issues even with the bad drives,
MHDD gives me a mental picture of the drive and i confidence to proced with data recovery.
I know, it's not done util whole data is safe.

[pepe]

surface scan is pointless in any situation when u need the data.
Larry is right, u can only loose time and chance. Anyway, what would you do if the surface scan revealed problems?
With the same effort you could clone it gives you a lot higher chance to recover your data.

From my Experience never had MHDD issues even with the bad drives,

it will not be MHDD's fault if the drive goes nuts, it will be yours.

pepe

[pcimage]

surface scan is pointless in any situation when u need the data.
Larry is right, u can only loose time and chance. Anyway, what would you do if the surface scan revealed problems?
With the same effort you could clone it gives you a lot higher chance to recover your data.

From my Experience never had MHDD issues even with the bad drives,

it will not be MHDD's fault if the drive goes nuts, it will be yours.

pepe

Exactly so, we clone EVERY SINGLE DRIVE we get in for recovery, even if it's a so-called software issue, and work from the clone only.

[purenoise]

Thank you guys for warning me:

- aware of the risk.

I now prepared, and
hope newer have that issues again ( it was the first).
Good that found instruction for my case to revive my hdd.

[purenoise]

SOLVED - FIXED - REVIVED - CLOSED

---------- th@nk -- y0u ------------