Member Avatar for reboot

We have an old Novell Server running 4.11 software with an external HP SureStore DAT8 tape drive. The tape drive developed backup problems (kept getting media errors even with new tapes).

We purchased a used (1 year warranty) tape drive that is the exact model as the one we had thinking that we could just swap them out without having to do any configuration.

We set the SCSI ID the same as the old drive. We powered off the tape drive, "downed" the server, powered the server off, and exchanged the drives. Then we powered on the new drive, and powered on the server.

The server did not see the tape drive. We tried it again after double-checking all connections and it still would not see the drive. We put the old drive back on and it was found on bootup.

Is there something more that needs to be done to make the server see the SCSI tape drive? If not, would you suspect the "new" tape drive?

Thanks...

  • 2 Contributors
  • 2 Replies
  • 233 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by reboot

Dani AI

Generated

Given the swap already performed by and the helpful prompt from about termination/LUNs, the next troubleshooting focus should be on signalling, cabling, and whether the replacement actually presents itself as a SCSI target. Identical model numbers do not guarantee identical electrical/configuration behaviour — mismatched signalling (SE vs LVD/HVD), connector type or a dead drive are common causes when a used unit is invisible while the original works.

Useful, sequential checks:

  • Confirm the replacement drive actually initializes at power‑up (front LEDs, audible spin/load cycles). No activity usually means a bad power supply or failed drive electronics.
  • Eliminate cable/connector variables by moving the known‑good SCSI cable and power lead from the working unit to the replacement. Use the same physical connector type (50/68/VHDCI) and the same active/passive terminator arrangement.
  • Verify signalling mode: some DAT drives have jumpers or internal PCBs to force SE or LVD. A controller and peripheral in different signalling modes can result in no devices visible.
  • Test the replacement on a different host or with a different SCSI port. If it appears elsewhere, the server/controller configuration or host cable is at fault; if it still disappears, the drive is suspect.
  • Run vendor diagnostics or check firmware revisions if available; some controllers require specific firmware/compatibility to enumerate certain tape models.

Note on LUNs: a LUN (Logical Unit Number) is how multi‑unit libraries expose multiple devices; a stand‑alone tape drive normally uses LUN 0, so LUN configuration is rarely the issue for a single DAT drive.

If the replacement fails all of the above, it is likely defective and should be returned or RMA'd.

Recommended Answers

All 2 Replies

Member Avatar for alc6379

I'd start with simple SCSI troubleshooting. Are there any LUN ID's to be set? Does the drive need any termination?

I know under Linux/UNIX, I'd check the startup messaging to see if the system saw it there. Have you tried it on another system?

Member Avatar for reboot

I don't know what a LUN ID is. There is a jumper on the back of the tape drives where you set the SCSI ID. It is set to 3 on both the old and the new drives.

Both drives are identical, so I put the terminator from the old drive on the new drive.

If everything works as it should, can't you swap one drive with another without any configuration except making sure that the SCSI ID is the same on the new drive?

Thanks...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.