WD40NDZW-11MR8S1 - not decrypting

[Alandata Recovery]

   Model : WDC WD40NDZW-11MR8S1
  Serial : WD-WXD2DB1L8LES
Firmware : 02.01A02
Capacity : 4 TB (7 813 971 632)

I have this drive.

Came ready slowly with USB but had media errors.

unlocked rom

converted to sata

read 190

blocked UA writing

backedup resources.

shifted SA

loaded dir and drives from files

H3 wont write

ram edit for no H3

soft reset

drive comes ready  ID;s

read sect 0 - its encrypted

select decrypt - says it finds keys

still encrypted.

Anyone seen this ?

Thanks

=======================

Drive power supply...................... : OFF
Drive power supply...................... : ON
Drive identification reading ........... : Ok
 
Resources folder........................ : <HDD Profile>\Data\SABackup\Modules\Copy 1
Cache ovl(10) data uploading............ : Ok
Permanent ovl (11) data uploading....... : Ok
Module 02 uploading..................... : Ok
 
Map data writing........................ : Ok
Software reset.......................... : Ok
Drive identification reading ........... : Ok
 
SED key checking
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
Encryption.............................. : Self Encryption HDD v2
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
SED key checking
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
Encryption.............................. : Self Encryption HDD v2
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
External encryption key checking
UA key reading:7 813 965 856............ : Ok
SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : Ok
 
UA key reading:7 813 967 235............ : Ok
SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : Ok
 
UA key reading:7 813 965 832............ : Ok
SA key reading:Copy 0................... : Has been already read
SA key reading:Copy 1................... : Has been already read
 
UA key reading:7 813 971 592............ : Ok
 
SED key checking
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
Encryption.............................. : Self Encryption HDD v2
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
SED key checking
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
Encryption.............................. : Self Encryption HDD v2
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
External encryption key checking
UA key reading:7 813 965 856............ : Ok
SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : Ok
 
UA key reading:7 813 967 235............ : Ok
SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : Ok
 
UA key reading:7 813 965 832............ : Ok
SA key reading:Copy 0................... : Has been already read
SA key reading:Copy 1................... : Has been already read
 
UA key reading:7 813 971 592............ : Ok

========================

--

Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, NAS, Linux, Tape, Disk, Forensics"

www.alandata.com   www.alandataRecovery.com

[pbzcbf...@gmail.com]

Why are you looking for a key in the USB-visible UA (7813971632 LBAs)? Convert the drive to SATA and then look for a key at the end of the real capacity (7814037168).

[pbzcbf...@gmail.com]

In fact, why are you trying to decrypt the already decrypted drive via USB? :-???

[wayne horner]

it is converted to sata.

H3 on the drive wont write.

So its not happy with USB interface

that dialogue is what pc3k does when you tell sector edit to decrypt.

It always has worked this way.

Those are the places that the pc3k looks for the keys.

Noticed that there is a SED key module in the ROM - thats new....

SED Key

Alandata Data Recovery -  (949)287-3282  

"Cleanroom Data Recovery of RAID, VMware, Network Attached Storage, Linux, Tape, Disk, Forensics"

www.AlanData.com   www.AlanDataRecovery.com

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/6a5453f4-8c81-4e25-83a8-aa63fe800f2dn%40googlegroups.com.

[Sling Shot]

That's a SpyGlass2 so will be MCU encrypted.

Use patient PCB with a SATA adapter and it should decrypt itself on the fly 

(no need for 25/38 decryption). 

 If not it could be file-vault encrypted (as its a passport for mac drive) or user encrypted via the WD utility bundled with the drive.

[pbzcbf...@gmail.com]

This is the capacity via USB: 7 813 971 632

This is the capacity via SATA: 7 814 037 168

PC3K is looking for a UA key at these 4 LBAs ...

7 813 965 832
7 813 965 856
7 813 967 235
7 813 971 592

7 813 971 632 = USB capacity

