Leaderboard

They just need to push Samba 4.9.5 before 6.7 final. It fixes this bug. https://www.samba.org/samba/history/samba-4.9.5.html @limetech

Allocation method is independent of split, and split takes precedence.

Yes. The first entry corresponds to some large number. The last entry corresponds to level 0. The ones in between correspond to levels 1 to 5.

This is a critical issue for me, a NAS that can't act as a NAS is somewhat pointless. Seems to be a Samba 4.9 issue which 6.7 introduces. https://bugzilla.samba.org/show_bug.cgi?id=13697 As suggested in multiple places (https://lists.samba.org/archive/samba/2018-September/218485.html) running net -s /dev/null groupmap add sid=S-1-5-32-546 unixgroup=nobody type=builtin fixes the problem. I've added this to my /boot/config/go script. However I am not 100% comfortable with this as not clear if this is going to cause other issues and the mapping created doesn't actually match the errors, but will run rc5 like this for now and see if anything crops up.

The permissions can be decoded as follows: r = read permission w = Write permission x = Execute permission (Need this to even run .exe. as file extensions have no special meaning to Linux.) - = Permission denied for this attribute (You will note that there are three groups of rwx permissions. The first group is for the owner (nobody), the second is for the group (users) and the third is for all others.) Thus, you do not have write access to these files (which you need to delete them) as you are a member of the users group! I believe you have the Fix Common Problems plugin installed. You should also have the Docker Safe New Perm tool installed ( Tools >>>> Docker Safe New Perm ). Run that tool and see if you can delete the files then. If so, figure out what Docker or plugin created those files as it is improperly configured.

The parity Check Tuning plugin is now available (as long as you are running Unraid6.7 rc4 or later) that allows you to run a parity check in increments spread over several days. See the forum Support thread for more details. Interesting point. If you have already scheduled parity check increments to run in system idle times I am not sure how much value this would add? It is worth adding to the Wish List for the plugin as it does feel it should not be too difficult to implement if a strong case is made for including such a feature.

Any updates on this thread. I am also experiencing this issue. I request to make this thread change from Minor to Urgent. Due to not being able to access the NAS via SMB it is a showstopper in my humble opinion

#!/bin/bash #This should always return the name of the docker container running plex - assuming a single plex docker on the system. con="`docker ps --format "{{.Names}}" | grep -i plex`" echo "" echo "<b>Applying hardware decode patch...</b>" echo "<hr>" #Check to see if Plex Transcoder2 Exists first. exists=`docker exec -i $con stat "/usr/lib/plexmediaserver/Plex Transcoder2" >/dev/null 2>&1; echo $?` if [ $exists -eq 1 ]; then # If it doesn't, we run the clause below docker exec -i $con mv "/usr/lib/plexmediaserver/Plex Transcoder" "/usr/lib/plexmediaserver/Plex Transcoder2" docker exec -i $con /bin/sh -c 'printf "#!/bin/sh\nexec /usr/lib/plexmediaserver/Plex\ Transcoder2 -hwaccel nvdec "\""\$@"\""" > "/usr/lib/plexmediaserver/Plex Transcoder";' docker exec -i $con chmod +x "/usr/lib/plexmediaserver/Plex Transcoder" docker exec -i $con chmod +x "/usr/lib/plexmediaserver/Plex Transcoder2" docker restart $con echo "" echo '<font color="green"><b>Done!</b></font>' #Green means go! else echo "" echo '<font color="red"><b>Patch already applied or invalid container!</b></font>' #Red means stop! fi EDIT: Just corrected some flawed assumptions on the logic above. Using grep -i to grab container name so that it matches without case sensitivity. Using a variable to capture the return value of the stat, since docker exec -it can't be used and docker exec -i always returns 0. Flipped -eq 0 to -eq 1 since that was the inverse of the intended behavior. Only weird thing is something prints "plex" lowercase and I don't know where. EDIT2: Figured that out, docker restart $con prints the name of the container once it's restarted. Could redirect the output to /dev/null, though.

The built-in schedules can be seen and adjusted at Settings - Scheduler - Fixed Schedules