Kern Sibbald wrote:
On Thursday 17 November 2005 11:01, Julien Cigar wrote:
I think I found the problem.
I changed the scsi id of the tape drive from ID 0 to ID 6 and it *seems*
to work better (I did a full backup and no problems occured yet). I read
that apparently ID 0 and ID 1 s
AltGrendel wrote:
John Stoffel wrote:
Julien> I think I found the problem. I changed the scsi id of the
Julien> tape drive from ID 0 to ID 6 and it *seems* to work better (I
Julien> did a full backup and no problems occured yet). I read that
Julien> apparently ID 0 and ID 1 should not be used
John Stoffel wrote:
Julien> I think I found the problem. I changed the scsi id of the
Julien> tape drive from ID 0 to ID 6 and it *seems* to work better (I
Julien> did a full backup and no problems occured yet). I read that
Julien> apparently ID 0 and ID 1 should not be used for tape drives
Jul
> "Julien" == Julien Cigar <[EMAIL PROTECTED]> writes:
Julien> I don't have any other scsi devices on that chain, the tape
Julien> drive is the only device. You're right, the scsi id of the
Julien> controller is 7 (it was 1 before, I've also changed this)
Oh good. Putting the controller any
John Stoffel wrote:
Julien> I think I found the problem. I changed the scsi id of the
Julien> tape drive from ID 0 to ID 6 and it *seems* to work better (I
Julien> did a full backup and no problems occured yet). I read that
Julien> apparently ID 0 and ID 1 should not be used for tape drives
Jul
Julien> I think I found the problem. I changed the scsi id of the
Julien> tape drive from ID 0 to ID 6 and it *seems* to work better (I
Julien> did a full backup and no problems occured yet). I read that
Julien> apparently ID 0 and ID 1 should not be used for tape drives
Julien> (it's for booting
On Thursday 17 November 2005 11:01, Julien Cigar wrote:
> I think I found the problem.
> I changed the scsi id of the tape drive from ID 0 to ID 6 and it *seems*
> to work better (I did a full backup and no problems occured yet). I read
> that apparently ID 0 and ID 1 should not be used for tape dr
I think I found the problem.
I changed the scsi id of the tape drive from ID 0 to ID 6 and it *seems*
to work better (I did a full backup and no problems occured yet). I read
that apparently ID 0 and ID 1 should not be used for tape drives (it's
for booting devices only ...)
Kern Sibbald wrot
Kern Sibbald wrote:
On Monday 07 November 2005 15:15, Julien Cigar wrote:
You think I can ignore the problem ?
When I list media you can see that the tape Weekly-0003 has not been
filled up completely (it was the tape with write errors ...)
Well, that answers the questio
On Monday 07 November 2005 15:15, Julien Cigar wrote:
> You think I can ignore the problem ?
> When I list media you can see that the tape Weekly-0003 has not been
> filled up completely (it was the tape with write errors ...)
Well, that answers the question I had: the drive could not recover from
You think I can ignore the problem ?
When I list media you can see that the tape Weekly-0003 has not been
filled up completely (it was the tape with write errors ...)
*list media
Pool: WeeklyFullBackupPool
+-+-+---+-+--+--+-+--
On Monday 07 November 2005 09:04, Julien Cigar wrote:
> Hello,
>
> I writed a mail some weeks ago for a problem with my Sony drive (write
> errors).
> The drive is a Sony SDX-500C on a Adaptec 2940 Ultra SCSI.
> Someone told me to upgrade the bios of the drive, which I did. It worked
> fine for a w
12 matches
Mail list logo
