aaru-dps/Aaru-aaru-dps
1
0
Fork 0
mirror of https://github.com/aaru-dps/Aaru.git synced 2026-02-04 00:54:33 +00:00
Code Issues 657 Packages Projects Releases 19 Wiki Activity

Dynamically decide how many times to retry unreadable sectors and subchannels #679

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

Originally created by @TheRogueArchivist on GitHub (Feb 27, 2021).

Check and fill as appropriate:

  • Support for a new media image format...
  • Support for identifying a new filesystem...
  • Support for extracting files from a new filesystem...
  • New command...
  • Improvement to output...
  • Other...

Detailed Description

Dynamically decide how many times to retry unreadable sectors and subchannels based on how many passes have been made without recovering any new data. It would probably also be a good idea to specify how many sectors/subchannels have to be correctly retried in order for Aaru to decide to perform another rerun. For example, for subchannel retries, you may want to specify a minimum of 10 successful retries on the current retry pass to decide if it's worth performing another pass.

Context

This is would be very useful in many cases, including on any CD dump made. For example, this would easily catch the vast majority of readable subchannel data by waiting until the drive has stopped returning successful retries before stopping new retires.

Originally created by @TheRogueArchivist on GitHub (Feb 27, 2021). <!--- Provide a general summary of the issue in the Title above --> ### Check and fill as appropriate: * [ ] Support for a new media image format... * [ ] Support for identifying a new filesystem... * [ ] Support for extracting files from a new filesystem... * [ ] New command... * [ ] Improvement to output... * [X] Other... ## Detailed Description <!--- Provide a detailed description of the change or addition you are proposing --> Dynamically decide how many times to retry unreadable sectors and subchannels based on how many passes have been made without recovering any new data. It would probably also be a good idea to specify how many sectors/subchannels have to be correctly retried in order for Aaru to decide to perform another rerun. For example, for subchannel retries, you may want to specify a minimum of 10 successful retries on the current retry pass to decide if it's worth performing another pass. ## Context <!--- Why is this change important to you? How would you use it? --> <!--- How can it benefit other users? --> This is would be very useful in many cases, including on any CD dump made. For example, this would easily catch the vast majority of readable subchannel data by waiting until the drive has stopped returning successful retries before stopping new retires.
claunia added the feature request label 2026-01-29 15:26:19 +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 feature request
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#679
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?