cancel
Showing results for 
Search instead for 
Did you mean: 

tape doesn't write

Helder Lopes_2
Occasional Visitor

tape doesn't write

Hello I have a Compaq ES40 with unix tru64 4.0.F.

I installed a tape Drive HP DDS4 model C5686B.

If I introduce a written tape and do "tar tv" it reads, but if I want to write to it using the following command tar cv /.
I get the following messages

a /
a / .tags/
a / .quota.user 16 blocks
tar : write : I/O error

tar : a write error has occurred

If I move the slip to no write on the tape I get the follwing messages

tar: cannot open /dev/nrmt0h: permission denied

I already tested the drive on a DS20 and it works fine.

I changed the cable and I have always the same problem.

What am I doing wrong.

Thanks
4 REPLIES
Han Pilmeyer
Esteemed Contributor

Re: tape doesn't write

Are both systems running the same version and patch kit?

Just guessing, but it could be that there is a density problem on the ES40. Densities are defined in the /etc/ddr.dbase file. You could compare those. In addition analyzing the error in the binary errorlog may reveal more.
Mulgund
Frequent Advisor

Re: tape doesn't write

Chk., if you have write permissions on /dev/nrmt0h
device special file?!?
-Srinivas
Helder Lopes_2
Occasional Visitor

Re: tape doesn't write

HI I have been looking at the files ddr.dbase and I'm lost what should I look for more exactly.

IN /dev I did ls -la and all the nrmt0h are wr_wr_wr_.

I tryied several types of tapes DDS2, DDS3 and DDS4.

they all get the same resulte.

I have an old external tape and I plugged it in configured it and it worked fine!!

why is the DDS4 drive tape not writing???

Thanks


Han Pilmeyer
Esteemed Contributor

Re: tape doesn't write

Yes, the protection had nothing to do with it. In incorrect protection would return "permission denied", not "I/O error".

When I said compare the ddr.dbase, I actually meant "diff" to see if they are identical. The denisities are defined in there, but I understand that may not be obvious to everyone. :-)

What about the version, patch kit and error log?

It could be that you have an older patch kit on the ES40 that doesn't support this drive. The drive is much newer than "base" V4.0F.