Hello all,
Debian Buster with R.14.07 (Development). I have an external SATA to USB enclosure with removable discs. When I slip a disc in and turn it on, I get a Konqueror error (unable to mount this device, see attachment). However, I can mount it with no problem from the command line.
My guess is that it's a timing problem, Konqueror trying to mount something that is not yet available, but I don't know what to do.
I did not have this with Stretch and "stable" TDE, so it might also ave to do with de "Development" version.
Thierry
Thierry de Coulon wrote:
My guess is that it's a timing problem, Konqueror trying to mount something that is not yet available, but I don't know what to do.
Hi Thierry, this should be a new installation for you - not an upgrade? IF so did you check your rights and permissions? So that the user is in the required group?
regards
Anno domini 2019 Mon, 09 Sep 08:43:44 +0200 deloptes scripsit:
Thierry de Coulon wrote:
My guess is that it's a timing problem, Konqueror trying to mount something that is not yet available, but I don't know what to do.
Hi Thierry, this should be a new installation for you - not an upgrade? IF so did you check your rights and permissions? So that the user is in the required group?
+1 - I remember, I had the same issue when I removed policykit on devuan.
regards
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net 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
On Monday 09 September 2019 08.43:44 deloptes wrote:
Hi Thierry, this should be a new installation for you - not an upgrade? IF so did you check your rights and permissions? So that the user is in the required group?
Yes, it's a new installation. My user has the usual groups, I can't see any group that would have to do with mounting removable drives.
What's more, some drives do mount (thumb drives), others don't, even some discs in my external enclosure mount, others don't. Very strange.
Thierry
Hi Thierry!
Anno domini 2019 Mon, 9 Sep 10:02:26 +0200 Thierry de Coulon scripsit:
On Monday 09 September 2019 08.43:44 deloptes wrote:
Hi Thierry, this should be a new installation for you - not an upgrade? IF so did you check your rights and permissions? So that the user is in the required group?
Yes, it's a new installation. My user has the usual groups, I can't see any group that would have to do with mounting removable drives.
What's more, some drives do mount (thumb drives), others don't, even some discs in my external enclosure mount, others don't. Very strange.
Could you check: Those that mount have a partitiontabe, those who don't do not have a partition table.
Nik
Thierry
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net 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
Anno domini 2019 Mon, 9 Sep 11:22:55 +0200 Dr. Nikolaus Klepp scripsit:
Hi Thierry!
Anno domini 2019 Mon, 9 Sep 10:02:26 +0200 Thierry de Coulon scripsit:
On Monday 09 September 2019 08.43:44 deloptes wrote:
Hi Thierry, this should be a new installation for you - not an upgrade? IF so did you check your rights and permissions? So that the user is in the required group?
Yes, it's a new installation. My user has the usual groups, I can't see any group that would have to do with mounting removable drives.
What's more, some drives do mount (thumb drives), others don't, even some discs in my external enclosure mount, others don't. Very strange.
Could you check: Those that mount have a partitiontabe, those who don't do not have a partition table.
Nik
Sorry, just saw your screenshot ... nothing to do with my old problem.
Nik
Thierry
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2019/09/09 03:29 PM, Thierry de Coulon wrote:
Hello all,
Debian Buster with R.14.07 (Development). I have an external SATA to USB enclosure with removable discs. When I slip a disc in and turn it on, I get a Konqueror error (unable to mount this device, see attachment). However, I can mount it with no problem from the command line.
My guess is that it's a timing problem, Konqueror trying to mount something that is not yet available, but I don't know what to do.
I did not have this with Stretch and "stable" TDE, so it might also ave to do with de "Development" version.
Thierry
Hi Thierry, a few questions to gather further info.
1) do you have policykit installed? I guess so, if you say some partitions on external drives can be mounted. 2) Does the disk have a valid partition in sdg1? 3) is the disk in /etc/fstab? 4) what command do you use to mount the partition from CLI? 5) if you retry from Konqueror, do you have a failure again? 6) what does "fdisk -l /dev/sdg" or "gdisk -l /dev/sdg" prints? 7) what happens if you try as root instead of normal user?
Additionally, do you have d-feet installed on your computer? That could help in troubleshooting since I see in your screenshot the error is reported by udisks2 dbus call.
Cheers Michele
On Monday 09 September 2019 13.58:29 Michele Calgaro via trinity-users wrote:
Hi Thierry, a few questions to gather further info.
- do you have policykit installed? I guess so, if you say some partitions
on external drives can be mounted.
Is installed
- Does the disk have a valid partition
in sdg1?
Yes. ext4, mbr
- is the disk in /etc/fstab?
No
- what command do you use to mount the partition from CLI?
mount /dev/sdx /<mount directory>. As root. sdx is usually sdg or sdi, depending on other connected drives.
- if you retry from Konqueror, do you have a failure again?
I don't see what you want me to do. The error message appears when I plug in / switch on the external drive. If/when it works the drive gets mounted on /media/<user>/<drive> and konqueror opens a window on its content. If/when it fails nothing is mounted and I can't do it from Konqueror (or I don't know I can :).
- what does "fdisk -l /dev/sdg" or "gdisk -l /dev/sdg" prints?
root@junior:/home/thierry# fdisk -l /dev/sdg Disk /dev/sdg: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: HD103SI Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xb6bc5d97
Device Boot Start End Sectors Size Id Type /dev/sdg1 63 1953520064 1953520002 931.5G 83 Linux
root@junior:/home/thierry# gdisk -l /dev/sdg GPT fdisk (gdisk) version 1.0.3
Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present
*************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. ***************************************************************
Disk /dev/sdg: 1953525168 sectors, 931.5 GiB Model: HD103SI Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 88036014-EE81-4D56-92FA-6212E6693E3C Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 8-sector boundaries Total free space is 5099 sectors (2.5 MiB)
Number Start (sector) End (sector) Size Code Name 1 63 1953520064 931.5 GiB 8300 Linux filesystem
Note that after running fdisk -l nothing happens, while after running gdisk the drive got mounted!
- what happens if you try as root instead of normal user?
It found the drive OK, but did not open Konqueror, instead asked what to do (attachment).
Additionally, do you have d-feet installed on your computer? That could help in troubleshooting since I see in your screenshot the error is reported by udisks2 dbus call.
I did not, I have now.
Cheers Michele
Also, I've noticed that "Safely remove" as user causes unmounting and immediate re-mounting, "unmount" correctly unmounts.
As root both work as expected.
Thanks,
Thierry
Thierry de Coulon wrote:
Also, I've noticed that "Safely remove" as user causes unmounting and immediate re-mounting, "unmount" correctly unmounts.
As root both work as expected.
I think we have updated the policy recently for this reason and AFAIR there was a ticket, but might be I am wrong.
My user is in 46(plugdev)
And also I recall now that it was udisks2 that provides the service for dbus
$ dpkg -S /etc/dbus-1/system.d/org.freedesktop.UDisks2.conf udisks2: /etc/dbus-1/system.d/org.freedesktop.UDisks2.conf
We actually simplyfied
/etc/dbus-1/system.d/org.trinitydesktop.hardwarecontrol.conf
but it is unrelated to this I guess.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
- if you retry from Konqueror, do you have a failure again?
I don't see what you want me to do. The error message appears when I plug in / switch on the external drive. If/when it works the drive gets mounted on /media/<user>/<drive> and konqueror opens a window on its content. If/when it fails nothing is mounted and I can't do it from Konqueror (or I don't know I can :).
Also, I've noticed that "Safely remove" as user causes unmounting and immediate re-mounting, "unmount" correctly unmounts.
As root both work as expected.
Thanks,
Thierry
Hi Thierry,
thanks for answering the list of questions.
As root both work as expected.
Do you mean that as root you don't have the problem at all?
Re 5), when it fails, you can go in Konqueror, search the Storage Media in the treeview which in turn lists the available known drives. Then double click on your failed disk and see if it gets mounted again or not. Alternatively, you can type "media:/sdg1" (or whatever path) in the location bar and press enter.
Now that you have d-feet installed, can you also make another test. After a failed mounting, open d-feet, search the system bus for udisk2 and select it. On the right side you will see many interfaces. Search for object path /org/freedesktop/UDisks2/block_devices/sdg1 (or other path), expand it and please paste a screenshot.
Finally, one more thing. Open KDCOP, search for kded -> mediamanager -> fullList function (going by memory here, may be slightly different name). Double click to execute. In the result section, you will have a list of known disks. Can you find your disk there? If so, can you paste a screenshot of the properties of that disk?
Last (but not least), is this a real system or is it running inside VirtualBox (or other VM)? (not a stupid question, trust me).
Cheers Michele
On Tuesday 10 September 2019 04.15:17 Michele Calgaro via trinity-users wrote:
As root both work as expected.
Do you mean that as root you don't have the problem at all?
I did not spend so much time logged as root. I did not see the problem then, but I'd have to spend more time trying to give a real answer.
Re 5), when it fails, you can go in Konqueror, search the Storage Media in the treeview which in turn lists the available known drives. Then double click on your failed disk and see if it gets mounted again or not. Alternatively, you can type "media:/sdg1" (or whatever path) in the location bar and press enter.
media:/sdg1 works
Now that you have d-feet installed, can you also make another test. After a failed mounting, open d-feet, search the system bus for udisk2 and select it. On the right side you will see many interfaces. Search for object path /org/freedesktop/UDisks2/block_devices/sdg1 (or other path), expand it and please paste a screenshot.
Done (4 snapshots!)
Finally, one more thing. Open KDCOP, search for kded -> mediamanager -> fullList function (going by memory here, may be slightly different name). Double click to execute. In the result section, you will have a list of known disks. Can you find your disk there? If so, can you paste a screenshot of the properties of that disk?
You get another snapshot
Last (but not least), is this a real system or is it running inside VirtualBox (or other VM)? (not a stupid question, trust me).
It's a real system.
Cheers Michele
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net 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
On Tuesday 10 September 2019 04:32:39 Thierry de Coulon wrote:
On Tuesday 10 September 2019 04.15:17 Michele Calgaro via trinity-users
wrote:
As root both work as expected.
Do you mean that as root you don't have the problem at all?
I did not spend so much time logged as root. I did not see the problem then, but I'd have to spend more time trying to give a real answer.
Re 5), when it fails, you can go in Konqueror, search the Storage Media in the treeview which in turn lists the available known drives. Then double click on your failed disk and see if it gets mounted again or not. Alternatively, you can type "media:/sdg1" (or whatever path) in the location bar and press enter.
media:/sdg1 works
Now that you have d-feet installed, can you also make another test. After a failed mounting, open d-feet, search the system bus for udisk2 and select it. On the right side you will see many interfaces. Search for object path /org/freedesktop/UDisks2/block_devices/sdg1 (or other path), expand it and please paste a screenshot.
Done (4 snapshots!)
Finally, one more thing. Open KDCOP, search for kded -> mediamanager -> fullList function (going by memory here, may be slightly different name). Double click to execute. In the result section, you will have a list of known disks. Can you find your disk there? If so, can you paste a screenshot of the properties of that disk?
You get another snapshot
Last (but not least), is this a real system or is it running inside VirtualBox (or other VM)? (not a stupid question, trust me).
It's a real system.
Cheers Michele
There are a lot of pages that come up under this and similar questions, but this one had answers that worked for me. https://www.linuxquestions.org/questions/linux-newbie-8/how-can-i-automount-...
With this, I created udev rules and a shell script (all should be explained in this page). On a new installation, I just copy these items (udev rules and shell script) from my secure storage location to these places, like so:
udev rules sudo cp -r -v -f /media/<storage_location>/etc/udev/rules.d/52-usb-memory.rules -t /etc/udev/rules.d/
mount script sudo cp -r -v -f /media/<storage_location>/usr/local/sbin/mount-usb.sh -t /usr/local/sbin/
After reboot, everything works like one expects, no surprises.
lotsa luck
Bill
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi Thierry, see comments below and screenshots attached.
I did not spend so much time logged as root. I did not see the problem then, but I'd have to spend more time trying to give a real answer.
That may help, jsut to understand if the problem is general or strictly related to user or policies.
Re 5), when it fails, you can go in Konqueror, search the Storage Media in the treeview which in turn lists the available known drives. Then double click on your failed disk and see if it gets mounted again or not. Alternatively, you can type "media:/sdg1" (or whatever path) in the location bar and press enter.
media:/sdg1 works
So the second time around it works.
Now that you have d-feet installed, can you also make another test. After a failed mounting, open d-feet, search the system bus for udisk2 and select it. On the right side you will see many interfaces. Search for object path /org/freedesktop/UDisks2/block_devices/sdg1 (or other path), expand it and please paste a screenshot.
Done (4 snapshots!)Sorry, that is the wrong path :-$
See example screenshot d-feet.png, take note the path includes "block_devices". If the disk is recognized, you should see your sdg1 disk there and using the Mount/Unmount functions you can try to mount/unmount the disk directly from d-feet. use {} as parameter of the calls.
Finally, one more thing. Open KDCOP, search for kded -> mediamanager -> fullList function (going by memory here, may be slightly different name). Double click to execute. In the result section, you will have a list of known disks. Can you find your disk there? If so, can you paste a screenshot of the properties of that disk?
You get another snapshot
See example screenshot kdcop.png. You need to double click fullList() function and search for your disk in the section below. This is to see if you disk has been detected by TDE or not.
It seems there may be something interfering with the first attempt of mounting the disk. Whether this is somewhere in TDE code or not, I am not sure. I will see if I can reproduce the problem here.
Cheers Michele
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2019/09/09 03:29 PM, Thierry de Coulon wrote:
Hello all,
Debian Buster with R.14.07 (Development). I have an external SATA to USB enclosure with removable discs. When I slip a disc in and turn it on, I get a Konqueror error (unable to mount this device, see attachment). However, I can mount it with no problem from the command line.
My guess is that it's a timing problem, Konqueror trying to mount something that is not yet available, but I don't know what to do.
I did not have this with Stretch and "stable" TDE, so it might also ave to do with de "Development" version.
Thierry
As an additional thought, it is possible that perhaps TDEHW is notified by udev of the existence of the new device before UDisks2 has created the related object path. Therefore an immediate attempt to automount the device would result in the error displayed in the original screenshot (object path /org/freedesktop/UDisks2/block_devices/sdg1 not existing). This would also be consistent with the fact that a later attempt to mount the device (even from Konqueror) works fine. I assume you have chosen to automount the device when inserted in the tde control center, right?
Cheers Michele
On Tuesday 10 September 2019 18.03:27 Michele Calgaro via trinity-users wrote:
As an additional thought, it is possible that perhaps TDEHW is notified by udev of the existence of the new device before UDisks2 has created the related object path. Therefore an immediate attempt to automount the device would result in the error displayed in the original screenshot (object path /org/freedesktop/UDisks2/block_devices/sdg1 not existing).
Sound plausible to me, as these disks do mount at a later stage
This would also be consistent with the fact that a later attempt to mount the device (even from Konqueror) works fine. I assume you have chosen to automount the device when inserted in the tde control center, right?
Humm... not really. I have "chosen" nothing (at least knowing I did). I may have said yes to mounting them the first time I got a popup window asking for it (which would explain why I get that window as root but not as user).
In storage media I have "Enable medium application autostart after mount" checked. "Mount automaticaly", "Read only" and "Quiet" are unchecked, "UTF-8" and "Mount as user" are checked, "Synchronous", "Access time updates" and "Flushed IO" show a minus, which I imagine means undefined.
Cheers Michele
Thierry
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
This would also be consistent with the fact that a later attempt to mount the device (even from Konqueror) works fine. I assume you have chosen to automount the device when inserted in the tde control center, right?
Humm... not really. I have "chosen" nothing (at least knowing I did). I may have said yes to mounting them the first time I got a popup window asking for it (which would explain why I get that window as root but not as user).
Hi Thierry, I have done some research in R14.0.x. Since your system tries to automap the disk when insterted, most likely you selected the option to automatically open the disk in Konqueror the very first time and then this is what is happening. No big deal though.
I have tried to replicate the problem here, but I am not able to do so. Do you see anything in your .xsession-errors log file that could give some clue (although you may need TDE compiled with debug options for that)?
Cheers Michele
-
deloptes -
Dr. Nikolaus Klepp -
Michele Calgaro via trinity-users -
Thierry de Coulon -
William Morder via trinity-users