boboy1
1 Copper

DRIVE_STATUS_VS_ASC_ASCQ

We encountered these alert from our networker server running on Win2003 using legato version 7.3.2 jumbo pack 1 and backup client running also on the same OS.

NetWorker media: (warning) rd=pofds3402:\\.\Tape2147483644 opening:
DRIVE_STATUS_VS_ASC_ASCQ

NetWorker media: (warning) rd=pofds3402:\\.\Tape2147483644 reading: read open error: drive status is Not Ready, ASC 0x3a ASCQ 0x04

Checked the RSM services and all is disabled. The servers are fiber attached and defined as storage nodes. Can anyone provide recommendation on how to resolve this alert message we received. Thanks.
Tags (1)
0 Kudos
7 Replies
smora1
2 Iron

Re: DRIVE_STATUS_VS_ASC_ASCQ

You should check whether there is a HW error on that drive.
0 Kudos
ble1
6 Indium

Re: DRIVE_STATUS_VS_ASC_ASCQ

Given ASC is not common combination so it could be drive specific - you will need to check manual. Judging from tape device name I would say you either have IBM drive using persistent binding or MS one. If second one there is second MS patch which reverts tape device name back to normal one keeping persistence. If using original persistent naming convention you need 7.3SP4 at least if using 7.3.x.
0 Kudos
t0mas1
1 Nickel

Re: DRIVE_STATUS_VS_ASC_ASCQ

Hello...I have the same problem as boboy

rd=pssdb06:/dev/rmt/2cbn opening: DRIVE_STATUS_VS_ASC_ASCQ
Feb 16 11:08:31 ffmbackup00 root: [ID 702911 daemon.notice] NetWorker media: (warning) rd=pssdb06:/dev/rmt/2cbn opening: DRIVE_STATUS_VS_ASC_ASCQ
Feb 16 11:08:31 ffmbackup00 root: [ID 702911 daemon.notice] NetWorker media: (warning) rd=pssdb06:/dev/rmt/2cbn reading: read open error: command completed successfully (drive status is Not Ready, ASC 0x3a ASCQ 0x04)

I am running NW server 7.4.4 on SunOS 5.9 and I have root permissions...

rd=pssdb06:/dev/rmt/2cbn is a remote drive configured from storagenode....

I seted optinon cleaning required for afected tape drive in networker GUI ... 5 min ago...
maybe it can solve this...
0 Kudos
ble1
6 Indium

Re: DRIVE_STATUS_VS_ASC_ASCQ

Most probably you two have library by same vendor as ASC/ASCQ combination seems to be vendor specific. In such case you should check in vendor docs what this combination really means.
0 Kudos
IKP1
2 Iron

Re: DRIVE_STATUS_VS_ASC_ASCQ

Hi,


A quick google for the message reveals this to have been previously reported / discussed in a NetWorker environment where Dynamic Drive Sharing is in place. May be worth taking a look at the device drivers being used and considering using a later version.

IKP
0 Kudos
Hari5
3 Argentium

Re: DRIVE_STATUS_VS_ASC_ASCQ

Device driver version would make sense in Windows environments but not when the remote drive is configured in a Solaris or some other Unix environment.
0 Kudos
t0mas1
1 Nickel

Re: DRIVE_STATUS_VS_ASC_ASCQ

for remote drive 2cbn no DRIVE_STATUS_VS_ASC_ASCQ was posted into logs... but now I have this message for another drive... on the same backupserver
0 Kudos