
Code: Select all
$ lsusb
Bus 003 Device 003: ID 05e3:0760 Genesys Logic, Inc. Card Reader
Bus 003 Device 002: ID 0ea0:2168 Ours Technology, Inc. Transcend JetFlash 2.0 / Astone USB Drive
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Code: Select all
$ cat /var/log/vereything/current
Mar 31 12:31:33 [kernel] usb 3-2: new high speed USB device using ehci_hcd and address 4
Mar 31 12:31:33 [kernel] usb 3-2: Product: Flash Disk
Mar 31 12:31:33 [kernel] usb 3-2: Manufacturer: USB
Mar 31 12:31:33 [kernel] usb 3-2: SerialNumber: 241F1E405AA6619F
Mar 31 12:31:33 [kernel] usb 3-2: configuration #1 chosen from 1 choice
Mar 31 12:31:33 [kernel] scsi2 : SCSI emulation for USB Mass Storage devices
Mar 31 12:31:38 [kernel] scsi 2:0:0:0: Direct-Access VMAX 128MB 2.00 PQ: 0 ANSI: 2
Mar 31 12:31:39 [kernel] ready
Mar 31 12:31:39 [kernel] SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
Mar 31 12:31:39 [kernel] sda: Write Protect is off
Mar 31 12:31:39 [kernel] sda: assuming drive cache: write through
Mar 31 12:31:39 [kernel] SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
Mar 31 12:31:39 [kernel] sda: Write Protect is off
Mar 31 12:31:39 [kernel] sda: assuming drive cache: write through
Mar 31 12:31:39 [kernel] sd 2:0:0:0: Attached scsi removable disk sda
Mar 31 12:31:39 [kernel] sd 2:0:0:0: Attached scsi generic sg1 type 0
Code: Select all
umount: /media/disk-1 is not in the fstab (and you are not root)
I do believe you as I have another KDE machine which unmounts fine without pmount... But I didn't want to pour gas where water is neededalbright wrote:at the risk of muddying the waters, I have no trouble mounting
and unmounting usb sticks/drives etc. and I do NOT have
pmount installed.
I wish I knew which ones...albright wrote:I think there is another problem lurking here (are you sure you
have the right kde services running?).
Look, I like that way as I perceive the current evolution of plugable devices to be independent from fstab. What are the rules that you have changed and what are these changes?janiskr wrote:i changed some udev rules, as result i have mounting and unmounting working very well![]()
dunno if it is good solution but works like a charm
You could run fuser -m <path to the mount point of your USB drive> to see which process uses files on the drive. Typically, used files prevent any mounted filesystem from being dismounted.Bobnoxous wrote:My setup still isn't working quite right, but I've worked around it. When I stick in a USB device, I can see it in rhythmbox, but if I just drag files over, the files get corrupted. I'll start to play a file, and it'll suddenly switch to an old file, as if the complete file didn't get written. Strange. And, I cannot unmount the device in rhythmbox.
But, if I mount the flash manually, remove old files and add new ones, and then unmount it, it works fine, so it only seems to be a problem when it's "mounted" automagically by rhythmbox, or whatever it is that actually handles accessing the device. I just don't know enough of what goes on underneath to troubleshoot this.