mirror of
https://github.com/aaru-dps/Aaru.git
synced 2026-02-04 09:04:35 +00:00
Address and mode bytes of intentional error sector on SecuROM CD sometimes zeroed out #875
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jbodoh7613 on GitHub (Apr 8, 2022).
Originally assigned to: @claunia on GitHub.
Version
5.3.0
Commit hash
No response
Tested debug version?
Which operating systems have you used?
What is the architectural bit size you're using?
What processor are you using?
Device manufacturer
LG HL-DT-ST
Device model
BD-RE BE16NU50
Bus the device uses to attach to the computer
USB cable or card reader manufacturer
No response
USB cable or card reader model
No response
What were you doing when it failed?
Description
When dumping a SecuROM CD, Aaru sometimes zeroes out the address and/or mode bytes of the intentional bad sector (the 4th to last sector) on the disc. This happens intermittently as, most of the time, I am able to get dumps of SecuROM CDs that match Redump hashes.
Exact command line used
aaru media dump --force True --speed 4 --retry-passes 5 --first-pregap True -d "H:" "RollerCoaster Tycoon 3 Platinum! (USA).aaruf"
Expected behavior
I would get a dump whose hashes would conform to http://redump.org/disc/16609/
Actual behavior
After converting to bin/cue, the resulting bin file differed from the image matching the Redump hash by 4 bytes. The 3 address bytes of the intentional bad sector, starting at file offset 0x30F8334C, should be "77 39 33," the correct address for the sector, but all 3 bytes are "00". The mode byte, found at file offset 0x30F8334F, should be "02" as the mode byte of the intentional bad sector on SecuROM discs always specify the incorrect mode for the sector ("02" for mode 1 sectors and "01" for mode 2 sectors). Instead, it is "00".
Note: The image file that https://github.com/aaru-dps/Aaru/issues/723 works with is dumped from the same disc and has the same issue, but the mode byte reads the proper value of "02."
Output of command execution with debug output enabled
Media details
https://i.ebayimg.com/images/g/pjUAAOSwhTxh80z1/s-l1600.jpg
@TheRogueArchivist commented on GitHub (Apr 8, 2022):
Would you be able to define "intermittently" please? As in, is it always the same CDs that are dumped incorrectly, or will the same disc be dumped differently by Aaru at different times?
@jbodoh7613 commented on GitHub (Apr 8, 2022):
Aaru seems to dump the same disc differently over multiple dumps. When I dumped the disc image used in the bug report https://github.com/aaru-dps/Aaru/issues/723, it properly dumped the mode byte of the sector, but later dumps of the same disc have that mode byte zeroed out. Also, there are a number of SecuROM discs that I have had to dump multiple times before Aaru would produce a dump that matched Redump, but I have not confirmed yet whether this was due to this bug.
@claunia commented on GitHub (Apr 8, 2022):
rtc3dump.txt