aaru-dps/Aaru-aaru-dps
1
0
Fork 0
mirror of https://github.com/aaru-dps/Aaru.git synced 2026-07-08 17:56:18 +00:00
Code Issues 657 Packages Projects Releases 19 Wiki Activity

Aaru reports inconsistent number of blocks while dumping #838

New Issue
Open
opened 2026-01-29 15:30:42 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 15:30:42 +00:00
Owner
Copy Link

Originally created by @TheRogueArchivist on GitHub (Nov 4, 2021).

Version

5.3.0

Commit hash

No response

Tested debug version?

  • Yes

Which operating systems have you used?

  • Windows
  • Linux
  • macOS
  • Other

What is the architectural bit size you're using?

  • 32-bit
  • 64-bit
  • Unsure or unknown

What processor are you using?

  • 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
  • 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?

  • 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

Originally created by @TheRogueArchivist on GitHub (Nov 4, 2021). ### 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 ```shell -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_
claunia added the bugmedia labels 2026-01-29 15:30:42 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
archive
beginner
bug
bug
dependencies
device
device
dump image format
duplicate
Epic
feature request
filesystem
filter
gui
gui
gui
help wanted
invalid
invalid
media
needs triage
partitioning scheme
pull-request
Mirrored from GitHub Pull Request
 upstream
wontfix
No Label bug media
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: aaru-dps/Aaru-aaru-dps#838
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?