On Monday 02 April 2007 19:40, Sebastiaan Veldhuisen wrote:
> On ma, 2007-04-02 at 17:20 +0200, Kern Sibbald wrote:
> > On Monday 02 April 2007 13:27, Sebastiaan Veldhuisen wrote:
> > > Hmmzz,
> > > 
> > > Houston we have a problem. This is a SATA drive so hooking it up to a
> > > SCSI HBA is impossible.
> > > 
> > > If i run the diagnostic tests of the Quantum DLT Sage Talk, read and
> > > write actions are working perfectly. If the drivers was bad, this should
> > > fail also.
> > 
> > If the diagnostic was written by a disk jockey, he may have overlooked the 
> > subtleties of tape drives.  There is a whole lot more to a tape driver 
than 
> > read and write actions.
> 
> You're right. My conclusion is incorrect.
> > 
> > > 
> > > I guess that Bacula only supports SCSI tape drives?
> > 
> > Sorry but you guess wrong.
> 
> I think you misunderstand me. I know Bacula can handle other devices
> quite well. My statement was that for tape drives, only SCSI types are
> working reliable on Linux with Bacula (can't say anything about
> Windows). 

It is not that simple. Bacula does work with some non-SCSI drives, but the 
only ones I know of are Windows drivers (just confirmed by Robert) and in the 
Unix/Linux world where I personally worked with the driver write (very long 
and tedious) to correct his understanding of what the driver needs to do to 
function correctly.  Driver writers generally don't understand end of tape 
handling because *very* few programs are capabable of writing multiple tape 
output.

> 
> >   
> > 
> > Bacula handles disk drive, DVD, USB removable drives, and a large variety 
of 
> > tape drives.  Each has quite different characteristics.  The canonical 
> > definition of how a tape drive works is available in the Solaris 
> > documentation (the Linux SCSI driver functions the same way by default). 
> > Bacula can handle many tape drives that do not meet the canonical 
definition, 
> > which covers 99% of all modern tape drives out of the box, but clearly the 
> > farther a drive/driver is from the canonical form the more difficult it 
is, 
> > and the more difficult it is for the user to configure Bacula correctly.  
> > There is a minimal functionality below which Bacula cannot work -- whether 
or 
> > not that is the case with your drive/driver, I cannot say.
> 
> My drive is detected as a SCSI device. Are you trying to suggest that my
> drive doesn't respect the native SCSI protocols? 

I'm saying what I said a few lines below: 

"My best guess is that Bacula wrote off the end of the tape because the driver 
did not properly indicate to Bacula that it was approaching the end of the 
tape (i.e. logical end of tape -- see Solaris documentation for what that 
means)."


> > 
> > The output you show below points *very* strongly toward a driver problem 
> > (after all, it clearly says Hardware Error), but since I don't recall 
seeing 
> > your Bacula SD conf file, a problem there is also a "small" possibility.  
> > My best guess is that Bacula wrote off the end of the tape because the 
driver 
> > did not properly indicate to Bacula that it was approaching the end of the 
> > tape (i.e. logical end of tape -- see Solaris documentation for what that 
> > means).
> 
> 
> 
> > 
> > In any case making an SATA driver work is probably not going to be fun.
> 
> \o/
> 
> I'm willing to give it a shot with some assistance :-)

I regret that I cannot help you out. Perhaps others on the list can try. 

I am not convinced it is going to work, but until you systematically try the 
correct combinations of the Bacula device conf directives you cannot be sure.

These things take months of intense effort and if my guess is correct, it is 
impossible without the close cooperation of the person who wrote the driver.

