Quadra 700 Sad Mac

[paws]

Today I tried setting up my Quadra 700 again. It's been in a cupboard for a few years, but was working fine before that.

Unfortunately, it now powers up to a Sad Mac, with error code 0000000F 00000003, which is apparently a "memory addressing error". I've removed all RAM, VRAM, and Nubus cards, but it gives the same error.

Does anybody know this error? Any tips on how to proceed with troubleshooting? There are no obvious physical problems that I can see, and I wouldn't expect cap damage on a 700? There's no battery leakage. I could bring it to a place with a scope, but I'm not sure where to start looking.

 

[paws]

HUH! This is a weird one: I tried one of of my Macs (LC III), and it gave the chimes of death. Then I tried my Q650 and it gave the exact same error as my Q700!

It seemed strange that all of my Macs had died at the same time... but then I realized my tests had one thing in common: A brand new ZuluSCSI Blaster with a dump of my old SCSI2SD drive on it. And yes, apparently this was the cause. All three boot to blinking question marks after I removed that dump from the SD card. Very strange. I'll try to dig deeper and maybe make a different thread.

 

[lobust]

What do you mean by "dump"?

ZuluSCSI and SCSI2SD work very differently, I don't think there's any indication that the images are interchangeable?

 

[paws]

I took the SD card and made a full copy of the entire drive (with dd on Linux) to a file, put that on the disk as HD2.img. Might've been naive...

The Quadra's fine, though. Phew.

 

[Phipli]

I took the SD card and made a full copy of the entire drive (with dd on Linux) to a file, put that on the disk as HD2.img. Might've been naive...

The Quadra's fine, though. Phew.

It depends how exactly your SCSI2SD was set up, it might have worked, but extrapolating from available evidence... I'm going to say you didn't have it set up in a way that meant that worked

 

[paws]

Haha, nope! I saw a reference to using the ZuluBlaster in initiator mode to dump it, I might try that.

 

[lobust]

I've only ever used my SCSI2SD (V6) with the provided utility program and presented it to my macs as raw disks, and formatted them on the mac.

Do the "devices" on a SCSI2SD even exist as image files, or are they some kind of raw data?
The fact that you set them up as contiguous blocks of sectors doesn't really suggest to me that they are neatly saved as image files on the card...

Haha, nope! I saw a reference to using the ZuluBlaster in initiator mode to dump it, I might try that.

I'm not sure this would work - the SCSI2SD is not a single scsi device as presented to the host - can the ZuluSCSI in initiator mode recognise a chain of drives with different id's?

I think if I wanted to migrate the data, I'd attach both the SCSI2SD and the ZuluSCSI to a host mac and transfer the contents at the file system level instead.

 

[Phipli]

Do the "devices" on a SCSI2SD even exist as image files, or are they some kind of raw data?

Yeah, it is just raw data. The setup lets you define ranges to be presented as the disk for different IDs. You can do fancy things with it, copy images on and off, but you have to pay super hard attention to block counts and boundaries. Like you say, simpler to just format it on the classic Mac.

 

[paws]

They're not image files, the card has a readable Apple partition map with actual partitions much as if it were a SCSI HD. I'm able to mount the Mac partitions on my Linux machine if I just plug the SD card into a reader, that's why I thought dumping the whole thing to a file would work. The dumped (dd'ed) file is identified by the 'file' utility as Apple disk image, much the same as the one I just created with Disk Jockey (well, djjr).

I don't remember if I created the card in question with a SCSI2SD v5.1 or v6, I've had both. I think it was the 5.1. It might depend on how you set it up with offsets, as far as I recall you can put numbers in manually, but my computer interprets it as a HD with a Mac partition. I can see the files, but obviously copying things will nix the resource forks. Unfortunately I just remembered that my 5.1 is dead, so I'm not even sure I have the option to connect it to a Mac again...

As far as using initiator mode, what happens if you plug the Blaster into a case with multiple drives are devices in it?