HDDSuperTool - WD 8TB RED scratchpad error

Mirarty

New member
I tried to dump all modules on 8TB WD RED and I got following error:

Error processing COPYBUFFERTOSCRATCHPAD command on line 143.

Do you guys have any idea how I can fix it?

Thank you.

Code:
ubuntu@ubuntu:~/Desktop/hddsupertool-free-1.10-1.8-x86$ sudo ./hddsupertoolhddsupertool 1.10-1.8 20170129
Finding devices

Q) Quit
R) Refresh drive list
1) /dev/sda (8001563222016) WDC WD80EFZX-68UW8N0 R6G917UY
Choose which drive > 1
 
Main menu
q) Quit
h) Toggle script help
1) Device information
2) Read sectors
3) Write sectors
4) Erase sectors
5) Tools
6) Security
7) VSC
8) Image device
9) Custom
Enter your choice:
> 7
7
 
VSC menu
q) Quit
p) Previous menu
h) Toggle script help
1) WD dump mod 42 (older Caviar drives)
2) WD royl (Marvel) dump mod 02
3) WD royl (Marvel) dump mod 32
4) WD royl (Marvel) patch mod 02 (slow fix)
5) WD royl (Marvel) patch mod 32 (slow fix)
6) WD royl (Marvel) dump all modules
7) WD royl (Marvel) dump selected module
8) WD royl (Marvel) read rom
9) WD royl (Marvel) check rom file
10) WD royl (Marvel) write rom
Enter your choice:
> 6
6
identify
Model: WDC WD80EFZX-68UW8N0
Serial: R6G917UY
enable vsc
prepare access
read sector
module length in sectors= 0
ERROR: Attempt to copy past end of scratchpad,
Error processing COPYBUFFERTOSCRATCHPAD command on line 143.
copybuffertoscratchpad 0 0 0x200
There was an error processing the script 'wd_royl_dump_mod_all'. Exiting...
Total program run time = 398 seconds
ubuntu@ubuntu:~/Desktop/hddsupertool-free-1.10-1.8-x86$
 

Jared

Administrator
Staff member
Perhaps it's because a module is larger than the program expected and thus exceeded the buffer (scratchpad) size.
 

Mirarty

New member
Is there anything I can try? This HDD is encrypted with JMS561chip and I need to find the key so I can decrypt this HDD. Do you guys know any solution how I can find the key on 8TB HDD?
Thanks.
 

maximus

Member
I know this is a late reply, but this can explain why.
module length in sectors= 0
When it tried to read the module (I think in this case this means the first module), the processing showed the module was 0 bytes in length. It likely means it read all zeros, which means there is likely no access to SA. The error is because the script is not expecting a zero result.
 

maximus

Member
Jared":34xtxl4u said:
[post]8748[/post] Maybe it's a SED???
Very possible. It looks like dump all modules was chosen, so it would have tried module 01 first to get the list of modules. Module 01 should always have data. There is not much error handling in the VSC scripts, only what is needed to prevent obvious damaging commands to be sent to the drive. It has been awhile since I have even worked with these scripts so I can't even remember all the details of my own work :?
 

maximus

Member
I would also like to add that I based the scripts from drives that worked and were able to access the data. It is very difficult to know what to expect from a drive that responds differently if you don't have one.
 
Top