Unsolved
This post is more than 5 years old
3 Posts
0
35708
November 7th, 2014 22:00
Event id 11 with Dell 6Gbps SAS HBA connected to TL2000 LTO
Afternoon,
Since adding a 6Gbps SAS HBA card to our backup server (backup exec 2014) we get constant event id 11 and 129 showing the card is receiving a "Reset to device, \Device\RaidPort1, was issued."
This is now resulting in no backups completing at all. On running a tracer on the scsi traffic i see the following error after about 17 gb,
Function : SRB_FUNCTION_EXECUTE_SCSI
SCSI Status : SCSISTAT_GOOD
Sense Lenght : 0
Data Lengh : 65536
Driver Result : STAUS_IO_DEVICE_ERROR
CBD Operation : WRITE6
LUN : 0
I have Replaced the card, all cables and even upgraded the LTO drive to LTO5, I have also upgraded Backup Exec 2010 R2 to 2014 incase it was an issue that could be solved via software.
The issue initially occurred after adding the first card connected to a new MD3220 storage array, and was failing just on backing data on the LUN's within the SAN, since getting the second 6Gbps SAS HBA card to connect to the Tape Library so it is all communicating at 6Gbps, it now fails on all areas of backup.
Symantec Advises to check all terminations , slow down the SCSI bus, and update to the latest firmware and drivers. No idea on how to slow the SCSI bus for these 2 cards, and my dell contact did not know either.
set up is r710, running server 2008 r2, 2 6Gbps SAS HBA cards (driver version 2.0.35.10), one card connected to MD3220 SAN, other card connected to Brand New TL2000 LTO5 tape library.
I am at my wits end, I can not be the only person running Dell cards in a Dell environment with failures with backup exec?


DELL-Sam L
Community Manager
•
8K Posts
•
357 Points
0
November 10th, 2014 07:00
Hello HTH-Aaron,
First thing that I would check is to make sure that the scsi Id for the tape drive is not the same as the sas card. Also what drivers are you using for the TL2000? Since you are using backup exec you should be using their drivers for the tape drive & unknown medium changer. When you hooked up the TL for the first time did you install the Dell drivers first then install the backup exec drivers? If you didn’t install the drivers then here is a link to the drivers & since you are using backup exec then you will want to select the nonexclusive install. http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=MNFYH&fileId=3332845538&osCode=WS8R2&productCode=powervault-tl2000&languageCode=EN&categoryId=TA
Please let us know if you have any other questions.
HTH-Aaron
3 Posts
0
November 11th, 2014 13:00
Thank you for the info, Since updating the Library drivers I can no longer see the library at all from backup exec, yet it passes the Dell hardware tests with flying colours. As this is a production server I will not be able to trouble shoot it properly till the weekend.
I will update this with the results then
Aaron
HTH-Aaron
3 Posts
0
November 16th, 2014 16:00
I have finished my testing, I removed the symantec drivers, updated all dell drivers, restarted, retested failed, then re updated and set up Symantec drivers again , tested failed.
I checked the SCSI Target id's none appeared to clash.
I set up a test sever running an old 5/e card and the original TL2000 LTO4 and it appears to back up fine, till it gets to the SAN connected to the original Backup server that is still connected to the 6Gbps SAS card, and then after a while I get the event id 11 again, and the card resets.
Everything is pointing to the SAS cards being the problem. It even first raised its head when I introduced the SAN and card into my environment.
I am going to try and track down some non-dell 6Gbps cards to test in our environment, but this may take some time.
DELL-Sam L
Community Manager
•
8K Posts
•
357 Points
0
November 17th, 2014 11:00
Hello Aaron,
I would say that based on your test that the SAS 6gb card that you have seems to be the issue. I would try another card if you have one & see if the errors still happens. If you got the card from Dell you can send me a private message with your order# & I can see if i can get that exchanged or not.
Please let us know if you have any other questions.