MSL6060 - SAN - error "Cannot open device ([2] No such file or directory)" Please help!

[Denza]

I am running DP5.1 on HP-UX 11i backing up via SAN to an MSL6060 tape library.

The problem we're having is this error:

/dev/MSL1_DRIVE4
Cannot open device ([2] No such file or directory)

The backup then fails and it's over.

We've had 2 drives replaced and the library given the ALL CLEAR by HP.

Has anyone seen anything like this please, or have any suggestions.

Many thanks.

[Thayanidhi]

Hi,
Is it recently got repaired. I hope MAP settings are disturbed in the NSR. verify that.
your device naming doesn't look default MSL1_DRIVE4?

Generally it will /dev/rmt/0mn or 1mn and so on.

Please post "ioscan -fnC tape" from hp-ux and verify the map settings

Regds
TT

[Hoang Chi Cong_1]

Does it work well before?
what is out put of "ioscan -fnC tape" command?

[Rajeev Shukla]

I am sure you have created a link to the actual tape device file.
Please verify that the link to the original tape drive which should be /dev/rmt/??mn is correct bu doing an ioscan -fntape

also check that the tape drives are appearing as claimed in ioscan

Cheers
Rajeev

[Mohanasundaram_1]

Hi,


TT is correct. Since you say you have replaced the drives twice, the most likely cause of this problem is NSR map changed.

If you have a copy of the NSR map prior to the problem, then compare it with the present map shown on the library.

This will show you if there are any changes in the map.

before trying with DP, check the drives from HP-UX using ioscan and then use tar or fbackup on a scratch tape.

This will indicate to you if the drives are fine until OS level.

Once the above are done and you are sure the NSR map and the drives are ok, then proceed to check the drive configuration in DP.

With regards,
Mohan.

[MRSG]

Thanks so much for your advice. Here is the result of the ioscan as you mentioned:

rtpbp01:/# ioscan -funC tape
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
tape 0 1/0/0/3/1.1.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/0m /dev/rmt/c3t1d0BESTn
/dev/rmt/0mb /dev/rmt/c3t1d0BESTnb
/dev/rmt/0mn /dev/rmt/c3t1d0DDS
/dev/rmt/0mnb /dev/rmt/c3t1d0DDSb
/dev/rmt/c3t1d0BEST /dev/rmt/c3t1d0DDSn
/dev/rmt/c3t1d0BESTb /dev/rmt/c3t1d0DDSnb
tape 1 1/0/8/0/0.5.15.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/MSL1_DRIVE1 /dev/rmt/c5t0d1BEST
/dev/rmt/1m /dev/rmt/c5t0d1BESTb
/dev/rmt/1mb /dev/rmt/c5t0d1BESTn
/dev/rmt/1mn /dev/rmt/c5t0d1BESTnb
/dev/rmt/1mnb
tape 3 1/0/8/0/0.5.15.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/MSL1_DRIVE2 /dev/rmt/c5t0d2BEST
/dev/rmt/3m /dev/rmt/c5t0d2BESTb
/dev/rmt/3mb /dev/rmt/c5t0d2BESTn
/dev/rmt/3mn /dev/rmt/c5t0d2BESTnb
/dev/rmt/3mnb
tape 69 1/0/10/0/0.6.15.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/MSL1_DRIVE3 /dev/rmt/69mn
/dev/rmt/2m /dev/rmt/69mnb
/dev/rmt/2mb /dev/rmt/c4t0d0BEST
/dev/rmt/2mn /dev/rmt/c4t0d0BESTb
/dev/rmt/2mnb /dev/rmt/c4t0d0BESTn
/dev/rmt/69m /dev/rmt/c4t0d0BESTnb
/dev/rmt/69mb
tape 4 1/0/10/0/0.6.15.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/MSL1_DRIVE4 /dev/rmt/c4t0d1BEST
/dev/rmt/4m /dev/rmt/c4t0d1BESTb
/dev/rmt/4mb /dev/rmt/c4t0d1BESTn
/dev/rmt/4mn /dev/rmt/c4t0d1BESTnb
/dev/rmt/4mnb

[Mohanasundaram_1]

Hi Denza,

The MSL1_DRIVE4 is available on this server. So try loading a tape into that drive and run a fbackup or tar. If it goes through properly, then you have a problem in the way the device is configured on DP.

Try to reconfigure the drive in DP and check the backup.

With Regards,
Mohan.

[MRSG]

It's not the hardware I don't believe. We have run backups to the dev drive_1 fine, then they knock over.

Another odd thing is that it is going to Mount Request for a time that is in the pool, but is not in the Library - and is Protected. You cannot get around this - you need to cancel the job.

It's very off this thing.