Benchmark VS80 Tape drive giving Bad Media messages
We are using the Benchmark with Veritas 9.1 software. We had the drive disconnected for several months but decided to start using it again on a different server. Now all the tapes originally used in this drive are giving a message.
We are trying to figure out if this is a problem with the drive or the Veritas installation. We have tried many different previously used tapes but don't have any brand new ones.
Re: Benchmark VS80 Tape drive giving Bad Media messages
Sounds a bit strange - I've seen this happen when tapes are re-used in a different drive but not when re-used in the same drive. You could try degaussing (magnetically wiping) the tapes. This should effectively make them appear as new ones.
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Hello, if it has an eject button, press it quickly several times (can't remember the exact number; try 3 first, then 5, then 7)the reason being that on earlier DLT's the firmware would cause a drive reset which would, if there wasn't a detached leader or other physical problem, result in a tape unload.
p.s. do let me know how you get on!
We have had the same problems with HP drives and Veritas. In our case it was not the drive per se. While I am assuming that based on the date of your post that you have moved to another solution, however, I will provide for you what we did.
First shut all down, disconnect the tape drive from the scsi cable, then restart. Go into computer management and turn all your backup exec services from auto to manual. Now go to devices and do a rescan. Once this is done and you see no tape drive whatsoever in the devices shut down the server. Reconnect the scsi cable to the drive and restart.
Go back into computer management, back to devices and rescan for hardware changes. Do you see it? If so, good! Sometimes a re-seating of connectors will do that. On the other hand, it could also be a tape driver from Veritas that just doesn't work (my case), take the original driver cd that came with the unit and start that loading up. Can you see it now? Can you use windows backup to access the tape drive? Now go into services and start the services individually. Go into backup exec and see if you can read your tape. Go back to services and reset all services back to auto. If you ever have to reinstall/upgrade backup exec, think twice about using their drivers.
on the trouble of the multiple messages of
"emmlib_update drive runtime failed: status 328"
Let's ensure the 'device mappings file' is current on this installation?
http://support.veritas.com/docs/302599 Veritas NetBackup (tm) Server / Enterprise Server 6.0 and 6.5 Device Mappings Package for Windows Servers 1.70
Download the small 14k text file
Copy the external_types.txt file from the temporary location to C:\Program Files\VERITAS\NetBackup\var\global\
C:\Program Files\VERITAS\Volmgr\bin\tpext -loadEMM
The problem you described is not a driver problem. So long as you are using the Veritas drivers you should be good to go.
SCSI time-outs and disconnects are hardware problems.
Sometimes they can be resolved by changing the throughput settings on the SCSI controller connected to the drive. Controllers usually default to very high speeds because they are used for hard drives. Lowering the speeds to support the slower throughput of tape drives can sometimes help.
During the POST there should be a key combination you can press to access the setup for the controller and modify the throughput settings.
Aside from that you have to replace the SCSI controller or tape drive until you figure out which one is causing the problem. Maybe the SCSI card is not seated properly.