I used builddisk to populate a blank 1GB image on a BlueSCSI. This was on a mono Turbo slab running OpenSTEP 4.2. That all seemed to work fine.
When I went to boot that image, and told bsd to use that image as the root device, it started to boot, and then complained about the disk being read-only, and the machine would not complete the boot.
I booted again from the internal disk and the machine came up fine, but the image on the BlueSCSI showed as a CD-ROM, and not as a spinny disk.
I then downloaded an .hda image created for Previous that is supposed to work with the BlueSCSI. It also started to boot, but again it was seen as a read-only device (sc0).
Is there something I need to do when creating the image or with the BlueSCSI to have these images be recognized as writable media?
OK - so during this I had the original spinning disk in the machine (SCSI ID 1) while the BlueSCSI had a higher address (tried both 6 and 2).
The BlueSCSI was in an external enclosure. Once I disconnected the internal drive so the BlueSCSI was the only thing on the bus, then it came up read/write and booted as expected.
So, some kind of SCSI voodoo or who knows? Anyway, it now works as I expected and I don't need to listen to that screaming Seagate anymore!