Open kkaisershot opened 2 years ago
May be a bug in calculating the SpamSum checksum, which will no longer be performed by default in 6.0. As a workaround for the time being, you can run the media dump command with “—metadata False” to bypass the checksumming. To retrieve the checksums after the initial dump, you can use the image checksum command, and use “—spamsum False” to hopefully skip the checksum that appears to be crashing.
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
Maxtor
Device model
6B160M0
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
Dumping large (over 100GB) hard disks to Aaru format results in a "System.Exception: Assertion failed" at SpamSumContext.cs:119 upon nearly completing hashing sectors. I encountered this with a 160GB drive.
Note that the dropdown in the bug report form only lets me select 5.3.0, however I was also able to reproduce this in 5.3.1, both release and debug builds.
Exact command line used
./aaru media dump -O compress=False,deduplicate=False -v -d /dev/sdb /mnt/B42HDP2H.aaruf 2>&1 | tee output.txt
Expected behavior
Hashing sectors should complete without error, proceeding to close the image.
Actual behavior
Output of command execution with debug output enabled
Media details
Maxtor DiamondMax 10 Model:6B160M0 160GB SATA150 HDD LBA: 320173056