... the key should be in this area (65536 "SmartWare" sectors) ...

7 814 037 168 = SATA capacity

Therefore, you must be searching for the key in USB mode, not SATA mode, otherwise PC3K has a stupid bug.

[t...@desertdatarecovery.com]

These are V2 encrypted. It cannot be decrypted on the fly.

PC3000 does find that its V2 encrypted within the USB range.

I doubt its smartware as Wayne would have seen that via USB when first connected.

--

Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/1162cdb6-9016-4184-83b9-91162a92267fn%40googlegroups.com.

[Alandata Recovery]

This is the original patient board

with sata adapter soldered on.

removed the caps also....

The drive is not user locked with wd.

When I first tested the drive I tried the USB stabilizer. It came up quickly and I got a root file list.

no password was required.  I only tested it that way for a few moments before deciding to not risk it through the USB anymore

I converted the board to sata.

I cant attempt to read beyond the 7 813 971 632 with clearing the HPA flag - which I dont want to risk at the moment.

besides the keys in the hpa havent been in use for some time since they switched to using the MCU based key

7 813 965 832
7 813 965 856
7 813 967 235
7 813 971 592

likewise the keys in mods 25 35 are no longer in use

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/1162cdb6-9016-4184-83b9-91162a92267fn%40googlegroups.com.

--

Alandata Data Recovery -  (949)287-3282  

[Alandata Recovery]

V2 right

So the only solution right now is to make it work with original USB board?

So best procedure is NOT modify original board.

write rom to matching board

use that to fix SA

If we write unlocked rom to original usb board

can we edit head map through USB or com port?

[t...@desertdatarecovery.com]

I would create a DE task via SATA.

Create a head map using T2.

Close the task.

Covert back to USB to see if data is now unencrypted.

If its readable, create a new DE Task with USB.

Import head map etc from SATA DE task into USB DE task.

Image.

 

 

From: datarecovery...@googlegroups.com <datarecovery...@googlegroups.com> On Behalf Of Alandata Recovery
Sent: Tuesday, September 5, 2023 4:45 PM
To: datarecovery...@googlegroups.com
Subject: Re: WD40NDZW-11MR8S1 - not decrypting

 

V2 right

 

So the only solution right now is to make it work with original USB board?

 

So best procedure is NOT modify original board.

 

write rom to matching board

 

use that to fix SA

 

If we write unlocked rom to original usb board

can we edit head map through USB or com port?

 

On Tue, Sep 5, 2023 at 4:38 PM Alandata Recovery <in...@alandata.com> wrote:

This is the original patient board

with sata adapter soldered on.

removed the caps also....

 

The drive is not user locked with wd.

When I first tested the drive I tried the USB stabilizer. It came up quickly and I got a root file list.

no password was required.  I only tested it that way for a few moments before deciding to not risk it through the USB anymore

I converted the board to sata.

 

I cant attempt to read beyond the 7 813 971 632 with clearing the HPA flag - which I dont want to risk at the moment.

 

besides the keys in the hpa havent been in use for some time since they switched to using the MCU based key

 

7 813 965 832
7 813 965 856
7 813 967 235
7 813 971 592

 

likewise the keys in mods 25 35 are no longer in use

 

 

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWTAcEaMYvA434LeY6JDE6dA3MX_vG%2BkpMTDa9omehGpbA%40mail.gmail.com.

[pbzcbf...@gmail.com]

I understand what you are saying. All I'm saying is that these lines are absurd:

UA key reading:7 813 965 856............ : Ok

UA key reading:7 813 967 235............ : Ok

UA key reading:7 813 965 832............ : Ok

UA key reading:7 813 971 592............ : Ok

It says that PC3K is looking for a key in the user's data area, ie within the USB mass storage device Obviously, there can never be a key in this area, else it would be overwritten by the file system.

