HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

%MOUNT-F-DRVERR, fatal drive error

 
SOLVED
Go to solution

%MOUNT-F-DRVERR, fatal drive error

Once again we are having trouble with our fibre attached tape drives...

Environment: 2 NI-clustered AlphaServer ES40 running OpenVMS V7.3-1, 2 Network Storage Router M2402 for each MSL5026S2

Problem: When mounting a tape on HOST2 $2$MGA0 the following error shows up
%MOUNT-F-DRVERR, fatal drive error
The same physical device works fine on HOST1...
Is there a procedure to bring the tape device back working again. MCR SYSMAN IO AUTOCONFIGURE, REBUILD and so on didn't fix the problem.
It's hard to find a time slot to reboot the node, since there are simulations running which take multiple weeks time...

Thanks for any help in advance
3 REPLIES
Uwe Zessin
Honored Contributor
Solution

Re: %MOUNT-F-DRVERR, fatal drive error

Adrian,
the systems have two paths to the tape drives. Last time I checked, tape multipath was only supported on the old MDR SCSI/FC converter, but it might have changed.

Assuming that the servers are cabled identically (both PGA0 goes to the same fabric), if you inspect your paths you will see that each server uses a different path.

You could try to move HOST2's current path to that of HOST1 with the 'SET DEVICE/SWITCH' command.
.
Vladimir Fabecic
Honored Contributor

Re: %MOUNT-F-DRVERR, fatal drive error

Did you try MCR SYSMAN IO REPLACE_WWID?
Do both machines see same WWID?
In vino veritas, in VMS cluster

Re: %MOUNT-F-DRVERR, fatal drive error

Thanks to Uwe! The tape drive is accessible again.

Answers to Vladimir's questions:
Both machines see the same devices / WWIDs in the SAN. The SYS$DEVICES.DAT also contains the same records. I tried the SYSMAN IO REPLACE_WWID command also. But it didn't help...