OK, Im confused.
As far as I can tell, all of the 'diagnostics' I can run LIE about where
a USB memory device is going to be found on the SCSI bus, or at best are
inconsistant.
This appears to be (mainly) a problem when you have multiple USB devices
that get plugged and unplugged (I have a 256Mb memory Key and a 20GB disk).
The results I see from diagnostics are dependant on whether
'cdrecord -scanbus' has previously 'seen' my REAL scsi cd-writer (sigh).
Here is an example.
If I HAVENT run cdrecord -scanbus previously, then the first memory device
I connect becomes sda1 and the second sdb1. But which is which depends on
the order thiat I first use them. At this point cdrecord -scanbus will NEVER
detect the SCSI CD-writer.
If I have previously run 'cdrecord -scanbus' (before inserting nay usb memory
device) so it has 'seen' the scsi cd-record device.
I now plug in once USB memory device, then unplug it.
I then plug in the OTHER USB memory device and unplug it.
I can repeat these last two steps several times, with no additional changes.
I now run 'cdrecord -scanbus, and get the following:
cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jvrg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
scsibus0:
0,0,0 0) *
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) 'HP ' 'CD-Writer+ 9600 ' '1.0a' Removable CD-ROM
0,6,0 6) *
0,7,0 7) *
scsibus1:
1,0,0 100) ' ' 'USB DISK ' '2.08' Removable Disk
1,1,0 101) *
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
scsibus2:
2,0,0 200) '' '' '' Removable not present Disk
2,1,0 201) *
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) *
If I had NOT run cdrecord -scanbus before connecting the USB memory device,
then the (real) CD-writer would not appear, and the two other sets of data
would be 'down one scsibus' form where they are now.
I would interpret this to say that my (real scsi) cd-writer is on sda5 (it is),
the USB Disk is on sdb1 (a 20 GB disk) while the USBKEY (256MB) is on
sdc1 (but its not currently connected.
looking at /proc/scsi/scsi I see:
[reg@orion scsi]$ more scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: HP Model: CD-Writer+ 9600 Rev: 1.0a
Type: CD-ROM ANSI SCSI revision: 04
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Model: USB DISK Rev: 2.08
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: IC25N020 Model: ATCS04-0 Rev: CA2O
Type: Direct-Access ANSI SCSI revision: 02
[reg@orion scsi]$
which can be interpreted the samy way channel 0/1/2 -> sda/sdb/sdc
[ note that if I hadnt run cdrecord -scanbus before connecting the usbmemory
devices, the first three lines for the CD-Recorder would not be there ]
---
Wrong.
If I try to MOUNT the /dev/sdb1 device when it is connected, I get an
error. I have to mount IT from /dev/sda1.
If I try to MOUNT the /dev/sdc1 device when it is connected, I get an
error. I have to mount IT from /dev/sdb1.
This is kernel 2.4.19, and I am NOT running devfs (would that help?)
and dont see anything over in /dev to help.
Ive looked at /proc/bus/usb, but dont see anything there that would
tell me anything about how these devices are connected to SCSI device
names.
--
So, what gives?
Is this a kernel or software error that is corrected someplace after
RH7.3 and Kernel 2.4.19???
I have to set these things up so that some folks that are NOT Unix
experts can USE THEM. Telling them to do a series of mounts till
one works is not acceptable.
other than a for loop on sda1, sdb1, sdc1, ... I dont see how to tell
what is going on since the /proc/scsi stuff is wrong (Ill assume
that the cdrecord info is just reformating of the /proc/scsi info)/
---
I think I saw a similar question (but in less detail) a few weeks ago,
but didnt see any answer.
Reg.Clemens
[EMAIL PROTECTED]
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
