it turns out that i had to create the ht0 device:
mortirolo: cd /dev
mortirolo: /dev# ./MAKEDEV -v ht
create ht0 c 37 0 root:tape 0660
create ht0 c 37 0 root:tape 0660
create nht0 c 37 128 root:tape 0660
mortirolo:/dev# mt -f /dev/ht0 status
drive type = 0
drive status = 26624
sense key error = 0
residue count = 0
file number = 0
block number = 0
gstat = 0
what confuses me that /dev/hdd is considered a disk device and as such is
created as block device:
mortirolo:/dev# ./MAKEDEV -n -v hdd
create hdd b 22 64 root:disk 0660
create hdd1 b 22 65 root:disk 0660
create hdd2 b 22 66 root:disk 0660
create hdd3 b 22 67 root:disk 0660
create hdd4 b 22 68 root:disk 0660
create hdd5 b 22 69 root:disk 0660
create hdd6 b 22 70 root:disk 0660
create hdd7 b 22 71 root:disk 0660
create hdd8 b 22 72 root:disk 0660
create hdd9 b 22 73 root:disk 0660
create hdd10 b 22 74 root:disk 0660
create hdd11 b 22 75 root:disk 0660
create hdd12 b 22 76 root:disk 0660
create hdd13 b 22 77 root:disk 0660
create hdd14 b 22 78 root:disk 0660
create hdd15 b 22 79 root:disk 0660
create hdd16 b 22 80 root:disk 0660
create hdd17 b 22 81 root:disk 0660
create hdd18 b 22 82 root:disk 0660
create hdd19 b 22 83 root:disk 0660
create hdd20 b 22 84 root:disk 0660
another confusing thing was that before i created ht0, it appeared in
/proc/devices but when i ran MAKEDEV -n -v it responded something like "don't
know what ht0 is"
-a
"Aaron M. Stromas" wrote:
> dean,
>
> thanks for pointing out the -f . i'm still not through with the problems:
>
> mortirolo:/# mt -f /dev/ht0 status
> mt: /dev/ht0: No such file or directory
> mortirolo:/# mt -f /dev/hdd rewind
> mt: /dev/hdd is not a character special file
>
> /dev/hdd appears to be the tape drive but the device file is wrong:
>
> mortirolo:/# file /dev/hdd
> /dev/hdd: block special (22/64)
>
> can somebody suggest how to make the correct device file? btw, there's some
> info in dmesg:
>
> ftape-2.08 960314
> (c) 1993-1995 Bas Laarhoven ([EMAIL PROTECTED])
> (c) 1995-1996 Kai Harrekilde-Petersen ([EMAIL PROTECTED])
> (c) 1996-1997 Claus Heine ([EMAIL PROTECTED])
> QIC-117 driver for QIC-40/80/3010/3020 tape drives
> Compiled for kernel version 2.0.36 with versioned symbols
> [000] fdc-io.c (fdc_config) - Using the standard fdc controller.
>
> [001] fdc-io.c (fdc_probe) - Type 82077AA FDC found.
> [002] ftape-ctl.c (ftape_activate_drive) - no tape drive found !.
>
> [003] fdc-io.c (fdc_result) - fdc not ready.
> [004] fdc-isr.c (fdc_isr) - probably fatal error during FDC
> Result Phase.
> [005] fdc-isr.c (fdc_isr) - drive may hang until (power) reset
> :-(.
> [006] kernel-interface.c (ftape_open) - _ftape_open failed.
> [007] ftape-ctl.c (ftape_activate_drive) - no tape drive found !.
>
> [008] fdc-io.c (fdc_result) - fdc not ready.
> [009] fdc-isr.c (fdc_isr) - probably fatal error during FDC
> Result Phase.
> [010] fdc-isr.c (fdc_isr) - drive may hang until (power) reset
> :-(.
> [011] kernel-interface.c (ftape_open) - _ftape_open failed.
>
> Dean Allen Provins wrote:
>
> > Aaron:
> >
> > Your command line should be something like:
> >
> > >mt -f /dev/ht0 status
> >
> > to get the drive status (assuming 'ht0' is the device, and a tape is
> > loaded). If you set environment variable TAPE to /dev/ht0 (as per
> >
> > >export TAPE=/dev/ht0
> >
> > then the following will work:
> >
> > >mt status
> >
> > as will all other commands listed in the 'mt' man page.
> >
> > Regards,
> >
> > Dean
> > ------------------------------------
> > > greetings,
> > >
> > > before upgrading the kernel i went for the first time to use my tape
> > > drive to back up my box. the dmesg output contained these lines:
> > >
> > >
> > > hdd: Seagate STT8000A, ATAPI TAPE drive
> > > ...
> > > ide-tape: hdd <-> ht0, 600KBps, 14*26kB buffer, 2600kB
> > > pipeline, 190ms tDSC
> > >
> > > but neither dump nor mt recognise it:
> > >
> > > mortirolo:/# mt /dev/ht0
> > > mt: invalid tape operation `/dev/ht0'
> > > mortirolo:/# mt /dev/hdd
> > > mt: invalid tape operation `/dev/hdd'
> > > mortirolo:/#
> > >
> > > can somebody lend a helping hand explaining what is wrong and how to fix
> > > it?
> > >
> > > for some reason i was convinced that i had a scsi tape drive, so i
> > > loaded the st module but got similar response:
> > >
> > > mortirolo:/# mt /dev/st0
> > > mt: invalid tape operation `/dev/st0'
> > >
> > > i also noticed the following line in demesg's output:
> > >
> > > Failed initialization of WD-7000 SCSI card!
> > >
> > > does it have something to do with my tape troubles? tia,
> > >
> > > -a
> > >
> > >
> > > --
> > > Aaron Stromas | "Tick-tick-tick!!!... ja, Pantani is weg..."
> > > Oracle Corp | BRTN commentator
> > > +1 703.708.68.21 | L'Alpe d'Huez
> > > 1995 Tour de France
> > >
> > >
>
> --
> Aaron Stromas | "Tick-tick-tick!!!... ja, Pantani is weg..."
> Oracle Corp | BRTN commentator
> +1 703.708.68.21 | L'Alpe d'Huez
> 1995 Tour de France
--
Aaron Stromas | "Tick-tick-tick!!!... ja, Pantani is weg..."
Oracle Corp | BRTN commentator
+1 703.708.68.21 | L'Alpe d'Huez
1995 Tour de France
