PC-3000 Forum

We have already changed the connection type from USB to SATA (using a compatible SATA PCB or SATA adapter), but when we start Marvell utility we see SED locked error.

1. Start the drive in Kernel mode: head isolation with connected spindle contacts
or short E47 PCB pin to the ground (tested on 2060-771961-000 REV P1). Status registers will be off, ID is not detected, but autodetect should work correct.


2. Follow Work with ROM->SA regions editor->Do it now.. button and Block SA access.



3. Power off the drive, remove the isolation.

4. Power the drive on.

5. Start the utility in Kernel mode, load DIR into RAM using Work with RAM->Load DIR in RAM option.




Exit from utility, start the utility in Normal mode.

6. Drive start with default -XYZ- in ID serial


7. Save Service Area modules by ABA:


8. Follow Work with service area->Solve Slow responding problem, do it by ABA, by copy 0.




9. Follow Work with service area->Edit HDD ID,


go to Security subsystem tab, remove SED checkbox, press OK.


Do it by copy 0 only


10. Follow Work with ROM->SA regions editor->Allow SA access, press OK.


11. Power off\on the drive, enter in WDC Marvell utility, drive should start with full ID and SA access.


12. Open Tools->Sector edit. Data looks encrypted.


13. Follow Reading options


and set Decrypt data checkbox, press OK


14. Autodetect the encryption type, choose Self encryption HDD and press OK.


15. Check if sectors are really decrypted in Sector edit.


16. Create a task in Data Extractor, go to Settings->Command to read tab, choose Decrypt checkbox, repeat the actions with encryption type search.

17. Read the data.

I just encountered my first one of these, 1TB passport with the SED blocking access to work with firmware.
Before finding this writeup, I cloned the entire drive before saving/working with modules and before trying this writeup, after only converting from USB-SATA and doing a normal clone in DE (without entering the WD Utility since the SED prevented access). It cloned with 0 bad sectors and the data/clone is not encrypted (without having to try to enable decryption or messing with anything...I just converted to SATA and cloned the whole thing normally).

I decided to use this drive as an test, since it's recovered, and I wasn't able to access the SA/modules yet.
I went through the procedure, which allowed me to save modules. When I chose to decrypt (in sector edit) it finds INIC3608
as the type, but "no key" under module 25. It alters the data in the selected sector (0), but it's not decrypted, just changed to some other encrypted-looking form. Starting a DE project as-is of course is also still unable to decrypt.

My assumption is that my drive isn't actually encrypted, and maybe the decrypt utility is pulling a blank or generic key and implementing that? I don't know how the self encryption works, and this is my first of its kind so I'm probably wrong...

If this drive had had the relo list problem, and I had had to fix that, should I have gone through the steps to access and save modules, solve the slow problem, and then just not continue with step #11 (remove the SED checkbox)? I assume if I stopped there, I still wouldn't have normal access to the WD utility control within DE for features like headmap, etc.

Am I missing something, or maybe do something wrong...or maybe the INIC3608 decryption feature isn't quite complete yet?

Dear ThomasH,

SED encryption can be decrypted only in PC-3000 v5.9.21.
Maybe you are using the older verison?
Please check your update box for latest software, and repeat the procedure.

I have a WD10JMVW-11AJGS1 with "SED DRIVE LOCKED". I converted USB to SATA first. The drive Fully IDs until I start the utility where it says "SED DRIVE LOCKED". So I followed the above instruction till level 6 where the drive should be able to save by ID but it shows neither copy0 not copy1. The box is just empty. Did I miss something?

Thanks,

After 'upload DIR to RAM' there is a dialogue box about the regime changing, you have to select 'yes' here, then you can read SA modules over ID (no ABA will be available at this stage).

Thank you AJ2008. I have modified the manual, made the steps a bit shorter and easier. The changes begun from step 5.
Everyone who had troubles, please try again in according with new steps.

Thanks for shared!

Great Solution. Thanks a lot. It worked fawlessly.

Model : WDC WD5000LMVW-11VEDS6
Serial : WD-WX51A63U4151
Firmware : 01.01A01
Capacity : 465.73 GB (976 707 633)

this is a wd usb3 drive. new for parts.
couldnt access sa with com or usb - was getting sed locked.
But the drive worked fine as usb for user area.
Ran this procesdure to clear the sed flag in the drive id.
After that I could read sa through com port. But now windows could not access through com port.
Reading sector 0 showed it looked encrypted.
Setting it back reversed everything.

drdoc wrote:Source of the post Reading sector 0 showed it looked encrypted.

With SED active, data will be decrypted by default. with SED disabled, decryption should be done via Self Encrypting Key found at drive - this can be done in the PC3000 / DE software.

Since ACE is sharing this excelent stuff, here is my contribution

I had the exact same case.
PC3K version is 5.9.21
Followed ALL the revised steps accordingly

I uncheck SED lock in Step 9
And them write by ABA using Copy0
And restore SA access
But WD drives continue to show SED error.

I also tried writing using all copies from ABA, and by ID
No luck

Then I tried Heads test
---------------------------------------
Heads test
Cylinder to test........................ : -10
Heads to test........................... : 0,1,2,3
Head 0.................................. : Error W : 0;R : 1480
Head 1.................................. : Ok
Head 2.................................. : Ok
Head 3.................................. : Ok

I suspected H0 is bad.
I run SA regions again, and change Region 0 to start at Region 1

Now Hdd can access and save partial user data
Cheers

Thank you for this little step-by-step reply.
Yes, important to check a Heads test and spare a regions of SA for problem head(s).

this problem with pc3000 udma or portable ? and which version?

atwartec, SED issue can be solved in PC-3000 Express/Portable/UDMA-E v6.0 and newer.

Hi, thanks for this most excellent tutorial!

Question 1: However, there are a couple steps before Step 14 where PC3K ask to repower the drive. But you do not mention to repower. Do I assume ignore PC3K until you actually say 're-power' in your tutorial?

Question 2: At Step 14,, after clicking Auto-detect, I get 2 choices. (see attached picture). I can only choose 1 of these items. Either one does NOT decrypt the data. What to do at this stage? (I have repeated procedure twice, with no change.)

P.S.: I have the newest PC3K software: PC-3000 v5.9.21

P.S.2: There are 4 heads, 0, 2, and 3 test okay, but Head 1 has errors. Is this the reason for failed de-cryption (SED)?

Thanks!
-PP