When I refer to "SmartWare", I'm referring to those 65536 sectors (32MiB) which were originally reserved for this purpose, and which now contain keys and other firmware components. Originally this area appeared within the OS as a VCD (Virtual CD). These days this area is mostly empty. It may not even be used at all.

[pbzcbf...@gmail.com]

What does "Ok" mean? Obviously PC3K did not find a key at any of these locations, so why not just say so, ie "No key found at this LBA".

[Desert Data Recovery]

I think it's just a carryover and they are too lazy to fix it. Apart from the early Spyglass which were SED locked, they have all been MCU encrypted. So I guess they didn't see a reason to fix it. 

--

Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/2acd04b1-0d39-41f6-b8b8-18c1aae9c65an%40googlegroups.com.

[Alandata Recovery]

yes its looking in the user area

OK mean the sector was readable

it then checks for the signature of a key-holding sector

which it doesnt find.

yes is just their programed brute-force way to search for keys

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAOasWztCPFd5WmN4MFfbwXYAJgss8EsrY8yWj1q_dzhpH76QVw%40mail.gmail.com.

--

Alandata Data Recovery -  (949)287-3282  

[Zyana It Solutions]

When we load 190 in ram that also show encryption many time in that case need to write t2 again to drive or try to read sector via techno mode that could help in this case. 

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWRv8LHitmL34if7MQr1KwJAw%2BCf1K2%2BS9jPkEp%2BP8YpPQ%40mail.gmail.com.

[Zyana It Solutions]

I had seen In some cases if we are reading drive sectors normally that shows encryption then we read via techno mode and it shows ok decrypted sectors

We never seen to get decryption via searching key modules in v2 case. 

[Artem Rubtsov]

SED encryption engine initialized only when a drive starts normally

So you cannot do this

shifted SA

loaded dir and drives from files

H3 wont write

ram edit for no H3

soft reset

drive comes ready  ID;s

and expect the encryption engine to work properly. 

[Artem Rubtsov]

Also you absolutely should not load dir from a file on any SMR drive, it is recipe for disaster. 

Always load dir from the drive.

[t...@desertdatarecovery.com]

Artem can I ask why?

 

 

From: datarecovery...@googlegroups.com <datarecovery...@googlegroups.com> On Behalf Of Artem Rubtsov
Sent: Wednesday, September 6, 2023 7:46 AM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>
Subject: Re: WD40NDZW-11MR8S1 - not decrypting

 

Also you absolutely should not load dir from a file on any SMR drive, it is recipe for disaster. 

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/b028b0f7-6c1b-4298-b247-583d8f07b855n%40googlegroups.com.

[wayne horner]

ok everything is back to normal

except UA writing blocked.

on power up it clicks and recals 4-5 times then goes quiet and comes ready as a normal quiet drive.

its not buzzy or noisy or clicky.

I can read sector 0

when I try to start a de task I get this

de looks like this

and sector 0 no longer reads in utility.

trying it with the sata 0 device didnt help

the drive shows up in disk management and I can read sector 0 with runtime disk explorer.

I tried to start rstudio.

Rstudio is apparently resetting the device it keeps clicking and recalling like 20 times.

I tried to kill rstudio - no response - rstudio has a bad habit of locking up when a device doesnt respond.

I finally pulled usb to make it stop.

At this point it looks like usb stabilizer is my only option..

====================

Family:................................. : SpyGlass2 2.5"
Techno mode key......................... : Ok
 
Debug Stop Code......................... : DM ABA OUT OF RANGE
 
HDD Status sector....................... : Ok
 
RAM:
System controller (SoC)................. : 88i1047F0 0x(5450)
HDD Info reading........................ : Ok
Heads number............................ : 10
Cyl Count............................... : 384
 
ROM:
Read ROM................................ : Ok
ROM Data size........................... : 512 Kb
Flash ROM dir reading................... : Ok
Flash ROM dir reading (Ext)............. : Ok (Active)
Modules directory address............... : 800 965
SA regions address...................... : by default
SA regions address (RAM)................ : by default
Module 02 access........................ : Granted
 
