ZuluSCSI RP2040 Initiator mode failing to read 20MB RODIME: RO652A

[davidfrerichs]

Hello, I am trying to image a RODIME: RO652A 20MB (yes, you read that right) hard drive from my Mac SE using Initiator mode but it is failing to read the drive. The drive works fine in the Mac SE, so I know it is functional.

It feels like I should be able to give the RP2040 a hint in the zuluscsi.ini about the nature of the drive, but I am unclear how to put the information into the config.

Helpful hints super appreciated.

The drive has the following stats:

• Form 3.5"/HH
• Cylinders 306
• Capacity form/unform 21/25 MB
• Heads 4
• Seek time/track 85.0/18.0 ms
• Sector/track 34 (or 32, documentation I found says both)
• Interleave Factor = 2
• Controller SCSI1 SINGLE-ENDED Precompensation
• Cache/Buffer 4 KB FIFO BUFFER Landing Zone
• Data transfer rate 0.937 MB/S int
• Bytes/Sector 512 (or 532, documentation I found says both)
• Recording method RLL 2/7

Here is the log:
[12ms] Platform: ZuluSCSI RP2040
[12ms] FW Version: 24.05.17-release May 17 2024 16:24:20
[13ms] DIP switch settings: debug log 0, termination 1
[13ms] SCSI termination is enabled
[14ms] Flash chip size: 4096 kB
[14ms] SCSI initiator mode selected by DIP switch, expecting SCSI disks on the bus
[33ms] SD card detected, FAT32 volume size: 7574 MB
[33ms] SD MID: 0x03, OID: 0x53 0x44
[33ms] SD Name: SA08G
[34ms] SD Date: 8/2022
[34ms] SD Serial: 0xBF0BAF43
[718ms] InitiatorID set to ID 0x07
[1251ms] Initialization complete!
[12754ms] scsiHostRead: received 0 bytes, expected 8
[12754ms] scsiHostRead failed, tried to read 8 bytes
[12755ms] SCSI ID 0 responds but ReadCapacity command failed
[12755ms] Possibly SCSI-1 drive? Attempting to read up to 1 GB.
[13513ms] Starting to copy drive data to HD00_imaged.hda
[13516ms] scsiInitiatorReadDataToFile: READ failed: -1 sense key 0x00
[13516ms] Failed to transfer 128 sectors starting at 0
[13517ms] Retrying.. 1/5
... (more of this forever)

[davidfrerichs]

UPDATE: turns out the drive was reporting on all LUNs (sub-addresses of the SCSI ID used to access multiple physical drives on a single device) which confused the process. Loaned the drive to RabbitHole so they could investigate a firmware fix.