OnStream B.V. claim:
ADR50 is Certified for Linux!
50GB compressed capacity
Up to 4MB/sec transfer rate with hardware
data compression
SCSI-3 LVD/SE interface
Works with standard Linux SCSI driver
Compatible with most server backup
applications for Linux
(Please check out compatibility chart for current and updated
software product certification)
ADR50 product information
Read the press release
(see ref. http://www.onstream.com/support/linux/index.html)
Return defective unit to where you sold it.
Regards,
/Karl
-----------------------------------------------------------------------
Karl Hammar Asp� Data [EMAIL PROTECTED]
Lilla Asp� 2340 +46 173 140 57
S-742 94 �sthammar Unix for the small company
Sweden +46 70 511 97 84 (mobile)
-----------------------------------------------------------------------
From: Tom Sedge <[EMAIL PROTECTED]>
Subject: SCSI write errors with Onstream ADR50 drive
Date: Mon, 3 Apr 2000 15:50:30 +0100 (BST)
> Hi,
>
> We've installed a new Onstream ADR50 drive (SCSI Ultra 3 LVD bus). It is
> sitting in a machine with the following spec:
>
> ASUS P2DS motherboard
> 2 x Dual PII 400Mhz
> 384RAM
> Onboard Adaptec 2940U2W SCSI Ultra 3 LVD bus
> 1 x Seagate Cheeta 9.1Gb SCSI drive
> 3 x Seagate Cheeta 18.2Gb SCSI drives
> D-link DFE530TX 10/100 Ethernet PCI
> RedHat Linux 6.1 patched to kernel 2.2.13 + ac3 (SMP).
> Software raid 5 across the 3 18.2Gb drives (not the boot drive)
>
> The drive is properly recognised and reported on startup, and assigned to
> /dev/st0.
>
> All is well until we try reading or writing to a tape. The drive starts
> to show write/read behaviour and then nothing happens for a minute or so
> until a large number of SCSI write errors are reported by the kernel. At
> this point the SCSI bus seems to go bananas an the hard drive light goes
> fully on. The machine then stops responding and a reset is needed (to
> reset the SCSI bus). After coming back up the machine is fine, and no
> problems occur unless we try accessing the drive. Nothing is logged in
> the system logs and there are no 'oopses'.
>
> We've checked for SCSI Id conflicts and termination of the bus. Both seem
> to be ok. Could this be an SMP problem? The addition of the ADR drive is
> the only change to this machine recently.
>
> If anyone can help, I'd be most grateful.
>
> Best Regards,
>
>
> Tom.
> --
> Cognality Ltd. [EMAIL PROTECTED] Where dreams become reality....
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
