HDD GURU FORUMS

This one is driving me mad !

Flash-extractor.

I've finally got a decent reading from all the nand but assembly is causing problems. The default model assembles fine, build the image but the file system is crap and a raw scan gives almost 100% damaged files.

Tried version 2 as this is exactly the board / revision https://flash-extractor.com/library/San ... 3__4x1__v2

That gives "Media Read Failure" and stops doing the assembler scan ( I have copied the dumps to another drive just in case but the errors are the same). Can anyone point me in the correct direction - This has been reading and ECCing for weeks.

Write here full 6th byte ID.

arvika wrote:Write here full 6th byte ID.

Mixed 2 cases up sorry - long week.

The 6 byte ID is 45 49 9a b3 7e 6b so it looks like there is a problem with the internal FE model and this would be the one ? https://www.flash-killer.com/library-ar ... 9b_b3__4x1

Did you make dumps in FE or other software?

Swiftdata wrote:Did you make dumps in FE or other software?

FE - Whilst arvika has the correct pcb model the nand are a different ID so needs more work than the clients budget allowed for and the drive has been returned.

I think the problem is average clients do not understand complexity in cases with flash devices and since they buy it for such low price they cannot comprehend costs to justify work and resources involved

I charge a flat fee on SSD's so on cases like this the client can save hundreds of pounds and have data recovered that they otherwise have lost; the drawback being if it then turns out to be a none standard case there's not enough in their budget to complete it. I have to write the case off but at least it's usually only time costs.