Re: [SLE] /dev/sda1 usb flash memory

From: steve-ss (mail_at_steve-ss.com)
Date: 08/15/04

  • Next message: Curtis Rey: "Re: [SLE] Microsoft sings a new tune on Linux" 
    To: suse-linux-e@suse.com
Date: Sun, 15 Aug 2004 21:19:45 +0200

    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. 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Curtis Rey: "Re: [SLE] Microsoft sings a new tune on Linux"

    Relevant Pages

    • Re: question re list
      ... >> stumped when lines kept disappearing and then reappearing from fstab. ... >> I can mount manually, which is fine, I guess. ... so why not a camera. ... Do not usb devices automount on your machine? ...
      (Fedora)
    • Re: [SLE] fstab entry info needed
      ... have to do to mount, etc., your USB floppy drive. ... > This is not a matter of idle curiosity; I want to make an entry to an fstab ... > fstab and found an entry for the floppy drive. ...
      (SuSE)
    • Re: How to set /etc/fstab again after system has started
      ... have to supply to the mount command to get it to complete the ... With an appropriate entry in fstab, it takes very little, ... Well, with the system I'm using, I plug in an MP3 player and an icon ...
      (comp.os.linux.misc)
    • Re: Newbie question....Copy Command...
      ... different mount command? ... You have to set it up in fstab for that. ... to set up a cdrom to mount on boot, since that's a drive you want to ... People often think they need an entry in fstab in order to use mount. ...
      (comp.os.linux.misc)
    • Re: How to set /etc/fstab again after system has started
      ... have to supply to the mount command to get it to complete the ... With an appropriate entry in fstab, it takes very little, ... Well, with the system I'm using, I plug in an MP3 player and an icon ...
      (comp.os.linux.misc)