Windows Server 2000/2003 Thread, LTO3 Tape drive error in Technical; I've got a Windows 2003 Server with Backup Exec and a Quantum LTO3 HH drive in it.Recently this is failing ...
-
24th January 2012, 12:26 PM #1 LTO3 Tape drive error
I've got a Windows 2003 Server with Backup Exec and a Quantum LTO3 HH drive in it.Recently this is failing during backups and the event viewer was showing an error on the SCSI card that the tape drive is attached to (i.e The driver detected a controller error on \Device\Scsi\adpu160m1) so I replaced the Adaptec 29160 SCSI card with a brand new Adaptec 29320 card and put the latest drivers on.
Backups still fail - same error except now saying the error is on controller \adpu320.
I've run the quantum diagnostics on this driver (using their XTalk console) and it fails with an error:
LTO Write Read Error Rate Test
Determining the drive type...
ULTRIUM 3 HH detected
Fetching the drive serial number...
SN: QD0724AM44
Loading Tape...
Determining the tape type...
ULTRIUM 3 tape detected
GB to Process: 18.180
Rewinding...
Disabling Compression...
Setting to Fixed Block Mode...
Clearing Counters...
Write operations in process...
Number of Blocks Written Mismatch Error Detected.
Sense: CC: CC ASC: CC ASCQ: CC = "No Sense Available for this condition"
Write operations error detected. Aborting operations.
Problem Detected
But when I run the same diagnostics on a different server (but exactly the same type of server) it passes the diagnostics. When I attach a known working LTO2 drive to this server it also fails the diagnostics. I've changed the cables, SCSI card and drivers but it seems to always fail.
I can't understand where the error is occuring now, the SCSI card is new, the tape drive effectively works elsewhere so I'm a bit stuck as where to look next.
Obviously the fault lies with the server somewhere, not the tape drive or SCSI card, but I'm not sure where - anyone got any ideas?
-
-
IDG Tech News
-
24th January 2012, 12:56 PM #2 I had a similar problem with an LTO3 autoloader once and it turned out it was due to a faulty SCSI terminator. Not sure what the original error code was though but it was definitely a 'Block Written Mismatch Error'.
HBJB
-
-
24th January 2012, 01:00 PM #3 I've used the same cable on a different server and it works fine though - and the dodgy server fails on two seperate LTO2 drives using different cables!
-
-
26th January 2012, 03:00 AM #4 Hmm, I am think it might be motherboard related. If you swapped it out with a new one and it still not working then it must be the connection point on the motherboard to SCSI card. I don't have experience with SCSI but that's what I would guess.
-
-
26th January 2012, 08:23 AM #5 Its not part of the motherboard in this case. The original SCSI card was an Adaptec PCI card, and the replacement was a PCI-E Adaptec card so it even used different card slots!
I've even managed to update the tape drive firmware using the scsi card - so it must have a half decent connectin. I then ran a full backup using NT Backup which worked without any errors!
Now its time to completely remove Backup Exec (and its ropey drivers) and try something else!
-
-
29th January 2012, 11:43 PM #6 I am glad you solved your problem. why not use ntbackup which come with windows. Just a suggestion.
-
SHARE: 
Similar Threads
-
By MatthewL in forum Classified Adverts
Replies: 0
Last Post: 25th February 2011, 08:47 PM
-
By Andie in forum Windows
Replies: 14
Last Post: 19th January 2008, 11:21 AM
-
By john in forum Hardware
Replies: 8
Last Post: 29th November 2007, 10:36 AM
-
By paul in forum Thin Client and Virtual Machines
Replies: 4
Last Post: 8th November 2007, 02:29 PM
-
By ctbjs in forum How do you do....it?
Replies: 5
Last Post: 17th July 2007, 08:04 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules