Aaru
Aaru copied to clipboard
Aaru reports inconsistent number of blocks while dumping
Version
5.3.0
Commit hash
No response
Tested debug version?
- [X] Yes
Which operating systems have you used?
- [X] Windows
- [ ] Linux
- [ ] macOS
- [ ] Other
What is the architectural bit size you're using?
- [ ] 32-bit
- [X] 64-bit
- [ ] Unsure or unknown
What processor are you using?
- [X] An Intel or AMD
- [ ] An ARM or Apple Silicon
- [ ] Unsure or unknown
Device manufacturer
Multiple
Device model
Multiple BD drives
Bus the device uses to attach to the computer
- [ ] Parallel ATA
- [X] Serial ATA
- [ ] SCSI (any)
- [ ] ATAPI (mark above if parallel or serial)
- [ ] USB
- [ ] FireWire
- [ ] PCMCIA
- [ ] SecureDigital
- [ ] MultiMediaCard
USB cable or card reader manufacturer
No response
USB cable or card reader model
No response
What were you doing when it failed?
- [X] I was dumping media (disk, tape, etc)...
- [ ] I was retrieving media (disk, tape, etc) information...
- [ ] I was scanning media (disk, tape, etc)...
- [ ] I was retrieving device information...
Description
When dumping, Aaru says that the drive reports a certain number of blocks two times, with both times being different from one another, with a difference of 1. For this specific disc, ImgBurn confirms a block number of 2992384, so that seems to be the right one.
Exact command line used
aaru m dump D: Nutcracker.aaruf
Expected behavior
Blocks reported to be identical
Actual behavior
Blocks reported off by one of each other.
Output of command execution with debug output enabled
-11-04T11:44:10 Output image format: Aaru Format.
2021-11-04T11:44:10 Device not in database, please create a device report and attach it to a Github issue.
2021-11-04T11:44:10 Device reports current profile is 0x0040
2021-11-04T11:44:10 Device reports disc has 2992383 blocks
2021-11-04T11:44:10 Reading Disc Information.
2021-11-04T11:44:10 Reading Burst Cutting Area.
2021-11-04T11:44:10 Initializing reader.
2021-11-04T11:44:10 Device reports 2992384 blocks (6128402432 bytes).
Media details
No response