I am running Amanda-2.4.2p2 and it works fine. I am also currently
running ftape-4.x-2002_03_21 that I expanded from a tar
ball. It runs fine. My problem is that just recently I
get the
following errors in my syslog:
May 28 18:26:49 stud kernel: [210] 0 ftape-io.c
(ftape_report_error)
- ftape_report_operation(ftape, &code, QIC_REPORT_ERROR_CODE, 16)
failed: -5.
May 28 18:26:49 stud kernel: [211] 0 ftape-ctl.c
(ftape_get_drive_status) - report_error_code failed: -5.
May 28 18:26:51 stud kernel: [220] 0
ftape-io.c
(ftape_report_raw_drive_status) - report_operation failed after 4
trials.
May 28 18:26:51 stud kernel: [221] 0
ftape-io.c
(ftape_wakeup_drive) - ftape_report_raw_drive_status(ftape, &status)
failed: -5.
May 28 18:26:51 stud kernel: [222] 0 ftape-io.c
(ftape_reset_drive)
- Wakeup failed !.
May 28 18:26:53 stud kernel: [231] 0
ftape-io.c
(ftape_report_raw_drive_status) - report_operation failed after 4
trials.
May 28 18:26:53 stud kernel: [232] 0
ftape-io.c (ftape_ready_wait)
- ftape_report_raw_drive_status(ftape, status) failed: -5.
Unusual System Events
=-=-=-=-=-=-=-=-=-=-=
May 28 18:26:27 stud kernel: fdc-internal.c: fdc_internal_register
@
0xf0862c40.
May 28 18:26:27 stud kernel: [154] 0
fdc-internal.c
(fdc_int_detect) - fdc[0] base: 0x03f0, irq: 6, dma: 2.
May 28 18:26:27 stud kernel: [160] 0 fdc-io.c
(fdc_probe) - Type
82077AA FDC found.
May 28 18:26:28 stud kernel: [161] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:29 stud kernel: [164] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:30 stud kernel: [166] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:31 stud kernel: [168] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:32 stud kernel: [170] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:33 stud kernel: [172] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:34 stud kernel: [174] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:34 stud kernel: [176] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:35 stud kernel: [178] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:36 stud kernel: [180] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:37 stud kernel: [182] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:38 stud kernel: [184] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:39 stud kernel: [186] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:40 stud kernel: [188] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:40 stud kernel: [190] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:41 stud kernel: [192] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:42 stud kernel: [194] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:43 stud kernel: [196] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:44 stud kernel: [198] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:45 stud kernel: [200] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:46 stud kernel: [202] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:46 stud kernel: [204] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:47 stud kernel: [206] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:48 stud kernel: [208] 0 ftape-ctl.c
(ftape_get_drive_status) - error status set.
May 28 18:26:49 stud kernel: [209] 0
ftape-io.c
(ftape_report_operation) - missing status stop bit.
May 28 18:26:49 stud kernel: [210] 0 ftape-io.c
(ftape_report_error)
- ftape_report_operation(ftape, &code, QIC_REPORT_ERROR_CODE, 16)
failed: -5.
May 28 18:26:49 stud kernel: [211] 0 ftape-ctl.c
(ftape_get_drive_status) - report_error_code failed: -5.
May 28 18:26:50 stud kernel: [212] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:50 stud kernel: [213] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:51 stud kernel: [214] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:51 stud kernel: [215] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:51 stud kernel: [216] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:51 stud kernel: [217] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:51 stud kernel: [218] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:51 stud kernel: [219] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:51 stud kernel: [220] 0
ftape-io.c
(ftape_report_raw_drive_status) - report_operation failed after 4
trials.
May 28 18:26:51 stud kernel: [221] 0
ftape-io.c
(ftape_wakeup_drive) - ftape_report_raw_drive_status(ftape, &status)
failed: -5.
May 28 18:26:51 stud kernel: [222] 0 ftape-io.c
(ftape_reset_drive)
- Wakeup failed !.
May 28 18:26:52 stud kernel: [223] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:52 stud kernel: [224] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:52 stud kernel: [225] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:52 stud kernel: [226] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:52 stud kernel: [227] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:52 stud kernel: [228] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:53 stud kernel: [229] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:53 stud kernel: [230] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:53 stud kernel: [231] 0
ftape-io.c
(ftape_report_raw_drive_status) - report_operation failed after 4
trials.
May 28 18:26:53 stud kernel: [232] 0
ftape-io.c (ftape_ready_wait)
- ftape_report_raw_drive_status(ftape, status) failed: -5.
May 28 18:26:54 stud kernel: [233] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:54 stud kernel: [234] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
May 28 18:26:54 stud kernel: [235] 0
ftape-io.c
(ftape_report_operation) - No acknowledge after 300 msec. (96 iter).
May 28 18:26:54 stud kernel: [236] 0
ftape-io.c
(ftape_report_operation) - timeout on Acknowledge.
I don't have any cron job running at 6:26 PM at night, so this alone
puzzles me. The Colorado T-3000 drive TR-3 tapes was working
fine up until 3 days ago. When I pull out the tape
that is in the drive the green light starts to blink. The only
way that
I can "reset" the drive is by killing the power and repluging the power
back in. I also cannot remove the zftape or ftape modules using
the
rmmod command because it say ftape: the device or resource is
busy. It almost seems like the Amanda job has not finished and it
is waiting for something. As
I said before I don't understand why all of a sudden this is happening.
Any help is appreciated.
Trevor
-- Trevor Morrison Hailix, LLC [EMAIL PROTECTED]
