Hi Tommy,

Are you getting any error message?

You can see the error messages in the Devices tab, you will see the red icon with the error, right click on it and select show details.

Otherwise in the daemon.raw you should be able to find the errors, once you render the daemon.raw.

If I remember well there used to be a limitation in the number of tapes to mount/label/unmount with some 7.6.x versions, but I would like to see the error message first.

Thank you.

Carlos.

Hi Tommy,

could you please provide some more details, such as error message or what is the behavior?

Is it PTL or VTL?

What is the OS of the NetWorker server or Storage node that have those devices attached?

Have you tried to run a quick inventory?:

nsrjb -IIvv

(note that is upper case "i" and not "l")

Thank you.

Carlos.

We try to rebuild inventory but that could not help us.

We are at 7.6.1 and OS is Linux 2.6.18.

VTL is it.

On Wed, Apr 4, 2012 at 12:17 PM, CarlosRojas

Manually I can do unload but its not being done during my scheduled backup,

which usually run during the night time.

On Wed, Apr 4, 2012 at 2:43 PM, Ahmed Bahaa

Hi Tommy,

Additionally, would you please provide us of the output of the unloading volume command ?

You have different ways to unload a volume,You can unload a particular volume, slot, or device. To unload volume vol028, use the -u option:

nsrjb–u vol028

To unload the volume in slot 28, use the –S option:

nsrjb–u–S 28

To unload the volume in device/dev/nrst3, use the –f option.

nsrjb–u–f /dev/nrst3

Please provide us of the output of one of these commands for unloading one of the volumes that you cannot unload in addition to the information requested by Carlos in the previous post.

Thanks,

Ahmed Bahaa

Tommy,

You are not really helping us here.

Can you please provide with the information requested? Otherwise we won't be able to move forward.

Thank you.

Carlos.

From the daemon file.

24 137 read open error: a system error occurred - see errno for more

information (drive status is Drive reports no error - but state is unknown)

7224 1333520492 2 0 0 834076992 27900 0 networker.love.com nsrd 5 %s %s 2 0

50 . 0 137 read open

error: a system erro

r occurred - see errno for more information (drive status is Drive reports

no error - but state is unknown)

67986 1333520492 2 0 0 2058490416 28179 0 networker.love.com nsrmmgd 50

Unloading volume `%s' from device `%s' to slot %d. 3 22 6 DD0342 21 52

/dev/tape/by-id/scsi-1I

BM_ULTRIUM-TD3_6271900007-nst 1 3 343

39077 1333520492 0 0 0 4130954128 29757 0 networker.love.com nsrlcpd#2 11

error, %s%s 2 49 212 15214 51 Jukebox:%s access:%s failed:%s key:%d

status:%s %s 6 0 20 1ST

K_L180_6271900000 0 41 /dev/tape/by-id/scsi-1STK_L180_6271900000 0 11 MOVE

MEDIUM 1 1 5 0 15 CHECK CONDITION 0 27 UNKNOWN, ASC 0x53 ASCQ 0x03 0 0

0 1333520493 2 0 0 2058490416 28179 0 networker.love.com nsrmmgd 2 %s 1 0

227 lcpd 2 at host networker.love.com reported error

'Jukebox:1STK_L180_6271900000 access:

/dev/tape/by-id/scsi-1STK_L180_6271900000 failed:MOVE MEDIUM key:5

status:CHECK CONDITION UNKNOWN, ASC 0x53 ASCQ 0x03' for the command `5'.

7224 1333520493 2 0 0 834076992 27900 0 networker.love.com nsrd 5 %s %s 2 0

50 . 0 153

Jukebox:1STK_L180_6271900000 a

ccess:/dev/tape/by-id/scsi-1STK_L180_6271900000 failed:MOVE MEDIUM key:5

status:CHECK CONDITION UNKNOWN, ASC 0x53 ASCQ 0x03

4690 1333520493 2 0 0 2058490416 28179 0 networker.love.com nsrmmgd 2 %s 1

0 153 Jukebox:1STK_L180_6271900000

access:/dev/tape/by-id/scsi-1STK_L180_6271900000 failed:

MOVE MEDIUM key:5 status:CHECK CONDITION UNKNOWN, ASC 0x53 ASCQ 0x03

On Wed, Apr 4, 2012 at 3:38 PM, CarlosRojas

Anyway Tonny,

Can you please run the commands and let us know the output?:

mt -f /dev/xxxxxx status

Where /dev/xxxxx is the name of your device.

Please run it for one working device and for one failing.

Thank you.

Carlos.

Hi Tommy,

If I remember well I worked on a similar case related to Data Domain, and we needed to change 2 parameters on the DD OS to fix this issue, but if this is not DD then the problem would be more likely a SCSI bus reset, but again, it was a long time since I saw that error message.

Also I remember a limitation when NetWorker could not handle to move more than 4 tapes at the same time, I believe, but don't remember either the exact version.

Probably Bill can paste in here the information about esg117145

Thank you.

Carlos.

Hi Tommy,

Can you please run these commands for the faulty drives?:

mt -f /dev/tape/by-id/scsi-1STK_L180_6271900000 status

mt -f /dev/tape/by-id/scsi-1STK_L180_6271900000

mt -f /dev/tape/by-id/scsi-1STK_L180_6271900000 rewoffl

Change the name of the devices accordingly and please provide us with the output.

I would suggest anyway to do as follows:

1.- Shut Down NW server

2.- Shut down VTL

3.- Start up VTL

4.- Once VTL is up and running start up NW server

After that run a full inventory:

nsrjb -Ivvv

Try the same operations again.

Thank you.

Carlos.