fsr errors during file restore

[sinkro]

Hello all,
I've encountered a frustrating error during a couple file restores from the past week. When Networker is searching for the files position on the tape it reports an error "media warning \\.\tape(x)moving: fsr 404:A tape access reached a filemark. Media emergency:could not position (x) to file (x) on LTO Ultrium tape (x).
Has any one encountered this before, and is there anyway to work around or fix it?
We are running legato networker 6.0.2 on a windows 2000 server box with LTO ultrim drives.
Thanks,

 

[MoshiachNow]

Hi,

Same used to happpen a lot on DLT drives.

1.Check old daemon.XXX for errors during writing this volume.
If any errors - the volume was badly written,not much can be done.

2.Another less likely possibility is some problem in the media DB.
Try "nsrck -L6",then read the same saveset again.

3.Try scanning the volume with "scanner -i",this may update the media DB in case of some position misinformation.
Observe scanner output for errors.

4.Try reading on the different drive.
Are all errors a certain drive oriented ?Then it's possibly a bad drive.

5.Try retrieving the saveset from the nwadmin ->retrieve SS option,it acts differently when positioning the tape. "Long live king Moshiach !"

http://www.noahide.com/

 

[Guest_imported]

This Problem can have two reasons:

1) Networker is writing with variable blocksize for the LTO Drive has a maximum blocksize higher than 64k, I dont know it exactly ( I think 215 k). For normal the most conroller on NT/W2k have a maximum of 64k blocksize, but there is registry parameter for the most conroler to extend the blocksize, if your tape is writen by such an controller you will get this error message.

You can check your blocksize with mt -f \\.\Tape0 status.

During the recover you can run the nsrd service in debug mode use nsrd -D9 >C:\temp\nsrd.debug 2>&1. If you get an error like couldnt possition to max blocksize, you have exactly this problem.

Change the paramater in the registry, check you adapter Vendor, ( search for "maximum sg list at internet".

2) Legato NetWorker 6.0.2 handles soferrors very bad, upgrade to 6.1.1 maybe than your recover will work. But your tape has errors.

greetings

Markus Trimmel

 

[rgzimmer]

Don't know about 6.0.2, but we had this error in 6.1. You can work around it by removing the volume. including media entries and scanning it back in.

Legato sent me three binaries as a temp fix, but it was completely fixed in 6.1.1.

The binaries are nsrmmd.exe, scanner.exe, and tapeexer.exe.