I am working on a VeniceR Plus 2 Lite Plus drive encountering issues loading module 01



Normally with this issue we block module 30, upload a loader and search SA for module 01 but the module search did not find it, but it found everything else. So I created a new module 01 based on the SA search, added a new entry for module 01 at a different ABA and then uploaded it to the drive. When I unblock module 01 and restart the drive it gets ready in kernel mode with the same error.. so I block 30 and upload loader back to the drive, module 01 has been rewritten with a corrupted version with only 14 modules listed. This happens no matter where I put it.
Heads can read and write just fine, but after restarting the drive it changes module 01 back.
Any advice would be appreciated.

This is a problem with this new Family and the Devs from Ace are already working on this issue.

In this Family the Modules in the dir have all a different ABA location, what makes the Mod01 in this family in fact "unique".

Exactly because of this behavior in this Familiy Ace implemented the warning in all SMR-Families, when you attempt to block the SA Access in ROM.

We were able to gain access to the SA again with files from a donor with same Size, Model, ROM F/W, Country, etc. Were even able to get full size back and start a copy via utility. But the translator-structure of this familiy isn't fully developed yet, so analyzing the T2 was not accurate so recovery brought only disfunctional files back.

You have to contact ace-support and hope that they were able to make some reverse-engineering progress over the past few weeks.

dunno what's so specific about these for you guys, i recall no problems with this family. T2 is static and linear, coz it is actually a CMR disk.
am i missing something obvious?

pepe

_________________
Adatmentés - Data recovery

Nobody said something else. The warning when blocking SA acess in ROM, appears (imho - correct me if i'm wrong) only in Drives with T2 Translator (so mostly SMR-Drives):



The struggle is real.


Did you tried to block the SA Access in ROM when you worked on those Drives?

i practically never shift regions..., most probably that's why i never met this dialog. Nor the problem itself...

_________________
Adatmentés - Data recovery

Ok, interesting. How do you prevent HDs internal Firmware loading process then?

i just came accross this page after I blocked SA in ROM and got access to user files with the file structure and all. But the files are all bad. How do I go back

Family:................................. : VeniceR
Techno mode key......................... : Ok

HDD Status sector....................... : Ok

RAM:
System controller (SoC)................. : 88i1054A1 (0x5471)
HDD Info reading........................ : Ok
Heads number............................ : 6
Cyl Count............................... : 384

ROM:
Read ROM................................ : Ok
ROM Data size........................... : 1024 Kb
Flash ROM dir reading................... : Ok (Active)
Flash ROM dir reading (Ext)............. : Ok
SA regions address...................... : by default
SA regions address (RAM)................ : by default
Module 02 access........................ : Granted

WWN..................................... : 50014EE2157E968F

SA SPT.................................. : 2700

SA Translator loading................... : Ok
SA defects assigned..................... : 6

ROM Modules:
ROM version............................. : 04.20H0
Module 4F F/W version................... : 0053004R
Overlay F/W version..................... : 04.21H0
Servo F/W version....................... : A8.1U

Heads configuration..................... : by map
Heads number............................ : 6
Heads number in use..................... : 6
Switched off heads...................... : No
Heads map............................... : 0,1,2,3,4,5

Relocations............................. : 0 (2 460)
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 | Mdl ID | Description (64-bits)
----+------+--------+------------------+----------+--------+----------------------------------------------
68 | 227 | 5.19 s | C000401217FFDFF | 51043746 | 13A | Load GPD-List (13A)(FM ERR NOT FOUND IN DIR)
89 | 223 | 6.73 s | 1C288421EFFFFDFF | 51043D9C | 190 | End Process 190(GPD-List (13A) not found)
----+------+--------+------------------+----------+--------+----------------------------------------------

Service area:
SA dir reading (ID)..................... : Ok
Dir items loaded........................ : 586

SA Access............................... : Copy 0,Copy 1

Configuration reading................... : Ok
DLG-II.................................. : Yes
DRAM-Egress Protection to SPI Flash..... : Yes
CFG tech mode lock...................... : No
Self encryption drive................... : No
Master Password......................... : has not been set
User Password........................... : has not been set
UA writing.............................. : Blocked

DCM in module 47........................ : JH
DCM in module 0A........................ : |R|GJHA4N7
DCM in module 02........................ : S|BRLNPGMJHHCAR4VNKAUP

Host Debug Stop Log..................... : 0421 (TRANSOVL) CB65 32D
DEBUGSTOP code 0x1A102, param 0x606C6AD8, flags 0x00000021 HOST DEBUGSTOP RESET TIMEOUT
Power on Hours: 358 (14d, 22h)

To be able to create utilty based DE task, start "Prepare to get UA PBA access"

Read sectors (2 048-1) ext error Device error detected "ABR"
Read sectors (11 721 045 167-1) ext error Device error detected "ABR"
SED key checking
Key 018D................................ : Module 18D not found
Key 018E................................ : Module 18E not found
Encryption.............................. : Self Encryption HDD v2
Key 0123................................ : Module 123 reading error: ABA 27 081 C:1(1) reading error Device Error Detected: "DISK ECU UNSAFE ERROR"
Key 0124................................ : Module 124 reading error: ABA 27 082 C:1(1) reading error Device Error Detected: "DISK ECU UNSAFE ERROR"
Key D004................................ : Module D004 reading error: ABA 27 087 C:1(1) reading error Device Error Detected: "DISK ECU UNSAFE ERROR"
Key 018D................................ : Module 18D not found
Key 018E................................ : Module 18E not found
SED key checking
Key 018D................................ : Module 18D not found
Key 018E................................ : Module 18E not found
Encryption.............................. : Self Encryption HDD v2
Key 0123................................ : Module 123 reading error: ABA 27 081 C:1(1) reading error Device Error Detected: "DISK ECU UNSAFE ERROR"
Key 0124................................ : Module 124 reading error: ABA 27 082 C:1(1) reading error Device Error Detected: "DISK ECU UNSAFE ERROR"
Key D004................................ : Module D004 reading error: ABA 27 087 C:1(1) reading error Device Error Detected: "DISK ECU UNSAFE ERROR"
Key 018D................................ : Module 18D not found
Key 018E................................ : Module 18E not found
External encryption key checking
SA key reading:Copy 0................... : Ok
SA key reading:Copy 1................... : With errors

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

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


Read sectors (11 721 045 167-1) ext error Device error detected "ABR"
Read sectors (5 000 000 000-1) ext error Device error detected "ABR"
Drive power supply...................... : OFF
Drive power supply...................... : ON
Drive power supply...................... : OFF
Drive power supply...................... : ON
Read sectors (11 721 045 167-1) ext error Device error detected "ABR"
Read sectors (0-1) ext error Device error detected "ABR"
HDD ID reading.......................... : Ok
HDD ID writing.......................... : Ok
Drive power supply...................... : OFF
Drive power supply...................... : ON
Read sectors (11 721 045 167-1) ext error Device error detected "ABR"
Read sectors (2 048-1) ext error Device error detected "ABR"
Read sectors (2 048-1) ext error Device error detected "ABR"
Read sectors (0-1) ext error Device error detected "ABR"