Unsolved
This post is more than 5 years old
9 Posts
0
43516
July 31st, 2009 14:00
ML6010 - CommVault shows SCSI Library controller offline
I have a ML6010 with one LTO3 SCSI drive connected to a PE1850. The configuration was one partition and the SCSI drive was the control path for the library. I recently added another drive to the ML6010. It is a LTO4 SAS drive. In the process of adding the drive I had to replace the PCI riser card in the 1850 with a PCIe riser. There is now a SCSI HBA and a SAS HBA in the server. These are connected to the drives in the ML6010 respectively. I deleted the original partition and created two new partitions; one for the LTO3 drive and one for the LTO4 drive. Each drive is the control path for it's partition. I have also upgraded all of the firmware (library and drives) to the latest versions. The server is running Windows Server 2003 sp2 and both drives and both medium changers are visible with no errors in Device Manager.
When I try to configure the libraries and drives in CommVault Simpana 8 the LTO4 SAS library configures with no problems and the LTO3 SCSI library always indicates that the library is not online (even though the ML6010 says it is). It detects that the library is there but indicates that it is not online and cannot determine the drive count. It is not a license issue 'cause all the proper licenses are installed.
Anybody have any idea of what I can do to get this working?
0 events found
DELL-Bob D
899 Posts
0
August 4th, 2009 14:00
Are you using the IBM driver for the drives? The driver pckg can be found here. <ADMIN NOTE: Broken link has been removed from this post by Dell>
Have you tried to disable the Medium Changers at the OS (device manager) prior to running the CV device setup. CV does not require a Medium Changer driver from the OS.
Bob
mltracy
9 Posts
0
August 4th, 2009 15:00
I am using the IBM driver for the drives. I discovered those on my journey to figure this out.
I have not tried disabling the medium changers in device manager. I'll give that a try and let you know.
Thanks!
mltracy
9 Posts
0
August 5th, 2009 10:00
Interestingly enough here's what worked:
I disbaled both Medium Changers in Device Manager. Then I ran the CommVault Library and Drive config and it discovered the SCSI Library and drive just fine however, the SAS Library and drive were not accessible. I went back into Device Manager and enabled the Medium Changer for the SAS connection and tried configuring the Library again. This time it identified it and both the SCSI and SAS libraries and drives are talking and happy now. So, evidently for the SAS connection it uses the Medium Changer driver and for the SCSI connection it uses it's own.
Thanks for your help Bob in getting me on the right path.