Bug 148032
| Summary: | Fails to automatically mount usb storage stick. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John-M <jmdharkness> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | CC: | michaelkofler, pfrields |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-10-03 00:18:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
John-M
2005-02-15 00:18:08 UTC
Assigning to kernel. I'm having what appears to be the same problem wih my lexar jumpdrive. Before a fresh install, it would be automatically mounted as /media/LEXAR_MEDIA and an icon would appear on the gnome desktop. Now, I can mount it manually, but it does not automount. It doesn't seem to work for either kernel-2.6.9-1.667 or kernel-2.6.10-1.770_FC3. My kernel before the fresh install (partition magic crashed, and with it, the MBR) was, I think, kernel-2.6.9-1.760 (at which time automounting worked). Also: Do I need to submit a new bug, or is my problem the same one as above? Thanks! IT also fails to notice my usb printer when i turn it on (like it used to) I got my usb jump drive to mount automatically by creating a directory /media/diskonkey and adding a line to /etc/fstab: /dev/sda1 /media/diskonkey vfat rw,user,exec,auto,sync,managed 0 0 Note the 'managed' there on the end. In the past, hotplug, or hal, or updfstab, or gnome-volume-control, or whichever one is in charge of automounting these days, would automatically create the entry, the directory, etc. I'm not at home, so I don't know if the same work around will automount the printer - I'll post again with those results later. Never mind about the printer - that was something I forgot to do. It's just the usb drive problem. New linux user here - this was the first bug I ran into (after two weeks - I love this OS). Anyway, when I plug my Kingston DataTraveler memory stick into the usb slot, automount works perfectly (icon appears in "Computer" alongside filesystem, cddrive, etc.) - but only the first time I use it. If I umount (via the GUI), take the stick out, and plug it back in, the automount fails to re- detect the drive. Anyway, here's the dmesg dump for the original mount, subsequent dismount, and failed second mount: *********************** usb 1-3: new high speed USB device using ehci_hcd and address 3 SCSI subsystem initialized Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning usbcore: registered new driver usb-storage USB Mass Storage support registered. Vendor: Kingston Model: DataTraveler 2.0 Rev: 6.00 Type: Direct-Access ANSI SCSI revision: 02 usb-storage: device scan complete SCSI device sda: 1001472 512-byte hdwr sectors (513 MB) sda: Write Protect is off sda: Mode Sense: 0b 00 00 08 sda: assuming drive cache: write through SCSI device sda: 1001472 512-byte hdwr sectors (513 MB) sda: Write Protect is off sda: Mode Sense: 0b 00 00 08 sda: assuming drive cache: write through sda: sda1 Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 SELinux: initialized (dev sda1, type vfat), uses genfs_contexts *************************************************** usb 1-3: USB disconnect, address 3 *************************************************** usb 1-3: new high speed USB device using ehci_hcd and address 4 scsi1 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning Vendor: Kingston Model: DataTraveler 2.0 Rev: 6.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 1001472 512-byte hdwr sectors (513 MB) sda: Write Protect is off sda: Mode Sense: 0b 00 00 08 sda: assuming drive cache: write through SCSI device sda: 1001472 512-byte hdwr sectors (513 MB) sda: Write Protect is off sda: Mode Sense: 0b 00 00 08 sda: assuming drive cache: write through sda: sda1 Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0 usb-storage: device scan complete Thanks for looking into this! An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. This bug has been automatically closed as part of a mass update. It had been in NEEDINFO state since July 2005. If this bug still exists in current errata kernels, please reopen this bug. There are a large number of inactive bugs in the database, and this is the only way to purge them. Thank you. |