Hello,
I am trying to use a USB memory stick with F9. When I plug it in, Nautilus shows an unmounted "USB Drive". Double-clicking on causes a "Unable to mount location - Can't mount file" error. Right-clicking and selecting "Mount Volume" appears to do nothing.
I can mount it from the shell with "mount /dev/sdb1 /media/abc -t msdos" (as root).
/var/log/messages excerpt:
Jul 1 08:22:57 localhost kernel: usb 1-6: new high speed USB device using ehci_hcd and address 10 Jul 1 08:22:57 localhost kernel: usb 1-6: configuration #1 chosen from 1 choice Jul 1 08:22:57 localhost kernel: scsi7 : SCSI emulation for USB Mass Storage devices Jul 1 08:22:57 localhost kernel: usb 1-6: New USB device found, idVendor=090c, idProduct=1000 Jul 1 08:22:57 localhost kernel: usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jul 1 08:22:57 localhost kernel: usb 1-6: Product: Flash Voyager Jul 1 08:22:57 localhost kernel: usb 1-6: Manufacturer: Corsair Jul 1 08:22:57 localhost kernel: usb 1-6: SerialNumber: A312000000000303 Jul 1 08:23:02 localhost kernel: scsi 7:0:0:0: Direct-Access Corsair Flash Voyager 1100 PQ: 0 ANSI: 0 CCS Jul 1 08:23:02 localhost kernel: sd 7:0:0:0: [sdb] 15728640 512-byte hardware sectors (8053 MB) Jul 1 08:23:02 localhost kernel: sd 7:0:0:0: [sdb] Write Protect is off Jul 1 08:23:02 localhost kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through Jul 1 08:23:02 localhost kernel: sd 7:0:0:0: [sdb] 15728640 512-byte hardware sectors (8053 MB) Jul 1 08:23:02 localhost kernel: sd 7:0:0:0: [sdb] Write Protect is off Jul 1 08:23:02 localhost kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through Jul 1 08:23:02 localhost kernel: sdb: sdb1 Jul 1 08:23:02 localhost kernel: sd 7:0:0:0: [sdb] Attached SCSI removable disk Jul 1 08:23:02 localhost kernel: sd 7:0:0:0: Attached scsi generic sg2 type 0
Any ideas? Worked as expected with F8, though it was a different drive (which I no longer have, so I can't test it).
A reply to my own post with a couple additional details;
> Any ideas? Worked as expected with F8, though it was a different drive
(which I no longer have, so I can't test it).
I tried it on my Ubuntu laptop, it does not work there either. I tried a different brand/model USB drive on F9 and it works fine. Looks like something specific to the Corsair Flash Voyager under linux... :-(
Brian Mury wrote:
Hello,
I am trying to use a USB memory stick with F9. When I plug it in, Nautilus shows an unmounted "USB Drive". Double-clicking on causes a "Unable to mount location - Can't mount file" error. Right-clicking and selecting "Mount Volume" appears to do nothing.
I can mount it from the shell with "mount /dev/sdb1 /media/abc -t msdos" (as root).
It looks from the messages that it is being properly detected, but HAL is not mounting it. While it does not explain the problem, you may be able to get it to mount if you give it a label. For the FAT file system used on most memory sticks, it is easy to do in Windows, but it is a bit complicated to do in Linux.
Mikkel
On Tue, 2008-07-01 at 17:58 -0500, Mikkel L. Ellertson wrote:
It looks from the messages that it is being properly detected, but HAL is not mounting it. While it does not explain the problem, you
lsusb shows it as "Feiya Technology Corp. Memory Bar". Google found this, and some other similar pages:
http://ubuntuforums.org/showthread.php?t=443674&page=2
Unfortunately that fix didn't work for me - the entry in 10-usb-music-players.fdi does not exist.
may be able to get it to mount if you give it a label. For the FAT file system used on most memory sticks, it is easy to do in Windows, but it is a bit complicated to do in Linux.
I tried it in Windows, it appears to already have a label ("CORSAIR").
If I mount it from the shell, as root, it shows up as "8.1 GB Media", no name... and the "USB Drive" is still there and unmountable (that is, there are two separate GNOME icons after mounting).
It is formatted as FAT32, BTW, so that should be ok.
===============================
Ok... This is strange... While writing this email, I was moving the drive back and forth between a Windows and a Fedora box. I mounted it as root, wrote a short text file to it, moved it to Windows, edited the file, moved it back to Fedora and it worked... Tried unplugging/plugging a few tries and it seems fine. Weird.
Brian Mury wrote:
On Tue, 2008-07-01 at 17:58 -0500, Mikkel L. Ellertson wrote:
It looks from the messages that it is being properly detected, but HAL is not mounting it. While it does not explain the problem, you
lsusb shows it as "Feiya Technology Corp. Memory Bar". Google found this, and some other similar pages:
http://ubuntuforums.org/showthread.php?t=443674&page=2
Unfortunately that fix didn't work for me - the entry in 10-usb-music-players.fdi does not exist.
may be able to get it to mount if you give it a label. For the FAT file system used on most memory sticks, it is easy to do in Windows, but it is a bit complicated to do in Linux.
I tried it in Windows, it appears to already have a label ("CORSAIR").
If I mount it from the shell, as root, it shows up as "8.1 GB Media", no name... and the "USB Drive" is still there and unmountable (that is, there are two separate GNOME icons after mounting).
It is formatted as FAT32, BTW, so that should be ok.
===============================
Ok... This is strange... While writing this email, I was moving the drive back and forth between a Windows and a Fedora box. I mounted it as root, wrote a short text file to it, moved it to Windows, edited the file, moved it back to Fedora and it worked... Tried unplugging/plugging a few tries and it seems fine. Weird
So now it mounts as a non-root user? Or was it never unmounted but just yanked from the machine? Sounds like a permissions problem with your mounting as a non-root user.
K
On Wed, 2008-07-02 at 07:43 -0500, Kevin Martin wrote:
So now it mounts as a non-root user?
Yes.
Or was it never unmounted but just yanked from the machine?
No, it was never unplugged without being unmounted.
Sounds like a permissions problem with your mounting as a non-root user.
Possible, but I'm not convinced. Even when mounted as root, I was getting weird errors trying to access it. It works fine now, no permission problems, and I haven't changed a thing.
On Tue, Jul 1, 2008 at 4:41 PM, Brian Mury brianmury@alumni.uvic.ca wrote:
On Tue, 2008-07-01 at 17:58 -0500, Mikkel L. Ellertson wrote:
It looks from the messages that it is being properly detected, but HAL is not mounting it. While it does not explain the problem, you
.......
===============================
Ok... This is strange... While writing this email, I was moving the drive back and forth between a Windows and a Fedora box. I mounted it as root, wrote a short text file to it, moved it to Windows, edited the file, moved it back to Fedora and it worked... Tried unplugging/plugging a few tries and it seems fine. Weird.
I have seen this as well.
What I suspect is that the interactions as root establish the correct mount flags for the device. Then at a future time a user can mount it because the config established by root is the configuration needed for the daemon to mount the device later.
There has been a lot of attention to company data theft via USB devices. It may be that you are seeing interactions with a policy framework intended to address this.
Do look for and at /media/.hal-mtab
Since it is a "one time only problem" it will take some care to file a productive bug with a test case, instructions to reproduce etc.
-- NiftyFedora T o m M i t c h e l l
-
Brian Mury -
Kevin Martin -
Mikkel -
Nifty Fedora Mitch