warning - media write protected or wrong density

[GuzaPasha]

Hi all,

I was trying to back up my system, but I got the following error code,

1040405 23:55:52|29913|root|[L167] device = /dev/rmt/ctape1, buffer = 20K bytes, media size = <unknown>, archive id = 4072465e74d9, (Op)
1040406 00:00:58|29913|root|[W067] warning - media write protected or wrong density
1040406 00:00:58|29913|root|[E154] error - timed out trying to write

I don't know how to manage with this?

Is the problem with the tape?
How can I check the tape?

Any idea would be helpfull

GuzaPasha

 

[KenCunningham]

Is the write-protect tab on the tape in the secure position? If it is, you need to find out why and whether it really is OK to overwrite this tape.

 

[stanhubble]

Is this a DAT tape drive?
DDS4 drives will not write DDS or DDS1 media.

Other cartridge tape devices (QIC,travan, etc) will not write to all the older (smaller) media. They usually have a range that they support.

And of course check the write protect tab.

 

[GuzaPasha]

I missed the following,

Some files are backed up, brulog is growing to the 250KB point, I did expect about 2MB, it stops at that point.

I did format disk, but nothing,

I will inform you about information that you need.

GuzaPasha

 

[stanhubble]

The files it logs are probably only those that would fit in the cache.

 

[GuzaPasha]

Here I am,

we checked the protection, it is unprotected.

What else should I check.
It is totaly new for me,

how can I check the size of a tape, and to list content.

/dev/rmt/ctape1 is the tape

What are the UNIX commands that I can use to manipulate with the tape?

Thanx in advance

 

[fredericofonseca]

What OS
What Tape model
What Tape Cartridge used

Regards

Frederico Fonseca
SysSoft Integrated Ltd

http://www.syssoft-int.com

 

[GuzaPasha]

Hi Frederico,

here it is

UnixWare 2.1.2
Tanberg tape drive,
4 GB tanberg tape

Regards,

 

[stanhubble]

Tandberg is a manufacturer not a model....it will say on the front of the door or on a label inside the door (my guess is that it is a QIC drive of some sort, probably an SLR5 if you are trying to use a 4 GB tape. I think the command in unixware is dcu, but i don't have a system here to confirm it, and it should return a line similar to:
name=Stp-0 vec=- dma=- Vendor=TANDBERG Product= XXXX X/XGB

What does it return for "Product = "?
What are you using to do the backup?

 

[GuzaPasha]

Thanx for asssting me

here is the info from the tape door

1653100102 WV1 0307 C2 2 MADE IN USA M4.0 GB

I will explore the net about this all, but if you find what you have asked for, pleasi inform me

I am totaly new to this all

I am using an application, that has build in backup item,

the command in the log is

command = 'bru -c -vvV -X -R -L /vs/data/backrest/full.label -Il,/vs/data/backrest/brulog.0 '

The dcu - returns nothing about the tape,....


Thanx in advance,
GuzaPasha

 

[GuzaPasha]

Here it is
TANDBERG SLR5 4GB

there is the tape in dev/rmt/ctape1

When I run the backup, lamp on the tape is flashing, so It looks like the tape drive is writing sth to the tape, but just for short time, then the message about protection and density appear ....

GuzaPasha

 

[stanhubble]

bru is a third party backup utility, from the online manual i found this:

[W067] warning - media appears to be write protected or wrong density
BRU received an error on its first attempt to write to an archive device. BRU has determined
that it might be caused by media that is write-protected. The UNIX system may not return the
proper error code, so it is not always possible for BRU to determine if the media is actually writeprotected.
BRU tries to determine the write-protect status by comparing the errno code returned
by UNIX with the value of wperr (as specified for the device in the brutab file). If wperr=0 (or is
not set) then BRU must “guess” at whether the device is truly write-protected. In this case, it
assumes that an error on the first write attempt is caused by write-protection, and issues the
above message.

from what is says it is guessing that it is a write protect problem. I would suggest that you try using another utility to try and write to the tape drive.

cd /usr/bin
find . -print | cpio -ocvB > /dev/rmt/ctape1

and see what happens.