![]() ![]() I then found this thread and tried the suggestion in the second post. #Htc permissions reset installI tried to install the plugin version instead and that failed, again saying permissions were too lax. However, after creating the jail, I opened a shell in it and was presented with nothing: none of the usual messages, no prompt, no flashing cursor. ![]() I assumed that this would set permissions to whatever the default values are in a new jail, which would hopefully fix the problem. #Htc permissions reset manualI deleted the existing Plex application jail and tried to reinstall it the way I'd installed it before, in a manual jail rather than as a plugin. datasets won't really care that much about file permissions (I should note that this is a home server, I'm the only user, and it's not accessible from outside of my home LAN) so hopefully I can just leave them in whatever state they're in now. Plex is more of a problem, but since I'd already followed some tips here and separated the Plex server data from the server installation (data's held in a separate dataset outside of the jails set), I figure I've got a reasonable chance of getting that running again without losing too much data. I immediately gave up on Nextcloud and Resilio, as my use of both of them is pretty simple and, once I'm able to get plugins running again, won't take long to set up again. I therefore apologise to anyone reading this for wasting their time with my stupidity and ask humbly for advice on fixing it. I therefore tried to change the permissions for the jails to something more restrictive (I think I tried 755, 770 and maybe 750).Ī little googling has revealed that I've almost certainly screwed everything up by forcing those permission changes. This failed, with an error message about the permissions (775 at this point) being too lax. This didn't help either, so I figured I'd just delete the jails and recreate them using the new FreeNAS interface. This did nothing, so (here's the dumb part) I did the same thing at the volume level. For some reason, I thought my new problem was caused by something similar, so I tried doing the same thing with the jails for the plugins. The solution has always been to recursively reset the permissions from the root of the dataset (I've never managed to work out the root cause, but this usually fixes things for a few weeks). I frequently find that my Windows PCs are restricted to read-only access when I try to delete or rename files in my various datasets (media, backups, Windows file history, etc.). Today I noticed that two of my plugins weren't working (Nextcloud and Resilio, both installed pre-11.2). #Htc permissions reset updateA few days/weeks ago I was notified that there was an update to 11.2.U4: I left it for a few days, then installed it yesterday. My system's running FreeNAS 11.2, having upgraded in-place from 11.1. Is there any way to fix it without deleting and recreating the volume? TLDR version: I messed up the permissions on my only volume. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |