mirror of
https://github.com/aaru-dps/Aaru.git
synced 2026-07-08 17:56:18 +00:00
Suddenly stopped working. Even with disks that worked before #1016
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 @agowa on GitHub (Sep 5, 2025).
Version
Development commit
Commit hash
5.3.2+f4fef21d
Tested debug version?
Which operating systems have you used?
What is the architectural bit size you're using?
What processor are you using?
Description
It worked before but when I try the exact same disk now it doesn't and shows weird behaviour from just crashing when trying to read the disk to the drive disconnecting and reconnecting. Also in the cases where it doesn't crash then later on while reading the disk the drive will just be idle when it tries to "reread sectors" or subchannels.
Sometimes it is also still working correctly.
While filling this report I tried it about 20 times, it crashed about 15 times, started to dump 4 times and then failed to retry sectors. Then it worked 1 time perfectly fine again. Where as previously it worked for multiple disks all on the first try.
Logs later on show "os error 121" followed by a lot "os error 55" lines.
Is this some kind of old copy protection or something that I accidentally triggered? Rebooting windows also didn't help.
I suspect some older version of Quicktime player the installer of one of these games tried to install but failed because of it being 16 bit right after it supposedly installed another version of it that is slightly older. Is there anything like this known that could cause any future run of Aaru to behave in such non-deterministic ways?
Console output when it crashes:
Exact command line used
aaru.exe --verbose True media dump --force True --speed 24 --retry-passes 5 D: "TEST.aaruf"
Expected behavior
working or helpful error message
Actual behavior
appears to be buggy and not working. May be caused by some environmental conditions as it worked perfectly fine a few hours ago.
Output of command execution with debug output enabled