BACKUP HANGUP

[Bona_1]

Hi all,
I just connected a new tape device (MSL 5026) to my server (GS160). It shows up as an MKC device when I boot up, and I can mount tapes, however, I start getting error counts when I try to run backup scripts.
The last one I got was
%BACKUP-E-FATALERR, fatal error on MKC100:[]ERIC.BCK;

-SYSTEM-F-VOLINV, volume is not software enabled

%BACKUP-I-OPERSPEC

Please assist

Bona

[Kris Clippeleyr]

Bona,

Do you see error counts increasing?
(SHOW ERROR)
Or is it just BACKUP complaining?
(tape initialized? tape label ok?, qualifiers with BACKUP (e.g. /REWIND), etc.)

Please clarify,

Kris

[Willem Grooters]

it _might_ be that your last error is a result from the numerous errors you get when running scripts.
I'm not familiar with this type of hardware, just a few hints, amongst (probably many) others, this can be wrong:
* Is your tape compatible with the drive?
* Is this unit and it's firmware compatible with VMS? (VMS can be quite stubbern on units and their firmware release).
* Has the right driver-software been loaded?

Willem

[Mohamed K Ahmed]

The MSL5026 uses a 110/220 GB tapes, did you initialize the tape?, are you sure you did load the tape to the right tape drive? (some of these models has 2 tape drives)
Are you sure you are pointing to the right tape drive.
Another thing to look at is the connections, you must have a terminator on the back of the unit, and there is a green led on the terminator.

HTH

Mohamed

[Jan van den Ende]

Bona,

"and I can mount tapes"

Does this mean, if you dor
$ MOUNT/FOREIGN MKC100:

that you get a response saying mounted?

If not,
what is the result of
$ INIT MKC100: ?

Please post the answers, we will take it from there.

It would be best if you post the complete, litteral answers.

Jan

[Martin Vorlaender]

The VOLINV error usually means the tape has been dismounted and unloaded, and must be loaded again manually before VMS can use it again.

HTH,
Martin

[Mobeen_1]

Bona,
My guess is that the volume is not initialised. Looks like the 2nd error message you posted says

"VOLINV, volume is not software enabled"

Explanation : The volume valid bit is not set for the volume. All physical and logical I/O operations will be rejected until the bit is set.

User Action: Check for a programming error. Verify that the volume is mounted and loaded. Check to see that the power is on before retrying the program.

regards
Mobeen

[Lawrence Czlapinski]

1. Before using a tape for the first time you do need to some form of:
$ INIT MKC100: /media_format=compaction

2. If the tape has been initialized, does it show a volume label after it is mounted. If not try cleaning the tape drive. The tape drive may be reading the tape incorrectly.

3. If the tape still doesn't work, try initializing the tape again:
$ INIT MKC100: /media_format=compaction

4. If the tape still doesn't work, try a different brand new tape.

[Alon Jacob]

Bona,

The VMS help states this message to probably be a "programming error".
My advice (like other responders wrote) is this :
1. Check the tape you're using to be compatible with your new drive. You may want to consult your HW supplier about that.
2. Use the "mcsysman io a" command to have your VMS re-bind the hardware installed, then use "sh dev mk" to see the tape's name.
3. init the tape : "init/media=compact "
4. Assuming the initializing went well, try to mount the tape by "mount/over=id ".

If all this workes well and your backup procedure still won't work look for errors in your backup command using VMS help.

P.S.
You can look for any error messages solutions usin : $ help/message ""

Good-luck.

[Martin P.J. Zinser]

Hello Bona,

my guess is the tape cartridge. Check you have the right medium for the new drive. SDLTs are picky in this respect.

On a general note:

In case of multiple warnings/errors usually the last one is the least interesting and most can be learnt from the --first-- one.

Greetings, Martin