> On Tuesday 04 December 2018 08:01:22 pm Kate Draven wrote: > > > On Tuesday 04 December 2018 07:26:54 pm Kate Draven wrote: > > > > Out of the blue I started getting this error msg. > > > > Using PCLOS 64bit > > > > > > > > Unable to mount this device. > > > > Potential reasons include: > > > > Improper device and/or user privilege level > > > > Corrupt data on storage device > > > > Technical details: > > > > org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sdk1 > > > > at /media/Lexar: Command-line > > > > `mount -t "vfat" -o > > > > > > "uhelper=3Dudisks2,nodev,nosuid,uid=3D0,gid=3D0,shortname=3Dmixed,utf8= > =3D1,showexec > > >,f > > > > > > >lush,noatime,shortname=3Dlower" "/dev/sdk1" "/media/Lexar"' exited with > > > > non-zero exit status 32: mount: /mnt/Lexar: /dev/sdk1 already mounted > > > > or mount point busy. > > > > > > > > It's random and sometimes suddenly goes away. > > > > I've tried it with a variety of USB sticks. > > > > > > I've had "mount point busy" come from both an open shell and a file > > > manager that's sitting on the mount point before. It can also block us= > er > > > > un-mounting > > > > > as well (although I think root umount force un-mounts?). > > > > > > --------------------------------------------------------------------- > > > > To my knowledge there is nothing at that mount point. > > I can connect 5 usb sticks and they will all give the same error. > > 5 different sticks are almost guaranteed to have different mount points, so= > =20 > having an open shell sitting at /mnt/Lexar/mystuff wouldn=E2=80=99t whack t= > he other=20 > 4. :( > > Do you have access to another comp to test one of the sticks, so you have=20 > a =E2=80=98known good?=E2=80=99 You could then try re-installing whatever = > provides UDisks2. =20 > After that file a bug with PCLOS so they can file an upstream bug. > > Best, > Michael > > --------------------------------------------------------------------- Michael My thinking exactly. I do have several computers in me wee lab. The sticks are all fine, mount and umount on all other computers, including another pclos 64 with the same kernels. At first I thought it was a kernel bug, wrong. I can only guess I'm installing something that messes it up. I reinstalled the OS into the test computer and incrementally installing packages until I find the culprit. I've noticed some odd behavior with some trinity packages such as trinity-tdeio-umountwrapper, it removes the "safely remove" from all menus related to removable drives. I think I'm installing an incompatible packages. I've done it before. Honestly I'm my own worst enemy. Thanks for the UDisks2 tip. I'll check into that. Kate --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
