PCB BIOS and FLASH swap

[zvit]

Yes it's possible but because you have a sata pcb (if are compatible) the conversion are very fast, you need to swap u12 chip rom on new pcb and enjoy if you want to use usb pcb you need to broke usb bridge and use e75 e73 e72 and e71 pin contact on pcb su sata port

Unfortunately, what I got was the same board as mine - with a USB connector. I saw about the 4 pin contacts and thought that's the only option. But I should have researched more to realize that maybe the SATA one is called 771692? Would you mind telling me if this 2060-771692-001 REV A would be a match where I would just need to swap the u12 chip? https://www.aliexpress.com/item/1005001318036478.html

My PCB is 2060-771761-001 REV A

[magnetepazzo]

Yes it's possible but because you have a sata pcb (if are compatible) the conversion are very fast, you need to swap u12 chip rom on new pcb and enjoy if you want to use usb pcb you need to broke usb bridge and use e75 e73 e72 and e71 pin contact on pcb su sata port

Unfortunately, what I got was the same board as mine - with a USB connector. I saw about the 4 pin contacts and thought that's the only option. But I should have researched more to realize that maybe the SATA one is called 771692? Would you mind telling me if this 2060-771692-001 REV A would be a match where I would just need to swap the u12 chip? https://www.aliexpress.com/item/1005001318036478.html

My PCB is 2060-771761-001 REV A

You need to use 771692-005

[Lardman]

Looking at the log file results that's a bad head or damage to that specific area to me. I very much doubt PCB swapping will help you.

As you've purchased the pro version of HDDSuperclone use direct ATA and turn on fast skipping and drop the timeout to 500ms, use phase 1 only and see if the entire drive or just a section.

[zvit]

Looking at the log file results that's a bad head or damage to that specific area to me. I very much doubt PCB swapping will help you.

As you've purchased the pro version of HDDSuperclone use direct ATA and turn on fast skipping and drop the timeout to 500ms, use phase 1 only and see if the entire drive or just a section.

When I try to continue the project in Direct USB ATA, I get a popup saying "The rescue is finished using the current setting."
Can I not continue if I started the project in passthrough mode?

[zvit]

Since the first scan only scanned 4%, I tried to create a new project in Direct mode but as soon as I clicked START, the HDD light turned off and Linux froze, crashed, and turned off.

[maximus]

The good news is that the drive was suffering from the slow responding issue, and you fixed it with the patch. The bad news is that the drive has a completely dead head that is not reading any data at all. The drive appears to have 6 heads, so the math would be such that you will not read more than about %83 of the sectors. You should turn the cluster size back down to 128, as a larger cluster size will just miss more data on the edge of the bad head. You can also turn the Skip Threshold back down to 1000 in case there is a weak spot in the good heads anywhere.

The bad head is taking the full time of 60 seconds (the OS driver timeout), which is why it is going so slow. Now that you have purchased the Pro version, you need to switch to Direct USB mode and use the timeouts. You should lower the Soft Reset Timeout to maybe as low as 1000ms or 500ms (I don’t recommend going lower than 500ms in Direct USB mode). If the resets work, you should see the Current/Recent/Longest read times go down. I would expect the reset to take at least 350ms to complete, so if you had the soft reset timeout at 1000ms then the bad read times should be around 1350ms or so, give or take on how long the reset actually takes. If you don’t have luck with the read times going down, we will need to look into changing the USB reset type, but hopefully the default works.

This concept will get the data out of the good heads while skipping out of the bad head as fast as possible. But in all reality, you can stop the recovery after phase 2 completes, because the other phases will just try to get data from the dead head. But if you do get the resets working in Direct USB mode, I would also do a Reset Log to start it over before you continue, using the settings I have suggested. This will not loose any good data that has already been read. The reason I say to do this is that now that the slow issue is fixed, you need to go back and retry the area at the beginning where it did a bunch of skipping because of the slow issue, plus get closer to the edge of the bad head in the areas already read with the larger cluster size.

I see you reported an issue with Direct USB mode while I was typing this. I will address that in another post. To work through any issues like that may require email correspondence. But the first thing I would try is using the HDDLiveCD instead of an installed OS to see if it works, if you are not already doing so. If you can’t get the Direct USB mode to work, the only other option to speed up the recovery would be to enable Skip Fast in the clone settings. You could also try turning down the General Timeout, but that usually doesn’t do anything. But I would still want to work with you to get Direct USB mode working, even after the recovery is done.

[maximus]

Also, I'd appreciate if someone can answer a quick question:
Everyone mentioned that the next step would be to convert to SATA.
Would it be correct to say that since there is no evidence that the current PCB has any issues, that I can just convert the current PCB to SATA without having to use the donor PCBs that I purchased?

Yes it's possible but because you have a sata pcb (if are compatible) the conversion are very fast, you need to swap u12 chip rom on new pcb and enjoy if you want to use usb pcb you need to broke usb bridge and use e75 e73 e72 and e71 pin contact on pcb su sata port

Would the data be encrypted on this drive if converted to SATA?

Edit: Also, since the slow patch was able to be applied, the ROM should be able to be read from the current USB board, and maybe even written to the spare board so it could possibly converted without touching the original board. But it would be able to be written to a SATA board without having to move the chip.

[zvit]

But the first thing I would try is using the HDDLiveCD instead of an installed OS to see if it works, if you are not already doing so.

I am trying to do what I can on my own to not use your time but there isn't much documentation on HDDSuperLive or HDDLiveCD on the site, nor on the forums, not even this one, and no results on youtube.

