[Unraid OS version 6.12.0-rc7 available]

15 minutes ago, bonienl said:

Do you have netbios enabled?

Problem with netbios is twofold (1) it doesn't support ipv6 and (2) it wants to use a broadcast address, which doesn't exist on a tailscale tunnel.

 

Netbios needs to be disabled and use WSD instead for host discovery.

 

 

 

well... just shoot me lol.. i wasted so many hours trying to figure this out.... i am eternaly gratefully sir..

[Unraid OS version 6.12.0-rc7 available]

2 hours ago, bonienl said:

Just tested zerotier (again) and SMB works fine.

Make sure you have correctly set up the zerotier address under Network Extra.

 

 

well this is what i got.. and when i run mount i get the error..
 

 

 

 

 

 

[Unraid OS version 6.12.0-rc7 available]

i'm really hoping there will be a fix for the smb issue..

before going to 6.12 (and all rc's above) the smb through zerotier was working perfectly between my 2 servers..

now its not.. i also have to do a manual tailscale set --accept-dns=true everytime i reboot else the dns will not work.. even though i have it set to yes in the tailscale settings..

[[6.8.3] docker image huge amount of unnecessary writes on cache]

On 8/21/2021 at 2:14 AM, TexasUnraid said:

 

While this works, it is not the proper way to do it as it does not keep everything contained inside the container.

 

The proper method is like was explained in the guide here:

 

Simply add this to the Extra Parameters of the container settings and it will create a ramdrive in the container mounted at /tmp.

 

--mount type=tmpfs,destination=/tmp,tmpfs-size=256000000

 

This prevents the container from mistakenly causing issues with the host system and can also limit the max size of that containers /tmp data. The last argument is the size, that is 256MB in the example.

 

Either way will reach the same result of causing the writes to go to ram. The above is just the native method for docker.

 

 

do you have this for normal intel ssd as well?

[[6.9.x - 6.11.x] intel i915 module causing system hangs with no report in syslog (not alder lake)]

and just had another crash.. funny thing is that i was opening the share without any issues. and 5 minutes later wanted to open unraid's page but it no longer responded.. 

[[6.9.x - 6.11.x] intel i915 module causing system hangs with no report in syslog (not alder lake)]

well it seems i also got this issue..

i miss 2 hours as you can see in the log i write to app pool:

 

Jan 18 08:02:41 Plex emhttpd: read SMART /dev/sdg
Jan 18 08:31:09 Plex webGUI: Successful login user root from 
Jan 18 10:02:17 Plex kernel: mdcmd (36): set md_write_method 1
Jan 18 10:02:17 Plex kernel: 

 

so the only fix seems to be disabling the i915 in total?

[[6.10.0 RC1] Rocket Lake S iGPU - Hardware Encoding/Decoding]

And how is the 4k working with transcoding? And with the HDR tonemapping?

[[6.10.0 RC1] Rocket Lake S iGPU - Hardware Encoding/Decoding]

Damn... And here i was thinking that upgrading to 6.10rc1 would fix my Plex 4k transcoding issues...

 

And for a brief moment I thought it was like that... Going raw into a 4k file of 65gb transcoding to 1080p 20mb/s.

Worked like a charm.. until I saw the CPU at 75% usage and no hw being used by Plex.

 

I really hope some1 has a way to fix this without having to rollback to 6.9 2.