But the physical issues are LIKELY, not for sure. There is no strange noises, drive spins perfectly, there was (I hope) no physical shock, personally I don't see any physical symptoms. I take it easy, no pressure, data is important, but I must consider all yes's and no's for any solution.


YES for m0... or YES for DR pro or YES for exhaustion aspect?

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

Hi:

In my experience, No HOST FIS-ReadyStatusFlags 0002A1A5 and N1 fail command is because there is not formatted user partition. After m0,2,2,,,,,22 command you will can do N1 command and ¨No HOST FIS-ReadyStatusFlags¨ error will not longer appear.

But this does not guarantes that drive will be recognize by bios. I´ve seems some cases like you and i think that the problems is some firmware module corrupted produced by bad sectors in the system area.

I think that the m0,2,2,,,,,22 does not affect data.

Running m0,2,2,,,,,22 on a 7200.12 drive is NOT a good idea.

Thank you for sharing your opinions, that's mean much.




Could you or anyone explain why it's not good please? Does it really affect the data? Is there any additional info/docs about what exactly that operation does.

Still undecided if should I risk with m0 or not. Any additional opinions are welcome.

m0,2, does not take into account the NRG list and you can end up with a lot of mess.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

You're going to run a command you know nothing about on the critically important drive? Get another drive and experiment on it first.

Considering the question above, it doesn't look like you know how to reassemble the translator manually should you have it ruined during regeneration.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.