VeniceR Plus 2 Lite Plus family Mod 01 issue

[beefstrudel]

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

Code:

17 |  105 | 13.23 s | 4000000003F | 51015181 | 01     | EXEC_POWERUP_LOAD_DIR_DATA(DISK DAM ERROR)

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.

[crashpcberlin]

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.

[pepe]

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

[crashpcberlin]

coz it is actually a CMR disk.

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):

Screenshot 2025-12-11 221200.png (9.63 KiB) Viewed 243 times

The struggle is real.


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

[pepe]

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

[crashpcberlin]

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

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