Build a BlueSCSI Vintage Hard Drive Emulator: SD Card SCSI Storage for Classic Mac, Amiga, and SGI Workstations
Vintage SCSI hard drives are dying, and they're not coming back — original 1980s and 1990s spinning SCSI disks are decades past their design life, and when one fails in a classic Mac, an Amiga, or an SGI or Sun workstation, replacing it with another equally old, equally failing drive just delays the same problem. BlueSCSI solves this the same way flash storage has solved it for IDE and floppy drives elsewhere in retrocomputing: an RP2040-based board emulates a SCSI hard drive (or CD-ROM, or removable media) entirely in firmware, reading and writing disk images from a modern SD card instead of spinning platters. This project covers building or configuring a BlueSCSI unit, preparing disk images, and getting it talking correctly to a specific vintage platform.
Why This Matters
SCSI was the standard storage interface across an entire generation of professional and prosumer computing — classic Macintoshes, Amiga expansion storage, early SGI and Sun UNIX workstations, and plenty of vintage scanners and other peripherals all speak it. Every one of those original drives is now an unreliable, increasingly rare point of failure. A SCSI emulator built on cheap, available modern hardware means a machine's storage becomes as durable and swappable as an SD card — image-based, easy to back up, and trivial to expand in capacity within whatever limits the target platform's BIOS or firmware supports.
Hardware Options
OptionCost/EffortNotes Pre-built BlueSCSI board (v2 and similar commercial boards)Low effort, moderate costReady to flash and use, good default choice for a first build DIY Raspberry Pi Pico + carrier boardHigher effort, lower costRequires soldering your own connector and level-shifting if needed; good option if you already have Picos on hand SCSI2SD (older, PIC-based alternative project)Comparable cost to pre-built BlueSCSIA related but separate project predating BlueSCSI — worth knowing about, BlueSCSI has broader active development at this pointTarget connector type depends entirely on what you're plugging into — classic Macs commonly use a DB25 SCSI port, while many workstations and internal drive bays use a 50-pin Centronics or IDC connector. Confirm your target machine's connector and cabling before ordering or building anything, since an adapter cable is a much simpler fix than discovering a connector mismatch after your board is soldered.
Building and Flashing
- Assemble or acquire your board. For a DIY Pico-based build, this means soldering the Pico to a carrier PCB (widely available as open-source design files) that breaks out the SCSI connector pins and handles the necessary termination and level-shifting for the SCSI bus's signaling voltage.
- Flash the BlueSCSI firmware. Like most RP2040 projects, this is a drag-and-drop UF2 flash — hold the Pico's BOOTSEL button, connect via USB, and copy the firmware file onto the drive that appears. No special programmer hardware needed.
- Set SCSI ID and termination. Every device on a SCSI bus needs a unique ID (0-7 typically, with ID 7 usually reserved for the host controller), and the last physical device on the chain needs termination enabled. BlueSCSI configures both of these in software/config file rather than physical jumpers on most builds, which is a genuine quality-of-life improvement over the DIP-switch fiddling original SCSI drives required.
Preparing Disk Images
BlueSCSI reads disk images directly off a FAT32-formatted SD card, with filenames that encode the target SCSI ID and device type (a naming convention documented in the project's own guide — get this wrong and the emulated device won't appear on the bus at all). For a classic Mac, you'll typically start from a blank image sized appropriately for your target OS and format it as HFS using period-appropriate tools running on the vintage machine itself (or use a pre-made, pre-formatted blank image from the community, which saves a chicken-and-egg problem when you have no working boot drive yet). For other platforms, the process is analogous but uses that platform's own filesystem and formatting utility. The BlueSCSI project also supports a special "shared" folder mode on some builds, mapping a single directory on the SD card as a live filesystem the vintage machine can read and write directly — handy for moving files on and off without swapping media.
Platform Notes
PlatformNotes Classic Macintosh (68k and early PowerPC)DB25 external or internal 50-pin, format via Apple HD SC Setup or a period-correct formatter run from the target Mac Commodore AmigaWorks with SCSI expansion cards; format using Amiga-native tools SGI / Sun workstationsInternal 50-pin, generally the most demanding platform for correct termination and ID configuration — check platform-specific BlueSCSI documentation closelyTroubleshooting
Most BlueSCSI problems trace back to one of three things: a SCSI ID conflict with another device already on the bus, missing or incorrect termination (especially common if you've got the emulator at the physical end of a chain but haven't enabled its termination), or a disk image filename that doesn't match the naming convention BlueSCSI expects. Check these three in order before assuming a hardware fault.
Enclosure and Integration
A bare Pico-and-carrier-board build works fine sitting loose inside a case, but a small 3D-printed enclosure — mounting the SD card for easy access and routing the SCSI cable and any activity LED cleanly — makes the difference between a permanent installation and something you're afraid to bump. This is a straightforward parametric design job in OpenSCAD or Fusion 360 once you have your specific board's mounting hole pattern measured.
BlueSCSI is one of the more quietly important projects in retrocomputing right now — it's the difference between a vintage machine being a museum piece you're afraid to power on and a machine with reliable, expandable, easily backed-up storage you can actually use. If you're already running RetroPie or other retro projects on Raspberry Pi hardware, this is a natural companion project for the actual vintage originals sitting on your shelf.
Related Guides
- CircuitPython for Makers: Getting Started on ESP32 and Raspberry Pi Pico
- Raspberry Pi Pico vs Arduino: Choosing the Right Board for Your Project
- Build a Standalone BadUSB Device with a Raspberry Pi Pico (No Flipper Required)
- Build a Custom MIDI Controller: Arcade Buttons, Potentiometers, and Raspberry Pi Pico as a USB MIDI Device