I`m fiddling around with ftape and 'Teak 400/800 floppy
tapedrive-internal', its for some time.
Problem is: It writes Backups in one go, allright but refuses to append
another volume.
I had this with ftape-4.02 und kernel 2.0.35 and now again with
ftape-4.03-pre-2 and kernel 2.0.36.
I ran all the tests *exactly* as described in ftape-4.x-doc-1.03.
It is a fact: whatever I do it allways starts from BOT writing backups.
Yes, I use nqft0!
Somehow my teakdrive seems to be too stupid to read filemarks
(although he can do so in WIN98!
and although it is listed in 'ftape-vendors.h' by: { 0x003ce,
77, wake_up_colorado, 0, "Teac 800" })
I made already several 'avances' to this list in the past
to get it fixed. And there seems to be some 'mystic' to it.
I had given it up allready
This now is another try.
There is one abnormality which might give a cue.
It seems so, as if ftape recognizes the standard fdc-
controller when its is freshly loaded and forgets about it
afterwards.
It starts all very fine.
Loading ftape with:
'modprobe ftape'
'modprobe zftape'
'modprobe ftape-internal '
results in a perfect:
May 23 14:46:53 vitzlipu kernel: (c) 1993-1996 Bas Laarhoven
May 23 14:46:53 vitzlipu kernel: (c) 1995-1996 Kai
Harrekilde-Petersen
May 23 14:46:53 vitzlipu kernel: (c) 1996-1998 Claus-Justus Heine
([EMAIL PROTECTED]
en.de)
May 23 14:46:53 vitzlipu kernel:
May 23 14:46:53 vitzlipu kernel: QIC-117 driver for
QIC-40/80/3010/3020/Ditto 2GB/MAX floppy
tape drives.
May 23 14:46:53 vitzlipu kernel: Compiled for Linux version 2.0.36
May 23 14:46:53 vitzlipu kernel: installing QIC-117 floppy tape
hardware drive ...
May 23 14:46:53 vitzlipu kernel: ftape_init @ 0x068121b0.
May 23 14:46:54 vitzlipu kernel: zftape for ftape v4.03-pre-2
11/05/98
May 23 14:46:54 vitzlipu kernel: (c) 1996, 1997 Claus-Justus Heine
([EMAIL PROTECTED]
hen.de)
May 23 14:46:54 vitzlipu kernel: vfs interface for ftape floppy tape
driver.
May 23 14:46:54 vitzlipu kernel: Support for QIC-113 compatible
volume table.
May 23 14:46:54 vitzlipu kernel: Compiled for Linux version 2.0.36
May 23 14:46:54 vitzlipu kernel: [000] zftape-init.c (zft_init) -
zft_init @ 0x0684498c.
M
May 23 14:46:54 vitzlipu kernel: [001] zftape-init.c (zft_init) -
installing zftape VFS in
terface for ftape driver ....
May 23 14:46:55 vitzlipu kernel: fdc-internal.c:
fdc_internal_register @ 0x0684c7e4.
May 23 14:46:55 vitzlipu kernel: [002] fdc-io.c (fdc_register) -
Probing for ftape-interna
l tape drive slot 0.
May 23 14:46:55 vitzlipu kernel: [003] 0 fdc-internal.c
(_fdc_int_detect) - called with coun
t 0.
May 23 14:46:55 vitzlipu kernel: [004] 0 fdc-internal.c
(_fdc_int_detect) - fdc[0] base: 0x0
3f0, irq: 6, dma: 2.
May 23 14:46:55 vitzlipu kernel: [005] 0 ftape-buffer.c
(add_one_buffer) - buffer nr #1 @ 0
220d618, dma area @ 00e58000.
May 23 14:46:55 vitzlipu kernel: [006] 0 ftape-buffer.c
(add_one_buffer) - buffer nr #2 @ 0
220d698, dma area @ 00d78000.
May 23 14:46:55 vitzlipu kernel: [007] 0 ftape-buffer.c
(add_one_buffer) - buffer nr #3 @ 0
220d718, dma area @ 00af0000.
Even:
'ftmt -f /dev/nqft0 status '
is still tolerable with maybe the exception of: error 26
"Power On Reset Occurred"
May 23 14:46:55 vitzlipu kernel: [003] 0 fdc-internal.c
(_fdc_int_detect) - called with coun
t 0.
May 23 14:46:55 vitzlipu kernel: [004] 0 fdc-internal.c
(_fdc_int_detect) - fdc[0] base: 0x0
3f0, irq: 6, dma: 2.
May 23 14:46:55 vitzlipu kernel: [005] 0 ftape-buffer.c
(add_one_buffer) - buffer nr #1 @ 0
220d618, dma area @ 00e58000.
May 23 14:46:55 vitzlipu kernel: [006] 0 ftape-buffer.c
(add_one_buffer) - buffer nr #2 @ 0
220d698, dma area @ 00d78000.
May 23 14:46:55 vitzlipu kernel: [007] 0 ftape-buffer.c
(add_one_buffer) - buffer nr #3 @ 0
220d718, dma area @ 00af0000.
May 23 14:52:00 vitzlipu su: (to root) hgt on /dev/ttyp4
May 23 14:55:43 vitzlipu kernel: [008] 0 ftape-calibr.c
(ftape_calibrate) -
calibr_count
: 5430, calibr_time: 9997 us.
May 23 14:55:43 vitzlipu kernel: [009] 0 ftape-calibr.c
(ftape_calibrate) -
TC for `fdc_
wait()' = 1841 nsec (at 5430 counts).
fta
May 23 14:55:43 vitzlipu kernel: [010] 0 fdc-io.c (fdc_probe) -
Type 82077AA FDC found.
May 23 14:55:45 vitzlipu kernel: [011] 0 ftape-ctl.c
(ftape_log_vendor_id) -
tape drive type: Teac 800.
May 23 14:56:50 vitzlipu kernel: [012] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 23 14:56:50 vitzlipu kernel: [013] 0 ftape-io.c
(ftape_report_error) - errorcode: 26. ^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
May 23 14:56:51 vitzlipu kernel: [014] 0 ftape-ctl.c
(ftape_get_drive_status) - status: new cartridge.
May 23 14:56:52 vitzlipu kernel: [015] 0 ftape-io.c
(ftape_report_configuration) - TR-1 tape detected.
May 23 14:56:52 vitzlipu kernel: [016] 0 ftape-ctl.c
(ftape_init_drive) - post QIC-117B drive @ 500 Kbps.
May 23 14:56:52 vitzlipu kernel: [017] 0 ftape-ctl.c
(ftape_calibrate_data_rate) - Highest FDC supported data rate: 1000
Kbps.
May 23 14:56:55 vitzlipu kernel: [018] 0 ftape-io.c
(ftape_report_configuration) - TR-1 tape detected.
May 23 14:56:55 vitzlipu kernel: [019] 0 ftape-ctl.c
(ftape_init_drive) - unknown length QIC-80 tape.
May 23 14:57:01 vitzlipu kernel: [020] 0 ftape-read.c
(ftape_decode_header_segment) - calculated tape length is 775 ft.
May 23 14:57:01 vitzlipu kernel: [021] 0 ftape-bsm.c
(print_bad_sector_map) - 394563 Kb usable on this tape.
May 23 14:57:01 vitzlipu kernel: [022] 0 ftape-bsm.c
(print_bad_sector_map) - 11 bad sectors.
May 23 14:57:01 vitzlipu kernel: [023] 0 zftape-read.c
(zft_read_header_segments) - Segments written since first format:
51649.
May 23 14:57:01 vitzlipu kernel: [024] 0 zftape-read.c
(zft_read_header_segments) - zftape->ftape->first_data_segment: 2,
zftape->ftape->last_data_segment: 13607.
May 23 14:57:07 vitzlipu kernel: [025] 0 ftape-ctl.c
(ftape_print_history) -
== Non-fatal errors this run: ==.
May 23 14:57:07 vitzlipu kernel: [026] 0 ftape-ctl.c
(ftape_print_history) -
fdc isr statistics:
May 23 14:57:07 vitzlipu kernel: id_am_errors : 0
May 23 14:57:07 vitzlipu kernel: id_crc_errors : 0
May 23 14:57:07 vitzlipu kernel: data_am_errors : 0
May 23 14:57:07 vitzlipu kernel: data_crc_errors : 0
May 23 14:57:07 vitzlipu kernel: overrun_errors : 0
May 23 14:57:07 vitzlipu kernel: no_data_errors : 0
May 23 14:57:07 vitzlipu kernel: retries : 0.
May 23 14:57:07 vitzlipu kernel: [027] 0 ftape-ctl.c
(ftape_print_history) -
ecc statistics:
May 23 14:57:07 vitzlipu kernel: crc_errors : 0
May 23 14:57:07 vitzlipu kernel: crc_failures : 0
May 23 14:57:07 vitzlipu kernel: ecc_failures : 0
May 23 14:57:07 vitzlipu kernel: sectors corrected: 0.
May 23 14:57:07 vitzlipu kernel: [028] 0 ftape-ctl.c
(ftape_print_history) -
tape motion statistics:
May 23 14:57:07 vitzlipu kernel: repositions : 2.
But here then comes the surprise.
An other:
'ftmt -f /dev/nqft0 status'
gives an awfull:
May 23 15:00:14 vitzlipu kernel: [029] 0 ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
May 23 15:00:14 vitzlipu kernel: [030] 0 ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 23 15:00:14 vitzlipu kernel: [031] 0 ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (95 iter).
May 23 15:00:14 vitzlipu kernel: [032] 0 ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 23 15:00:14 vitzlipu kernel: [033] 0 ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (95 iter).
May 23 15:00:14 vitzlipu kernel: [034] 0 ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 23 15:00:15 vitzlipu kernel: [035] 0 ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 23 15:00:15 vitzlipu kernel: [036] 0 ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 23 15:00:15 vitzlipu kernel: [037] 0 ftape-io.c
(ftape_report_raw_drive_status) - report_operation failed after 4
trials.
May 23 15:00:15 vitzlipu kernel: [038] 0 ftape-io.c
(ftape_wakeup_drive) - ftape_report_raw_drive_status(ftape, &status)
failed: -5.
May 23 15:00:15 vitzlipu kernel: [039] 0 ftape-ctl.c
(ftape_activate_drive) - known wakeup method failedTrying all the
(four) others ....
May 23 15:01:20 vitzlipu kernel: [040] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 23 15:01:21 vitzlipu kernel: [041] 0 ftape-io.c
(ftape_report_error) - errorcode: 26.
...
[41] and following are the same as [018] - [028]
An this goes on and on with any new command thats being typed into
the console. There is always the same awfull message. Inspite of
the fact that in the end the commands like for instance 'tar xfv
/dev/nqft0 /etc' are correctly executed.
I take from that message that fdc controller isn`t responding
anymore. ( That it did already I take from [004]: (_fdc_int_detect)
- fdc[0] base: 0x0).
Am I right with that?
What does this tell to someone who is familiar with the interiours of
ftape and - who -hopefully- read that far?
--
Hartmut Gehrke-Tschudi* Es gab immer nur gerechte Kriege
Bochum * Wars always were justified
BRD *
