External USB disks, camera and GPS device are mounted automatically when plugged in to USB. This works sometimes and sometime it does not work. Trying then to mount manually takes a very long time and often aborts with the message: Can’t mount device. Frequently I need to unplug and plug in again to get the devices mounted.
Linux 3.11.10-21-desktop, openSUSE 13.1 (Bottle) (x86_64), KDE 4.11.5
And which desktop environment are you using?
This type of mounting (what you call “automatic”) is done through the desktop, thus it may matter.
And you also may explain what you do when you “mount manualy”.
On 2014-10-04 21:26, karlmistelberger wrote:
> Linux 3.11.10-21-desktop, openSUSE 13.1 (Bottle) (x86_64), KDE 4.11.5
You have to mount manually with the “-v” switch, and have a look at the
log, for clues.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
erlangen:/home/karl # mount -v /dev/sde7 /mnt/
mount: /dev/sde7 mounted on /mnt.
erlangen:/home/karl #
/var/log/messages has:
2014-10-04T21:41:18.555950+02:00 erlangen kernel: [357140.528448] EXT4-fs (sde7): mounting ext3 file system using the ext4 subsystem
2014-10-04T21:41:18.597364+02:00 erlangen kernel: [357140.569590] EXT4-fs (sde7): mounted filesystem with ordered data mode. Opts: (null)
On 2014-10-04 21:56, karlmistelberger wrote:
> erlangen:/home/karl # mount -v /dev/sde7 /mnt/
> mount: /dev/sde7 mounted on /mnt.
> erlangen:/home/karl #
>
> /var/log/messages has:
> 2014-10-04T21:41:18.555950+02:00 erlangen kernel: [357140.528448]
> EXT4-fs (sde7): mounting ext3 file system using the ext4 subsystem
> 2014-10-04T21:41:18.597364+02:00 erlangen kernel: [357140.569590]
> EXT4-fs (sde7): mounted filesystem with ordered data mode. Opts: (null)
That’s a successful one. We need to see a failed one 
A comment: Next time, when pasting here computer commands and such,
please use a CODE BLOCK, so that the forum software doesn’t do silly
things like converting URLS to tiny urls or otherwise hide or alter the
commands you entered. You get them by clicking on the ‘#’ button in the
forum editor. http://susepaste.org/images/15093674.jpg
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-10-04 21:36, hcvv wrote:
>
> And which desktop environment are you using?
He said: “openSUSE 13.1 (Bottle) (x86_64), KDE 4.11.5”
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Sorry, my fault, Missed that for some reason :shame:
In that case, a pop-up should show shortly after the device is connevted,280 Does that happen?
We realy do not ave much information on what happens and what not.
On Sat 04 Oct 2014 08:23:07 PM CDT, Carlos E. R. wrote:
On 2014-10-04 21:56, karlmistelberger wrote:
> erlangen:/home/karl # mount -v /dev/sde7 /mnt/
> mount: /dev/sde7 mounted on /mnt.
> erlangen:/home/karl #
>
> /var/log/messages has:
> 2014-10-04T21:41:18.555950+02:00 erlangen kernel: [357140.528448]
> EXT4-fs (sde7): mounting ext3 file system using the ext4 subsystem
> 2014-10-04T21:41:18.597364+02:00 erlangen kernel: [357140.569590]
> EXT4-fs (sde7): mounted filesystem with ordered data mode. Opts:
> (null)
That’s a successful one. We need to see a failed one
A comment: Next time, when pasting here computer commands and such,
please use a CODE BLOCK, so that the forum software doesn’t do silly
things like converting URLS to tiny urls or otherwise hide or alter the
commands you entered. You get them by clicking on the ‘#’ button in the
forum editor. SUSE Paste
Hi
I don’t think you will mounting manually as root… as a user it’s
using gvfs/fuse, the op needs to mount as user with fuse tools…
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-21-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On 2014-10-04 22:58, malcolmlewis wrote:
> Hi
> I don’t think you will mounting manually as root… as a user it’s
> using gvfs/fuse, the op needs to mount as user with fuse tools…
Good point.
But it may not matter, if as I guess it is a hardware issue.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Mount is done automatically and devices are displayed in the system tray by the device notifier. I checked /var/log/messages for 'erlangen kernel:
’ and found the following mostly related to USB:
2014-10-04T20:24:28.190559+02:00 erlangen kernel: [352534.139496] EXT4-fs (sde7): mounting ext3 file system using the ext4 subsystem
2014-10-04T20:24:28.244484+02:00 erlangen kernel: [352534.192273] EXT4-fs (sde7): mounted filesystem with ordered data mode. Opts: (null)
2014-10-04T20:24:36.544554+02:00 erlangen kernel: [352542.485823] EXT4-fs (sde6): mounting ext3 file system using the ext4 subsystem
2014-10-04T20:24:36.578841+02:00 erlangen kernel: [352542.520026] EXT4-fs (sde6): mounted filesystem with ordered data mode. Opts: (null)
2014-10-04T20:24:38.325556+02:00 erlangen kernel: [352544.265229] FAT-fs (sde1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
2014-10-04T20:24:47.145712+02:00 erlangen kernel: [352553.077827] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
2014-10-04T20:27:57.730557+02:00 erlangen kernel: [352743.495216] usb 3-13: new high-speed USB device number 27 using xhci_hcd
2014-10-04T20:27:57.742555+02:00 erlangen kernel: [352743.508088] usb 3-13: New USB device found, idVendor=04da, idProduct=2372
2014-10-04T20:27:57.742566+02:00 erlangen kernel: [352743.508092] usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2014-10-04T20:27:57.742567+02:00 erlangen kernel: [352743.508094] usb 3-13: Product: DMC-TZ10
2014-10-04T20:27:57.742568+02:00 erlangen kernel: [352743.508096] usb 3-13: Manufacturer: Panasonic
2014-10-04T20:27:57.742568+02:00 erlangen kernel: [352743.508097] usb 3-13: SerialNumber: 0000000000000000005F1500160556
2014-10-04T20:27:57.743565+02:00 erlangen kernel: [352743.508604] usb-storage 3-13:1.0: USB Mass Storage device detected
2014-10-04T20:27:57.743573+02:00 erlangen kernel: [352743.508634] usb-storage 3-13:1.0: Quirks match for vid 04da pid 2372: 90
2014-10-04T20:27:57.743574+02:00 erlangen kernel: [352743.508657] scsi22 : usb-storage 3-13:1.0
2014-10-04T20:27:58.746393+02:00 erlangen kernel: [352744.510914] scsi 22:0:0:0: Direct-Access MATSHITA DMC-TZ10 0100 PQ: 0 ANSI: 2
2014-10-04T20:27:58.746405+02:00 erlangen kernel: [352744.511067] sd 22:0:0:0: Attached scsi generic sg6 type 0
2014-10-04T20:27:58.747550+02:00 erlangen kernel: [352744.512198] sd 22:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
2014-10-04T20:27:58.747555+02:00 erlangen kernel: [352744.512201] sd 22:0:0:0: [sdf] 32372735 512-byte logical blocks: (16.5 GB/15.4 GiB)
2014-10-04T20:27:58.748551+02:00 erlangen kernel: [352744.512491] sd 22:0:0:0: [sdf] Write Protect is on
2014-10-04T20:27:58.748556+02:00 erlangen kernel: [352744.512493] sd 22:0:0:0: [sdf] Mode Sense: 04 00 80 00
2014-10-04T20:27:58.748557+02:00 erlangen kernel: [352744.512796] sd 22:0:0:0: [sdf] No Caching mode page found
2014-10-04T20:27:58.748558+02:00 erlangen kernel: [352744.512797] sd 22:0:0:0: [sdf] Assuming drive cache: write through
2014-10-04T20:27:58.749556+02:00 erlangen kernel: [352744.513678] sd 22:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
2014-10-04T20:27:58.749560+02:00 erlangen kernel: [352744.514183] sd 22:0:0:0: [sdf] No Caching mode page found
2014-10-04T20:27:58.749561+02:00 erlangen kernel: [352744.514185] sd 22:0:0:0: [sdf] Assuming drive cache: write through
2014-10-04T20:27:58.769227+02:00 erlangen kernel: [352744.533909] sdf: sdf1
2014-10-04T20:27:58.769237+02:00 erlangen kernel: [352744.533915] sdf: p1 size 32364544 extends beyond EOD, enabling native capacity
2014-10-04T20:27:58.770560+02:00 erlangen kernel: [352744.534461] sd 22:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
2014-10-04T20:27:58.770567+02:00 erlangen kernel: [352744.534978] sd 22:0:0:0: [sdf] No Caching mode page found
2014-10-04T20:27:58.770568+02:00 erlangen kernel: [352744.534981] sd 22:0:0:0: [sdf] Assuming drive cache: write through
2014-10-04T20:27:58.790669+02:00 erlangen kernel: [352744.554852] sdf: sdf1
2014-10-04T20:27:58.790683+02:00 erlangen kernel: [352744.554857] sdf: p1 size 32364544 extends beyond EOD, truncated
2014-10-04T20:27:58.791559+02:00 erlangen kernel: [352744.555667] sd 22:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
2014-10-04T20:27:58.795558+02:00 erlangen kernel: [352744.559376] sd 22:0:0:0: [sdf] No Caching mode page found
2014-10-04T20:27:58.795562+02:00 erlangen kernel: [352744.559379] sd 22:0:0:0: [sdf] Assuming drive cache: write through
2014-10-04T20:27:58.795563+02:00 erlangen kernel: [352744.559381] sd 22:0:0:0: [sdf] Attached SCSI removable disk
2014-10-04T20:28:15.883560+02:00 erlangen kernel: [352761.632294] usb 3-9: new full-speed USB device number 28 using xhci_hcd
2014-10-04T20:28:15.883570+02:00 erlangen kernel: [352761.632484] usb 3-9: Device not responding to set address.
2014-10-04T20:28:16.084574+02:00 erlangen kernel: [352761.833292] usb 3-9: Device not responding to set address.
2014-10-04T20:28:16.285568+02:00 erlangen kernel: [352762.033942] usb 3-9: device not accepting address 28, error -71
2014-10-04T20:28:26.778557+02:00 erlangen kernel: [352772.517742] usb 3-9: new full-speed USB device number 30 using xhci_hcd
2014-10-04T20:28:26.778568+02:00 erlangen kernel: [352772.517877] usb 3-9: Device not responding to set address.
2014-10-04T20:28:26.979560+02:00 erlangen kernel: [352772.718568] usb 3-9: Device not responding to set address.
2014-10-04T20:28:27.180556+02:00 erlangen kernel: [352772.919380] usb 3-9: device not accepting address 30, error -71
2014-10-04T20:28:52.638556+02:00 erlangen kernel: [352798.355867] usb 3-13: USB disconnect, device number 27
2014-10-04T20:28:59.497556+02:00 erlangen kernel: [352805.208054] usb 3-13: new high-speed USB device number 32 using xhci_hcd
2014-10-04T20:28:59.509560+02:00 erlangen kernel: [352805.220979] usb 3-13: New USB device found, idVendor=04da, idProduct=2372
2014-10-04T20:28:59.509569+02:00 erlangen kernel: [352805.220982] usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2014-10-04T20:28:59.509570+02:00 erlangen kernel: [352805.220985] usb 3-13: Product: DMC-TZ10
2014-10-04T20:28:59.509571+02:00 erlangen kernel: [352805.220986] usb 3-13: Manufacturer: Panasonic
2014-10-04T20:28:59.509571+02:00 erlangen kernel: [352805.220988] usb 3-13: SerialNumber: 0000000000000000005F1500160556
2014-10-04T20:28:59.510729+02:00 erlangen kernel: [352805.221499] usb-storage 3-13:1.0: USB Mass Storage device detected
2014-10-04T20:28:59.510736+02:00 erlangen kernel: [352805.221555] usb-storage 3-13:1.0: Quirks match for vid 04da pid 2372: 90
2014-10-04T20:28:59.510737+02:00 erlangen kernel: [352805.221569] scsi23 : usb-storage 3-13:1.0
2014-10-04T20:29:00.512827+02:00 erlangen kernel: [352806.223195] scsi 23:0:0:0: Direct-Access MATSHITA DMC-TZ10 0100 PQ: 0 ANSI: 2
2014-10-04T20:29:00.512838+02:00 erlangen kernel: [352806.223349] sd 23:0:0:0: Attached scsi generic sg6 type 0
2014-10-04T20:29:00.514806+02:00 erlangen kernel: [352806.224706] sd 23:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
2014-10-04T20:29:00.514813+02:00 erlangen kernel: [352806.224711] sd 23:0:0:0: [sdf] 32372735 512-byte logical blocks: (16.5 GB/15.4 GiB)
2014-10-04T20:29:00.514814+02:00 erlangen kernel: [352806.224991] sd 23:0:0:0: [sdf] Write Protect is on
2014-10-04T20:29:00.514815+02:00 erlangen kernel: [352806.224994] sd 23:0:0:0: [sdf] Mode Sense: 04 00 80 00
2014-10-04T20:29:00.515549+02:00 erlangen kernel: [352806.225495] sd 23:0:0:0: [sdf] No Caching mode page found
2014-10-04T20:29:00.515553+02:00 erlangen kernel: [352806.225497] sd 23:0:0:0: [sdf] Assuming drive cache: write through
2014-10-04T20:29:00.516616+02:00 erlangen kernel: [352806.226292] sd 23:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
2014-10-04T20:29:00.516620+02:00 erlangen kernel: [352806.226780] sd 23:0:0:0: [sdf] No Caching mode page found
2014-10-04T20:29:00.516621+02:00 erlangen kernel: [352806.226782] sd 23:0:0:0: [sdf] Assuming drive cache: write through
2014-10-04T20:29:00.536554+02:00 erlangen kernel: [352806.246747] sdf: sdf1
2014-10-04T20:29:00.536564+02:00 erlangen kernel: [352806.246753] sdf: p1 size 32364544 extends beyond EOD, enabling native capacity
2014-10-04T20:29:00.537555+02:00 erlangen kernel: [352806.247305] sd 23:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
2014-10-04T20:29:00.537558+02:00 erlangen kernel: [352806.247950] sd 23:0:0:0: [sdf] No Caching mode page found
2014-10-04T20:29:00.537559+02:00 erlangen kernel: [352806.247952] sd 23:0:0:0: [sdf] Assuming drive cache: write through
2014-10-04T20:29:00.557561+02:00 erlangen kernel: [352806.267908] sdf: sdf1
2014-10-04T20:29:00.557572+02:00 erlangen kernel: [352806.267913] sdf: p1 size 32364544 extends beyond EOD, truncated
2014-10-04T20:29:00.558552+02:00 erlangen kernel: [352806.268706] sd 23:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
2014-10-04T20:29:00.559835+02:00 erlangen kernel: [352806.269412] sd 23:0:0:0: [sdf] No Caching mode page found
2014-10-04T20:29:00.559840+02:00 erlangen kernel: [352806.269415] sd 23:0:0:0: [sdf] Assuming drive cache: write through
2014-10-04T20:29:00.559841+02:00 erlangen kernel: [352806.269417] sd 23:0:0:0: [sdf] Attached SCSI removable disk
2014-10-04T20:29:04.181557+02:00 erlangen kernel: [352809.887949] usb 3-9: new full-speed USB device number 33 using xhci_hcd
2014-10-04T20:29:04.192805+02:00 erlangen kernel: [352809.899635] usb 3-9: New USB device found, idVendor=091e, idProduct=2519
When connecting a device to USB, device notifier pops up and shows all devices available; this works reliably.
What does not work reliably is automatic mounting when attaching the device. Very often devices checked for automatic mounting (see below) will not mount. When trying to mount by clicking the USB icon in device notifier, there is a long wait and finally device notifier displays a message: Can’t mount device. 
I’ve observed intermittent USB behaviour in mounting with my laptop, which turned out to be dependent on whether I had other USB devices plugged in at the same time. ie if I had no other USB devices plugged in, typically the USB would work. But once i started to plug in additional USB devices, then I had an intermittent problem. My assessment was this is power related (in my case).
You could check and then eliminate that as a possibility in your case.
I unplugged everything, cleaned device notifier and started again with my GARMIN GPS device:
2014-10-05T10:10:46.094645+02:00 erlangen kernel: [402069.497296] usb 3-10: new full-speed USB device number 92 using xhci_hcd
2014-10-05T10:10:46.094654+02:00 erlangen kernel: [402069.497485] usb 3-10: Device not responding to set address.
2014-10-05T10:10:46.295640+02:00 erlangen kernel: [402069.698295] usb 3-10: Device not responding to set address.
2014-10-05T10:10:46.496656+02:00 erlangen kernel: [402069.898934] usb 3-10: device not accepting address 92, error -71
2014-10-05T10:10:57.701641+02:00 erlangen kernel: [402081.094115] usb 3-10: new full-speed USB device number 94 using xhci_hcd
2014-10-05T10:10:57.701649+02:00 erlangen kernel: [402081.094249] usb 3-10: Device not responding to set address.
2014-10-05T10:10:57.902642+02:00 erlangen kernel: [402081.294950] usb 3-10: Device not responding to set address.
2014-10-05T10:10:58.103639+02:00 erlangen kernel: [402081.495748] usb 3-10: device not accepting address 94, error -71
2014-10-05T10:11:08.673643+02:00 erlangen kernel: [402092.056492] usb 3-10: new full-speed USB device number 96 using xhci_hcd
2014-10-05T10:11:08.685822+02:00 erlangen kernel: [402092.068224] usb 3-10: New USB device found, idVendor=091e, idProduct=2519
2014-10-05T10:11:08.685842+02:00 erlangen kernel: [402092.068229] usb 3-10: New USB device strings: Mfr=0, Product=0, SerialNumber=5
2014-10-05T10:11:08.685844+02:00 erlangen kernel: [402092.068232] usb 3-10: SerialNumber: 0000e7434bc9
2014-10-05T10:11:08.688374+02:00 erlangen kernel: [402092.070595] usb-storage 3-10:1.0: USB Mass Storage device detected
2014-10-05T10:11:08.688389+02:00 erlangen kernel: [402092.070797] scsi41 : usb-storage 3-10:1.0
2014-10-05T10:11:08.689207+02:00 erlangen mtp-probe: checking bus 3, device 96: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10"
2014-10-05T10:11:08.689548+02:00 erlangen mtp-probe: bus: 3, device: 96 was not an MTP device
2014-10-05T10:11:09.693356+02:00 erlangen kernel: [402093.072569] scsi 41:0:0:0: Direct-Access Garmin GARMIN Flash 1.00 PQ: 0 ANSI: 5
2014-10-05T10:11:09.693368+02:00 erlangen kernel: [402093.072763] sd 41:0:0:0: Attached scsi generic sg3 type 0
2014-10-05T10:11:09.693369+02:00 erlangen kernel: [402093.073519] scsi 41:0:0:1: Direct-Access Garmin GARMIN Card 1.00 PQ: 0 ANSI: 5
2014-10-05T10:11:09.693370+02:00 erlangen kernel: [402093.073625] sd 41:0:0:1: Attached scsi generic sg5 type 0
2014-10-05T10:11:09.700641+02:00 erlangen kernel: [402093.083480] sd 41:0:0:0: [sdc] 7634944 512-byte logical blocks: (3.90 GB/3.64 GiB)
2014-10-05T10:11:09.701639+02:00 erlangen kernel: [402093.084478] sd 41:0:0:1: [sde] 15353856 512-byte logical blocks: (7.86 GB/7.32 GiB)
2014-10-05T10:11:09.703648+02:00 erlangen kernel: [402093.086039] sd 41:0:0:0: [sdc] Write Protect is off
2014-10-05T10:11:09.703655+02:00 erlangen kernel: [402093.086041] sd 41:0:0:0: [sdc] Mode Sense: 23 00 00 00
2014-10-05T10:11:09.704646+02:00 erlangen kernel: [402093.087030] sd 41:0:0:1: [sde] Write Protect is off
2014-10-05T10:11:09.704651+02:00 erlangen kernel: [402093.087033] sd 41:0:0:1: [sde] Mode Sense: 23 00 00 00
2014-10-05T10:11:09.705640+02:00 erlangen kernel: [402093.088011] sd 41:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
2014-10-05T10:11:09.706636+02:00 erlangen kernel: [402093.089009] sd 41:0:0:1: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
2014-10-05T10:11:09.726640+02:00 erlangen kernel: [402093.108645] sdc:
2014-10-05T10:11:09.733646+02:00 erlangen kernel: [402093.115651] sde: sde1
2014-10-05T10:11:09.748641+02:00 erlangen kernel: [402093.130834] sd 41:0:0:0: [sdc] Attached SCSI removable disk
2014-10-05T10:11:09.749635+02:00 erlangen kernel: [402093.131809] sd 41:0:0:1: [sde] Attached SCSI removable disk
2014-10-05T10:12:10.968648+02:00 erlangen kernel: [402154.297703] usb 3-10: USB disconnect, device number 96
2014-10-05T10:12:10.969642+02:00 erlangen kernel: [402154.298031] sd 41:0:0:0: [sdc] Synchronizing SCSI cache
2014-10-05T10:12:10.969649+02:00 erlangen kernel: [402154.298064] sd 41:0:0:0: [sdc]
2014-10-05T10:12:10.969651+02:00 erlangen kernel: [402154.298065] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
2014-10-05T10:12:10.973429+02:00 erlangen kernel: [402154.301062] sd 41:0:0:1: [sde] Synchronizing SCSI cache
2014-10-05T10:12:10.973439+02:00 erlangen kernel: [402154.301091] sd 41:0:0:1: [sde]
2014-10-05T10:12:10.973440+02:00 erlangen kernel: [402154.301093] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Same problem with the camera, device notifier detects the device, but mounting by clicking the USB symbol fails:
2014-10-05T10:43:57.416645+02:00 erlangen kernel: [404059.073624] usb 3-13: new high-speed USB device number 102 using xhci_hcd
2014-10-05T10:43:57.432060+02:00 erlangen kernel: [404059.086944] usb 3-13: New USB device found, idVendor=04da, idProduct=2372
2014-10-05T10:43:57.432075+02:00 erlangen kernel: [404059.086948] usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2014-10-05T10:43:57.432076+02:00 erlangen kernel: [404059.086950] usb 3-13: Product: DMC-TZ10
2014-10-05T10:43:57.432076+02:00 erlangen kernel: [404059.086952] usb 3-13: Manufacturer: Panasonic
2014-10-05T10:43:57.432077+02:00 erlangen kernel: [404059.086954] usb 3-13: SerialNumber: 0000000000000000005F1500160556
2014-10-05T10:43:57.432078+02:00 erlangen kernel: [404059.088234] usb-storage 3-13:1.0: USB Mass Storage device detected
2014-10-05T10:43:57.432079+02:00 erlangen kernel: [404059.088328] usb-storage 3-13:1.0: Quirks match for vid 04da pid 2372: 90
2014-10-05T10:43:57.432079+02:00 erlangen kernel: [404059.088362] scsi43 : usb-storage 3-13:1.0
2014-10-05T10:43:57.432486+02:00 erlangen mtp-probe: checking bus 3, device 102: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-13"
2014-10-05T10:43:57.432732+02:00 erlangen mtp-probe: bus: 3, device: 102 was not an MTP device
2014-10-05T10:43:58.433643+02:00 erlangen kernel: [404060.090392] scsi 43:0:0:0: Direct-Access MATSHITA DMC-TZ10 0100 PQ: 0 ANSI: 2
2014-10-05T10:43:58.433654+02:00 erlangen kernel: [404060.090536] sd 43:0:0:0: Attached scsi generic sg3 type 0
2014-10-05T10:43:58.436639+02:00 erlangen kernel: [404060.093192] sd 43:0:0:0: [sdc] Adjusting the sector count from its reported value: 32372736
2014-10-05T10:43:58.436646+02:00 erlangen kernel: [404060.093195] sd 43:0:0:0: [sdc] 32372735 512-byte logical blocks: (16.5 GB/15.4 GiB)
2014-10-05T10:43:58.436647+02:00 erlangen kernel: [404060.093454] sd 43:0:0:0: [sdc] Write Protect is on
2014-10-05T10:43:58.436648+02:00 erlangen kernel: [404060.093456] sd 43:0:0:0: [sdc] Mode Sense: 04 00 80 00
2014-10-05T10:43:58.436648+02:00 erlangen kernel: [404060.093701] sd 43:0:0:0: [sdc] No Caching mode page found
2014-10-05T10:43:58.436649+02:00 erlangen kernel: [404060.093702] sd 43:0:0:0: [sdc] Assuming drive cache: write through
2014-10-05T10:43:58.437642+02:00 erlangen kernel: [404060.094605] sd 43:0:0:0: [sdc] Adjusting the sector count from its reported value: 32372736
2014-10-05T10:43:58.438639+02:00 erlangen kernel: [404060.095384] sd 43:0:0:0: [sdc] No Caching mode page found
2014-10-05T10:43:58.438646+02:00 erlangen kernel: [404060.095386] sd 43:0:0:0: [sdc] Assuming drive cache: write through
2014-10-05T10:43:58.458640+02:00 erlangen kernel: [404060.115561] sdc: sdc1
2014-10-05T10:43:58.458651+02:00 erlangen kernel: [404060.115569] sdc: p1 size 32364544 extends beyond EOD, enabling native capacity
2014-10-05T10:43:58.459635+02:00 erlangen kernel: [404060.116124] sd 43:0:0:0: [sdc] Adjusting the sector count from its reported value: 32372736
2014-10-05T10:43:58.459639+02:00 erlangen kernel: [404060.116620] sd 43:0:0:0: [sdc] No Caching mode page found
2014-10-05T10:43:58.459639+02:00 erlangen kernel: [404060.116621] sd 43:0:0:0: [sdc] Assuming drive cache: write through
2014-10-05T10:43:58.480643+02:00 erlangen kernel: [404060.136806] sdc: sdc1
2014-10-05T10:43:58.480655+02:00 erlangen kernel: [404060.136810] sdc: p1 size 32364544 extends beyond EOD, truncated
2014-10-05T10:43:58.480656+02:00 erlangen kernel: [404060.137584] sd 43:0:0:0: [sdc] Adjusting the sector count from its reported value: 32372736
2014-10-05T10:43:58.484639+02:00 erlangen kernel: [404060.141364] sd 43:0:0:0: [sdc] No Caching mode page found
2014-10-05T10:43:58.484650+02:00 erlangen kernel: [404060.141366] sd 43:0:0:0: [sdc] Assuming drive cache: write through
2014-10-05T10:43:58.484650+02:00 erlangen kernel: [404060.141368] sd 43:0:0:0: [sdc] Attached SCSI removable disk
2014-10-05T10:45:16.676644+02:00 erlangen kernel: [404138.264866] usb 3-13: USB disconnect, device number 102
On 2014-10-05 06:56, karlmistelberger wrote:
> Mount is done automatically and devices are displayed in the system tray
> by the device notifier. I checked /var/log/messages for 'erlangen
> kernel:
> ’ and found the following mostly related to USB:
> 2014-10-04T20:24:38.325556+02:00 erlangen kernel: [352544.265229] FAT-fs (sde1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
> 2014-10-04T20:24:47.145712+02:00 erlangen kernel: [352553.077827] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
This one will not automatically mount, you need to fsck it first.
> 2014-10-04T20:27:57.730557+02:00 erlangen kernel: [352743.495216] usb 3-13: new high-speed USB device number 27 using xhci_hcd
> 2014-10-04T20:27:57.742555+02:00 erlangen kernel: [352743.508088] usb 3-13: New USB device found, idVendor=04da, idProduct=2372
> 2014-10-04T20:27:57.742566+02:00 erlangen kernel: [352743.508092] usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> 2014-10-04T20:27:57.742567+02:00 erlangen kernel: [352743.508094] usb 3-13: Product: DMC-TZ10
> 2014-10-04T20:27:57.742568+02:00 erlangen kernel: [352743.508096] usb 3-13: Manufacturer: Panasonic
> 2014-10-04T20:27:57.742568+02:00 erlangen kernel: [352743.508097] usb 3-13: SerialNumber: 0000000000000000005F1500160556
> 2014-10-04T20:27:57.743565+02:00 erlangen kernel: [352743.508604] usb-storage 3-13:1.0: USB Mass Storage device detected
> 2014-10-04T20:27:57.743573+02:00 erlangen kernel: [352743.508634] usb-storage 3-13:1.0: Quirks match for vid 04da pid 2372: 90
> 2014-10-04T20:27:57.743574+02:00 erlangen kernel: [352743.508657] scsi22 : usb-storage 3-13:1.0
> 2014-10-04T20:27:58.746393+02:00 erlangen kernel: [352744.510914] scsi 22:0:0:0: Direct-Access MATSHITA DMC-TZ10 0100 PQ: 0 ANSI: 2
> 2014-10-04T20:27:58.746405+02:00 erlangen kernel: [352744.511067] sd 22:0:0:0: Attached scsi generic sg6 type 0
> 2014-10-04T20:27:58.747550+02:00 erlangen kernel: [352744.512198] sd 22:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
> 2014-10-04T20:27:58.747555+02:00 erlangen kernel: [352744.512201] sd 22:0:0:0: [sdf] 32372735 512-byte logical blocks: (16.5 GB/15.4 GiB)
> 2014-10-04T20:27:58.748551+02:00 erlangen kernel: [352744.512491] sd 22:0:0:0: [sdf] Write Protect is on
> 2014-10-04T20:27:58.748556+02:00 erlangen kernel: [352744.512493] sd 22:0:0:0: [sdf] Mode Sense: 04 00 80 00
> 2014-10-04T20:27:58.748557+02:00 erlangen kernel: [352744.512796] sd 22:0:0:0: [sdf] No Caching mode page found
> 2014-10-04T20:27:58.748558+02:00 erlangen kernel: [352744.512797] sd 22:0:0:0: [sdf] Assuming drive cache: write through
> 2014-10-04T20:27:58.749556+02:00 erlangen kernel: [352744.513678] sd 22:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
> 2014-10-04T20:27:58.749560+02:00 erlangen kernel: [352744.514183] sd 22:0:0:0: [sdf] No Caching mode page found
> 2014-10-04T20:27:58.749561+02:00 erlangen kernel: [352744.514185] sd 22:0:0:0: [sdf] Assuming drive cache: write through
> 2014-10-04T20:27:58.769227+02:00 erlangen kernel: [352744.533909] sdf: sdf1
> 2014-10-04T20:27:58.769237+02:00 erlangen kernel: [352744.533915] sdf: p1 size 32364544 extends beyond EOD, enabling native capacity
> 2014-10-04T20:27:58.770560+02:00 erlangen kernel: [352744.534461] sd 22:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
> 2014-10-04T20:27:58.770567+02:00 erlangen kernel: [352744.534978] sd 22:0:0:0: [sdf] No Caching mode page found
> 2014-10-04T20:27:58.770568+02:00 erlangen kernel: [352744.534981] sd 22:0:0:0: [sdf] Assuming drive cache: write through
> 2014-10-04T20:27:58.790669+02:00 erlangen kernel: [352744.554852] sdf: sdf1
> 2014-10-04T20:27:58.790683+02:00 erlangen kernel: [352744.554857] sdf: p1 size 32364544 extends beyond EOD, truncated
> 2014-10-04T20:27:58.791559+02:00 erlangen kernel: [352744.555667] sd 22:0:0:0: [sdf] Adjusting the sector count from its reported value: 32372736
> 2014-10-04T20:27:58.795558+02:00 erlangen kernel: [352744.559376] sd 22:0:0:0: [sdf] No Caching mode page found
> 2014-10-04T20:27:58.795562+02:00 erlangen kernel: [352744.559379] sd 22:0:0:0: [sdf] Assuming drive cache: write through
> 2014-10-04T20:27:58.795563+02:00 erlangen kernel: [352744.559381] sd 22:0:0:0: [sdf] Attached SCSI removable disk
This one has other kind of problems. It apparently reports a sector
count and Linux thinks it has less, and adjusts. Then later it thinks
that it goes beyond the end, and gets puzzled. Or something of the sort.
It is treated special because of this: “Quirks match for …”, which
looks like buggy hardware to me, that Linux knows about, and tries to
compensate in some database of known bad hardware.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-10-05 10:26, karlmistelberger wrote:
> I unplugged everything, cleaned device notifier and started again with
> my GARMIN GPS device:
....
> 2014-10-05T10:11:09.726640+02:00 erlangen kernel: [402093.108645] sdc:
> 2014-10-05T10:11:09.733646+02:00 erlangen kernel: [402093.115651] sde: sde1
> 2014-10-05T10:11:09.748641+02:00 erlangen kernel: [402093.130834] sd 41:0:0:0: [sdc] Attached SCSI removable disk
> 2014-10-05T10:11:09.749635+02:00 erlangen kernel: [402093.131809] sd 41:0:0:1: [sde] Attached SCSI removable disk
> 2014-10-05T10:03:45.493572+02:00 erlangen polkitd[674]: Operator of unix-session:455 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.1500 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:karl)
> 2014-10-05T10:11:11.764649+02:00 erlangen polkitd[674]: Operator of unix-session:74 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.265 [kdeinit4: kded4 [kdeinit]] (owned by unix-user:charlemagne)
This one might be the problem, failed authentication.
And notice there are two distinct users involved: karl and charlemagne. :-?
> 2014-10-05T10:12:10.968648+02:00 erlangen kernel: [402154.297703] usb 3-10: USB disconnect, device number 96
> 2014-10-05T10:12:10.969642+02:00 erlangen kernel: [402154.298031] sd 41:0:0:0: [sdc] Synchronizing SCSI cache
> 2014-10-05T10:12:10.969649+02:00 erlangen kernel: [402154.298064] sd 41:0:0:0: [sdc]
> 2014-10-05T10:12:10.969651+02:00 erlangen kernel: [402154.298065] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> 2014-10-05T10:12:10.973429+02:00 erlangen kernel: [402154.301062] sd 41:0:0:1: [sde] Synchronizing SCSI cache
> 2014-10-05T10:12:10.973439+02:00 erlangen kernel: [402154.301091] sd 41:0:0:1: [sde]
> 2014-10-05T10:12:10.973440+02:00 erlangen kernel: [402154.301093] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
On 2014-10-05 10:56, karlmistelberger wrote:
Same problem with the camera, device notifier detects the device, but
mounting by clicking the USB symbol fails:
This one I told you about before:
> 2014-10-05T10:43:57.432078+02:00 erlangen kernel: [404059.088234] usb-storage 3-13:1.0: USB Mass Storage device detected
> 2014-10-05T10:43:57.432079+02:00 erlangen kernel: [404059.088328] usb-storage 3-13:1.0: Quirks match for vid 04da pid 2372: 90
....
> 2014-10-05T10:43:58.436639+02:00 erlangen kernel: [404060.093192] sd 43:0:0:0: [sdc] Adjusting the sector count from its reported value: 32372736
> 2014-10-05T10:43:58.436646+02:00 erlangen kernel: [404060.093195] sd 43:0:0:0: [sdc] 32372735 512-byte logical blocks: (16.5 GB/15.4 GiB)
....
> 2014-10-05T10:43:58.458651+02:00 erlangen kernel: [404060.115569] sdc: p1 size 32364544 extends beyond EOD, enabling native capacity
Faulty thing. Unfortunate being a camera. Perhaps a bug report is in
order, or google about that particular device :-?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I tried this device again.
2014-10-05T21:11:04.072933+02:00 erlangen kernel: [27931.204584] usb 4-5: New USB device found, idVendor=1058, idProduct=1048
2014-10-05T21:11:04.072940+02:00 erlangen kernel: [27931.204595] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5
2014-10-05T21:11:04.072941+02:00 erlangen kernel: [27931.204602] usb 4-5: Product: Elements 1048
2014-10-05T21:11:04.072942+02:00 erlangen kernel: [27931.204609] usb 4-5: Manufacturer: Western Digital
2014-10-05T21:11:04.072944+02:00 erlangen kernel: [27931.204615] usb 4-5: SerialNumber: 575843314131344D35383138
2014-10-05T21:11:04.073977+02:00 erlangen kernel: [27931.206070] usb-storage 4-5:1.0: USB Mass Storage device detected
2014-10-05T21:11:04.073985+02:00 erlangen kernel: [27931.206107] scsi10 : usb-storage 4-5:1.0
2014-10-05T21:11:04.074516+02:00 erlangen mtp-probe: checking bus 4, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-5"
2014-10-05T21:11:04.074761+02:00 erlangen mtp-probe: bus: 4, device: 2 was not an MTP device
2014-10-05T21:11:05.076756+02:00 erlangen kernel: [27932.208496] scsi 10:0:0:0: Direct-Access WD Elements 1048 1025 PQ: 0 ANSI: 6
2014-10-05T21:11:05.076774+02:00 erlangen kernel: [27932.208712] sd 10:0:0:0: Attached scsi generic sg4 type 0
2014-10-05T21:11:05.078978+02:00 erlangen kernel: [27932.210613] sd 10:0:0:0: [sdd] Spinning up disk...
2014-10-05T21:11:11.091014+02:00 erlangen kernel: [27933.211209] ......ready
2014-10-05T21:11:11.091040+02:00 erlangen kernel: [27938.217337] sd 10:0:0:0: [sdd] 1953519616 512-byte logical blocks: (1.00 TB/931 GiB)
2014-10-05T21:11:11.091043+02:00 erlangen kernel: [27938.217651] sd 10:0:0:0: [sdd] Write Protect is off
2014-10-05T21:11:11.091046+02:00 erlangen kernel: [27938.217660] sd 10:0:0:0: [sdd] Mode Sense: 47 00 10 08
2014-10-05T21:11:11.092012+02:00 erlangen kernel: [27938.218150] sd 10:0:0:0: [sdd] No Caching mode page found
2014-10-05T21:11:11.092029+02:00 erlangen kernel: [27938.218157] sd 10:0:0:0: [sdd] Assuming drive cache: write through
2014-10-05T21:11:11.094011+02:00 erlangen kernel: [27938.220570] sd 10:0:0:0: [sdd] No Caching mode page found
2014-10-05T21:11:11.094029+02:00 erlangen kernel: [27938.220578] sd 10:0:0:0: [sdd] Assuming drive cache: write through
2014-10-05T21:11:11.109978+02:00 erlangen kernel: [27938.235793] sdd: sdd1 sdd2
2014-10-05T21:11:11.110972+02:00 erlangen kernel: [27938.236856] sd 10:0:0:0: [sdd] No Caching mode page found
2014-10-05T21:11:11.110976+02:00 erlangen kernel: [27938.236859] sd 10:0:0:0: [sdd] Assuming drive cache: write through
2014-10-05T21:11:11.110976+02:00 erlangen kernel: [27938.236861] sd 10:0:0:0: [sdd] Attached SCSI disk
2014-10-05T21:11:11.459500+02:00 erlangen kernel: [27938.585438] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
2014-10-05T21:11:11.462296+02:00 erlangen udisksd[1299]: Mounted /dev/sdd1 at /run/media/karl/WD25-VFAT on behalf of uid 1000
2014-10-05T21:12:02.609910+02:00 erlangen udisksd[1299]: Mounted /dev/sdd2 at /run/media/karl/WD25-BACKUP on behalf of uid 1000
2014-10-05T21:12:02.610210+02:00 erlangen kernel: [27989.690021] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: (null)
2014-10-05T21:12:44.592848+02:00 erlangen udisksd[1299]: Cleaning up mount point /run/media/karl/WD25-VFAT (device 8:49 is not mounted)
2014-10-05T21:12:44.596705+02:00 erlangen udisksd[1299]: Unmounted /dev/sdd1 on behalf of uid 1000
2014-10-05T21:12:45.840669+02:00 erlangen udisksd[1299]: Cleaning up mount point /run/media/karl/WD25-BACKUP (device 8:50 is not mounted)
2014-10-05T21:12:46.259008+02:00 erlangen udisksd[1299]: Unmounted /dev/sdd2 on behalf of uid 1000
2014-10-05T21:13:07.970011+02:00 erlangen kernel: [28054.993534] usb 4-5: USB disconnect, device number 2
2014-10-05T21:13:07.972038+02:00 erlangen kernel: [28054.996355] usb 4-5: Set SEL for device-initiated U1 failed.
2014-10-05T21:13:07.972061+02:00 erlangen kernel: [28054.996367] usb 4-5: Set SEL for device-initiated U2 failed.
Actually FAT-fs (sdd1) was mounted automatically, as can seen from the time stamps. EXT4-fs (sdd2) did not mount automatically. But I could mount it manually by clicking on the USB symbol in device notifier. This disk had the same problems as described above several times before: no automatic mounting, no manual mounting by clicking device notifier.
I was not able to view messages from device notifier itself. Is there a way to invoke it from a shell?
Regarding fsck there were some problems with EXT4-fs (sdd2) which were solved. But fsck failed on FAT-fs (sdd1):
erlangen:/var/log # fsck.vfat /dev/sdd1
fsck.fat 3.0.22 (2013-07-19)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
Leaving filesystem unchanged.
/dev/sdd1: 1 files, 1/1048319 clusters
erlangen:/var/log # fsck.vfat /dev/sdd1
fsck.fat 3.0.22 (2013-07-19)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
Leaving filesystem unchanged.
/dev/sdd1: 1 files, 1/1048319 clusters
erlangen:/var/log #
Any idea how to fix this? File system is unmounted. I tried several times to no avail.
Regards, Karl
On 2014-10-05 21:46, karlmistelberger wrote:
>
> I tried this device again.
> Code:
> --------------------
....
> 2014-10-05T21:11:11.459500+02:00 erlangen kernel: [27938.585438] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
> 2014-10-05T21:11:11.462296+02:00 erlangen udisksd[1299]: Mounted /dev/sdd1 at /run/media/karl/WD25-VFAT on behalf of uid 1000
> 2014-10-05T21:12:02.609910+02:00 erlangen udisksd[1299]: Mounted /dev/sdd2 at /run/media/karl/WD25-BACKUP on behalf of uid 1000
Well, sdd1 is corrupt.
> Actually FAT-fs (sdd1) was mounted automatically, as can seen from the
> time stamps. EXT4-fs (sdd2) did not mount automatically.
sdd2 is ext4.
Mine don’t mount automatically, but I always disable that feature.
> I was not able to view messages from device notifier itself. Is there a
> way to invoke it from a shell?
Dunno.
> Regarding fsck there were some problems with EXT4-fs (sdd2) which were
> solved. But fsck failed on FAT-fs (sdd1):
…
> Any idea how to fix this? File system is unmounted. I tried several
> times to no avail.
Well, you see, fsck.vfat doesn’t write anything unless you give it the
-a or -r switches. So says the man page. I would try “-aV”.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
fsck -aV fixed that.:shame:
> Actually FAT-fs (sdd1) was mounted automatically, as can seen from the
> time stamps. EXT4-fs (sdd2) did not mount automatically.
sdd2 is ext4.
Mine don’t mount automatically, but I always disable that feature.
Changed setting of device notifier. The first time since installation it does what is advertised. :shame:
Regards, Karl
I checked again several times and found device notifier to be very shaky, even with only one user being logged in. Checked items can go unchecked and vice versa without ever clicking them. Multiple entries with the same disk label may appear.
For sure there is an additional problem with two distinct users logged in via KDM. With desktop of karl in the foreground device notifier asks for authorization on desktop of charlemagne in the background. This makes absolutely no sense to me. How can I change this behavior? I never want to mount the device on behalf of user charlemagne. Mount should be on behalf of user karl in the foreground and should not require authorization.
When I detach and reattach the device mounting works for user karl with the authorization window still waiting on desktop charlemagne.
