Asus SDRW-08D2S-U support?

[gingerbeardman]

I bought a SDRW-08D2S-U but redumper is not detecting it?

https://github.com/superg/redumper/blob/1f4a560dd4dd6b704e5dcf9aa5c71aa59e2c01d0/drive.ixx#L205

[superg]

By not detecting you mean what exactly, unable to dump anything and mass errors?

[gingerbeardman]

When I run redumper it says no recognised drives are found (or something along those lines)

Even though the drive is connected and has power and I can dump using other tools.

[superg]

Can you provide a log output?

[gingerbeardman]

Sure, but please tell me exactly how to produce the logs you need.

% ./redumper
error: no ready drives detected on the system

There is a disc in the drive (I've tried with it mounted and unmounted)

[superg]

So that has nothing to do with not detecting the drive, basically something holds the drive and redumper doesn't see it. Which OS do you use, is it Windows?

[gingerbeardman]

No, I'm on macOS. I will see what could be holding the drive.

I tried in Windows 11 ARM VMware and the drive is recognised and dumping begins.

PS C:\Users\matt\Desktop\redumper-2024.04.07_build317-win64\bin> ./redumper.exe
warning: drive read offset not found in the database
redumper v2024.04.07 build_317 [Apr  7 2024, 19:05:43]

drive path: D:
drive: ASUS - SDRW-08D2S-U (revision level: BA01, vendor specific: 2019/06/21 12:53)
drive configuration: GENERIC (read offset: +0, C2 shift: 0, pre-gap start: +0, read method: BE, sector order: DATA_C2_SUB)
drive read speed: <optimal>

current profile: CD-ROM

image path: .
image name: dump_240407_215355_D

*** DUMP

disc TOC:
  track 1 {  data }
    index 01 { LBA:      0, MSF: 00:02:00 }
  track A {  data }
    index 01 { LBA: 134983, MSF: 30:01:58 }

warning: unsupported drive read method
warning: unable to read CD-TEXT, SCSI (SC: CHECK CONDITION, SK: ILLEGAL REQUEST, ASC: INVALID FIELD IN CDB)
/ [  2%] LBA:   2777/134983, errors: { SCSI: 0, C2: 2778, Q: 2778 }

Regarding "warning: drive read offset not found in the database" just now I read at accuraterip that this drive has been purged from recommendation due to hardware changes throughout its lifespan. I guess my drive is a recent one (BA01, year 2019) and has different read offset than the earlier hardware (B901, year 2015).

[superg]

Did you unmount the drive? There are steps in readme on how to do it.

[gingerbeardman]

Yes, indeed, I did unmount the drive on macOS.

The problem is present with the drive unmounted.

[gingerbeardman]

here's a screenshot

[gingerbeardman]

I notice with this drive it's not possible to dump mixed mode discs, even on Windows?

[superg]

Let's solve one issue at a time. I've just realized you didn't provide --drive argument to redumper. Execute diskutil list and provide this argument like it is described in https://github.com/superg/redumper/blob/main/README.md#macos

[gingerbeardman]

% ./redumper --drive=disk5
error: failed to create service plugin interface, MACH ((iokit/common) resource shortage)

I also just read in the readme that I shouldn't have bought this drive, so feel free to close and I will buy a more supported one, and I will use it in Windows VM.

[superg]

If you read https://github.com/superg/redumper/blob/main/README.md#macos until the end - there is an answer, just copy binary to /usr/local/bin and it will work. It's irrelevant of the drive, it will happen even with plextor or asus. Mac is full of undocumented surprises.

[gingerbeardman]

Ah, yes. Thanks!

To summarise: the following error is when all partitions are not unmounted (mixed mode CD) which can happen if you use Disk Utility GUI to unmount, but not when you use diskutil unmountDisk disk5

matt@matt ~
% redumper --drive=disk5 
error: failed to obtain exclusive access, MACH ((iokit/common) Device Busy)

[superg]

This is different error, looks like there are two issues. error: failed to create service plugin interface, MACH ((iokit/common) resource shortage) - this is the error related to where redumper is run from.

The other message error: failed to obtain exclusive access, MACH ((iokit/common) Device Busy) basically mean that something else is using the drive.