USB Storage with 9.1?

From: Oliver Cromwell (cromwell.nospam_at_arcor.de)
Date: 05/31/04 

Date: Mon, 31 May 2004 19:45:37 +0200

Hi!

I have a card-reader for various types of Cards (CF, SD, etc...) It connects
via USB.

Under 9.0 it was simple: One slot was address as /dev/sda1, the other as
sdb1. There were mounted to whereever I wanted them to be mounted, and
hotplug wrote also an entry into the /etc/fstab file.

Having upgraded to 9.1 it seems to be difficult.

I can't access the cards like I did before. According to /var/log/messages
it recognizes the card-reader, but still I can't mount it...

Messages says:

May 31 17:57:20 durkheim kernel: usb 1-1: new full speed USB device using
address 5
May 31 17:57:20 durkheim kernel: usb 1-1: Product: eUSB ORCA Quad Reader
May 31 17:57:20 durkheim kernel: usb 1-1: Manufacturer: SCM Microsystems
Inc.
May 31 17:57:20 durkheim kernel: usb 1-1: SerialNumber: 00000000002D
May 31 17:57:20 durkheim kernel: scsi2 : SCSI emulation for USB Mass Storage
devices
May 31 17:57:20 durkheim kernel: Vendor: eUSB Model: Compact Flash
Rev: 5.07
May 31 17:57:20 durkheim kernel: Type: Direct-Access
ANSI SCSI revision: 02
May 31 17:57:20 durkheim /etc/hotplug/usb.agent[16005]: need a device for
this command
May 31 17:57:21 durkheim kernel: SCSI device sda: 500736 512-byte hdwr
sectors (256 MB)
May 31 17:57:21 durkheim kernel: sda: assuming Write Enabled
May 31 17:57:21 durkheim kernel: sda: assuming drive cache: write through
May 31 17:57:21 durkheim kernel: sda:
May 31 17:57:21 durkheim kernel: Attached scsi removable disk sda at scsi2,
channel 0, id 0, lun 0
May 31 17:57:21 durkheim kernel: Attached scsi generic sg0 at scsi2, channel
0, id 0, lun 0, type 0
May 31 17:57:21 durkheim kernel: Vendor: eUSB Model: SD-MS-SM
Rev: 5.07
May 31 17:57:21 durkheim kernel: Type: Direct-Access
ANSI SCSI revision: 02
May 31 17:57:22 durkheim /etc/hotplug/block.agent[16072]: new block
device /block/sda
May 31 17:57:23 durkheim kernel: SCSI device sdb: 121856 512-byte hdwr
sectors (62 MB)
May 31 17:57:23 durkheim kernel: sdb: assuming Write Enabled
May 31 17:57:23 durkheim kernel: sdb: assuming drive cache: write through
May 31 17:57:23 durkheim kernel: sdb:
May 31 17:57:23 durkheim kernel: Attached scsi removable disk sdb at scsi2,
channel 0, id 0, lun 1
May 31 17:57:23 durkheim kernel: Attached scsi generic sg1 at scsi2, channel
0, id 0, lun 1, type 0
May 31 17:57:23 durkheim kernel: USB Mass Storage device found at 5
May 31 17:57:24 durkheim /etc/hotplug/block.agent[16210]: waiting
for /var/lock/block.agent.lock, process 16072 holds it
May 31 17:57:33 durkheim /etc/hotplug/block.agent[16210]: new block
device /block/sdb

Can anybody help? How has this changed since 9.0?

Thanks!

Relevant Pages

  • 2.6.17 Panic
    ... we've had these same type panics using ... SCSI device sda: 286492672 512-byte hdwr sectors ... sda: assuming drive cache: write through ... SCSI device sdb: 1171431424 512-byte hdwr sectors ...
    (Linux-Kernel)
  • Re: RHEL4 - Boot hangs
    ... sda: assuming drive cache: write through ... sdb: assuming drive cache: write through ... I also tried booting to a previous version via grub ...
    (RedHat)
  • [2.6.13-rc6-latest] SCSI disk registration msgs repeat themselves
    ... I just added some usb-storage devices to my system and got the below. ... sda: assuming drive cache: write through ... sdb: assuming drive cache: write through ...
    (Linux-Kernel)
  • SCSI "asking for cache data failed"
    ... | sda: assuming drive cache: write through ... I'm wondering WHY can't the caching mode cannot be obtained by the kernel? ... disk, and the sda and sdb it sees are actually logical drives, and the ...
    (Linux-Kernel)
  • RHEL4 - Boot hangs
    ... sda: assuming drive cache: write through ... sdb: assuming drive cache: write through ... jared davis. ...
    (RedHat)