Start a Conversation

Unsolved

This post is more than 5 years old

J

1527

May 24th, 2010 09:00

Logical drives operation fails during "Verify Label in progress"

Hi

I'm having the following problem with some logical drives of a library: Any operation ends with error after a few minutes showing "verify label in progress" repeatedly. In some cases the drive identify the volume as NULL, in other cases, just ends with "verify label in progress".

I'm using Legato Networker 7.4 sp2, and the messages are as follows

cancellation: none;
             completion code: ;
               error message: verify label in progress on DRIVE05,
                              verify label in progress on DRIVE05,
                              Expected volume `D00182' in slot `54'. The actual volume is ` '.,
                              verify label in progress on DRIVE05;
                 last update: 1274716795;
                    messages: Unloading volume `-' from device `DRIVE05' to slot 54.;
                        name: SILOSTK;
          operation instance: 7675;
            operation source: GUI jb op;
                    progress: failed;
             prompt response: ;
                      prompt: ;
                  start time: 1274716657;
                      status: failed

------------>Other case<----------------

cancellation: none;
             completion code: ;
               error message: verify label in progress on DRIVE02,
                              verify label in progress on DRIVE02,
                              verify label in progress on DRIVE02;
                 last update: 1274719430;
                    messages: ;
                        name: SILOSTK;
          operation instance: 7694;
            operation source: GUI jb op;
                    progress: retryable;
             prompt response: ;
                      prompt: ;
                  start time: 1274719235;
                      status: retryable

Someone knows how can I solve this Issue?

445 Posts

May 24th, 2010 10:00

Do you have AlphaStor software also here? How are you expecting NetWorker to get the information regarding which physical drive to access? Do you think this will be supplied by ACSLS directly to NetWorker? Why have you configured logical drives rather than physical.

Regards,

Bill Mason

May 24th, 2010 10:00

jejejeje, How are you expecting ACSLS to supply any information directly to NetWorker or someone to deploy a backup infrastructure with Networker and ACSLS without Aplhastor? Yes, I have an Alphastor server.  Sorry, I forgot this detail. Can you help me?

445 Posts

May 25th, 2010 06:00

OK that’s good! SO there are a few things now: -

1. Is this the only storage node you are having issues with? Is it all drives or just some with which you are seeing this?

2. Are you presenting the same drives out from ACSLS to different storage nodes (like Dynamic Drive Sharing in NetWorker) or are drives only seen by the storage node which uses them?

3. As it ever worked?

4. Does the AlphaStor Device Activity report show the corresponding drive loaded with the correct tape?

5. Can you successfully mount and unmount via AlphaStor command line to this/these drives?

Regards,

Bill Mason

2 Intern

 • 

14.3K Posts

June 3rd, 2010 03:00

juan_israel wrote:

How are you expecting ACSLS to supply any information directly to NetWorker or someone to deploy a backup infrastructure with Networker and ACSLS without Aplhastor?

It certainly did work for me very well without AS

So, as Bill has said first thing is to check AS side and confirm load and unload works fine.  It seems as while command is executed it does not get response from mapped device name as drive which has drive loaded.  To confirm load/communication, check also ACSLS side logs.

June 10th, 2010 08:00

Hi Bill,

We have been visited by an EMC support a few weeks ago. Thanks anyway

Regards,

Israel

No Events found!

Top