The HBA is :
Hewlett Packard 64-bit/133MHz dual channel ultra320 SCSI Adapter
From the dmesg:
scsi3 : ioc0: LSI53C1030, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=20
ata2.00: configured for UDMA/33
scsi: waiting for bus probes to complete ...
scsi 3:0:4:0: Sequential-Access HP Ultrium 3-SCSI D22W PQ: 0 ANSI: 3
target3:0:4: Beginning Domain Validation
target3:0:4: Ending Domain Validation
target3:0:4: FAST-160 WIDE SCSI 320.0 MB/s DT IU RTI PCOMP (6.25 ns, offset 64)
scsi 3:0:4:1: Medium Changer HP 1x8 G2 AUTOLDR 1.70 PQ: 0 ANSI: 5
From lspci:
03:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)
My OS is:
Debian Sarge Kernel 2.6.22-3-686
The SCSI card is from Hewlett Packard, but the chipset is LSI. I think i did not install any drivers for it as the OS auto detects the card. Could it be the problem??
On Wed, Sep 10, 2008 at 3:20 PM, Arno Lehmann
<al AT its-lehmann DOT de> wrote:
Hi,
10.09.2008 07:04, Danz Aurora wrote:
> Hi.. my vendor came down and have a look, he says its the compatibility
> issue between the Linux OS (unsupported by HP) and the Hp scsi card..
This leaves you with some options:
- switch the OS to one HP supports (they usually support SLES, RH, and
debian)
- use another SCSI HBA
- compile the driver (version) a supported linux would use for your
current kernel (maintenance nightmare ahead!)
> how can i really verify that without having a change of OS? i installed
> LTT tool from HP and ran the test, it works fine with no errors.. can
> someone advise if it is bacula's problem or OS or hardware problem?
This is most probably not a Bacula problem, as Bacula relies on the
underlying OS services when it comes to device access.
If HP does not support the combination of OS and hardware there can be
good reasons for it. (Although I'm running some unsupported
combinations as well, without issues.) However, if you told us which
OS and HBA you use someone here might have an idea.
Arno
--
