Discussions related to PC-3000
Please no pirated software here!
December 21st, 2025, 11:43
The drive experienced a short-circuit on its PCB, which subsequently damaged the CPU. Fortunately, the ROM remains intact, and prior to the CPU failure, I was able to retrieve some modules from the drive.
I transferred the original ROM to a donor PCB and powered on the drive. It is now being recognized, and PC-3000 displays all the hard drive information correctly. However, the data appears to be encrypted. I attempted to decrypt it using PC-3000, but the software could not locate the encryption key.
To address this, I wrote some modules back to the drive. After doing so, PC-3000 was able to detect the encryption key, yet the data remains encrypted. I also tried disabling the Self-Encrypting Drive (SED) option in the "Edit HDD ID" settings, but this did not resolve the issue.
Could you please provide guidance on how to proceed? Recovering this data is extremely important to me.
Thank you for your time and assistance.
Best regards,
tarasheh
December 21st, 2025, 14:58
Is your MCU one of those with a unique encryption key? Is the PCB 2060-800067?
December 22nd, 2025, 1:46
fzabkar wrote:Is your MCU one of those with a unique encryption key? Is the PCB 2060-800067?
I don't know about MCU but pcb is PCB 2060-800067
December 22nd, 2025, 1:55
December 22nd, 2025, 3:41
The capacitor and resistor around that IC show zero on the multimeter and most likely that IC is burnt out. and i have usb to sata pcb like that image on link and i test these drive only with that
December 22nd, 2025, 3:43
i have backup of module d000,d001,d004 these aren't help?
December 23rd, 2025, 6:11
tarasheh wrote:The capacitor and resistor around that IC show zero on the multimeter ...
Zero what? Volts or ohms? What voltage do you measure across the caps?
December 24th, 2025, 3:53
I diagnosed the original PCB using a diode test and an ohms test. I followed the circuit path to isolate the fault rather than applying 5V power to the board.
Most components were removed, leaving only the two large ICs: the Marvell controller and the motor driver IC. The problem was a very small capacitor located behind the USB socket. It had failed but showed no visible damage, even under a loupe.
Now, aside from these issues, when the Marvell IC burns out, is there anything else that can be done?
December 24th, 2025, 5:36
tarasheh wrote:Now, aside from these issues, when the Marvell IC burns out, is there anything else that can be done?
No, if it's burned, it's not possible to decrypt the data at this moment. Probably will never be as it's quite different than other WD encryption ways.
I would transfer it with original ROM to a new PCB to make sure that nothing else can be done.
December 24th, 2025, 9:59
oh ok.thanks melvin
December 24th, 2025, 14:29
tarasheh wrote:I diagnosed the original PCB using a diode test and an ohms test. I followed the circuit path to isolate the fault rather than applying 5V power to the board.
Most components were removed, leaving only the two large ICs: the Marvell controller and the motor driver IC. The problem was a very small capacitor located behind the USB socket. It had failed but showed no visible damage, even under a loupe.
Now, aside from these issues, when the Marvell IC burns out, is there anything else that can be done?
Are you now saying that the MCU is OK?
Powered by phpBB © phpBB Group.