HELP!! Error 109 (unexpected filemark or FTP end of file)

[tavarvel]

I recently had to replace my old HP SureStore DAT 24 SCSI tape drive with a new HP StorageWorks DAT 40 USB. I have not had the need to access any of the old tapes for over a year or so. Recently, after trying to restore files from an old tape, I discovered that my drive would not load any of my tapes.

 

After research, I found that the HP Storageworks DAT 40 USB was my best bet because it can read DDS2, DDS3, and DDS4 tapes. I do have 6 DDS tapes but will probably have to live without getting that data for now.

 

Here's my problem...Retrospect finds my specific file in my backup set and informs me of the appropriate tape that it is on. When I load the correct tape, Retrospect confirms that it is the correct tape, however, when it tries to search for the file, I eventually, after a few minutes, receive an error. Error 109 (unexpexted filemark or FTP end of file)

 

Can I still read the data from tapes written by my old SureStore DAT 24 drive with my new StorageWorks DAT 40 USB? What are my alternatives? Any help would be appreciated.

[rhwalker]

Here's my problem...Retrospect finds my specific file in my backup set and informs me of the appropriate tape that it is on.

That's a catalog operation, and you don't need to read the tape to get that far.

 

If you have DDS, DDS2, DDS3, and DDS4 tapes that you are trying to read, I would bet that they weren't written by Retrospect 8 (which can't read old backup sets), and can only read media sets (the new terminology) that it created.

 

Try firing up Retrospect 6.1 and seeing if it can read the older tapes.

 

If that doesn't work, is there a possibility that you used hardware compression on the SureStore? Hopefully, HP would have made the tapes upward compatible, but there's always the chance that the compression algorithm isn't forward compatible.

 

There's also the possibility that the old tape drive was out of alignment, and could only read its own tapes. You might try another tape drive just to confirm that.

 

See what Retrospect 6 says.

 

Russ

[rhwalker]

I see that you have made this same post to the forum for MacOS Classic (Mac OS 9 and before, for ancient versions of Retrospect):

Same post in Mac OS 9 and earlier forum

 

Just exactly what version of MacOS are you running, what version of Retrospect (x.x.x) are you running, and, if you are running a version of Retrospect older than Retrospect 8.0, what Retrospect Driver Update (x.x.x.x) do you have?

 

The answer to your question will depend on the missing information.

 

Russ