I'm using a standalone drive on a storage node in a far away country. every time I want to mount a new volume on the drive, I'm receiving the message "volume not in media index". After the acknowledge I'm mounting it a second time and then tape is mounted with any further error message. Networker 7.6.3 server is on Linux. Anybody seen this problem before?
as you mentioned you when you are using a new volume, and that is your answer.
Whenever you add a volume, which is new to networker, networker will complain that, it is not present in the media database. This even applies to any volume, which was labelled and used in any other networker datazone.
This is a standard behavior. If you get the same message, again on an existing volume, then this calls for a concern.
As Hrvoje said, i would leave the values at default, if there is no issue occuring.
I wonder why the media should unmount itself at all? - By default this is not the case for a standalone drive.
This makes sense as for a remote location you would need somebody to reinsert the media, if required.
However, you did not mention an unload issue but an unmount issue.
In this case, i expect "a SCSI related issue" which causes the tape to be unmounted while NW (the media index?) still thinks it is mounted. That's what might confuse the media index. To clear a SCSI error, you usually must issue two attempts - with the first try, you become aware of the problem which is then cleared by the second attempt so the retry would usually end successfully.
It is, however, not a SCSI Reset issue as this would physically unload/eject the tape.
I checked it again, but first the volumes are unmounted, then taken out of the drive. So the volume is unounted correctly. Then another volume is put into the drive and a mount attempt is started.
singhmridul
17 Posts
1519
0
Posted June 6th, 2013 00:00
as you mentioned you when you are using a new volume, and that is your answer.
Whenever you add a volume, which is new to networker, networker will complain that, it is not present in the media database. This even applies to any volume, which was labelled and used in any other networker datazone.
This is a standard behavior. If you get the same message, again on an existing volume, then this calls for a concern.
As Hrvoje said, i would leave the values at default, if there is no issue occuring.