FrostyWolf

Members
  • Posts

    36
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

FrostyWolf's Achievements

Noob

Noob (1/14)

2

Reputation

  1. I'm still having this issue. I messed around a bit today and I still can't figure this out... Die Hard (1988).mkv - When I connected to my server via samba share, I can edit, delete, etc this file Nobody (2021).mp4 - When I connected to my server via samba share, I get the you need permission error If I run Fix Permissions, I can then access both. I'm not linux vet...but don't they have the same permissions? What is fix permissions doing that lets me then access it? EDIT: After some more digging, the issue seems to be with the directory permissions: And just to show: I am not doing anything with permissions with radarr (or any container) and this happens on all files, not just movies. Also: Umask is off in nzbget, which is where the files came from. When I run the umask command in terminal in unraid, it is set to 0000 for /mnt/, /mnt/user, and /mnt/user/Movies I do not understand where and why these permissions are getting set from on new directories. You can see the same thing is happening in /mnt/user/downloads/ March 30th was the last day I ran fix permissions, everything after that doesn't have write access. A Band-Aid fix is I can tell radarr/sonarr/etc and go through every single one of my containers that has the option and set them all, but I want to understand why this is suddenly happening for everything.
  2. It's because the mount is flagged NOEXEC. You can chmod it yourself to fix it, but the problem will keep coming back everytime it tries to update the codec. I have no idea what causes this and I am in the same boat as you.
  3. Maybe I'm not explaining this correctly. Any file that gets written to any share on the server, by anything, I can not access till I run New Permissions. After I run New Permissions, I can not access any file written after the last time I have run it. It does not matter what creates/writes the file. It happens in all my shares. SWAG updates and gets new conf files? I can't edit them. Deluge/nzbget download a file? I can't touch it. Sonarr/Radarr move that file to the array and rename it? I still can't touch it there. All of my shares are public. My guest account in unraid is showing Read/Write for all of them.
  4. Yes. I keep them secure by having them on a VLAN segregated on my home network that only one admin laptop can access.
  5. I understand where you are coming from, but my server hasn't had a issue running for a couple of years, and recently it now does this for all files, from 15 different dockers. I have to run New Permissions twice a week to fix things. I feel like this is something wrong deeper then a misconfigured docker container. I've never messed with permissions in any container before. They are all pretty much stock installs. If everything is causing it wouldn't the common factor be the account trying to access it, not whats writing the files? This is in the array, on both cache arrays. It's all appdata files. It's everything. I can not delete/edit files that have been written since the last time I have run New Permissions. Everything I try to do gives me the "You Require Permission from Unix User\nobody" error. Is it possible my guest account or whatever account gets used for Samba shares has been corrupted?
  6. I dunno if this is related, but I'm having other issues that seem to tie into permissions. Plex for instance is throwing this error cause it can't replace the codec files with the new ones. I have to stop the docker, run new permissions, then start it back up again so it can properly replace the files. Also, this goes with all my files, not just some. Literally any new file on my array or appdata.
  7. When ever a new file or folder gets added to appdata or my array, when I try to access it via samba share I get this: I then have to go to tools, run and run "New Permissions" to fix it. This happens no matter what docker creates the files or folder. I don't even know where to begin tracking down what is going on.
  8. That's what I was following, and things def don't work as I excepted on 6.9.0-rc2. I started with 1TB cache and wanted to upgrade it to 2 x 2TB in a Raid 1. I added one 2TB to the 1TB, and let it complete it's balance operation. What I expected was a 1TB cache, now mirrored across the 1TB and 2TB drive. What I got was a 2.5TB cache? I then tried to drop the 1TB and replace it with the 2TB, which lead to a error telling me too many missing disks. I then added the 1TB back, and then added the 2nd 2TB, so the cache pool was 2 x 2TB and 1 x 1TB. This resulted in a 3.5TB cache (?????). After that, I tried to drop the 1TB, and still got the same too many missing disks error. I fixed it by converting it to a Raid1c3, then dropping the 1TB, then converting it back to a Raid 1, which resulted in a 2 TB raid 1 cache.
  9. I am currently on 6.9.0-rc2 I have 3 drives in my Cache. I would like to remove the 1TB drive, preferably without having to move my entire cache to the array, then rebuilding the cache and moving it back. Is there anyway to do that?
  10. Ok thank you, I'll ask in main unraid support then.
  11. I asked about this over on and they say it's more of a unraid issue then a transmission issue.
  12. I am getting a bunch of: I believe this info might be helpful reading other people that have this same issue: Not sure how to proceed.
  13. I installed Tautulli and it did its thing but it never showed up under Dockers. Now if I try to install it, I get this message: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='tautulli' --net='bridge' -e TZ="America/New_York" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/tautulli/config/':'/config':'rw' -v '':'/log':'rw' 'tautulli/tautulli' /usr/bin/docker: Error response from daemon: invalid volume spec ":/log:rw": invalid volume specification: ':/log:rw'. See '/usr/bin/docker run --help'. The command failed.
  14. My old array was drivepool. These drives are from that. Since drivepool was in windows, it was probably just me accidently missing the shift key when I made the folder on that particular drive. It never got noticed cause windows doesn't care about case. The drive is a 8 year old 3TB WD green, one of the oldest drives in my previous array. After the data is off of it I'm just going to be formatting/testing it and then reusing it elsewhere in the house.
  15. So I'm in the middle of transferring data over from my old array (drivepool) using Dolphin and I didn't notice till I started the copy that one of the Movies directories had a lowercase "m". It's still in the middle of the transfer now (2.95TB) but when it is done, how to I go about fixing this? It seems like it also made a new share as well. Can I just used dolphin and move the contents from "movies" to "Movies" then delete the directory/share?