On Jan 31, 2008 12:52 PM, Dustin J. Mitchell <[EMAIL PROTECTED]> wrote:
> On Jan 31, 2008 12:41 PM, FL <[EMAIL PROTECTED]> wrote: > > Ok, then I have another problem--possibly timeouts with the tape > changer. > > My exabyte 224 LTO3 library has a bizarre problem (verified numerous > times): > > connecting the ethernet port to a 100mb/sec switch causes the unit to > time > > out. > > Sounds like a (very weird) grounding or termination problem to me. > > Dustin > > -- > Storage Software Engineer > http://www.zmanda.com > That could be--I could try another terminator. As for removing and relabeling Daily08, amanda claims that Daily08 is not in the tapelist Amanda Tape Server Host Check ----------------------------- Holding disk /var/lib/amanda/holdingdisk: 60199272 KB disk space available, that's plenty amcheck-server: slot 7: date 20071215 label Daily07 (active tape) amcheck-server: slot 8: date 20071205 label Daily08 (Not in tapelist) amcheck-server: slot 9: date 20071206 label Daily09 (active tape) amcheck-server: slot 10: date 20071207 label Daily10 (active tape) amcheck-server: fatal slot 11: mtx: Request Sense: Long Report=yes ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 587.029 seconds Amanda Backup Client Hosts Check -------------------------------- Client check: 4 hosts checked in 10.083 seconds, 0 problems found (brought to you by Amanda 2.4.4p3) A subsequent amcheck Daily resulted in this Amanda Tape Server Host Check ----------------------------- Holding disk /var/lib/amanda/holdingdisk: 60199208 KB disk space available, that's plenty amcheck-server: slot 10: date 20071207 label Daily10 (active tape) amcheck-server: fatal slot 11: mtx: Request Sense: Long Report=yes ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 115.114 seconds Amanda Backup Client Hosts Check -------------------------------- Client check: 4 hosts checked in 10.059 seconds, 0 problems found (brought to you by Amanda 2.4.4p3) The mtx failure happens during amcheck but apparently not during amdump...
