--=-6/cLM8GEewwGjWWTkOND
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Could your problem be that you have the ops backwards? I don't know
about tar+tape but tar+file is
tar -cvf out.tar file
Also, the 'f' is for file output so you are trying to output to a file
named home which can't be done because that's already a directory, and
put /dev/ht0 in it. It blinks because it's being read. How about
tar cv /dev/ht0 /home/
?
On Sat, 2003-11-08 at 18:08, Bob Holtzman wrote:
> On Fri, 7 Nov 2003, Alan Dayley wrote:
>=20
> > On Friday 07 November 2003 10:46 pm, Bob Holtzman wrote:
> > > I just had a Seagate Tapestor 40Gb Travan drive installed in my
> >=20
> > I am not familiar with Travan drives BUT, let's see if my guesses might=
spur=20
> > your thoughts.
> >=20
> > > RH7.3 box. The drive is detected on /dev/ht0 which is correct.
> > > When I ran mt -f /dev/ht0 reten it returned an message aboutan I/O
> > > error and an unrecoverable error. When I tried to create an archive
> >=20
> > I don't know about this error. Do you have more information? Did the =
tape=20
> > activity light blink so you know it was hit with a command?
>=20
> The drive appeared to be working. The light was blinking after the=20
> command.
>=20
> > > ( I should have known better ) I got:
> > >
> > > [root@localhost root]# tar cvf /dev/ht0 home
> > > tar: home: Cannot stat: No such file or directory
> > > tar: /dev/ht0: Wrote only 0 of 10240 bytes
> > > tar: Error is not recoverable: exiting now
> >=20
> > - From your command line prompt, "[root@localhost root]" I assume you w=
ere in=20
> > the /root directory. The command line that you issued requested the ba=
ckup=20
> > of the /root/home directory. Does this directory exist? Did you mean =
to=20
> > backup the /home directory instead?
>=20
> Tried it both ways ( home and /home ) from the /root and / directories.=20
> >From the / cirectory I get:
>=20
> [root@localhost /]# tar cvf home /dev/ht0
> tar: home: Cannot open: Is a directory
> tar: Error is not recoverable: exiting now
> [root@localhost /]# tar cvf /home /dev/ht0
> tar: /home: Cannot open: Is a directory
> tar: Error is not recoverable: exiting now
>=20
> which really snows me. I can't understand why tar run as root can't open =
a=20
> directory. I've never had trouble with this command before. The messages=20
> log shows nothing pertaining to this.=20
>=20
> > > /var/log/messages showed:
> > >
> > > Nov 7 22:12:24 localhost su(pam_unix)[5745]: session opened for user=
root
> > > by holtzm(uid=3D500)
> > > Nov 7 22:13:06 localhost kernel: ide-tape: ht0: I/O error, pc =3D a=
, key =3D=20
> > > 5, asc =3D 22, ascq =3D 0
> >=20
> > The key, asc and ascq values are response codes. In this case 5,22,0. =
I=20
> > believe they are actually hexidecimal values, at least they would be in=
the=20
> > SCSI world. A key value of 5 indicates an illegal request. The asc an=
d ascq=20
> > are extended sense key codes indicating that the illegal request was an=
=20
> > illegal function. (Seagate has some pretty extensive drive documentati=
on on=20
> > their support site. Go try them. These key code values are at:=20
> > http://www.seagate.com/support/kb/disc/scsi_sense_keys.html and the ext=
ended=20
> > key values are at:=20
> > http://www.seagate.com/support/kb/disc/scsi_sense_error12-13.html. Loo=
k=20
> > around there some more as there may be lots of information for your=20
> > particular drive. Maybe start here in the "Disc Knowledge Base"=20
> > http://www.seagate.com/support/kb/disc/index.html).
>=20
> I'll get on these as soon as I have some time. Many thanks for the=20
> pointers.
--=20
Bryce C <
Plug@BryceCo.Net>
CoBryce Communications
--=-6/cLM8GEewwGjWWTkOND
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQA/rZB4/wbq/C6yyPcRAqHTAJ9dyrIvI4ir9mpbQi/FQuHRIph3NgCgvM9L
HlHtKIqAyPulD1FanrBYE2g=
=zK6U
-----END PGP SIGNATURE-----
--=-6/cLM8GEewwGjWWTkOND--
(text/plain)