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

Problems dumping MO discs #197

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

Originally created by @Altheos on GitHub (Feb 23, 2018).

Prerequisites

  • Are you running the latest version? 4.0.1.0
  • Can you reproduce the problem in the debug version? can't compile it

Check and fill as appropiate:

  • [x ] I was running DiscImageChef under Linux Ubuntu 17.10
  • ...using Mono 4.6.2.7
  • ...in 32-bit

Description

When dumping MO Disc, if DIC encounter a "bad" sector or a read problem, it can't pass thru.
The MO drive seems to be stuck trying to read. After reboot, DIC can read sectors and retry "bad" sectors successfully. Could possibly be a SCSI module problem.

Exact command line used:

sudo mono DiscImageChef.exe dump-media -i /dev/sdb -v -d --persistent=true -f -p 5 -w doe

Expected behavior:

DIC should bypass bad sector and not hang SCSI drive

Actual behavior:

SCSI drive can't read more sectors and a reboot is needed to recover

If command was expected to work with a device fill this:

  • Manufacturer: IBM
  • Model: MTA-3230
  • Bus:
    • SCSI (any)

Output of command execution with debug output enabled

DEBUG (SCSI Reader): READ error:
SCSI SENSE: MEDIUM ERROR
On logical block 125557
ID CRC OR ECC ERROR

Reading sector 125568 of 446325 (0,032 MiB/sec.)DEBUG (SCSI Device): READ (12) took 15620 ms.
DEBUG (SCSI Reader): READ error:

Reading sector 125632 of 446325 (0,002 MiB/sec.)DEBUG (SCSI Device): READ (12) took 47104 ms.
DEBUG (SCSI Reader): READ error:

STATE CUE CARD: (? means a positive number, usually 1 or 2, * means any number)
0x0 - starting (GOOD, unless the thread is running managed code)
0x1 - running (BAD, unless it's the gc thread)
0x2 - detached (GOOD, unless the thread is running managed code)
0x?03 - async suspended (GOOD)
0x?04 - self suspended (GOOD)
0x?05 - async suspend requested (BAD)
0x?06 - self suspend requested (BAD)
0x*07 - blocking (GOOD)
0x?08 - blocking with pending suspend (GOOD)
--thread 0xb58005e0 id 0xb7967b40 [(nil)] state 105
--thread 0x8b8d1e0 id 0xb7c8c700 [(nil)] state 1 GC INITIATOR
WAITING for 1 threads, got 0 suspended
suspend_thread suspend took 200 ms, which is more than the allowed 200 ms

[ 1224.856804] scsi host2: scsi scan: INQUIRY result too short (8), using 36
[ 1226.977866] sd 2:0:0:0: Attached scsi generic sg2 type 7
[ 1226.996147] sd 2:0:0:0: [sdb] 446325 512-byte logical blocks: (229 MB/218 MiB)
[ 1227.000442] sd 2:0:0:0: [sdb] Write Protect is on
[ 1227.000459] sd 2:0:0:0: [sdb] Mode Sense: 49 03 80 08
[ 1227.009274] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1227.177706] sdb:
[ 1227.214147] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 1230.093834] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[ 1230.093857] sd 2:0:0:0: [sdb] tag#0 CDB: ATA command pass through(16) 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00
[ 1420.268231] sdb: detected capacity change from 228518400 to 0

Originally created by @Altheos on GitHub (Feb 23, 2018). ### Prerequisites * [x] Are you running the latest version? 4.0.1.0 * [ ] Can you reproduce the problem in the debug version? can't compile it ### Check and fill as appropiate: * [x ] I was running DiscImageChef under Linux Ubuntu 17.10 * [x] ...using Mono 4.6.2.7 * [x] ...in 32-bit ### Description When dumping MO Disc, if DIC encounter a "bad" sector or a read problem, it can't pass thru. The MO drive seems to be stuck trying to read. After reboot, DIC can read sectors and retry "bad" sectors successfully. Could possibly be a SCSI module problem. ### Exact command line used: sudo mono DiscImageChef.exe dump-media -i /dev/sdb -v -d --persistent=true -f -p 5 -w doe ### Expected behavior: DIC should bypass bad sector and not hang SCSI drive ### Actual behavior: SCSI drive can't read more sectors and a reboot is needed to recover ### If command was expected to work with a device fill this: * **Manufacturer**: IBM * **Model**: MTA-3230 * **Bus**: * [x] SCSI (any) ### Output of command execution with debug output enabled DEBUG (SCSI Reader): READ error: SCSI SENSE: MEDIUM ERROR On logical block 125557 ID CRC OR ECC ERROR Reading sector 125568 of 446325 (0,032 MiB/sec.)DEBUG (SCSI Device): READ (12) took 15620 ms. DEBUG (SCSI Reader): READ error: Reading sector 125632 of 446325 (0,002 MiB/sec.)DEBUG (SCSI Device): READ (12) took 47104 ms. DEBUG (SCSI Reader): READ error: STATE CUE CARD: (? means a positive number, usually 1 or 2, * means any number) 0x0 - starting (GOOD, unless the thread is running managed code) 0x1 - running (BAD, unless it's the gc thread) 0x2 - detached (GOOD, unless the thread is running managed code) 0x?03 - async suspended (GOOD) 0x?04 - self suspended (GOOD) 0x?05 - async suspend requested (BAD) 0x?06 - self suspend requested (BAD) 0x*07 - blocking (GOOD) 0x?08 - blocking with pending suspend (GOOD) --thread 0xb58005e0 id 0xb7967b40 [(nil)] state 105 --thread 0x8b8d1e0 id 0xb7c8c700 [(nil)] state 1 GC INITIATOR WAITING for 1 threads, got 0 suspended suspend_thread suspend took 200 ms, which is more than the allowed 200 ms [ 1224.856804] scsi host2: scsi scan: INQUIRY result too short (8), using 36 [ 1226.977866] sd 2:0:0:0: Attached scsi generic sg2 type 7 [ 1226.996147] sd 2:0:0:0: [sdb] 446325 512-byte logical blocks: (229 MB/218 MiB) [ 1227.000442] sd 2:0:0:0: [sdb] Write Protect is on [ 1227.000459] sd 2:0:0:0: [sdb] Mode Sense: 49 03 80 08 [ 1227.009274] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1227.177706] sdb: [ 1227.214147] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 1230.093834] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK [ 1230.093857] sd 2:0:0:0: [sdb] tag#0 CDB: ATA command pass through(16) 85 06 20 00 05 00 fe 00 00 00 00 00 00 40 ef 00 [ 1420.268231] sdb: detected capacity change from 228518400 to 0
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
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#197
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?