Re: [SLE] /dev/sda1 usb flash memory
From: Kastus (NOSPAM_at_tprfct.net)
Date: Sun, 15 Aug 2004 10:40:37 -0700 To: email@example.com
On Sun, Aug 15, 2004 at 11:13:44AM +0200, steve-ss wrote:
> My camera flash card has an fstab entry like this:
> /dev/sda1 /media/sda1 auto sync,noauto,user,exec 0 0
> #HOTPLUG 4t_9.GdvU0fSB2R0
fstab entry doesn't mean that file system is mounted.
> I get this error when trying to access it:
> Could not enter
> folder /media/usb-storage-000000000002:0:0:0p1
As you see, mount point is different from entry in fstab.
Generally, you don't need an entry in fstab for the camera on 9.1,
the mount point is created dynamically by hotplug.
Are you using standard 9.1 hotplug or did you disable subfs?
If it's standard unchanged hotplug, then after connecting your camera
you should see something like this in your /var/log/messages:
(I'm using latest updates from YOU, hotplug-0.44-32.22 and submount-0.9-33.6)
Aug 15 10:13:14 fizia kernel: usb 1-2.1: new full speed USB device using address 6
Aug 15 10:13:15 fizia kernel: usb 1-2.1: Product: C5050Z
Aug 15 10:13:15 fizia kernel: usb 1-2.1: Manufacturer: OLYMPUS
Aug 15 10:13:15 fizia kernel: usb 1-2.1: SerialNumber: 000242727020
Aug 15 10:13:15 fizia kernel: scsi3 : SCSI emulation for USB Mass Storage devices
Aug 15 10:13:15 fizia kernel: Vendor: OLYMPUS Model: C5050Z Rev: 1.00
Aug 15 10:13:15 fizia kernel: Type: Direct-Access ANSI SCSI revision: 02
Aug 15 10:13:15 fizia kernel: SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
Aug 15 10:13:15 fizia kernel: sda: assuming Write Enabled
Aug 15 10:13:15 fizia kernel: sda: assuming drive cache: write through
Aug 15 10:13:15 fizia /etc/hotplug/usb.agent: need a device for this command
Aug 15 10:13:15 fizia /etc/hotplug/block.agent: try 1 while waiting for /block/sda's bus_id 3:0:
Aug 15 10:13:15 fizia kernel: sda: sda1
Aug 15 10:13:15 fizia kernel: Attached scsi removable disk sda at scsi3, channel 0, id 0, lun 0
Aug 15 10:13:15 fizia kernel: Attached scsi generic sg0 at scsi3, channel 0, id 0, lun 0, type 0
Aug 15 10:13:15 fizia kernel: USB Mass Storage device found at 6
Aug 15 10:13:16 fizia /etc/hotplug/block.agent: new block device /block/sda/sda1
Aug 15 10:13:16 fizia /etc/hotplug/block.agent: waiting for /var/lock/block.agent.lock, process
7974 holds it
Aug 15 10:13:21 fizia /etc/hotplug/block.agent: mount by-path/usb-storage-000242727020:0:0:0p1
Aug 15 10:13:21 fizia /etc/hotplug/block.agent: new block device /block/sda
Mount command should now report your camera mounted at a dynamically created mount point:
/dev/sda1 on /media/usb-storage-000242727020:0:0:0p1 type subfs (rw,noexec,nosuid,nodev,sync,procuid,iocharset=utf8)
The directory name will be different in your case, most probably it will be
If you cannot access your camera at this point (try something like
ls -l /media/usb-storage-000000000002\:0\:0\:0p1) and it's reported as mounted,
then for diagnosing purposes unmount it manually with command:
and then mount it manually:
mount -t vfat /dev/sda1 /media/usb-storage-000000000002\:0\:0\:0p1
If you can access it after that, then it means some problem with subfs/submountd.
If not, the problem is at some other layer.
I don't know if this procedure will help you, at least it provides some guidelines
where to look.
-- (suse-lists at tprfct dot net) -- Check the headers for your unsubscription address For additional commands send e-mail to firstname.lastname@example.org Also check the archives at http://lists.suse.com Please read the FAQs: email@example.com