StoreEver Tape Storage
1819904 Members
2028 Online
109607 Solutions
New Discussion юеВ

Re: Tape swap gone bad

 
BR796391
New Member

Tape swap gone bad

I had a problem with a 20/40 DAT on a ML370. I received a replacement and proceeded to replace the drive. I unscrewed the old tape and disconnected the SCSI and power, and put the new one in place. Everything looked good. I booted up the server, and the drive showed up offline. I powered down, and then took the drive back out, and made sure all the jumper settings were the same. I put it back in, and I had the same problem. Since I am using Windows 2000 Server, I looked in the Removable Storage MMC, and it showed that the drive was offline. Well, I Figured it was looking for the old drive. So, I then proceeded to delete the instance of the 20/40 drive, thinking that when I reboot or restart the service it would see the new drive. No luck. Is it a faulty drive or faulty administrator?
3 REPLIES 3
Lewis Finch
Honored Contributor

Re: Tape swap gone bad

Bryan, The first place to start would be at the base hardware level. Check for possible bent pins and see if the drive is shown during POST.
"You can't lead the orchestra without turning your back to the crowd"
BR796391
New Member

Re: Tape swap gone bad

I forgot this part, When the server boots up, there are no SCSI devices found. This led me to believe that there was something wrong with the drive. However, I thought maybe this was a SCSI ID problem. I checked the jumpers and although they are identical to the previous it does have jumpers on SCSI ID 0 and SCSI ID 1.
Lewis Finch
Honored Contributor

Re: Tape swap gone bad

Bryan, my first repy still stands. see if the drive is seen on POST and in the SCSI BIOS. If it's not there you may have bent pins or a defective drive.
"You can't lead the orchestra without turning your back to the crowd"