2

When I copy to a tape (LTO-6 for instance) the drive eject and retract the tape multiple times during the copy process. After a while it finishes and the files validate when I do a checksum test after the copy process has finished. But because of this kerfuffle, it takes a lot longer to copy.

I'm using Windows 11, TeraCopy (have tried native copy as well) and I'm using regular HP LTO-6 tapes. I mount the tapes using LTFS-configurator provided by HP. I have also tried to run a cleaning tape through the drive a couple of times as well, but this does not seem to make any difference.

What is causing this and is this normal behavior. Should I be concerned? HPE support is not the best and fastest responder either.

Ole Aldric
  • 451
  • 5
  • 17
  • Have you tried more than one tape? – harrymc Apr 13 '23 at 13:44
  • Yes, this occurs on all tapes I try – Ole Aldric Apr 14 '23 at 13:05
  • You asked r/techsupport but why not r/DataHoarder/? – Gantendo Apr 18 '23 at 08:11
  • The real question is why I didn't ask here in the first place. – Ole Aldric Apr 18 '23 at 08:44
  • Which tape-drive is used, and which computer model ? – harrymc Apr 18 '23 at 09:11
  • It is a standalone internal drive, in a AMD driven computer. The drive is connected through a HP H220 HBA – Ole Aldric Apr 18 '23 at 09:14
  • Have you updated the last driver - [link](https://support.hpe.com/connect/s/product?language=en_US&l5oid=5263565&kmpmoid=5263567&tab=driversAndSoftware&environmentType=2200014&environmentSubtype=2000151&manualsAndGuidesFilter=66000043) ? Note that the last driver was for Windows Server 2016 (!). The technical [specs](https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c04111455) (page 8) give LTO-5 as the last supported tape version. – harrymc Apr 18 '23 at 17:45
  • The driver link is unfortunately useless, since, as you say, there is only a driver for WS2016. I also have a Ultrium 30750 connected to the same card with no issues. So that support file is probably outdated. – Ole Aldric Apr 20 '23 at 13:49
  • Have you tried older tapes up to LTO-5? – harrymc Apr 24 '23 at 08:32

1 Answers1

1

As the tape system seems to have its age (driver support ended 2016), there might be a mechanical problem:

Tape drives probably measures the tension of the tape, i.e. to recognize the end of tape. I could imagine, the grease meanwhile got muddey and stiff, dust in the corners and hairballs wrapped around the axes of moving parts. So the measured tension is not all from tape but from the resistance in the mechanics.

Your normal operation mode might be just at the edge of the tension tolerance and a small deviation might trigger the event "End of Tape", that probably will trigger the eject.

Just running a cleaning tape will clean the magnetic heads, perhaps also eliminate dust in the path, but because of the age that is not enough.

I think, the tape drive has to be opened and get an inspection (cleaning + re-greaceing).

But beware to just take some grease laying around quite handy!
If you're lucky you find some technical service details. Else I would suggest

  • use a grease (no oil)
  • the grease should not be a creeping grease
  • fit for high-speed movement (search i.e. for fast moving ball bearings)
  • have constant lubrication and low resistance for normal and operation temperature.
  • be aware for lifetime lubrication

Or you find a professional technical service.

As a first an easy step, I would try to carefully eliminate any visible dust in the mechanics, especially searching for hair wrapped around the moving parts.

This already might get the necessary drift back to the valid tolerances.
Simply a wrapped hairball might suddenly get hooked during its movement so suddenly raising the resistance and triggering the "tape end, so do eject"-event.

dodrg
  • 1,284
  • 1
  • 11
  • Thank you for this. One thing I should've mentioned is that the drive was new when I bought it. It came in a sealed antistatic bag and according to the seller (reputable) it was new in 2020 (when I bought it). It has been like this since I got it. I wonder if this has something to do with the drivers or firmware? – Ole Aldric May 02 '23 at 09:29