> 
> > 
> > > 
> > > 
> > > 
> > > On ma, 2007-04-02 at 13:14 +0200, Kern Sibbald wrote:
> > > > I suspect that you have a bad driver.  I don't think I have ever seen 
a 
> > > > non-SCSI tape driver that works correctly, probably because they are 
> > written 
> > > > by disk driver programmers that don't understand the subtleties of 
tape 
> > > > drivers.
> > > > 
> > > > I'd recommend that if possible you hook your drive up through a good 
SCSI 
> > > > card.  
> > > > 
> > > > On Monday 02 April 2007 00:28, Sebastiaan Veldhuisen wrote:
> > > > > Minor update.
> > > > > 
> > > > > I tried the bacula 2.0.0-1 debs and redid the btape fill. At the end 
I
> > > > > get the following in my kernel.log:
> > > > > 
> > > > > Apr  2 00:10:17 debian kernel: st0: Current [descriptor]: sense key:
> > > > > Hardware Error
> > > > > Apr  2 00:10:17 debian kernel:     Additional sense: No additional 
sense
> > > > > information
> > > > > Apr  2 00:10:17 debian kernel: Descriptor sense data with sense
> > > > > descriptors (in hex):
> > > > > Apr  2 00:10:17 debian kernel:         72 04 00 00 00 00 00 0e 09 0e 
00
> > > > > 52 00 03 00 00 
> > > > > Apr  2 00:10:17 debian kernel:         00 00 00 00 a0 51 
> > > > > Apr  2 00:10:19 debian kernel: ata2.00: exception Emask 0x0 SAct 0x0
> > > > > SErr 0x0 action 0x0
> > > > > Apr  2 00:10:19 debian kernel: ata2.00: (BMDMA stat 0x20)
> > > > > Apr  2 00:10:19 debian kernel: ata2.00: tag 0 cmd 0xa0 Emask 0x1 
stat
> > > > > 0x51 err 0x52 (device error)
> > > > > Apr  2 00:10:19 debian kernel: ata2: EH complete
> > > > > Apr  2 00:10:19 debian kernel: st0: Current [descriptor]: sense key:
> > > > > Hardware Error
> > > > > Apr  2 00:10:19 debian kernel:     Additional sense: No additional 
sense
> > > > > information
> > > > > Apr  2 00:10:19 debian kernel: Descriptor sense data with sense
> > > > > descriptors (in hex):
> > > > > Apr  2 00:10:19 debian kernel:         72 04 00 00 00 00 00 0e 09 0e 
00
> > > > > 52 00 03 00 00 
> > > > > Apr  2 00:10:19 debian kernel:         00 00 00 00 a0 51 
> > > > > Apr  2 00:10:21 debian kernel: ata2.00: exception Emask 0x0 SAct 0x0
> > > > > SErr 0x0 action 0x0
> > > > > Apr  2 00:10:21 debian kernel: ata2.00: (BMDMA stat 0x20)
> > > > > Apr  2 00:10:21 debian kernel: ata2.00: tag 0 cmd 0xa0 Emask 0x1 
stat
> > > > > 0x51 err 0x52 (device error)
> > > > > Apr  2 00:10:21 debian kernel: ata2: EH complete
> > > > > Apr  2 00:10:21 debian kernel: st0: Current [descriptor]: sense key:
> > > > > Hardware Error
> > > > > Apr  2 00:10:21 debian kernel:     Additional sense: No additional 
sense
> > > > > information
> > > > > Apr  2 00:10:21 debian kernel: Descriptor sense data with sense
> > > > > descriptors (in hex):
> > > > > Apr  2 00:10:21 debian kernel:         72 04 00 00 00 00 00 0e 09 0e 
00
> > > > > 52 00 03 00 00 
> > > > > Apr  2 00:10:21 debian kernel:         00 00 00 00 a0 51 
> > > > > Apr  2 00:10:23 debian kernel: ata2.00: exception Emask 0x0 SAct 0x0
> > > > > SErr 0x0 action 0x0
> > > > > Apr  2 00:10:23 debian kernel: ata2.00: (BMDMA stat 0x20)
> > > > > Apr  2 00:10:23 debian kernel: ata2.00: tag 0 cmd 0xa0 Emask 0x1 
stat
> > > > > 0x51 err 0x52 (device error)
> > > > > Apr  2 00:10:23 debian kernel: ata2: EH complete
> > > > > Apr  2 00:10:23 debian kernel: st0: Current [descriptor]: sense key:
> > > > > Hardware Error
> > > > > Apr  2 00:10:23 debian kernel:     Additional sense: No additional 
sense
> > > > > information
> > > > > Apr  2 00:10:23 debian kernel: Descriptor sense data with sense
> > > > > descriptors (in hex):
> > > > > Apr  2 00:10:23 debian kernel:         72 04 00 00 00 00 00 0e 09 0e 
00
> > > > > 52 00 03 00 00 
> > > > > Apr  2 00:10:23 debian kernel:         00 00 00 00 a0 51 
> > > > > Apr  2 00:10:25 debian kernel: ata2.00: exception Emask 0x0 SAct 0x0
> > > > > SErr 0x0 action 0x0
> > > > > Apr  2 00:10:25 debian kernel: ata2.00: tag 0 cmd 0xa0 Emask 0x1 
stat
> > > > > 0x51 err 0x52 (device error)
> > > > > Apr  2 00:10:25 debian kernel: ata2: EH complete
> > > > > Apr  2 00:10:25 debian kernel: st0: Current [descriptor]: sense key:
> > > > > Hardware Error
> > > > > Apr  2 00:10:25 debian kernel:     Additional sense: No additional 
sense
> > > > > information
> > > > > Apr  2 00:10:25 debian kernel: Descriptor sense data with sense
> > > > > descriptors (in hex):
> > > > > Apr  2 00:10:25 debian kernel:         72 04 00 00 00 00 00 0e 09 0e 
00
> > > > > 52 00 03 00 00 
> > > > > Apr  2 00:10:25 debian kernel:         00 00 00 20 a0 51 
> > > > > 
> > > > > 
> > > > > My question is: is my problem is Bacula or kernel related?
> > > > > 
> > > > > Thanks for your time
> > > > > 
> > > > > Sebastiaan
> > > > > 
> > > > > On zo, 2007-04-01 at 11:02 +0200, Sebastiaan Veldhuisen wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > I'm trying to get a Quantum DLT-V4 SATA to work on my Debian Etch 
> > Bacula
> > > > > > setup. My knowledge about Linux is good, but I don't have a lot of
> > > > > > experience with Tape drives and/ or Bacula.  Did a lot of testing 
with
> > > > > > btape (as in days), but it is still not working. I'm really done 
with
> > > > > > testing, therefore my hope is targeted at some gurus on the 
> > mailinglist
> > > > > > that can tell me what is wrong (or what I am doing wrong).
> > > > > > Any help would be great!
> > > > > > 
> > > > > > Some notes:
> > > > > > If I schedule a backup inside Bacula it works (completes 
> > successfully).
> > > > > > I can't do a restore, which gives me the same errors as with 
btape.
> > > > > > 
> > > > > > -------------------------------
> > > > > > *version
> > > > > > -------------------------------
> > > > > > debian-dir Version: 1.38.11 (28 June 2006)
> > > > > > 
> > > > > > -------------------------------
> > > > > > debian:~# cat /proc/scsi/scsi 
> > > > > > -------------------------------
> > > > > > Attached devices:
> > > > > > Host: scsi0 Channel: 00 Id: 00 Lun: 00
> > > > > >   Vendor: ATA      Model: SAMSUNG SP1614C  Rev: SW10
> > > > > >   Type:   Direct-Access                    ANSI SCSI revision: 05
> > > > > > Host: scsi1 Channel: 00 Id: 00 Lun: 00
> > > > > >   Vendor: QUANTUM  Model: DLT-V4           Rev: 0800
> > > > > >   Type:   Sequential-Access                ANSI SCSI revision: 02
> > > > > > 
> > > > > > -------------------------------
> > > > > > debian:~# cat /etc/stinit.def
> > > > > > -------------------------------
> > > > > > # QUANTUM DLT-V4
> > > > > > manufacturer=QUANTUM model="DLT-V4" {
> > > > > > timeout=3600
> > > > > > long-timeout=14400
> > > > > > can-partitions=0
> > > > > > drive-buffering=1
> > > > > > no-wait=0
> > > > > > buffering=0
> > > > > > async-writes=0
> > > > > > read-ahead=0
> > > > > > two-fms=0
> > > > > > auto-lock=0
> > > > > > fast-eom=0
> > > > > > can-bsr=1
> > > > > > noblklimits=0
> > > > > > mode1 blocksize=0 density=0x51 compression=1 # DLT-V4 density,
> > > > > > compression on
> > > > > > }
> > > > > > 
> > > > > > -------------------------------
> > > > > > device section from bacula-sd.conf:
> > > > > > -------------------------------
> > > > > > Device {
> > > > > >   Name = DLT-V4
> > > > > >   Media Type = DLT
> > > > > >   Archive Device = /dev/nst0
> > > > > >   LabelMedia = yes;
> > > > > >   AutomaticMount = yes;               # when device opened, read 
it
> > > > > >   AlwaysOpen = no;
> > > > > >   RemovableMedia = yes;
> > > > > >   RandomAccess = no;
> > > > > >   # too bad, tapeinfo not supported on this device :(
> > > > > >   #Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
> > > > > > }
> > > > > > 
> > > > > > -------------------------------
> > > > > > When i do a btape test, everything seems ok:
> > > > > > -------------------------------
> > > > > > === Write, rewind, and re-read test ===
> > > > > > 
> > > > > > I'm going to write 1000 records and an EOF
> > > > > > then write 1000 records and an EOF, then rewind,
> > > > > > and re-read the data to verify that it is correct.
> > > > > > 
> > > > > > This is an *essential* feature ...
> > > > > > 
> > > > > > btape: btape.c:795 Wrote 1000 blocks of 64412 bytes.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:811 Wrote 1000 blocks of 64412 bytes.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:820 Rewind OK.
> > > > > > 1000 blocks re-read correctly.
> > > > > > Got EOF on tape.
> > > > > > 1000 blocks re-read correctly.
> > > > > > === Test Succeeded. End Write, rewind, and re-read test ===
> > > > > > 
> > > > > > 
> > > > > > === Write, rewind, and position test ===
> > > > > > 
> > > > > > I'm going to write 1000 records and an EOF
> > > > > > then write 1000 records and an EOF, then rewind,
> > > > > > and position to a few blocks and verify that it is correct.
> > > > > > 
> > > > > > This is an *essential* feature ...
> > > > > > 
> > > > > > btape: btape.c:907 Wrote 1000 blocks of 64412 bytes.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:923 Wrote 1000 blocks of 64412 bytes.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:932 Rewind OK.
> > > > > > Reposition to file:block 0:4
> > > > > > Block 5 re-read correctly.
> > > > > > Reposition to file:block 0:200
> > > > > > Block 201 re-read correctly.
> > > > > > Reposition to file:block 0:999
> > > > > > Block 1000 re-read correctly.
> > > > > > Reposition to file:block 1:0
> > > > > > Block 1001 re-read correctly.
> > > > > > Reposition to file:block 1:600
> > > > > > Block 1601 re-read correctly.
> > > > > > Reposition to file:block 1:999
> > > > > > Block 2000 re-read correctly.
> > > > > > === Test Succeeded. End Write, rewind, and re-read test ===
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > === Append files test ===
> > > > > > 
> > > > > > This test is essential to Bacula.
> > > > > > 
> > > > > > I'm going to write one record  in file 0,
> > > > > >                    two records in file 1,
> > > > > >              and three records in file 2
> > > > > > 
> > > > > > btape: btape.c:438 Rewound "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:338 open device "DLT-V4" (/dev/nst0): OK
> > > > > > btape: btape.c:438 Rewound "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1061 Now moving to end of medium.
> > > > > > btape: btape.c:490 Moved to end of medium.
> > > > > > We should be in file 3. I am at file 3. This is correct!
> > > > > > 
> > > > > > Now the important part, I am going to attempt to append to the 
tape.
> > > > > > 
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:438 Rewound "DLT-V4" (/dev/nst0)
> > > > > > Done appending, there should be no I/O errors
> > > > > > 
> > > > > > Doing Bacula scan of blocks:
> > > > > > 1 block of 64448 bytes in file 1
> > > > > > End of File mark.
> > > > > > 2 blocks of 64448 bytes in file 2
> > > > > > End of File mark.
> > > > > > 3 blocks of 64448 bytes in file 3
> > > > > > End of File mark.
> > > > > > 1 block of 64448 bytes in file 4
> > > > > > End of File mark.
> > > > > > Total files=4, blocks=7, bytes = 451,136
> > > > > > End scanning the tape.
> > > > > > We should be in file 4. I am at file 4. This is correct!
> > > > > > 
> > > > > > The above Bacula scan should have output identical to what 
follows.
> > > > > > Please double check it ...
> > > > > > === Sample correct output ===
> > > > > > 1 block of 64448 bytes in file 1
> > > > > > End of File mark.
> > > > > > 2 blocks of 64448 bytes in file 2
> > > > > > End of File mark.
> > > > > > 3 blocks of 64448 bytes in file 3
> > > > > > End of File mark.
> > > > > > 1 block of 64448 bytes in file 4
> > > > > > End of File mark.
> > > > > > Total files=4, blocks=7, bytes = 451,136
> > > > > > === End sample correct output ===
> > > > > > 
> > > > > > If the above scan output is not identical to the
> > > > > > sample output, you MUST correct the problem
> > > > > > or Bacula will not be able to write multiple Jobs to 
> > > > > > the tape.
> > > > > > 
> > > > > > 
> > > > > > === Write, backup, and re-read test ===
> > > > > > 
> > > > > > I'm going to write three records and an EOF
> > > > > > then backup over the EOF and re-read the last record.
> > > > > > Bacula does this after writing the last block on the
> > > > > > tape to verify that the block was written correctly.
> > > > > > 
> > > > > > This is not an *essential* feature ...
> > > > > > 
> > > > > > btape: btape.c:438 Rewound "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:674 Wrote first record of 64412 bytes.
> > > > > > btape: btape.c:685 Wrote second record of 64412 bytes.
> > > > > > btape: btape.c:696 Wrote third record of 64412 bytes.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:712 Backspaced over EOF OK.
> > > > > > btape: btape.c:717 Backspace record OK.
> > > > > > btape: btape.c:735 
> > > > > > Block re-read correct. Test succeeded!
> > > > > > === End Write, backup, and re-read test ===
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > === Forward space files test ===
> > > > > > 
> > > > > > This test is essential to Bacula.
> > > > > > 
> > > > > > I'm going to write five files then test forward spacing
> > > > > > 
> > > > > > btape: btape.c:438 Rewound "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1531 Wrote one record of 64412 bytes.
> > > > > > btape: btape.c:1533 Wrote block to device.
> > > > > > btape: btape.c:469 Wrote 1 EOF to "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:438 Rewound "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1276 Now forward spacing 1 file.
> > > > > > We should be in file 1. I am at file 1. This is correct!
> > > > > > btape: btape.c:1288 Now forward spacing 2 files.
> > > > > > We should be in file 3. I am at file 3. This is correct!
> > > > > > btape: btape.c:438 Rewound "DLT-V4" (/dev/nst0)
> > > > > > btape: btape.c:1301 Now forward spacing 4 files.
> > > > > > We should be in file 4. I am at file 4. This is correct!
> > > > > > 
> > > > > > btape: btape.c:1319 Now forward spacing 1 more file.
> > > > > > We should be in file 5. I am at file 5. This is correct!
> > > > > > 
> > > > > > === End Forward space files test ===
> > > > > > 
> > > > > > 
> > > > > > -------------------------------
> > > > > > However the fill test gives me the following error:
> > > > > > -------------------------------
> > > > > > 01-Apr 10:14 btape: btape Error: block.c:538 Write error at 
216:694 on
> > > > > > device "DLT-V4" (/dev/nst0). ERR=Input/output error.
> > > > > > 01-Apr 10:14 btape: btape Error: Error writing final EOF to tape. 
This
> > > > > > Volume may not be readable.
> > > > > > dev.c:1542 ioctl MTWEOF error on "DLT-V4" (/dev/nst0). 
> > ERR=Input/output
> > > > > > error.
> > > > > > btape: btape.c:2301 Last block at: 216:693 this_dev_block_num=694
> > > > > > btape: btape.c:2335 End of tape 216:694. 
> > VolumeCapacity=148,615,818,480.
> > > > > > Write rate = 9076.9 KB/s
> > > > > > Done writing ...
> > > > > > Wrote state file last_block_num1=693 last_block_num2=0
> > > > > > 
> > > > > > -------------------------------
> > > > > > With the above btape error, a kernel error is also presented:
> > > > > > -------------------------------
> > > > > > Apr  1 10:39:42 debian kernel: ata2.00: qc timeout (cmd 0xa0)
> > > > > > Apr  1 10:39:42 debian kernel: ata2.00: exception Emask 0x0 SAct 
0x0
> > > > > > SErr 0x0 action 0x2 frozen
> > > > > > Apr  1 10:39:42 debian kernel: ata2.00: (BMDMA stat 0x20)
> > > > > > Apr  1 10:39:42 debian kernel: ata2.00: tag 0 cmd 0xa0 Emask 0x5 
stat
> > > > > > 0x51 err 0x51 (timeout)
> > > > > > Apr  1 10:39:49 debian kernel: ata2: port is slow to respond, 
please 
> > be
> > > > > > patient
> > > > > > Apr  1 10:40:12 debian kernel: ata2: port failed to respond (30 
secs)
> > > > > > Apr  1 10:40:12 debian kernel: ata2: soft resetting port
> > > > > > Apr  1 10:40:13 debian kernel: ata2: SATA link up 1.5 Gbps 
(SStatus 
> > 113
> > > > > > SControl 300)
> > > > > > Apr  1 10:40:13 debian kernel: ata2.00: configured for UDMA/133
> > > > > > Apr  1 10:40:13 debian kernel: ata2: EH complete
> > > > > > Apr  1 10:40:13 debian kernel: st0: Current [descriptor]: sense 
key:
> > > > > > Medium Error
> > > > > > Apr  1 10:40:13 debian kernel:     Additional sense: Address mark 
not
> > > > > > found for data field
> > > > > > Apr  1 10:40:13 debian kernel: Descriptor sense data with sense
> > > > > > descriptors (in hex):
> > > > > > Apr  1 10:40:13 debian kernel:         72 03 13 00 00 00 00 0e 09 
0e 
> > 00
> > > > > > 51 00 03 00 00 
> > > > > > Apr  1 10:40:13 debian kernel:         00 00 00 00 a0 51 
> > > > > > Apr  1 10:40:25 debian kernel: st0: Current: sense key: Unit 
Attention
> > > > > > Apr  1 10:40:25 debian kernel:     Additional sense: Scsi bus 
reset
> > > > > > occurred
> > > > > > Apr  1 10:41:08 debian kernel: ata2.00: qc timeout (cmd 0xa0)
> > > > > > Apr  1 10:41:08 debian kernel: ata2.00: exception Emask 0x0 SAct 
0x0
> > > > > > SErr 0x0 action 0x2 frozen
> > > > > > Apr  1 10:41:08 debian kernel: ata2.00: (BMDMA stat 0x20)
> > > > > > Apr  1 10:41:08 debian kernel: ata2.00: tag 0 cmd 0xa0 Emask 0x5 
stat
> > > > > > 0x51 err 0x51 (timeout)
> > > > > > Apr  1 10:41:15 debian kernel: ata2: port is slow to respond, 
please 
> > be
> > > > > > patient
> > > > > > Apr  1 10:41:39 debian kernel: ata2: port failed to respond (30 
secs)
> > > > > > Apr  1 10:41:39 debian kernel: ata2: soft resetting port
> > > > > > Apr  1 10:41:39 debian kernel: ata2: SATA link up 1.5 Gbps 
(SStatus 
> > 113
> > > > > > SControl 300)
> > > > > > Apr  1 10:41:39 debian kernel: ata2.00: configured for UDMA/133
> > > > > > Apr  1 10:41:39 debian kernel: ata2: EH complete
> > > > > > Apr  1 10:41:39 debian kernel: st0: Current [descriptor]: sense 
key:
> > > > > > Medium Error
> > > > > > Apr  1 10:41:39 debian kernel:     Additional sense: Address mark 
not
> > > > > > found for data field
> > > > > > Apr  1 10:41:39 debian kernel: Descriptor sense data with sense
> > > > > > descriptors (in hex):
> > > > > > Apr  1 10:41:39 debian kernel:         72 03 13 00 00 00 00 0e 09 
0e 
> > 00
> > > > > > 51 00 03 00 00 
> > > > > > Apr  1 10:41:39 debian kernel:         00 00 00 00 a0 51 
> > > > > > 
> > > > > > I tried appending  "irqpoll acpi=noirq" to see wether it is a 
kernel
> > > > > > problem, but that didn't make any difference. As writing seems to 
> > work,
> > > > > > I guess it is not a kernel problem.
> > > > > > 
> > > > > > -- 
> > > > > > Regards,
> > > > > > 
> > > > > > Sebastiaan
> > > > > > 
> > > > > > 
> > > > > 
> > 
> -------------------------------------------------------------------------
> > > > > > Take Surveys. Earn Cash. Influence the Future of IT
> > > > > > Join SourceForge.net's Techsay panel and you'll get the chance to 
> > share 
> > > > your
> > > > > > opinions on IT & business topics through brief surveys-and earn 
cash
> > > > > > 
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > > > > > _______________________________________________
> > > > > > Bacula-users mailing list
> > > > > > Bacula-users@lists.sourceforge.net
> > > > > > https://lists.sourceforge.net/lists/listinfo/bacula-users
> > > > > -- 
> > > > > Met vriendelijke groeten,
> > > > > 
> > > > > Sebastiaan Veldhuisen
> > > > > Arsenso B.V.
> > > > > Europalaan 16
> > > > > 2408 BG Alphen aan den Rijn
> > > > > T: 0172-49 14 16
> > > > > F: 0712-49 14 04
> > > > > E: [EMAIL PROTECTED]
> > > > > 
> > > > > 
> > > > 
> > 
> -------------------------------------------------------------------------
> > > > > Take Surveys. Earn Cash. Influence the Future of IT
> > > > > Join SourceForge.net's Techsay panel and you'll get the chance to 
share 
> > your
> > > > > opinions on IT & business topics through brief surveys-and earn cash
> > > > > 
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > > > > _______________________________________________
> > > > > Bacula-users mailing list
> > > > > Bacula-users@lists.sourceforge.net
> > > > > https://lists.sourceforge.net/lists/listinfo/bacula-users
> > > > > 
> > > -- 
> > > Met vriendelijke groeten,
> > > 
> > > Sebastiaan Veldhuisen
> > > Arsenso B.V.
> > > Europalaan 16
> > > 2408 BG Alphen aan den Rijn
> > > T: 0172-49 14 16
> > > F: 0712-49 14 04
> > > E: [EMAIL PROTECTED]
> > > 
> > > 
> > 
> -------------------------------------------------------------------------
> > > Take Surveys. Earn Cash. Influence the Future of IT
> > > Join SourceForge.net's Techsay panel and you'll get the chance to share 
your
> > > opinions on IT & business topics through brief surveys-and earn cash
> > > 
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > > _______________________________________________
> > > Bacula-users mailing list
> > > Bacula-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bacula-users
> > > 
> -- 
> Met vriendelijke groeten,
> 
> Sebastiaan Veldhuisen
> Arsenso B.V.
> Europalaan 16
> 2408 BG Alphen aan den Rijn
> T: 0172-49 14 16
> F: 0712-49 14 04
> E: [EMAIL PROTECTED]
> 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to