The device, \Device\Tape0, has a bad block.

Soldato
Joined
17 Sep 2005
Posts
2,983
Location
Everywhere
Hello,

Having some problems with our backups. The job fails, sometimes before it starts and sometimes in the middle. I have checked the event viewer and we get the error;

The device, \Device\Tape0, has a bad block.

To me, this sounds like a duff Tape? But i tried a different tape and still the same error. So i though it could be the MSA, i cleaned it, still the same.

I thought something wrong with maybe the SCSI card?

I am now sweating my ass off because data is not being backed up :(

Any help?

Cheers,
Jay
 
Have you tried formatting a tape and trying again? Maybe trying to backup just a small amount of data in a new job.

Tried a brand new tape?

If you've tried all of the above then it sounds like you have a hardware fault.
 
Depends on how old the tapedrive is. I remember this being a common issue on old dds* units on linux boxes I used to look after years ago. Usually accompanied with lots of whirring & clicking noises.
 
Try and create a small backup with a different tape, that should eliminate any hardware problems. It sounds like the tape is dead, i get this from time to time.
 
Still Problems :( I have tried different tapes etc. It gives me and error :

Weekly - Data -- The job failed with the following error: A tape read/write error has occurred. This is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues.

I have cleaned it several times and different cleaning tapes, new tapes etc etc. Before it was saying no permission.

Event viewer says :

halfinchVRTS error :
The device, \Device\Tape0, has a bad block.

Any ideas? :) Thanks.
 
This does sound like the heads in the drive are way beyond being cleaned using a cleaning tape.... Have you got a spare tape drive or the ability to "Borrow" one?
I have had a similar issue, and it turned out the Drive was at fault, after changing Tapes, SCSI cards, cables, connectors and terminators!

Rob
 
Back
Top Bottom