Start a Conversation

Solved!

Go to Solution

6453

December 14th, 2018 23:00

TL2000 issues on fresh OS

Hello,

I was previously running MS System Center 2012 on a Windows 2008 Server, was working fine.  I have reinstalled Server 2016 and now I have issues.  No cabling, or bios, or adapters were modified.

  • The TL2000 has 2 drives, and 1 tape library with 23 slots.
  • The OS Device Manager sees 2 drives "IBM ULT3580-HH5 SCSI Sequential Device"
  • DPM sees the two drives listed as individual devices (previously on 2008, the two drives were listed under the library which makes more sense).
  • The OS Device Manager sees 2 devices under "Medium Changer devices as "Unknown Media Changer" (listed twice, not sure why).
  • DPM does not display anything about the library, and does not display and tapes or slots.

Any tips?

I have:

  • downloaded the latest IBM Driver package IBM_Driver_Package_6265_ZPE.exe (**issues)
  • updated TL2000 firmware
  • When I try to use the IBM drivers, I don't quite understand, the 'installer' doesn't really work. 
    • I tried the "install_exclusive.exe" and "install_nonexclusive.exe" with the same failed results... the when I use the dos prompt to run the EXE, it shows that it cannot find the files (the installer script is hard coded to a path that doesn't exist). 
    • I've tried manually updating the drivers using Device Manager and pointing it to the IBM driver unzip location.  That works, however, after the reboot the device in Device Manager under "Meduim Changer devices" changes to "IBM TotalStorage 3573 Tape Library" (which is the correct model, see below) has an exclamation mark with the error "Windows cannot initialize the device driver for this hardware. (Code 37) Object Name not found".
    • I've tried uninstalling and removing the driver and pointing to both the W12 and W16 folders (assumed it means Server 2012 and Server 2016, and tried both just in case, same result).

I've pasted info about the TL2000 below.  Why does it show SAS 6Gbps, when in the above I see the two drives are SCSI?  I'm not physically there to confirm how the TL2000 is connected to the windows server.  If it is SAS or SCSI, do I need to do any configuration on the server before it starts working (I don't remember doing this before)

-confused and frustrated

 

TL2000 Info

Library Identity

 

Serial Number

FRU789 (no just kidding)

Service Tag

oicu812 (no just kidding)

Product ID

3573-TL

Currently Installed Library Firmware

F.11 / 3.20e

Bootcode Firmware Revision

0.82

Barcode Reader

SE625

IPv4 Address

172.x.x.x

MAC Address

000E1114D6FE

Library Mode

Random

WWide Node Name

2000000E1114D6FE

 

Drive Identity 1 (LUN)

 

Vendor ID

IBM

Product ID

ULT3580-HH5

Serial Number

906809wxyz

Firmware Revision

H971

World Wide ID - Port A

5000E1114D6FE002

World Wide ID - Port B

5000E1114D6FE003

Element Address

256

Control Path Drive

Yes

Data Compression

Yes

Interface Type

SAS

 

Drive Identity 2 (LUN)

 

Vendor ID

IBM

Product ID

ULT3580-HH5

Serial Number

10WT06wxyz

Firmware Revision

H971

World Wide ID - Port A

5000E1114D6FE005

World Wide ID - Port B

5000E1114D6FE006

Element Address

257

Control Path Drive

Yes

Data Compression

Yes

Interface Type

SAS

 

16 Posts

December 17th, 2018 11:00

I've reinstalled Server 2016, SQL, DPM, same issue. Then I installed the recommended IBM drivers from Dell's website and it appears to be working normally now. Not too sure what I did differently this time :(

December 17th, 2018 00:00

Hi

You have 2 control path drives, im pretty sure there should only be one unless maybe its partitioned.

SAS = Serial attached SCSI. even FC drives appear as scsi sequential drives

non exclusive drivers should be correct

Moderator

 • 

6.9K Posts

December 17th, 2018 07:00

Hello Andrew_P76,

Which exe install are you selecting?  Since you are using DPM, you will want to use the install_nonexclusive drivers for your TL2000.  When you get an error code 37 that is normally a communication error.  One thing I would check is that you are using the correct drivers for your SAS HBA.  Which version of DPM are you using?  According to our support matrix DPM 2007, 2010, & 2012 are showing as supported on page 15. https://downloads.dell.com/manuals/common/rd1000_lt05_lt06_lt07_lt08_114x_ml6000_tl1000_tl2000_tl4000_ml3_compatibility_matrix_en-us.pdf

Please let us know if you have any other questions.

16 Posts

December 17th, 2018 11:00

Thank you.  And yes, on the latest OS install from this morning I used the nonexclusive installer which did work properly this time, no errors.

10 Posts

August 5th, 2021 08:00

Hi guys I have the same problem and I dont have experince with these, the whem I run the job for the backup tape its reaching 1.2 tb and became bad tape, 

 

I have unknow medium changer

 

I have dell power TL2000

and the status became in warning and giving bad tape 

 

If any one can help I would appreciate 

10 Posts

August 5th, 2021 13:00

Dear Dylan,

Thank you for your response, I did install them but it show that error code 37, I am really have this problem since two months and I don’t know how it’s gonna work 

2.9K Posts

August 5th, 2021 13:00

Hello,

 

All software downloads are available from the product support page below:

https://dell.to/2VwSjIe

10 Posts

August 5th, 2021 13:00

Dear Dylan , 

 

can you please give me a link for the rest because I am confusing with that  I would appreciate 

2.9K Posts

August 5th, 2021 13:00

Hello,

 

Have you installed the IBM drivers Andrew mentioned? If you have the same issue, I'd look for that driver.

2.9K Posts

August 5th, 2021 13:00

Like Sam had mentioned, the error that you're seeing is generally a communications issue. If the driver didn't do it, I'd consider reinstalling the rest of the software, such as DPM, and reseating cabling. 

10 Posts

August 5th, 2021 19:00

Dear Dylan,  I did install the rest and still didnt work, could you please tell me how i reset the cable ?

Thank you

4 Operator

 • 

2.7K Posts

August 6th, 2021 07:00

Hello @falanazi,

 

I hope you are well.

 

Dylan's recommendation is not about "Reseting" but "Reseating". That means to disconect the cable and connecting it again, so you are reaseting the connection to check if it had a connection problem

 

Regards.

2.9K Posts

August 6th, 2021 08:00

The documentation for the tape library is available below.

 

https://dell.to/37ouEfx

2.9K Posts

August 6th, 2021 08:00

Reseating cables would involve shutting the chassis off, then disconnecting and reconnecting cables. I would refer to the owner's manual for the TL2000, if you need reference documentation. The owner's manual will have the diagrams relevant to the TL2000.

10 Posts

August 6th, 2021 08:00

Dear Diogo, 

 

do you mean I switch off the Dell hardware of TL2000 power , and take off the cables and put them back and switch on !! 

 

Really don’t have experience what is that mean please explain steps of reseating cables 

 

thank you so much 

No Events found!

Top