Thomas Schmitt wrote:
> Hi,
>
>> Nov 13 08:02:29 BigMutt kernel: [34669.493879] st 0:0:0:0: [st0] Error
>> e (driver bt 0x0, host bt 0xe).
>> Nov 13 08:02:31 BigMutt kernel: [34671.743714] st 0:0:0:0: [st0] Error
>> 1 (driver bt 0x0, host bt 0x1).
>
> This looks electrical, not
On Thu, 2 Jan 2020 16:15:07 -0500
Gene Heskett wrote:
> > For more long range, I'll second Gene Heskett's recommendation for
> > external USB drives. You can use amanda or any number of other
> > tools. I use several.
>
> No external usb drives allowed, I've found them to be many times less
On Thursday 02 January 2020 15:32:39 Charles Curley wrote:
> On Thu, 2 Jan 2020 10:51:45 -0600
>
> Jack G F Hill wrote:
> > All this leads to the hardware question, "What is failing": Tape
> > Drive? Cartridge(s)? Cable? SAS Controller?
>
> The first thing I would do is take the thing apart,
On Thu, 2 Jan 2020 10:51:45 -0600
Jack G F Hill wrote:
> All this leads to the hardware question, "What is failing": Tape
> Drive? Cartridge(s)? Cable? SAS Controller?
The first thing I would do is take the thing apart, pull the
connectors, clean them, and re-seat them. Then I would look for
Gene Heskett wrote:
> On Thursday 02 January 2020 12:13:43 Dan Ritter wrote:
>
> > Jack G F Hill wrote:
> > > So, is the culprit the LTO-5 drive? Cartridge? possibly the I/O
> > > signal cable? the SAS Controller? What do I need to do to determine
> > > the true cause of the errors with
Hi,
> Nov 13 08:02:29 BigMutt kernel: [34669.493879] st 0:0:0:0: [st0] Error e
> (driver bt 0x0, host bt 0xe).
> Nov 13 08:02:31 BigMutt kernel: [34671.743714] st 0:0:0:0: [st0] Error 1
> (driver bt 0x0, host bt 0x1).
This looks electrical, not mechanical or magnetical.
I am sure that
On Thursday 02 January 2020 12:13:43 Dan Ritter wrote:
> Jack G F Hill wrote:
> > All this leads to the hardware question, "What is failing": Tape
> > Drive? Cartridge(s)? Cable? SAS Controller?
> >
> > Rather than just blindly substitute parts (expensive, time
> > consuming, frustratingly
Jack G F Hill wrote:
> All this leads to the hardware question, "What is failing": Tape Drive?
> Cartridge(s)? Cable? SAS Controller?
>
> Rather than just blindly substitute parts (expensive, time consuming,
> frustratingly inconclusive) and try to eliminate that way, I'd really like
> to have a
I've been trying to diagnose and resolve this since November, and am
still having trouble figuring out what is happening... Debian 10 doesn't
present any real easy way to decode and find details about the
hexadecimal error messages.
I know this is kinda "old-school", but I'm backing up
9 matches
Mail list logo
