peclark
Member
I haven't been able to find any other posts about getting a ZuluSCSI to work with an AT&T 3b2/600, so I thought I'd share my experience here.
My 3b2/600 has 2 70MB ESDI hard disks in it, and they are connected to the SCSI controller through an Emulex SCSI to ESDI bridge card. I figured I could connect the ZuluSCSI directly to the SCSI controller and get the machine up and running on a hard disk image on the ZuluSCSI, but was having trouble getting the Unix kernel to recognize the Zulu SCSI device. I figured I needed to get the device ID string that's returned from the real hard disk so that I could get the Zulu to emulate that same device ID, and sure enough, that fixed the problem.
The interesting thing about this (at least to me) was that it was actually the Emulex SCSI to ESDI bridge device ID that the kernel was looking for. In my case, here's the settings I had to use in the ZuluSCSI config.
[SCSI1]
Vendor = "EMULEX "
Product = "MD23/S2 ESDI"
Version = "B00 "
Type = 0
One of the new features of the new ZuluSCSI enabled me to capture this - I used the initiator mode of the Zulu, connected as a "SCSI Controller" to the Emulex board. This allowed me to capture the device ID string, and also to image the physical ESDI hard disk (as if it was a SCSI disk). (It only imaged the first hard disk for some reason, and I haven't looked into why yet, but for me it didn't really matter as there really isn't much on the second hard disk - just a /usr2 filesystem without anything on it...).
I haven't had success yet getting my 3b2 to read a scsi tape, but I don't think that is the fault of the Zulu, I think it is more to do with the file format I am using for the tape files. I've been trying to work with some of the SVR 3.2.3 install tapes, that have the install kernel first on the tape, then a directory of the features that can be installed, then disk images following that... The problem I've been running into is whenever I try to use the package management feature to install features, it will access the tape, but always returns that reading the tape header failed, so I have some more work to do to figure out what the right format is I believe.
Anyway, just wanted to share the config info if anyone else has been having issues getting a scsi emulator working to replace the physical hard disks in a computer like this...
My 3b2/600 has 2 70MB ESDI hard disks in it, and they are connected to the SCSI controller through an Emulex SCSI to ESDI bridge card. I figured I could connect the ZuluSCSI directly to the SCSI controller and get the machine up and running on a hard disk image on the ZuluSCSI, but was having trouble getting the Unix kernel to recognize the Zulu SCSI device. I figured I needed to get the device ID string that's returned from the real hard disk so that I could get the Zulu to emulate that same device ID, and sure enough, that fixed the problem.
The interesting thing about this (at least to me) was that it was actually the Emulex SCSI to ESDI bridge device ID that the kernel was looking for. In my case, here's the settings I had to use in the ZuluSCSI config.
[SCSI1]
Vendor = "EMULEX "
Product = "MD23/S2 ESDI"
Version = "B00 "
Type = 0
One of the new features of the new ZuluSCSI enabled me to capture this - I used the initiator mode of the Zulu, connected as a "SCSI Controller" to the Emulex board. This allowed me to capture the device ID string, and also to image the physical ESDI hard disk (as if it was a SCSI disk). (It only imaged the first hard disk for some reason, and I haven't looked into why yet, but for me it didn't really matter as there really isn't much on the second hard disk - just a /usr2 filesystem without anything on it...).
I haven't had success yet getting my 3b2 to read a scsi tape, but I don't think that is the fault of the Zulu, I think it is more to do with the file format I am using for the tape files. I've been trying to work with some of the SVR 3.2.3 install tapes, that have the install kernel first on the tape, then a directory of the features that can be installed, then disk images following that... The problem I've been running into is whenever I try to use the package management feature to install features, it will access the tape, but always returns that reading the tape header failed, so I have some more work to do to figure out what the right format is I believe.
Anyway, just wanted to share the config info if anyone else has been having issues getting a scsi emulator working to replace the physical hard disks in a computer like this...