Hi Rob,
ok, this sounds not really bad. But one question is still
open. One of your last logs showed that you have a 765
compatible fdc. AFAIK this supports at max. 500kbps. Please
have a look at your /var/log/messages file. There you should
find a message like
Highest FDC supported data rate
There ftape-ctl.c should report a value of at least 1000kbps.
Any value below won't work with your ditto 2GB. This is
definitive and a limitation by design of the IOMEGA drive.
If this is true it's useless to do anymore work on this issue
until you have a ditto dash. It's not expensive, I did pay
something about DM 75,-- (approx Euro 38).
> With a bit of fiddling with settings, I now have the Ditto drive in a more functional
> state. ftmt now works, for rewind and reten, but ftmt status gives 'Input/output
>error'
This is typical if tape isn't able to read the data from the
tape. The status command tries to read the header segment
with technical information and this fail's with the wrong
data rate.
> and any action with tar makes the drive wind eternally, and fills the
>/var/log/messages
> with lines like this:
>
> Jan 2 18:49:23 redhat kernel: [215] 0 ftape-rw.c (determine_position) -
>ftape_report_drive_status: 0x24.
> Jan 2 18:49:24 redhat kernel: [216] 0 ftape-rw.c (determine_position) -
>ftape_report_drive_status: 0x24.
> Jan 2 18:49:24 redhat kernel: [217] 0 ftape-rw.c (determine_position) -
>ftape_report_drive_status: 0x24.
> Jan 2 18:49:24 redhat kernel: [218] 0 ftape-rw.c (ftape_start_tape) - panic:
>location not known.
> Jan 2 18:49:25 redhat kernel: [219] 0 ftape-rw.c (determine_position) -
>ftape_report_drive_status: 0x24.
> Jan 2 18:49:26 redhat kernel: [220] 0 ftape-rw.c (determine_position) -
>ftape_report_drive_status: 0x24.
> Jan 2 18:49:27 redhat kernel: [221] 0 ftape-rw.c (determine_position) -
>ftape_report_drive_status: 0x24.
>
> Rob
>
>
Martin
--
Martin Jacobs * Windsbach * [EMAIL PROTECTED]
Registered Linux User #87175
