Search results

NO! Under no circumstance should you ever initialize a drive you are trying to recover data from. To "initialize" means to create a new partition table and that can be data destructive. The drive is having hardware issues, at the very least it has bad sectors and could be much worse. How...

With ECC off, you will read a lot of garbage because there's no ECC (Error Correction Code). The slow reading is probably due to it reading the same sectors multiple times before enough accurate data is read for the ECC to actually correct the sector and return proper data. Likely the platter...

At the time I had posted this, UFS hadn't been updated in some time and it seemed like R-Explorer was the product he was actively developing and updating. It seemed for a time like UFS was being abandoned. Now, he's keeping both products updated and has branched them out to a pro line (UFS)...

0% chance. Exactly 0%. You've probably already destroyed any hope of recovery.

Sometimes terminal boards just go bad. I've had to replace a couple.

Try using an older version of the driver. I have an issue where Win 11 keeps updating the driver for the PC-3000 terminal, and then saying "it's not compatible with this version of Windows", but reinstalling the older version fixes it every time.

The drive either has a weak/failed read-write head, or it has a malfunction of the firmware related to the bad sector reallocation functions. DIY repair will be very difficult to nearly impossible without access to tools like PC-3000 to properly diagnose and correct the issue. Is the data of...

Cool, thanks!

The link still works when I click it.

If the ROM is in fact burned out, then recovery won't be possible. So it's important to be sure. What makes you assume this?

And posted in a thread that's supposed to have been locked. Guess the migration unlocked it.

I'm wondering if it might be a bad head and it's repowering when it gets to buffering from that head. Have you tried messing with the head map to disable heads?

What makes you assume the ROM is burned out? Where did this prognosis come from?

I'm afraid free tools don't provide any way to correlate what files the unread sectors belong to. That's getting into the realm of professional data recovery systems costing thousands.

No, you'd just need to re-open the project file and you can resume where you left off. But, if you are using a Linux live build without persistent storage, the file might not really exist anywhere but in RAM. Just be sure you actually have a copy of that project file you created. Seems that...

If you try pulling out the heads/ramp together at the same time, the ramp will almost always just fall out and the heads will snap together. Game over for the heads. You really need a proper tool for these.

Thanks for sharing.

1. The guide should still work. DDrescue is a raw copy tool that's able to work fairly well with drives that have bad sectors. You also might consider trying HDDSuperClone. It's a newer Linux tool, with a GUI that is also quite good. 2. Whether you image to a file or do a drive-to-drive clone...

I've never used DFL tools, so I don't know if it's even capable of pulling this information.

You clearly didn't read any of the initial post. This is an SSHD that isn't spinning up. F commands will do nothing to an SSHD that is stuck busy and never spins up. For an F command to even matter, you need to first have SA access which can't happen with a platter that doesn't spin. I'm...