You are not logged in.
Posting this in OT as it's not likely to be Arch-specific but I want to narrow down the possible causes.
A recent sync to Manjaro from Arch stable has introduced a regression somewhere along the line - neither Xfce nor MATE will automount optical media [1]. Mounting manually with `sudo mount` works as normal. This is not something I've seen before, and there's nothing immediately obvious from web searches.
The issue is easily replicated with e.g.:
$ gvfs-mount -d /dev/sr0
This tool has been deprecated, use 'gio mount' instead.
See 'gio help mount' for more info.
Error mounting /dev/sr0: Error mounting /dev/sr0 at /run/media/jonathon/dvdimagename: Mount syscall failed: 13.
Essentially, all I need to know is whether this can be replicated/is known on plain Arch. If not, it's a Manjaro regression.
[1] https://forum.manjaro.org/t/mount-dvd-e … d-13/26750
Last edited by jonathon (2017-06-29 20:47:47)
Offline
I'll leave this open until someone can verify or refute the regression on Arch Linux. I note that this is not a request for assistance with Manjaro.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Thank you.
I note that this is not a request for assistance with Manjaro.
I wouldn't do that to you - and I tell off any of our users who I see doing that. I do wonder about people sometimes though; there was one user recently asking for help with RHEL... (and another user who's on a mission to respond to posts with only video).
Last edited by jonathon (2017-06-29 20:31:12)
Offline
Same problem with Arch, trying to mount with gvfs-mount, gio mount, or udisksctl fails. The error message is always the same: "Mount syscall failed: 13". Mounting manually works fine.
Edit:
Heads-up: I'm not sure it was caused by trying to use gvfs-mount, gio or udisksctl and having mount fail but all of my mounted partitions have just been remounted ro with lots of dmesg spam which unfortunately was not saved to the journal.
I have booted into my "recovery" usb flash drive and checked all partitions and apparently there was no problem but I don't plan to test again until I can make a full disk image.
Last edited by R00KIE (2017-06-29 23:35:40)
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Thank you for checking this!
lots of dmesg spam
I haven't seen any dmesg errors on my Manjaro systems, but that doesn't necessarily mean anything.
Same problem with Arch
What's the right way for me to get awareness raised on this? I'm not sure I can do it myself (e.g. bug report) without it being summarily binned.
Offline
You can file a bug report and mention this thread in the report.
Offline
OK, fingers crossed they don't stop reading at "Manjaro".
Offline
Thank you for checking this!
lots of dmesg spam
I haven't seen any dmesg errors on my Manjaro systems, but that doesn't necessarily mean anything.
It wasn't right away, I tested it and kept working and after a while things started falling apart, complaining they couldn't access the disk or write. A quick look at the output of mount and the reason was obvious, the next step was try to check dmesg for any hints but the start of the problem as not even in the buffer anymore, that's how much spam there was. This made me worried for a little while until I could check everything was ok and I didn't lose anything important (I do have backups but I don't backup every hour ).
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
I have the same error with a SanDisk USB drive.
Offline
Same error here (with usb and dvd)
Offline
Since this has been verified to happen on Arch, I am moving this thread to "Applications and DEs".
Offline
Just to finish off the thread, this should now be fixed with libblockdev=2.10.
Offline