Re: Colorado Jumbo 250

Ken Arck <[email protected]> Sun, 30 Jun 2002 08:56:26 -0700
Newsgroups gmane.linux.tape
Message-ID <3.0.32.20020630085624.01c78eec@repeater>
At 08:41 AM 6/29/02 -0400, Douglas Bollinger wrote:

>Grab the absolute latest ftape drivers (in the unstable/testing dir).
>
>Make sure your current kernel has ftape support OFF.  You will also need
>the source of your current kernel, then read the instructions and compile
>the ftape drivers.

<----Been there, done that. I installed the latest ftape
(ftape-4.x-2002_06_13) I know the drive is ok, as it runs fine under DOS
(another machine). I also installed ftape-tools. Here's some more info..

[root@rush root]# ftmt -f /dev/ftape status
ftmt: /dev/ftape: Input/output error
[root@rush root]# 

Pertinent syslog info:

Jun 30 08:52:14 rush kernel: [044]      zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 0.
Jun 30 08:52:24 rush kernel: [045]      zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 1.
Jun 30 08:52:24 rush kernel: [046]     zftape-write.c
(zft_write_header_segments) - Warning: update of first header segment failed.
Jun 30 08:52:24 rush kernel: [047]     zftape-write.c
(zft_write_header_segments) - Warning: update of second header segment failed.
Jun 30 08:52:24 rush kernel: [048]     zftape-write.c
(zft_write_header_segments) - Error: update of both header segments failed..
Jun 30 08:52:24 rush kernel: [049]    zftape-write.c
(zft_update_header_segments) - zft_write_header_segments(zft_hseg_buf)
failed: -5.
Jun 30 08:52:24 rush kernel: [050]   zftape-ctl.c (mtioctop) -
zft_update_header_segments() failed: -5.
Jun 30 08:52:32 rush kernel: [051]     zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 0.
Jun 30 08:52:42 rush kernel: [052]     zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 1.
Jun 30 08:52:42 rush kernel: [053]    zftape-write.c
(zft_write_header_segments) - Warning: update of first header segment failed.
Jun 30 08:52:42 rush kernel: [054]    zftape-write.c
(zft_write_header_segments) - Warning: update of second header segment failed.
Jun 30 08:52:42 rush kernel: [055]    zftape-write.c
(zft_write_header_segments) - Error: update of both header segments failed..
Jun 30 08:52:42 rush kernel: [056]   zftape-write.c
(zft_update_header_segments) - zft_write_header_segments(zft_hseg_buf)
failed: -5.
Jun 30 08:52:44 rush kernel: [057]   ftape-ctl.c (ftape_disable_R7b52f04b)
- == Non-fatal errors this run: ==.
Jun 30 08:52:44 rush kernel: [058]   ftape-ctl.c (ftape_disable_R7b52f04b)
- fdc isr statistics:
Jun 30 08:52:44 rush kernel:  id_am_errors     :   0
Jun 30 08:52:44 rush kernel:  id_crc_errors    :   0
Jun 30 08:52:44 rush kernel:  data_am_errors   :   0
Jun 30 08:52:44 rush kernel:  data_crc_errors  :   0
Jun 30 08:52:44 rush kernel:  overrun_errors   :   0
Jun 30 08:52:44 rush kernel:  no_data_errors   :   0
Jun 30 08:52:44 rush kernel:  retries          :   0.
Jun 30 08:52:44 rush kernel: [059]   ftape-ctl.c (ftape_disable_R7b52f04b)
- ecc statistics:
Jun 30 08:52:44 rush kernel:  crc_errors       :   0
Jun 30 08:52:44 rush kernel:  crc_failures     :   0
Jun 30 08:52:44 rush kernel:  ecc_failures     :   0
Jun 30 08:52:44 rush kernel:  sectors corrected:   0.
Jun 30 08:52:44 rush kernel: [060]   ftape-ctl.c (ftape_disable_R7b52f04b)
- tape motion statistics:
Jun 30 08:52:44 rush kernel: repositions       :   8.
Jun 30 08:52:44 rush kernel: [061] zftape-init.c (zft_close) - _zft_close
failed.

I have more syslog info from running erase, but it's quite long. I'll send
it only if it's necessary. 

I also tried tar'ing a file to the drive and it gives no error messages:

[root@rush root]# tar -cvf /dev/ftape install.log
install.log
[root@rush root]# 

Syslog shows:

Jun 30 08:55:20 rush kernel: [062]     zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 0.
Jun 30 08:55:29 rush kernel: [063]     zftape-rw.c
(zft_verify_write_segments) - Failed to verify written segment 1.
Jun 30 08:55:29 rush kernel: [064]    zftape-write.c
(zft_write_header_segments) - Warning: update of first header segment failed.
Jun 30 08:55:29 rush kernel: [065]    zftape-write.c
(zft_write_header_segments) - Warning: update of second header segment failed.
Jun 30 08:55:29 rush kernel: [066]    zftape-write.c
(zft_write_header_segments) - Error: update of both header segments failed..
Jun 30 08:55:29 rush kernel: [067]   zftape-write.c
(zft_update_header_segments) - zft_write_header_segments(zft_hseg_buf)
failed: -5.
Jun 30 08:55:32 rush kernel: [068]   ftape-ctl.c (ftape_disable_R7b52f04b)
- == Non-fatal errors this run: ==.
Jun 30 08:55:32 rush kernel: [069]   ftape-ctl.c (ftape_disable_R7b52f04b)
- fdc isr statistics:
Jun 30 08:55:32 rush kernel:  id_am_errors     :   0
Jun 30 08:55:32 rush kernel:  id_crc_errors    :   0
Jun 30 08:55:32 rush kernel:  data_am_errors   :   0
Jun 30 08:55:32 rush kernel:  data_crc_errors  :   0
Jun 30 08:55:32 rush kernel:  overrun_errors   :   0
Jun 30 08:55:32 rush kernel:  no_data_errors   :   0
Jun 30 08:55:32 rush kernel:  retries          :   0.
Jun 30 08:55:32 rush kernel: [070]   ftape-ctl.c (ftape_disable_R7b52f04b)
- ecc statistics:
Jun 30 08:55:32 rush kernel:  crc_errors       :   0
Jun 30 08:55:32 rush kernel:  crc_failures     :   0
Jun 30 08:55:32 rush kernel:  ecc_failures     :   0
Jun 30 08:55:32 rush kernel:  sectors corrected:   0.
Jun 30 08:55:32 rush kernel: [071]   ftape-ctl.c (ftape_disable_R7b52f04b)
- tape motion statistics:
Jun 30 08:55:32 rush kernel: repositions       :   5.
Jun 30 08:55:32 rush kernel: [072] zftape-init.c (zft_close) - _zft_close
failed.

Need more at this point?

Ken


, but when I try to verify it, I get the following:






------------------------------------------------------------------------------
Amateur Radio Station AH6LE
http://www.ah6le.net
http://www.ah6le.com
AH6LE/R - IRLP Node 300
http://www.irlp.net

RC Websites
http://oregonbarnstormers.rcclubs.com
http://pegasus.rcplanet.com
-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html