Unsolved
This post is more than 5 years old
232 Posts
0
39516
Error trying to clean drive on PV-136T-LTO2 using CommVault 5.9 SP4
I'm not having ANY problems running backups and restores, but, my drives need cleaning, and, everytime I try to clean them (right-click on drive and choose Clean Drive) I get the below error (from CommVault Library Log). I have LTO-2 drives, tried two new cleaning tapes, and, the tapes ARE labeled as Cleaning Tapes, and, ARE in the Cleaning Media Pool.
Any ideas?
Thanks!
5740 c50 06/13 16:59:26 ### CV_ValidateHostEntry()() - Host entry validation will NOT be skipped
5740 c50 06/13 16:59:26 ### Init() - Initializing job control, serverName [ControlSet001(vhaechcomserve1)], ControlFlag [1], Job Id [62206]
5740 c50 06/13 16:59:26 ### setupControl() - Created SemName : 62206:5740
5740 1708 06/13 16:59:26 ### controlThread() - Going to wait on semaphor 62206:5740
5740 c50 06/13 16:59:26 ### registerJob() - Sent Message to CVD, 62206
5740 c50 06/13 16:59:26 62206 CVJobCtrlClient::registerJob() Successfully received acknowledgement for job registration.
5740 c50 06/13 16:59:26 ##### CVJobCtrlLog::registerProcess(): successfuly created file [C:\Program Files\CommVault Systems\Galaxy\Base\JobControl\5.740]
5740 c50 06/13 16:59:26 ##### Api\DBmethods.cpp Database profiling (statistics) will not be collected or reported
5740 c50 06/13 16:59:26 ##### Api\DBmethods.cpp CacheHigh for service [Default] now set to [20]
5740 c50 06/13 16:59:26 62206 LIBOPER [ ] The schedule is an immediate schedule
5740 c50 06/13 16:59:26 62206 MAIN [ ] The number of threads in the thread pool is [1]
5740 b9c 06/13 16:59:26 62206 LIBOPER [ ] Going to clean Drive [9] using controller [-1]
5740 c50 06/13 16:59:26 62206 LIBOPER [ ] Number of operation threads threads started = [1]
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Failed to clean Drive [9] using controller [-1].Error code[764], error string [The request could not be performed because of an I/O device error.DELL PV-136T-LTO2_2 returned error while performing cleanDrive ]
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Will not retry the cleaning media mount.....
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Failed to mount the media and perform the library operation
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Going to quit the thread as the operation need not be retried
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Decremented the number of running threads. The current count is [0]
5740 c50 06/13 17:00:56 62206 LIBOPER [ ] Number of operation threads threads started = [0]
5740 c50 06/13 17:00:56 62206 LIBOPER [ ] Done with processing all the parameters.. time to quit
5740 c50 06/13 17:00:56 ##### COMPLETE CALLED (PHASE Status::FAIL), Job ID = 62206
5740 c50 06/13 16:59:26 ### Init() - Initializing job control, serverName [ControlSet001(vhaechcomserve1)], ControlFlag [1], Job Id [62206]
5740 c50 06/13 16:59:26 ### setupControl() - Created SemName : 62206:5740
5740 1708 06/13 16:59:26 ### controlThread() - Going to wait on semaphor 62206:5740
5740 c50 06/13 16:59:26 ### registerJob() - Sent Message to CVD, 62206
5740 c50 06/13 16:59:26 62206 CVJobCtrlClient::registerJob() Successfully received acknowledgement for job registration.
5740 c50 06/13 16:59:26 ##### CVJobCtrlLog::registerProcess(): successfuly created file [C:\Program Files\CommVault Systems\Galaxy\Base\JobControl\5.740]
5740 c50 06/13 16:59:26 ##### Api\DBmethods.cpp Database profiling (statistics) will not be collected or reported
5740 c50 06/13 16:59:26 ##### Api\DBmethods.cpp CacheHigh for service [Default] now set to [20]
5740 c50 06/13 16:59:26 62206 LIBOPER [ ] The schedule is an immediate schedule
5740 c50 06/13 16:59:26 62206 MAIN [ ] The number of threads in the thread pool is [1]
5740 b9c 06/13 16:59:26 62206 LIBOPER [ ] Going to clean Drive [9] using controller [-1]
5740 c50 06/13 16:59:26 62206 LIBOPER [ ] Number of operation threads threads started = [1]
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Failed to clean Drive [9] using controller [-1].Error code[764], error string [The request could not be performed because of an I/O device error.DELL PV-136T-LTO2_2 returned error while performing cleanDrive ]
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Will not retry the cleaning media mount.....
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Failed to mount the media and perform the library operation
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Going to quit the thread as the operation need not be retried
5740 b9c 06/13 17:00:55 62206 LIBOPER [ ] Decremented the number of running threads. The current count is [0]
5740 c50 06/13 17:00:56 62206 LIBOPER [ ] Number of operation threads threads started = [0]
5740 c50 06/13 17:00:56 62206 LIBOPER [ ] Done with processing all the parameters.. time to quit
5740 c50 06/13 17:00:56 ##### COMPLETE CALLED (PHASE Status::FAIL), Job ID = 62206
dell-richard g
605 Posts
0
July 26th, 2006 03:00
Bill Bradley
232 Posts
0
July 26th, 2006 03:00
It's connected via fibre.
I opened an incident with CommVault,1-167622, and, they told me that this is a "known firmware problem with ADIC and Dell (ADIC) changers, and that Dell knows about this, and that the drive is REALLY getting cleaned, even though it says it's erroring out". They also said that there is no fix.
From your response, I gather this is NOT the case?
Everything else works fine, just the cleaning...
Any other suggestions for me to try?
Thanks.
dell-richard g
605 Posts
0
July 26th, 2006 20:00
I have checked into this further and yes, there is an open defect on this issue. It is still being resolved and the resolution date is still TBD. There is also an tech support notification that documents this issue.
You will need to occassionally check the latest download sections for the 136t over the next couple months to see if there is a new firmware posting for the library. Either that, I will respond to this thread when it is available.
Bill Bradley
232 Posts
0
July 26th, 2006 20:00
Would you be able to give me the Document or Incident number, so, I can at least know what to refer a Tech to?
Thanks. I'm glad that CommVault's statement was correct, as, so often I'm caught between two vendors...
Thanks, again!
dell-richard g
605 Posts
0
July 27th, 2006 03:00
The document id is: 292236. As mentioned, there is still no date yet for a fix. Please continue to check the support web site for new library firmware.
Workaround to prevent the cartridge from getting stuck in the drive.
In CommVault, enable the option Attempt to remove media from the drive when unload fails in Library Properties so that CommVault removes the cleaning media from the drive after the reported error. The drive may also need to be marked as clean from within CommVault to enable it for use.
Bill Bradley
232 Posts
0
July 27th, 2006 03:00
Thanks.
At least in my case...the cleaning tape does NOT stick in the drive, I just get the error message. CommVault says they think it actually IS cleaning, but...
Bill Bradley
232 Posts
0
August 31st, 2006 23:00
This has now become a priority, as, I'm getting errors in writes on two of the drives, that appear to be from being dirty. I have A19 firmware, and, have waited, patiently, for newer firmware, but, I need some way to clean the drives. Although ADIC states that drive cleaning can be done via the front panel, this seems to be disabled in the Dell version.
What to do, in lieu of updated firmware?
Thanks.
dell-richard g
605 Posts
0
September 1st, 2006 00:00
Bill
The status on this issue is still open. As a suggestion, if you need to clean your tape drives, you can manually insert the cleaning cartridge in your drive. The drive will automatically eject the cartridge when the cleaning is complete. I realize that it may not be desirable to manually clean the drive, but this is the quicket fix to cleaning the drives.
Also, the complete document ID for this issue is:
Document Id: 292236, 015BB31EC3A264B7E0401E0A55176D48
Bill Bradley
232 Posts
0
September 7th, 2006 05:00
Richard,
How should I do that? Open the front door, while it's on, and, just put the tape in, or, what?
Thanks.
dell-richard g
605 Posts
0
September 7th, 2006 12:00
Bill Bradley
232 Posts
0
September 7th, 2006 13:00
Bill Bradley
232 Posts
0
September 7th, 2006 13:00
Thanks. That's what I thought, but, wasn't sure.
Should not only the software NOT be running, should the drive be disconnected from the network?
Thanks!
dell-richard g
605 Posts
0
September 7th, 2006 13:00
You do not have to disconnect the drive from the network. Just make sure there are no scheduled jobs that are started. With CommVault, you may be able to "down" the drive via the GUI as a safeguard .
Or the best thing to do is stop the CommVault services than clean the drive.
Bill Bradley
232 Posts
0
December 6th, 2006 08:00
Bill Bradley
232 Posts
0
January 28th, 2007 15:00