VOGONS


First post, by ziper

User metadata
Rank Newbie
Rank
Newbie

Hello,
I am attempting to repair a scanning electron microscope made by a now-defunct company called Tracor-Northern, mid 80s vintage. It has not been used in at least a decade. I believe all the microscope hardware should be functioning. The computer hardware and software, however, is rather questionable. I don't know how much damage may have been caused before it was mothballed, by my repair efforts, or simply by age. If the computer half of the system is beyond repair, it is possible to reuse the microscope hardware with a new control system. The cost for such a refit starts at least $50,000. (And, of course, it is much more satisfying to get the original stuff working).

I have no documentation whatsoever on the machine. I can only hope there is a digital copy somewhere that can be recovered from what I have.

I made a very foolish error already by connecting a ground wire to the 5v rail. (In my defense, it was the same color as the +5v wiring, but I still should've rung it out). A jumper on the back of the hard drive smoked. I have no idea how much current was shunted or how much may have been going around damaging things.

The computer does not POST. It gives a beep code (that I have no idea the meaning of) and turns on the displays, but does not display anything. I am now trying to use a blueSCSI to clone the HD or any of the 3 tapes that I think have copies of the OS. Hopefully, I can run that software on the blueSCSI to get the computer to POST or at least get some documentation. (Yes, I probably should've done this before trying to power the machine.)

So, the hard drive: made in 1987 by Magnetic Peripherals, Inc. MN 94171-307, PN 77777009, no marked capacity, 50 pin SCSI connector. Besides the previously mentioned smoked jumper, no visible damage on any of the boards. When powered on, the spindle twitches, but does not spin up. It is free to move by hand, so probably not a friction issue. blueSCSI reports "NOT_READY, running STARTSTOPUNIT", so the board is able to communicate at least somewhat. A handful of similar (but not identical) SCSI drives are available on ebay. If the issue is the spindle motor controller, I could replace that IC from a donor board, but I'm not sure if that is the issue or even which chip is the controller. Am I correct in assuming that swapping over the whole PCB assembly would not work? (I know newer drives you can't do this, but maybe these drives are primitive enough that you could get away with that).

Or, the tapes. They are QIC-120, 3M DC 6150. They show the usual tape issues of the tensioning band being totally toast, but I have replacement bands and they seem to have been parked in the no data section, so I think the data should be recoverable. Theoretically, assuming the computer works, I could get an image from one of them and do a fresh install on on a blank blueSCSI, right? The drive powers up and tries to work, but instead of advancing the tape the stepper motor on the bottom left just twitches, and blueSCSI reports "START STOP UNIT on target 1 failed, sense key 0x04". Is there any reason I can't use a relatively easy to get, somewhat more modern SCSI tape drive to get the data off the tapes?

Thank you in advance for any advice, guidance, or criticism.
Pictures of the hard drive and tape drive attached, as well as the computer cabinet and a random board.

Reply 1 of 4, by Horun

User metadata
Rank l33t++
Rank
l33t++

The HD is a CDC Wren, using the model gives this: https://bk0010.narod.ru/DRIVESPECS/CDC/320.txt or
https://stason.org/TULARC/pc/hard-drives-hdd/ … H-SCSI1-SE.html

Hate posting a reply and then have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. Stuff: https://archive.org/details/@horun

Reply 2 of 4, by Deunan

User metadata
Rank Oldbie
Rank
Oldbie
ziper wrote on 2025-03-22, 18:36:

I made a very foolish error already by connecting a ground wire to the 5v rail.

More details please? What wire, where did you connect it, was the system powered at the time, etc. I mean how did it even affect the HDD and not the PSU if you basically created a short on the 5V power rail.
Did you perhaps short out the TMPWR line on SCSI connector? If that's the case the jumper in question could be setting the 5V source for that (HDD or controller). Quite a few early SCSI HDDs will refuse to work properly if the terminator pack is in but it has no power. This tends to drive all signals to active state and confuse the controller chip on the HDD.

If you intend to repair this HDD then you should measure the coils in the main spindle motor for open/burned out state. Make sure none of the tantalum caps are shorted - these yellow tubular ones. Now these rarely short but it might happen. Make sure you have 12V present alongside 5V. If you are powering this HDD from a lab supply make sure your 12V output has current limit set to 4A at least, these old clunkers can require that much to get platters moving. Not all of them will retry the spin-up so just because it gives up early and doesn't do anything anymore is not a sign it's toast. Could be the current limit. 4A can cause a lot of damage though so make sure the caps are OK first.
These 2 yellow DIPs near SCSI connector should be the terminating resistor packs, figure out if they are powered and by what. The most common setup is powered by the host controller card, so in other words the HDD might not spin unless it's connected to a controller or rejumpered to HDD terminator power. DO NOT connect HDD jumpered to internal/HDD terminator power to unknown host if you don't know for sure it can handle it.

ziper wrote on 2025-03-22, 18:36:

Or, the tapes. They are QIC-120, 3M DC 6150. They show the usual tape issues of the tensioning band being totally toast, but I have replacement bands and they seem to have been parked in the no data section, so I think the data should be recoverable.

Since you know about the band issues I guess you know what you are doing. I'm certainly no expert in the tapes but IIRC every one of those is a particular standard (like DDS or SLR) and generation (capacity basically). You need a drive compatible with the tapes you have and some of them are quite expensive. If you want to revive the tapes the best, though most expensive I guess, way would be to get another tape of same type. From ebay or such. Swap the belt, get this tape to work in the drive. By doing it with another tape you do not risk the originals in case the drive is faulty. If you can't get the drive to work at all then the next step is to buy a drive compatible with the standard but in working condition.

Reply 3 of 4, by ziper

User metadata
Rank Newbie
Rank
Newbie

The HD is a CDC Wren, using the model gives this: https://bk0010.narod.ru/DRIVESPECS/CDC/320.txt or
https://stason.org/TULARC/pc/hard-drives-hdd/ … H-SCSI1-SE.html

Thank you, I must've made a typo or something when I looked it up before because I couldn't find anything.

More details please? What wire, where did you connect it, was the system powered at the time, etc. I mean how did it even affect the HDD and not the PSU if you basically created a short on the 5V power rail.
Did you perhaps short out the TMPWR line on SCSI connector?

Just a wire from +5v to the chassis ground. No, I have no idea what happened either, since it should've done nothing except damage the power supply. The errant wire had most of the insulation burnt off. The burnt jumper was the one connecting the HDD power ground to the chassis ground. However, the errant ground wire didn't connect to the chassis anywhere near the HDD chassis ground...

If you are powering this HDD from a lab supply make sure your 12V output has current limit set to 4A at least, these old clunkers can require that much to get platters moving.

This was exactly the issue. Tried it again with a beefier power supply and it spun right up. When I hooked it back up to the initiator mode blueSCSI, this what I got:

SCSI ID 6 capacity 586764 sectors x 512 bytes
SCSI-1: Vendor: CDC , Product: 94171-9 , Version: 6261
Drive total size is 286 MiB
Imaging filename: HD6_imaged-002.hda.
Starting to copy drive data to HD6_imaged-002.hda
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 256 sectors starting at 0
Retrying.. 1/5
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 256 sectors starting at 0
Retrying.. 2/5
Multiple failures, retrying sector-by-sector
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 0
Retrying.. 3/5
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 0
Retrying.. 4/5
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 0
Retrying.. 5/5
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 0
Retry limit exceeded, skipping one sector
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x01 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 1
Retrying.. 1/5
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x01 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 1
Retrying.. 2/5
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x01 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 1
Retrying.. 3/5
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x01 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 1
Retrying.. 4/5
RequestSense response: 0xF0 0x00 0x04 0x00 0x00 0x00 0x01 0x0A 0x00 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x04
Failed to transfer 1 sectors starting at 1
Retrying.. 5/5

And it just does that on and on. So, it correctly identifies the drive, but I'm not sure what the failure is after that. 0x04 is a hardware error, right? does that mean the drive is definitely toast?

About the tape drive, I fiddled with the drive motor and it started working. The tape drive will position the head, advance the capstan (properly, as far as I can tell) and then spit out a similar error:

scsiHostRead: received 14 bytes, expected 18
RequestSense response: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
READ CAPACITY on target 1 failed, sense key 0x05
SCSI ID 1 responds but ReadCapacity command failed
Possibly SCSI-1 drive? Attempting to read up to 1 GB.
Unhandled device type: 0x01. Handling it as Direct Access Device.
Imaging filename: HD1_imaged-003.hda.
Starting to copy drive data to HD1_imaged-003.hda
scsiHostRead: received 14 bytes, expected 18
RequestSense response: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x05
Failed to transfer 128 sectors starting at 0
Retrying.. 1/5
scsiHostRead: received 14 bytes, expected 18
RequestSense response: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
scsiInitiatorReadDataToFile: READ failed: 2 sense key 0x05
Failed to transfer 128 sectors starting at 0
Retrying.. 2/5
etc....

Does this sounds like a terminating issue? The blueSCSI provides terminating power. It doesn't seem to matter how I set the drive termination jumper. Both the drives have terminating resistors. ( I don't understand how that was supposed to work in the original configuration, considering that the tape drive was in the middle of the chain, but I don't think that is relevant to trying to get them working with the blueSCSI.) I understand that blueSCSI isn't generally guaranteed to work with tape drives, but any tips on how to proceed with either the tape or hard drive? Is this something that is worth reporting to the blueSCSI people?

Since you know about the band issues I guess you know what you are doing.

Haha, absolutely not. I've never touched any sort of tape besides an audio cassette in my life. The band issue was just obvious enough and the solution just google-able enough that I could figure that much out. I have three different copies of the software so I'm not too worried about ruining the first one.

Reply 4 of 4, by Deunan

User metadata
Rank Oldbie
Rank
Oldbie
ziper wrote on 2025-03-27, 19:47:

The burnt jumper was the one connecting the HDD power ground to the chassis ground. However, the errant ground wire didn't connect to the chassis anywhere near the HDD chassis ground...

That would mean this is the lowest resistance connection between GND and chassis. Perhaps even the only one. Which is not great, if there is another connection and it's screw-based (that is, wire with screw terminals, bolted on both sides) then perhaps it has badly oxidated. Shouldn't really happen but might be the screws are loose. If there isn't any other connection then consider adding one. That one poor jumper should not be handling the entire chassis grounding.

ziper wrote on 2025-03-27, 19:47:

So, it correctly identifies the drive, but I'm not sure what the failure is after that. 0x04 is a hardware error, right? does that mean the drive is definitely toast?

Well that's not good. Could be even a rippped off head. Try reading blocks/sectors about 32 addresses apart. So 0, then 32, 64, etc. One damaged head will result in unreadable gaps but you should be able to extract sectors from other surfaces. If you get to 1024 and still nothing then it would be all heads being bad, that's unlikely. Not impossible (internal corrosion of the wires) but it's very rare. I would assume it's something wrong with positioning or head amplifiers - which in turn might be a damaged or missing part on the PCBs. Usually a ripped head will also cause the arm to scrape the platter, the sound of it is rather telling. Quite different from the usual loud bearing.

There is an LED, usually it'll light up during spin-up and then, after the rotation speed is stable and the heads do their calibration dance, the LED should go off. Does it? Or does it stay on all the time?

ziper wrote on 2025-03-27, 19:47:

About the tape drive, I fiddled with the drive motor and it started working. The tape drive will position the head, advance the capstan (properly, as far as I can tell) and then spit out a similar error:
scsiHostRead: received 14 bytes, expected 18

This seems like protocol issue. Again, tape drives is something I have little experience with. However I did get some working by interfacing them to AHA-2940U2W (or UW) PCI card in a PC running modern Debian Linux. I installed some SCSI tape tools and read the kernel boot logs to figure out what device was detected and is it looking like working or not. Try that route maybe.

Some of these drives require cleaning tape to be run every X hours of use but should still operate if it's not done. Might be weird status LEDs being lit and/or some error codes being thrown at you. Sadly it's not just about cleaning the heads, the stupid things actually detect the cleaning tape and will not exit the "cleaning required" mode unless it's run. It's a firmware thing. But I have SLR drive that wants cleaning but, other than the LEDs, works just fine since I clenead it myself.