I have an ORB disk as well, and as you can see below, it is correctly
detected as a removable disk, along with my Jazz disk.
The only problem I have with my ORB disk is that if the drive
spins-down, any further attempt to access the disk fails, unless the
drive is unmounted and mounted again (according to Castlewood, they're
working on it... whatever - I wonder if I can make it an automount
device...).
The SCSI driver is compiled into the Kernel (not a module).
As far as I know, I didn't do anything special to use the drive.
..John
Linux version 2.2.16-9mdk (root@whitestar) (gcc version 2.95.3 19991030
(prerelease)) #2 Mon Jul 3 17:18:08 EDT 2000
[...]
scsi-ncr53c7,8xx : at PCI bus 0, device 10, function 0
scsi-ncr53c7,8xx : warning : revision of 35 is greater than 2.
scsi-ncr53c7,8xx : NCR53c810 at memory 0xd5000000, io 0xb800, irq 5
scsi0 : burst length 16
scsi0 : NCR code relocated to 0x7ae0610 (virt 0xc7ae0610)
scsi0 : test 1 started
scsi0 : NCR53c{7,8}xx (rel 17)
scsi : 1 host.
scsi0 : target 3 accepting asynchronous SCSI
scsi0 : setting target 3 to asynchronous SCSI
Vendor: iomega Model: jaz 1GB Rev: J^77
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi removable disk sda at scsi0, channel 0, id 3, lun 0
scsi0 : target 6 accepting asynchronous SCSI
scsi0 : setting target 6 to asynchronous SCSI
Vendor: CWS ORB2 Model: -SE U ID 6 Rev: D20
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi removable disk sdb at scsi0, channel 0, id 6, lun 0
scsi : detected 2 SCSI disks total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 2091050 [1021 MB] [1.0
GB]
sda: Write Protect is off
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 4307184 [2103 MB] [2.1
GB]
sdb: Write Protect is off
".sig" wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have a SCSI castlewood ORB drive connected internally to an adaptec 2940
> UW. It works fine under windows as a Removeable SCSI device, but under
> linux it only works as a fixed drive. If the system is started with out a
> disk in the drive, the boot sequence gives:
>
> (scsi0:0:6:0) Synchronous at 10.0 Mbyte/sec, offset 8.
> Vendor: CWS Model: _SI I ID 6 Rev: D33
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi removabel disk sdc at scsi0, channel 0, id 6, lin0
> scsi: aborting command due to timeout: pid 42, scsi0, channel 0, id6, lun0
> Read Capacity 00 00 00 00 00 00 00 00
> scsi: aborting command due to timeout: pid 42, scsi0, channel 0, id6, lun0
> Read Capacity 00 00 00 00 00 00 00 00
> SCSI host 0 aboart (pid 42) timed out-reseting
> SCSI bus is beig reset for host 0 channel 0
> SCSI host 0 aboart (pid 42) timed out-reseting
> SCSI bus is beig reset for host 0 channel 0
> SCSI host 0 aboart (pid 42) timed out-reseting
> SCSI bus is beig reset for host 0 channel 0
> SCSI host 0 aboart (pid 42) timed out-reseting
> SCSI bus is beig reset for host 0 channel 0
> SCSI host 0 aboart (pid 42) timed out-reseting
> SCSI bus is beig reset for host 0 channel 0
> Probably an unrecoverable SCSI bus or device hang.
> (scsi0:0:6:0) Synchronous at 10.0 Mbyte/sec, offset 8.
>
> and then the machine hangs. If a disk is present on boot up the disk is
> detected correctly:
>
> (scsi0:0:6:0) Synchronous at 10.0 Mbyte/sec, offset 8.
> Vendor: CWS ORB2 Model: -SI U ID 6 Rev: D33
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi removable disk sdc at scsi0, channel 0, id 6, lun 0
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 8895370 [4343 MB] [4.3
> GB]
> sda: sda1 sda2
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 17916240 [8748 MB] [8.7
> GB]
> sdb: sdb1
> SCSI device sdc: hdwr sector= 512 bytes. Sectors= 4307184 [2103 MB] [2.1
> GB]
> sdc: Write Protect is off
> sdc: sdc1 < sdc5 >
>
> and the disk sdc5 works fine as a fixed drive. When the disk is ejected,
> the machine starts hitting the SCSI bus real hard and grinds the system to
> a halt.
>
> The device is an Ultra Wide scsi device connected to an adaptec 2940UW,
> internally. The linux kernel version is 2.2.16. There is a bit in the
> orb's firmware that toggels between fixed mode and removeable mode. I
> set the bit to removeable, and windows accepts it as a removeable
> drive, but linux does not. Does anyone have any ideas as to why the scsi
> drivers get upset over having an empty removeable Orb drive?
>
> thanks
>
> - ---
> cya
> .sig
>
> Aaron VanDevender
> (.sig (DOT), [EMAIL PROTECTED], [EMAIL PROTECTED])
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP for Personal Privacy 5.0
> Charset: noconv
>
> iQA/AwUBOWYPzUzrqJsFu33/EQL2CACeMAiuwWT6/aOGgdPad1Aa+SdiVQIAoM8y
> 0c719oQdTaWLyJ4d4oVoAXVe
> =rBOc
> -----END PGP SIGNATURE-----
>
> -
> 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]
