>> > I use /dev/ht0 or /dev/nht0 instead of /dev/tape and the W option
>> > works. I've done that ever since RH6.0. Let me know if it works for
>> > you.
>> /dev/tape is just a link to /dev/st0.
>> Somewhere along in the progression from RH 6 to RH 7 the device for the
>> tape unit changed from /dev/ht0 to /dev/st0.
> Not true. I was using /dev/ht0 with RH7.2.
>> So now under
>> RH 7.2 if I try to use /dev/ht0, I get this:
>> tar: /dev/ht0: Cannot open: No such device
>> (even though 'ls -l /dev/ht0' shows there is an entry under /dev for
>> If there's a way of forcing the old /dev/ht0, I don't know what it is.
> Try changing the link to from /dev/st0 to /dev/ht0 assuming your tape
> drive works with IDE ATAPI and not SCSI.
The link shouldn't come into play if I specify the actual device, i.e.,
/dev/st0 or /dev/ht0, rather than /dev/tape. But I changed it anyway and
it didn't make a difference.
There may be a simpler way by fiddling with /etc/modules.conf, but what I
found I had to do to use /dev/ht0 as the tape device is append
"hdd=ide-tape" to the kernel in lilo. I previously had appended
"hdc=ide-scsi" for my CD burner and it appears that the system used it for
the tape drive as well.
However 'tar -cvWf /dev/ht0 xxxx' and 'tar -rvf /dev/ht0 xxxx' still don't
work. But now I'm seeing messages to the effect "unable to write EOF
mark". (Just using 'tar -cvf /dev/ht0 xxxx' seems to backup correctly,
with no error messages.)
When /dev/st0 was the tape device, 'dmesg' showed this message:
"st0: Error with sense data: Current st09:00: sense key Illegal Request
Additional sense indicates Invalid command operation code"
Are you using ide-scsi for any devices on your system?
My drive is identified by Linux as "Seagate STT20000A ATAPI TAPE Drive".