"Error reading file: Arithmetic operation resulted in an overflow." extracting specific image #786

Open
opened 2026-01-29 15:29:46 +00:00 by claunia · 1 comment
Owner

Originally created by @TheRogueArchivist on GitHub (Jul 22, 2021).

Prerequisites

  • Are you running the latest version?
  • Can you reproduce the problem in the debug version?

Check and fill as appropriate:

  • I was running Aaru under Windows 10...
  • I was running Aaru under Linux [version here]...
  • I was running Aaru under macOS [version here]...
  • ...in 32-bit
  • ...in 64-bit
  • ...using an Intel / AMD processor
  • ...using an ARM or Apple Silicon processor
    • Image format: TOC
    • Application that created the image: cdrdao
  • I was converting the image...
    • ...Destination image format:
  • I was listing the filesystem contents...
  • I was extracting the filesystem contents...
    • ...Filesystem: ISO9660
    • Analyze command recognizes the filesystem
  • I was creating a metadata sidecar
  • I was checksumming the image
  • I was verifying the image

Description

When extracting a specific image, Aaru errors out on the 18th partition with "Error reading file: Arithmetic operation resulted in an overflow.". This may be an overflow due to the number of tracks, or may be some identification issue, since Aaru says "Identified by Microsoft File Allocation Table." when it should be an audio track.

Exact command line used:

aaru fs extract .\MediaDesignInteractive_Grooves.toc -x 1

Output of command execution with debug output enabled

...
Partition 17:
Identifying filesystem on partition
Filesystem not identified

Partition 18:
Identifying filesystem on partition
Identified by Microsoft File Allocation Table.
Error reading file: Arithmetic operation resulted in an overflow.

Image

https://archive.org/details/mediadesigninteractive_grooves

Originally created by @TheRogueArchivist on GitHub (Jul 22, 2021). ### Prerequisites * [X] Are you running the latest version? * [X] Can you reproduce the problem in the debug version? ### Check and fill as appropriate: * [X] I was running Aaru under Windows 10... * [ ] I was running Aaru under Linux [version here]... * [ ] I was running Aaru under macOS [version here]... * [ ] ...in 32-bit * [ ] ...in 64-bit * [ ] ...using an Intel / AMD processor * [ ] ...using an ARM or Apple Silicon processor * **Image format**: TOC * **Application that created the image**: cdrdao * [ ] I was converting the image... * ...**Destination image format**: * [ ] I was listing the filesystem contents... * [X] I was extracting the filesystem contents... * ...**Filesystem**: ISO9660 * [X] Analyze command recognizes the filesystem * [ ] I was creating a metadata sidecar * [ ] I was checksumming the image * [ ] I was verifying the image ### Description <!-- Description of the bug --> When extracting a specific image, Aaru errors out on the 18th partition with "Error reading file: Arithmetic operation resulted in an overflow.". This may be an overflow due to the number of tracks, or may be some identification issue, since Aaru says "Identified by Microsoft File Allocation Table." when it should be an audio track. ### Exact command line used: `aaru fs extract .\MediaDesignInteractive_Grooves.toc -x 1` ### Output of command execution with debug output enabled ``` ... Partition 17: Identifying filesystem on partition Filesystem not identified Partition 18: Identifying filesystem on partition Identified by Microsoft File Allocation Table. Error reading file: Arithmetic operation resulted in an overflow. ``` ### Image <!-- Upload the image, compressed and with the number of this issue. --> <!--- If the image contains personal data contact the project lead, and the image contents will be handled confidentially under the GDPR requirements. --> https://archive.org/details/mediadesigninteractive_grooves
claunia added the bugfilesystem labels 2026-01-29 15:29:46 +00:00
Author
Owner

@TheRogueArchivist commented on GitHub (Jul 23, 2021):

Doesn't occur on other 90+ track image, so this isn't purely an overflow due to a large number of tracks.

@TheRogueArchivist commented on GitHub (Jul 23, 2021): Doesn't occur on other 90+ track image, so this isn't purely an overflow due to a large number of tracks.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: aaru-dps/Aaru-aaru-dps#786