Hi Neil,
> The backup did fail in the manner described in my PR#50 on the ftape
> support web-page. It seems intermittent for this version of ftape.
>
> Reinstalled ftape-4.03 and ftape-tools-1.08 and repeated the backup
> on a fresh tape with clean heads.
>
> Attached are environmental setup files e.g.:
>
> MCONFIG.patch - changes to MCONFIG for my system
> conf.modules - additions to standard file for my system
>
> The backup failed in the same manner as on 3 previous occasions. The
> attached file, failure.asc, details ftape output at the point of
> failure (I've removed other processes cruft and repeated close fails).
> Jul 10 12:38:01 ideal kernel: repositions : 23.
> Jul 10 12:39:40 ideal kernel: [001] 0 ftape-write.c
>(ftape_loop_until_writes_done_R003ed2ea) - error status set.
> Jul 10 12:39:40 ideal kernel: [002] 0 ftape-io.c (ftape_report_drive_status)
>- warning: error status set!.
> Jul 10 12:39:41 ideal kernel: [003] 0 ftape-io.c
>(ftape_report_error_R999edffd) - errorcode: 39.
This means "EOT/BOT System Failure".
> Jul 10 12:39:43 ideal kernel: [004] 0 ftape-io.c
>(ftape_report_error_R999edffd) - errorcode: 20.
This means "Self-Diagnostic Failed".
Doesn't look good. Can you verify that the tape drive still works,
e.g. by running it under Windoze?
Claus
--
Claus-Justus Heine
[EMAIL PROTECTED]
http://www.instmath.rwth-aachen.de/~heine/
Ftape - the Linux Floppy Tape Project
Home Page : http://www.instmath.rwth-aachen.de/~heine/ftape/
Mailing-list: [EMAIL PROTECTED]
