-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automount mounts in Read only #237
Comments
Hi, try creating a config file at device_config:
- id_type: vfat
options: [rw]
sorry, I really ought to improve documentation, but not seeing it happen soon. Any PRs of course appreciated. |
In that you have Usb's in arch have been my bane so far. 😭 |
As default for all FS: device_config:
- options: [rw] (but usually always get rw by default anyway except NTFS, so it's a bit weird that it's not the case for you) |
Actually it's really weird. I'll mount it with udisks. check with |
Think I may have figured it out
I would like it to |
Yep, looks like theres some underlying issue. Found this on dmesg after it swapped to read only |
Gonna just format the drive and see if that fixes anything |
Good luck! |
For some reason I'm having trouble with udiskie opening my container as read only.
|
Hi, thanks for your input.
Your case is a bit different, because you're working with a loop device. I can reproduce this example and have a fix for it. It boils down to the fact that udiskie currently doesn't bother with the Was the loop device the original scenario in which your problem occurred, or just a believed minimal-working-example?
Yeah, that's because, currently, udiskie always sets up the loop device as readonly.
Just FYI, this is not causing the problem in your example, but: device config is a list, and options are given in rule entries, so there is a device_config:
- options: [rw] |
I actually do have some LUKS containers like above that I use for storing various keyfiles etc.
Ah thanks for spotting that. In any case I think your above explanation is quite likely because I also tried with If the fix is easy that'd be really cool as udiskie is a nice little portable program for this purpose. |
a quick-and-dirty fix itself is relatively easy. Making it configurable (whether rw/ro should be used) is more effort. So that'll probably take a while, but I can for now release a version that will make RW the default if sufficient permissions are available. |
I wonder if this is related?
In this case I was trying to decrypt my 3rd partition on my NVMe. |
Unrelated. Probably same as #220. |
Closing this since the original issue was probably due to faulty device. |
I have a vfat USB. Running Arch + Bspwm
When udiskie automounts it, the filesystem is read only.
I started udiskie with the
-s
option, and have not created a custom config file.udiskie -s
When I mount the USB like so
usdisksctl mount -b /dev/sdc1 -o rw
it works fine.This may just be a user error. But any support would be much appreciated. I search for 3 hours, and didn't find many useful threads or wikis.
The text was updated successfully, but these errors were encountered: