Unsolved
This post is more than 5 years old
1 Message
0
2635
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.
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.
smora1
253 Posts
0
May 6th, 2008 04:00
ble1
2 Intern
2 Intern
•
14.3K Posts
0
May 12th, 2008 14:00
t0mas1
6 Posts
0
February 16th, 2009 23:00
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...
ble1
2 Intern
2 Intern
•
14.3K Posts
0
February 17th, 2009 00:00
IKP1
198 Posts
0
February 17th, 2009 07:00
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
Hari5
443 Posts
0
February 17th, 2009 21:00
t0mas1
6 Posts
0
February 19th, 2009 06:00