Your live cd iso is just the lubuntu v18.04.4 OS and at boot, it asks me if I want to install or try. The way I know live CDs is that they are supposed to just boot into some OS at startup. Would I be correct to say that if I choose to "try," this functions as a live cd and is what you want me to do?

If I don't install lubuntu, I can't save my license information.

[maximus]

Yes, try without installing. You can install your license while booted into the live cd, but obviously you would have to do that each time you booted into the cd as it would not be able to remember.

[zvit]

UPDATE:

There was no "Direct USB" mode in Linux, only "Direct USB ATA."
In the lubunu there are two separate modes, "Direct USB" and "Direct ATA." I'm assuming at this point I should choose the first.
Maybe that helps to understand something about the crash in Linux?

[maximus]

That is very interesting, I don't know why in the installation the "Direct USB" option is not visible but the "Direct USB ATA" mode is, possibly a bug related to your OS UI that caused the previous display issue.

The ATA one should work as it is an ATA device, assuming your are choosing the correct device. If you are choosing an incorrect device it could cause a lockup. But if it does lock up with the correct device, then using the other mode may work.

Are you running Ubuntu with the Unity desktop? Here is something in the known bugs list:

* It has been reported that in regular Ubuntu with the Unity desktop, the program menu bar may not show up. This has been reported for the LTS versions 14.04 and 16.04. I have not been able to reproduce this using a live CD, so it may be limited to OS installation. A quick Google search finds issues with the menu bar in those versions, and possibly others. Just another reason for me to hate the Unity desktop. My suggestion is to switch to the Gnome desktop, or better yet, just use one of the other flavors of ubuntu (lubuntu, xubuntu, kubuntu). Unity sucks!

[zvit]

UPDATE:

Same thing happened. Setup everything like you said. When I clicked START, drive immediately disconnected, and PC froze. But this time all of my USB connections disconnected as well, including USB hubs, mouse and keyboard. So I had to do a hard restart to the PC.

If you want to move this to email (ztwersky@gmail.com) that's ok, or if you want to keep it here to benefit others that's fine too. I'm ready to do whatever the next step is.

EDIT:
While I was writing, I see you responded.
I choose USB and not ATA so I will try that now.

[Lardman]

UPDATE: if you want to keep it here to benefit others that's fine too. I'm ready to do whatever the next step is.

I've done well over 300 drives with HDDSuperclone now and I've not had the sort of issues you're seeing.... be nice to keep the outcome/solution public if you could - just in case,

I've had memory bug problems in lubuntu and ubuntu switching into direct mode but never the items missing from the menus.

[zvit]

Are you running Ubuntu with the Unity desktop? Here is something in the known bugs list:

I did not run Ubuntu at all with your software. I was running it on Kali Linux. Does that matter?

[zvit]

UDATE:

Tried Direct USB ATA. Clicking START will immediately disconnect the drive but at least this time nothing froze. Just an error that drive got disconnected and scan stopped.

I attached here the new log file to the new project with the new settings.
I also attached a file called "Log3 terminal" which has the terminal log where you can see what happened.
The issue started here:

Code:

Checking progress log file...
Interface connected
USB raw read error -110 (Connection timed out)
USB endpoint in reset
USB command data transfer short return or error -110 (Connection timed out)
usb reset needed 30
USB Reset Recovery
15.32.17.128498 usb bulk reset

Attachments

Log3 terminal.txt

(2.46 KiB) Downloaded 651 times

tal.log3.txt

(6.1 KiB) Downloaded 601 times

[zvit]

I was thinking, I can start a scan on a good, spare drive I have, in ATA mode, just to see if the system will crash. If not, it would be a problem with my bad drive. If yes, it's a problem with my system. Let me know if this test would help you.

[maximus]

UDATE:

Tried Direct USB ATA. Clicking START will immediately disconnect the drive but at least this time nothing froze. Just an error that drive got disconnected and scan stopped.

I attached here the new log file to the new project with the new settings.
I also attached a file called "Log3 terminal" which has the terminal log where you can see what happened.
The issue started here:

Code:

Checking progress log file...
Interface connected
USB raw read error -110 (Connection timed out)
USB endpoint in reset
USB command data transfer short return or error -110 (Connection timed out)
usb reset needed 30
USB Reset Recovery
15.32.17.128498 usb bulk reset

I have sent you an email, to continue this part of the troubleshooting via email. But what I see from this is that the USB bridge may not be responding as desired to resets. This may not be a good sign, but more tests are needed to be sure. It is never a guarantee that a USB drive will respond to the resets.

[maximus]

Are you running Ubuntu with the Unity desktop? Here is something in the known bugs list:

I did not run Ubuntu at all with your software. I was running it on Kali Linux. Does that matter?

I didn't catch this until watching a video of the issue in the email communication. This screenshot shows exactly what the biggest issue is. It has nothing to do about Kail Linux (maybe the missing menu item is). The reason for the Direct USB mode to fail is clear in this image. Look closely...

[zvit]

I already know because you told me... we'll see if anyone else can guess )
As I mentioned via email, I'll have an answer about the live cd test after I fix the boot issue.

[Lardman]

I already know because you told me... we'll see if anyone else can guess ).

Virtual machine and USB pass through doesn't work properly ?

Whilst we have your attention maximus - any chance you can add the open project file name to hddscviewer somewhere - it's a pain when keeping track with multiple windows open.