(Crossposting from 68kmla as the BlueSCSI website advises coming here)
I have a puzzling BlueSCSI situation on my long-suffering Mac Classic. The Classic works, the original HDD works, and the BlueSCSI works, but the BlueSCSI will not boot from an image of the hard drive.
The Classic: An ordinary Mac Classic with 4 MiB of RAM. My first computer.
The BlueSCSI: A brand new BlueSCSI v2, confirmed working (you can boot the System 6.0.8 image in the "collection of... bootstrap images" linked from here). SD card is one of those recommended here, formatted as recommended.
The HDD: A bit of an oddball. On the surface, it's a 50 MB Quantum ProDrive LPS 52S. What's strange is that my Classic was sold with this drive as a third-party drive, with various bits of "internal" branding (e.g. via "Get Info") for GCC Technologies. When we got the computer, the Finder name for the drive was "GCC 50" instead of "Macintosh HD". Boots and runs, although I expect it's getting a wee bit sticky on the inside as most Quantums are. The third block of the disk image contains this, which I guess is part of some kind of driver (hidden for space):
It is also notable perhaps that what we see in block 1 is not the usual Apple_partition_map but instead just this:
and all zeroes everywhere else.
Anyway, in Initiator Mode, BlueSCSI will image this drive without issues. But turn around and try to use the drive image, and you get the blinking-? floppy icon. Drag the disk image onto an Infinite Mac emulation session, and the OS will ask you if you want to initialise an unreadable 50 MB hard disk. GCC Technologies must have done something weird when they prepared this otherwise ordinary hard drive to work with Macs, though you have to expect that given their history they knew what they were doing.
Does anyone have any idea of what might be going on here, and how I might successfully replicate my old Quantum drive with a BlueSCSI?
As a final clue (hopefully), here are the SCSI transactions you see when listening to the BlueSCSI over USB serial with Debug=1:
And then a little later:
And that's all there is as far as SCSI traffic goes: from here it's all just blinking-?
I have a puzzling BlueSCSI situation on my long-suffering Mac Classic. The Classic works, the original HDD works, and the BlueSCSI works, but the BlueSCSI will not boot from an image of the hard drive.
The Classic: An ordinary Mac Classic with 4 MiB of RAM. My first computer.
The BlueSCSI: A brand new BlueSCSI v2, confirmed working (you can boot the System 6.0.8 image in the "collection of... bootstrap images" linked from here). SD card is one of those recommended here, formatted as recommended.
The HDD: A bit of an oddball. On the surface, it's a 50 MB Quantum ProDrive LPS 52S. What's strange is that my Classic was sold with this drive as a third-party drive, with various bits of "internal" branding (e.g. via "Get Info") for GCC Technologies. When we got the computer, the Finder name for the drive was "GCC 50" instead of "Macintosh HD". Boots and runs, although I expect it's getting a wee bit sticky on the inside as most Quantums are. The third block of the disk image contains this, which I guess is part of some kind of driver (hidden for space):
Code:
00000400: 4efa 03de 6f00 0000 0000 0000 05fe 0858 N...o..........X
00000410: 06fa 07a0 06a6 072e 4658 6472 7672 061e ........FXdrvr..
00000420: 24b4 94f2 03e8 0008 2020 2047 4348 5831 $....... GCHX1
00000430: 5155 414e 5455 4d20 5034 3053 2020 2020 QUANTUM P40S
00000440: 5038 3053 2020 2020 5031 3035 5320 2020 P80S P105S
00000450: 4c50 3532 5320 2020 4c50 3130 3553 2020 LP52S LP105S
00000460: 2043 6f70 7972 6967 6874 2031 3938 362d Copyright 1986-
00000470: 3139 3930 2c20 4743 4320 5465 6368 6e6f 1990, GCC Techno
00000480: 6c6f 6769 6573 2049 6e63 2e20 4279 2046 logies Inc. By F
00000490: 7261 6e6b 2053 6c61 7567 6874 6572 2c20 rank Slaughter,
000004a0: 4461 6e20 5363 6877 696e 6e2c 2044 6176 Dan Schwinn, Dav
000004b0: 6520 4d63 436f 6f6c 2c20 4461 7665 2048 e McCool, Dave H
000004c0: 696c 6c2c 204c 6169 7264 2050 6f70 6b69 ill, Laird Popki
000004d0: 6e2c 2061 6e64 204d 6963 6861 656c 2046 n, and Michael F
000004e0: 7279 6172 2e00 003f fc00 0040 0600 00f0 ryar...?...@....It is also notable perhaps that what we see in block 1 is not the usual Apple_partition_map but instead just this:
Code:
00000200: 5453 0000 0080 0001 8e9b 5446 5331 0000 TS........TFS1..and all zeroes everywhere else.
Anyway, in Initiator Mode, BlueSCSI will image this drive without issues. But turn around and try to use the drive image, and you get the blinking-? floppy icon. Drag the disk image onto an Infinite Mac emulation session, and the OS will ask you if you want to initialise an unreadable 50 MB hard disk. GCC Technologies must have done something weird when they prepared this otherwise ordinary hard drive to work with Macs, though you have to expect that given their history they knew what they were doing.
Does anyone have any idea of what might be going on here, and how I might successfully replicate my old Quantum drive with a BlueSCSI?
As a final clue (hopefully), here are the SCSI transactions you see when listening to the BlueSCSI over USB serial with Debug=1:
Code:
[60317ms] DBG ---- SELECTION: 0
[60318ms] DBG ---- COMMAND: 0x08 (Read6)
[60318ms] DBG ------ OUT: 0x08 0x00 0x00 0x00 0x01 0x00
[60318ms] DBG BlueSCSI Toolbox enabled = enabled
[60318ms] DBG ------ Read 1x512 starting at 0
[60319ms] DBG ---- DATA_IN
[60322ms] DBG ---- Total IN: 512 OUT: 0 CHECKSUM: 31910
[60322ms] DBG ---- STATUS: 0 GOOD
[60330ms] DBG ---- MESSAGE_IN
[60330ms] DBG ------ IN: 0x00
[60331ms] DBG -- BUS_FREE
[60575ms] DBG -- BUS_BUSY
[60575ms] DBG ---- SELECTION: 0
[60576ms] DBG ---- COMMAND: 0x08 (Read6)
[60576ms] DBG ------ OUT: 0x08 0x00 0x00 0x02 0x13 0x00
[60576ms] DBG ------ Read 19x512 starting at 2
[60577ms] DBG ---- DATA_IN
[60577ms] DBG ------ Found 7 sectors in prefetch cache
[60635ms] DBG ---- Total IN: 9728 OUT: 0 CHECKSUM: 16263
[60635ms] DBG ---- STATUS: 0 GOOD
[60641ms] DBG ---- MESSAGE_IN
[60641ms] DBG ------ IN: 0x00
[60642ms] DBG -- BUS_FREE
[60642ms] DBG ---- SELECTION: 0
[60644ms] DBG ---- COMMAND: 0x08 (Read6)
[60644ms] DBG ------ OUT: 0x08 0x00 0x00 0x01 0x01 0x00
[60644ms] DBG ------ Read 1x512 starting at 1
[60644ms] DBG ---- DATA_IN
[60647ms] DBG ---- Total IN: 512 OUT: 0 CHECKSUM: 19221
[60647ms] DBG ---- STATUS: 0 GOOD
[60653ms] DBG ---- MESSAGE_IN
[60653ms] DBG ------ IN: 0x00And then a little later:
Code:
[62196ms] DBG ---- SELECTION: 0
[62197ms] DBG ---- COMMAND: 0x12 (Inquiry)
[62197ms] DBG ------ OUT: 0x12 0x00 0x00 0x00 0x6A 0x00
[62197ms] DBG ---- DATA_IN
[62198ms] DBG ---- Total IN: 106 OUT: 0 CHECKSUM: 7793
[62198ms] DBG ---- STATUS: 0 GOOD
[62206ms] DBG ---- MESSAGE_IN
[62206ms] DBG ------ IN: 0x00And that's all there is as far as SCSI traffic goes: from here it's all just blinking-?