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 I get this error when trying to access it: Could not enter folder /media/usb-storage-000000000002:0:0:0p1 Can anyone help? Thanks, Steve. 9.1
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[7887]: need a device for this command Aug 15 10:13:15 fizia /etc/hotplug/block.agent[7950]: try 1 while waiting for /block/sda's bus_id 3:0: 0: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[7974]: new block device /block/sda/sda1 Aug 15 10:13:16 fizia /etc/hotplug/block.agent[7950]: waiting for /var/lock/block.agent.lock, process 7974 holds it Aug 15 10:13:21 fizia /etc/hotplug/block.agent[7974]: mount by-path/usb-storage-000242727020:0:0:0p1 Aug 15 10:13:21 fizia /etc/hotplug/block.agent[7950]: new block device /block/sda Mount command should now report your camera mounted at a dynamically created mount point: mount /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 /media/usb-storage-000000000002:0:0:0p1 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: umount /media/usb-storage-000000000002\:0\:0\:0p1 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. Regards, -Kastus -- (suse-lists at tprfct dot net)
On Sunday 15 August 2004 19:40, Kastus wrote:
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[7887]: need a device for this command Aug 15 10:13:15 fizia /etc/hotplug/block.agent[7950]: try 1 while waiting for /block/sda's bus_id 3:0: 0: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[7974]: new block device /block/sda/sda1 Aug 15 10:13:16 fizia /etc/hotplug/block.agent[7950]: waiting for /var/lock/block.agent.lock, process 7974 holds it Aug 15 10:13:21 fizia /etc/hotplug/block.agent[7974]: mount by-path/usb-storage-000242727020:0:0:0p1 Aug 15 10:13:21 fizia /etc/hotplug/block.agent[7950]: new block device /block/sda
Mount command should now report your camera mounted at a dynamically created mount point:
mount
/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 /media/usb-storage-000000000002:0:0:0p1
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:
umount /media/usb-storage-000000000002\:0\:0\:0p1
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.
Regards, -Kastus -- (suse-lists at tprfct dot net)
Hi. Thanks. I can mount it manually no problem. So from what I understand then I should simply delete the entry from fstab no? THanks again, Steve.
On Sun, Aug 15, 2004 at 09:19:45PM +0200, steve-ss wrote:
Hi. Thanks. I can mount it manually no problem. So from what I understand then I should simply delete the entry from fstab no?
Yes, please try without that entry in /etc/fstab. The new mount point should appear automatically after connecting the camera with file system type subfs. Then subfs does its magic when you access files below that mount point. Regards, -Kastus
participants (2)
-
Kastus
-
steve-ss