[Unraid OS version 6.12.0-rc6 available]

On 5/25/2023 at 11:04 PM, baujahr said:

These changes need to be optional, I'm using Tailscale (via Docker) and a Wireguard tunnel to access the server and this has stopped smb and ssh from working.

Automatically adding the only Wireguard tunnel solves half of my problem as remote users access via Tailscale.

 

I understand that they are working on it for another release but there is a fix or configuration that i can set to make it work in the mean time?

Maybe in the Samba Extra configuration?

I use Wireguard to connect two servers in different locations and this will break things

[Unraid OS version 6.10.0-rc3 available]

On 3/14/2022 at 6:24 PM, ljm42 said:

 

Interesting. Did you find this documented anywhere or just figure it out?

 

I did try a lot of things in RC2 to no avail and then RC3 was out some days ago and i wanted to try it in case that my problem was fixed.

After upgrading i did have the same error, VMs and accessing shares from VMs, gui, dockers and such works fine but accessing shares from the network was very problematic so re-read the release notes and noticed that samba multichannel was enabled by default from RC2 onwards and i did 1+1. I searched how to disable it and voilà. I have LACP, i have no need for SMB multichannel.

 

I hope that devs put no a disclaimer or remove the "enabled by default". Maybe put an option and a notification in case you try to enable LAGG with smb multichannel enabled

[Unraid OS version 6.10.0-rc3 available]

So, i had the same problems that i had with RC2.

When i upgraded i had a big problem with File transfers, the transfer will work for 1-2 seconds and then drop to 0 and hangs.

Turns out that was samba multichannel that was added in RC2 and enabled by default

 

If you have a LAGG setup of any kind (in my case was LACP or 802.3ad) you can have problems with samba multichannel;

just add:

Quote

server multi channel support = no

in Settings -> SMB -> Samba extra configuration

 

That solved my problems, I think you should add a warning when tou enable any nic bonding

 

[Unraid OS version 6.10.0-rc2 available]

I have a weird "bug" since i upgraded to RC2 from RC1

My network connection on the server goes "down" every now and again.

What happens is, for example, I copy a file from unraid to my machine at 100 something mb/s then at mid transfer goes to 0 byte/s and then restart after a while. This happen on Win10, 11 over wired or wireless. I tried in a VM on my Unraid server and the transfer has no issues.

Web interface works fine even during the 0byte/s interval

What i tried:

- Changing MTU back to 1500 on UNRAID, switch and machines - changed nothing

- Changing network card on the client - nothing

- Upgrading from 10 to 11 on a client - nothing

- Update driver on network card on client - nothing

- Restarting both clients and unraid - nothing

 

My config:

Supermicro X9SRL-F with a Xeon E5-2670 and 64gb ram

2x intel 82574L gigabit onboard with a LACP bond that worked fine up to RC1

8 disks, various sizes with 1 parity

1 cache nvme ssd

 

I will try to disable the bond next but i need it and it worked fine up to RC1

I attached diagnostics

unraidsrv-diagnostics-20211113-1517.zip

 

EDIT: nope, its not the bond, problem occurs even with just one cable connected and bond removed

EDIT2: i tried with a broadcom nextreme II that i had laying around and i have the same problem. I also tried safe mode to no avail. I guess ill just revert to RC1 for the moment

EDIT3: i can confirm that on RC1 i do not have the problem and everything works fine except my win11 vm that I created on RC2 but i can understand that because the TPM template was added in that version

[Unraid OS version 6.9.0-beta22 available]

I dont think its a general support issue... i explain:

 

I had the time to restore the usb backup i made before installing the beta 22.

Now i can delete the docker and with the beta i couldnt and now the scrub works instead of stopping with 0 seconds and aborted as status.

 

[Unraid OS version 6.9.0-beta22 available]

Not sure if anyone posted this already but i installed the beta a couple days ago and im getting a strange behavior with dockers.

First time half the dockers running just didnt work anymore out of the blue giving me errors of read-only file system. Restarted the server and everything worked.

Recently i tried to update Handbrake and in the middle of the update gave up errors of read only file system.

The docker now is present in the list with a questionmark and a "not available" on the version column and i cannot remove/reinstall it. It gives me a generic server error.  I tried even to remove it from the terminal:

root@UNRAIDSRV:~# docker rmi cf94ba0a9bd0
Error response from daemon: open /var/lib/docker/image/btrfs/.tmp-repositories.json462281471: read-only file system

Or reinstall it to no avail

 

Not sure if this could be the beta build or something else.

 

One more thing: if i go in Settings -> Dockers and i do a Scrub it just doesnt start. Duration 0, status aborted with or without correct file system errors