-
Files uploaded via NFS Mount have wrong user and Permissions ("drwxr-xr-x" for Directories and "-rw-r--r--" for files)
You are a hero!! You explained the process clearer than any of the guides I found. Mounted a share and it worked perfectly. And with the serverside SMB config it creates everything as it should!! (also I added a link to your post to the comments of my fstab for future reference :D) Thank you both so much!!
-
Files uploaded via NFS Mount have wrong user and Permissions ("drwxr-xr-x" for Directories and "-rw-r--r--" for files)
I cannot get SMB automounted, that is why I switched to NFS when I manually connect to the SMB server I can enter username and password, and everything works as intended. But whenever I add the Share via FSTAB I get a 177 error that implies I don't have write access. //<server>/<share> /mnt/unraid/<sharename> cifs defaults,credentials=/home/<user>/.smbcredentials,rw 0 0 and //<server>/<share> /mnt/unraid/<sharename> cifs defaults,credentials=/home/<user>/.smbcredentials,,uid=99,gid=1000,iocharset=utf8,vers=3.0,nofail,rw 0 0 Both produce the following error when trying to write a file All Shares that I didn't mount but authenticated manually in dolphin with the same credentials still work....
-
Files uploaded via NFS Mount have wrong user and Permissions ("drwxr-xr-x" for Directories and "-rw-r--r--" for files)
I have decided to switch to Linux from Windows a month ago, and therefore mounted the Shares via NFS. I use the following config (removed IPs and names just to be save): Export as Private with the following rules: <ipofclient>(async,no_subtree_check,rw,sec=sys,anongid=100,anonuid=99,root_squash) and in my fstab i have the following mount <ipofserver>:/mnt/user/<share> /mnt/unraid/<sharename> nfs hard,timeo=50,retrans=5,relatime,rsize=1048576,wsize=1048576 0 0 Whenever I create a file it is owned by the user I am using on my linuxbox (the username exists on unraid as well) and has the permissions drwxr-xr-x" for Directories and "-rw-r--r--" for files. Other things I tried so far: - nfs4 instead of nfs - no difference - umask=022 - error when trying to mount the share I read in some spaces that i should use setfacl to enforce permissions but I haven't found a guide to acl yet that gave me the confidence of messing around with permissions for my shares. I also noticed that when I use docker apps (i.e double commmander) created folders and files get the same permissions but at least the user is set to nobody instead of my username, so it might be a general setting in unraid that is wrong. I am currently running Unraid 7.2.0
-
[SUPPORT] Allthemods10 & ALLthemods10-TTS
Something seems to be not quite working. When I delete the Zip it still downloads the 4.2 version: curl -Lo Server-Files-4.2.zip https://mediafilez.forgecdn.net/files/6696/937/ServerFiles-4.2.zip Any way I can force it? Edit: Nevermind - it Updated over night.
-
[Support] ich777 - Application Dockers
I have an error in Sonnarr that looks rather weird to me since the Log demands an .exe: 24/04/2023 11:06:55 ---Successfully downloaded Sonarr v4.0.0.455--- 24/04/2023 11:06:55 mkdir: cannot create directory ‘/sonarr/Sonarr’: File exists 24/04/2023 11:06:56 ---Preparing Server--- 24/04/2023 11:06:56 ---Starting Sonarr--- 24/04/2023 11:06:56 Cannot open assembly '/sonarr/Sonarr/Sonarr.exe': No such file or directory. 24/04/2023 11:07:48 ---Ensuring UID: 99 matches user--- 24/04/2023 11:07:48 usermod: no changes 24/04/2023 11:07:48 ---Ensuring GID: 100 matches user--- 24/04/2023 11:07:48 usermod: no changes 24/04/2023 11:07:48 ---Setting umask to 0000--- 24/04/2023 11:07:48 ---Checking for optional scripts--- 24/04/2023 11:07:48 ---No optional script found, continuing--- 24/04/2023 11:07:48 ---Taking ownership of data...--- 24/04/2023 11:07:48 ---Starting...--- 24/04/2023 11:07:48 ---Version Check--- 24/04/2023 11:07:48 ---Sonarr not found, downloading and installing v4.0.0.455...--- 24/04/2023 11:07:49 /sonarr/Sonarr-v4.0 0%[ ] 0 --.-KB/s /sonarr/Sonarr-v4.0 17%[==> ] 16.33M 81.6MB/s /sonarr/Sonarr-v4.0 41%[=======> ] 39.55M 98.9MB/s /sonarr/Sonarr-v4.0 65%[============> ] 61.38M 102MB/s /sonarr/Sonarr-v4.0 88%[================> ] 83.82M 105MB/s /sonarr/Sonarr-v4.0 100%[===================>] 94.35M 105MB/s in 0.9s 24/04/2023 11:07:49 ---Successfully downloaded Sonarr v4.0.0.455--- 24/04/2023 11:07:49 mkdir: cannot create directory ‘/sonarr/Sonarr’: File exists 24/04/2023 11:07:51 ---Preparing Server--- 24/04/2023 11:07:51 ---Starting Sonarr--- 24/04/2023 11:07:51 Cannot open assembly '/sonarr/Sonarr/Sonarr.exe': No such file or directory. I don't know when this started but a reinstall of Sonarr didn't help.. I haven't changed any configs but had autoupdate enabled on Sonarr. Sorry if this already has been discussed, I couldn't find anything via google other than a 3 year old post where the problem resolved itself on github.
-
You need permission from \nobody to make changes to this file.
Just took the time to run the check with just the -v flag nothing changed.
-
You need permission from \nobody to make changes to this file.
But shouldn't it at least tell me if something is wrong?
-
-
You need permission from \nobody to make changes to this file.
Hello everyone I have spent several hours googling, searching the forums and trying things but nothing helped. Some files on my Array (well in the share I backup my onedrive to from my Windows Machine, but i am certain the error will crop up on other shares at some point) throw the following error Other files on the same Share work without problems. I did try to use Syncthing at one point but the Scan of the Folder took so long every time, that it wasn't feasible. I am not 100% sure but it might be that the errors started back when i was testing that. I just didn't want to delete everything on my Unraid instance unless I have to, especially since I have some symlinks pointing at folders inside my onedrive backup for the foundryvtt instance I am running. I tried the following fixes: Run New Perms The Perms are OK - everyone should be able to R/W according to my chek in Krusader: create a new user, that isn't in any way related to my windows login. Delete all saved credentials in windows several times. I think the files are all on disk2 so started the array in maintenance mode and rand the filesystem check but it didn't find any errors might have not done everything right here. basically added the -nv flag and ran the check in my webgui.
-
Flash is being Reported as Full in Main but 0B used in Dashboard
Replacement key shows up with full stats. Seems to have done the trick. I will likely replace the USB as well once I get my new Unraid build. Thanks a ton.
-
Flash is being Reported as Full in Main but 0B used in Dashboard
OK will do, got a few USB sticks to spare, but the only ones I have are also quite small Samsung ones, the full size USB sticks I have are all SanDisk - hopefully they are not of teh coutnerfeits. Got them from a reputable dealer here in Switzerland though. I hope they are fine.
-
Flash is being Reported as Full in Main but 0B used in Dashboard
I switched my Unraid to a new (temporary) Box about a week ago, since then my Flash gets filled up within about 24 hours of a reboot and the log is filling up rather quick as welll. In Dashboard the Flash is shown as 0B used / 0B free. The Flash itself is only around 500MB, so nowhere near full. I tried multiple USB Ports (both 2.0 and 3.0) and the behaviour stays the same. Any tips what I should check next, or will I have to do regular reboots until I can get new hardware? Or is it "just" my USB failing? mainframe-diagnostics-20220206-2140.zip
-
Unraid 6.9.1 - var/log full after 4 days + Docker Corruption
Will do. I just rebuilt the docker image and reinstalled the docker apps. I have been planning on upgrading the servers hardware sometime anyway. Some of it is nearly 10 years old. I might just do it a bit sooner than planned. I did have to do a hard reset though, as the Interface didn't let me shutdown or reboot. Running parity checks now.
-
Unraid 6.9.1 - var/log full after 4 days + Docker Corruption
I actually didn't reboot the system for 4 days. I will try and get better diagnostics next time. Thanks
-
Unraid 6.9.1 - var/log full after 4 days + Docker Corruption
After years of smooth sailing, I started having problems with Unraid lately. My Docker Image corrupted 3 times in the last month and after the last reboot the var/log filled within 4 days. I have a suspicion, that my cache drive could be the culprit for the Docker Corruption. I don't know why the var/log fills so fast though. I attached the diagnostics as per this morning to the Post and would be very thankful if someone here has a solution or at least can point me in the right direction. Thanks in advance!! mainframe-diagnostics-20210705-0830.zip
Sam_Axe
Members
-
Joined
-
Last visited