SA SPT.................................. : 2136
 
SA Translator loading................... : Ok
SA defects assigned..................... : 10
 
ROM Modules:
ROM version............................. : 02.0AS
Module 4F F/W version................... : 0002000A
Overlay F/W version..................... : 02.0BS
Servo F/W version....................... : 03.7B
 
Heads configuration..................... : by map
Heads number............................ : 10
Heads number in use..................... : 10
Switched off heads...................... : No
Heads map............................... : 0,1,2,3,4,5,6,7,8,9
 
Relocations............................. : 0 (2 459)
Read ROM DCM............................ : Ok
 
Power up log reading.................... : Ok
Power up load dir data.................. : Yes
Power up load permovl................... : Yes
Power up load CFG data.................. : Yes
----+------+--------+------------------+----------+-------------------------------------------
 NN | Step |   Time |            Flags |     Info | Description                              
----+------+--------+------------------+----------+-------------------------------------------
 66 |  227 | 2.44 s | 14000401217FFDFF | 51043746 | PWR act code 227(FM ERR NOT FOUND IN DIR)
----+------+--------+------------------+----------+-------------------------------------------
 
Service area:
SA dir reading (ID)..................... : Ok
Dir items loaded........................ : 654
 
SA Access............................... : Copy 0,Copy 1
 
Configuration reading................... : Ok
CFG tech mode lock...................... : No
Self encryption drive................... : Yes
SED Info read........................... : Ok
Master Password......................... : Yes
User Password........................... : No
SED tech mode lock...................... : No
UA writing.............................. : Blocked
 
DCM in module 47........................ : ZE
DCM in module 0A........................ : |W|2ZEDH27
DCM in module 02........................ : S|BWL|P2MZHECDRHV2KBUN
 

=================================

Alandata Data Recovery -  (949)287-3282  

"Cleanroom Data Recovery of RAID, VMware, Network Attached Storage, Linux, Tape, Disk, Forensics"

www.AlanData.com   www.AlanDataRecovery.com

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/004b01d9e0d1%24cb6c7650%24624562f0%24%40desertdatarecovery.com.

[wayne horner]

I explained all these steps in detail to ace

this was their response.

and this picture

I explained that I already tried sata board but it wont decrypt v2

I explained that I had 2 boards ready, a sata connector with alien MCU and the OG USB - working and reading.

Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, Network Attached Storage, Linux, Tape, Disk, Forensics"

www.AlanData.com   www.AlanDataRecovery.com

[Artem Rubtsov]

as of "why you should not load dir to memory?"

1. Loading dir to memory will enable drive to immediately access modules.

2. Most of the modules have checksum and all of the modules have headers. But some important modules are not read as a module but rather as random sectors (the most important one is module 0x190) 

3. While SA regions are shifted most of modules reading will return an error (because all module headers are invalid because of the SA shift) but 190 is read randomly so it still can be read by the drive

If you by any chance have dir loaded to memory from a file but forgot to fix the SA regions shift in memory and send a reset to the drive, the drive would try to load the rest of SA. 

Module 190 is loaded separately from other modules and processed by a separate code block. It will be loaded to memory even if the SA regions are shifted (incorrectly, obviously)

After the module 190 is processed and found incorrect there would be several scenarios (depending on FW revision) from completely destroying(cleaning) 190 in SA, to updating random pages inside 190, to doing nothing to 190.

But you don't want to find out which FW revision your HDD is running the hard way. As one of the scenarios will result in completely destroyed 190. And yes, people who try to repair drives often kill 190 by their own hands due to lack of this knowledge. 

That's why loading dir from the drive is preferable, because it can only be done when SA regions are fixed in memory and drive can access all modules properly. 

[t...@desertdatarecovery.com]

Thanks for sharing Artem. Much appreciated by all I think.

 

Tim Homer - Lead Engineer

Desert Data Recovery

t...@desertdatarecovery.com

www.desertdatarecovery.com

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/a5af04ca-5cb4-44ed-b84c-2c7e998141c9n%40googlegroups.com.

[t...@desertdatarecovery.com]

Also can I ask. There are quite often times when we can read all the SA except for 190. I presume this is because it is stored as random sectors rather than a module. So is 190 still stored as the same format as the rest of the SA, or is it different and that is why sometimes it cannot be read? There are also instances where 190 cannot be read by PC3000, but the drive can be imaged without an issue. Wonder if you can shed some light on that?

 

Tim Homer - Lead Engineer

Desert Data Recovery

t...@desertdatarecovery.com

www.desertdatarecovery.com

 

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/a5af04ca-5cb4-44ed-b84c-2c7e998141c9n%40googlegroups.com.

[Artem Rubtsov]

The drive only accesses the sectors needed, there are some portions of 190 that drive never accesses, it includes reading and writing.

Thus it is possible that some areas of 190 were never written and these sectors are not "formatted" properly and are unreadable while the drive is completely blind to it, as it never accesses those sectors. 

[t...@desertdatarecovery.com]

Thans for sharing.

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/2a9740fb-93f8-49a4-90bb-3c4b585be2c8n%40googlegroups.com.

[VietGamer]

My drive got the same problem

Family:................................. : SpyGlass2 Ultra 2.5"

Techno mode key......................... : Ok

 ead ROM................................ : Ok

ROM Data size........................... : 512 Kb

Flash ROM dir reading................... : Ok

Flash ROM dir reading (Ext)............. : Ok (Active)

Modules directory address............... : 801 050

SA regions address...................... : by default

SA regions address (RAM)................ : by default

Module 02 access........................ : Granted

 

SA SPT.................................. : 2136

 

SA Translator loading................... : Ok

SA defects assigned..................... : 17

 

ROM Modules:

ROM version............................. : 00.0AA

Module 4F F/W version................... : 0000000A

Overlay F/W version..................... : 00.0BA

Servo F/W version....................... : 03.7B

 

Heads configuration..................... : by map

Heads number............................ : 10

Heads number in use..................... : 10

Switched off heads...................... : No

Heads map............................... : 0,1,2,3,4,5,6,7,8,9

 

Relocations............................. : 0 (2 459)

Read ROM DCM............................ : Ok

 

Power up log reading.................... : Ok

Power up load dir data.................. : Yes

Power up load permovl................... : Yes

Power up load CFG data.................. : Yes

: Copy 0,Copy 1

 

Configuration reading................... : Ok

CFG tech mode lock...................... : No

Self encryption drive................... : Yes

SED Info read........................... : Ok

Master Password......................... : No

User Password........................... : No

SED tech mode lock...................... : No

UA writing.............................. : Granted

 

DCM in module 47........................ : ZE

DCM in module 0A........................ : |W|MZEDH2F

DCM in module 02........................ : S|BWL|PMMZHECDRHV2KBUN

 

   Model : WDC WD40NDZW-11A8JS1

  Serial : WD-WXQ2E60CUVW1

Firmware : 01.01A01

Capacity : 4 TB (7 813 971 632)

ERROR IN DE UPON T2 HEAD BUILD. NOTHING SHOWS WITH QUICK ANALYSIS

Reading method.......................... : VSC command (T2 Data read)
T2 read................................. : Ok
Zone type............................... : Type 2
Zones................................... : 5 865
SMR zone read........................... : Ok
SMR zone indexing....................... : Ok
26 329 / 9.............................. : 193 030 -- 195 885 # 173 119
26 329 / 10............................. : 196 121 -- 196 983 # 173 119
2 296 / 4............................... : 197 227 -- 203 049 # 173 119
2 296 / 12.............................. : 203 050 -- 208 570 # 173 119
38 749 / 5.............................. : 208 571 -- 214 399 # 173 119
41 036 / 4.............................. : 206 153 -- 206 860 # 176 129
58 306 / 4.............................. : 206 861 -- 207 364 # 176 129
58 306 / 7.............................. : 207 365 -- 207 857 # 176 129
35 207 / 11............................. : 208 036 -- 208 801 # 176 129
35 207 / 13............................. : 208 802 -- 209 013 # 176 129
35 207 / 15............................. : 209 014 -- 209 436 # 176 129
1 456 / 11.............................. : 209 437 -- 209 778 # 176 129
1 456 / 15.............................. : 209 779 -- 210 319 # 176 129
1 456 / 19.............................. : 210 320 -- 210 814 # 176 129
1 456 / 24.............................. : 210 962 -- 211 410 # 176 129
58 346 / 17............................. : 211 411 -- 212 003 # 176 129
58 346 / 20............................. : 212 180 -- 212 541 # 176 129
58 482 / 1.............................. : 212 542 -- 213 295 # 176 129
58 482 / 4.............................. : 213 296 -- 213 819 # 176 129
58 482 / 6.............................. : 213 820 -- 214 196 # 176 129
62 835 / 2.............................. : 215 802 -- 216 264 # 176 129
39 545 / 6.............................. : 216 265 -- 216 571 # 176 129
39 545 / 8.............................. : 216 572 -- 216 681 # 176 129
39 545 /........ And So On 

On Wednesday, September 6, 2023 at 3:37:55 AM UTC+7 Alandata Recovery wrote:

   Model : WDC WD40NDZW-11MR8S1
  Serial : WD-WXD2DB1L8LES
Firmware : 02.01A02
Capacity : 4 TB (7 813 971 632)

I have this drive.

Came ready slowly with USB but had media errors.

unlocked rom

converted to sata

read 190

blocked UA writing

backedup resources.

shifted SA

loaded dir and drives from files

H3 wont write

ram edit for no H3

soft reset

drive comes ready  ID;s

read sect 0 - its encrypted

select decrypt - says it finds keys

still encrypted.

Anyone seen this ?

Thanks

=======================

Drive power supply...................... : OFF
Drive power supply...................... : ON
Drive identification reading ........... : Ok
 
Resources folder........................ : <HDD Profile>\Data\SABackup\Modules\Copy 1
Cache ovl(10) data uploading............ : Ok
Permanent ovl (11) data uploading....... : Ok
Module 02 uploading..................... : Ok
 
Map data writing........................ : Ok
Software reset.......................... : Ok
Drive identification reading ........... : Ok
 
SED key checking
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
Encryption.............................. : Self Encryption HDD v2
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
SED key checking
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
Encryption.............................. : Self Encryption HDD v2
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
External encryption key checking

UA key reading:7 813 965 856............ : Ok

SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : Ok

 
UA key reading:7 813 967 235............ : Ok

SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : Ok

 
UA key reading:7 813 965 832............ : Ok

SA key reading:Copy 0................... : Has been already read
SA key reading:Copy 1................... : Has been already read

 
UA key reading:7 813 971 592............ : Ok
 

SED key checking
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
Encryption.............................. : Self Encryption HDD v2
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
SED key checking
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
Encryption.............................. : Self Encryption HDD v2
Key 018D................................ : Wrong single key size
Key 018E................................ : Wrong single key size
External encryption key checking

UA key reading:7 813 965 856............ : Ok

SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : Ok

 
UA key reading:7 813 967 235............ : Ok

SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : Ok

 
UA key reading:7 813 965 832............ : Ok

SA key reading:Copy 0................... : Has been already read
SA key reading:Copy 1................... : Has been already read

 
UA key reading:7 813 971 592............ : Ok

========================

[pbzcbf...@gmail.com]

What would happen if you were to remove the DIR entry for mod 190 from the DIR? That would be a relatively trivial edit.

[pbzcbf...@gmail.com]

Are these areas at the end pf the module? If so, couldn't we avoid loading these areas by reducing the size of the module in the DIR?