Akilae

Members
  • Posts

    13
  • Joined

  • Last visited

Akilae's Achievements

Noob

Noob (1/14)

4

Reputation

  1. I'm not able to get any faster speeds than around 7Gbit on this card (also I'm not able to turn off flow control). I'm not testing SMB yet it's just iperf3 bandwidth. SMB is even slower. What can I tune / do different? Diagnostics are attached. I tried it using a client with Windows / Ubuntu using an asus xc100c v2 card. The client is using a Ryzen 9 5950 CPU and the server is using an Intel i5-12500T CPU. Both are not at all under load during my tests. Physical Layer: I'm using CAT8.1 cabling in my house and also tried a directly connected CAT7 cable from the client to the server (10m). Both provide the exact same results. nas01-diagnostics-20230718-1602.zip
  2. Since RC4(1) my server looses internet connection after a few minutes of runtime. While VMs are still running, most docker containers and especially the server itself aren't able to connect anymore. If you connect using ssh it's possible to ping outside or resolve domains. My diagnostics are attached. nas01-diagnostics-20230429-2321.zip
  3. Ah, this makes absolute sense. Yes, I have a running script which is getting the keyfile from a SMB share (which is currently not active), but the deletion script is still running. Thank you for pointing me in the right direction. It works now.
  4. I upgraded to rc2, stopped the array to set one of the disks to ZFS - encrypted. -> didn't work for said reason. I restored back to 6.11.5 and waited for rc3. I now did the same again, updated to rc3. Tried to format to ZFS - encrypted -> didnt work. Then I tried creating a ZFS non-ecrypted filesystem. This worked without issue for me. Then I set the disk back to ZFS - encrypted -> didn't work. Then I emptied another disk and set it to ZFS - encrypted. -> didn't work aswell. I've attached my diagnostics. nas01-diagnostics-20230420-0148.zip
  5. Now that rc3 is out it seems that the bug described in this thread is still not solved.
  6. Hello everyone, I've experienced the following behavior after using vlans on unraid. I create a vlan enabled network bridge (br0). Now my br0 behaves like a trunking port and receives every vlan which my network switch provides. If I manually create a tagged vlan now on my br0 (i.e. br0.12) what I would expect is that I receive traffic for every vlan (untagged and every vlan aside of br0.12) on br0 while being directly able to assign vlan br0.12 for example to a docker container or VM. The actual behavior is the following: I receive untagged traffic on br0. I receive tagged (VLAN 12) traffic on br0.12. Every other VLAN gets stripped away. Now my question. Is this an intended behavior? If yes, is it possible to use maybe two network bridges on the same nic? Why is this an issue for me: I would like to use vlans on unraid for the docker containers / VMs without loosing the possibility to host a Firewall VM on the same nic. I do not have the possibility to use a second nic on this system. Best regards,
  7. Hey, @ich777, here are my Diagnostics. I'm also not sure if there wasn't an issue using 6.10.0rc4. It was simply a release where I had no freezes for about 20 days until rc5 was released. Also, I tried to use ipvlan and everything "seems" normal up to a point when Docker isn't able to connect to github anymore, container updates are failing, etc. I doubt that my Sophos Firewall is the issue here tho. nas01-diagnostics-20220609-0835.zip
  8. I also have to report that on my Skylake the freezes are only happening while the igpu is not blacklisted. Everything is stable when there is no transcoding happening (means: /dev/dri is not forwarded to plex or the igpu is blacklisted as whole). Everything was fine with 200+ days uptime on 6.8.3 like I wrote earlier in this thread. I thought that using a dummy plug fixed my issues on 6.10-rc4 but after that the freezes where back. Greetings from Vienna btw ;).
  9. Hello, I just wanted to follow up on my earlier post in this thread, the error is back. It unluckily wasn't just a hickup and I had to remove /dev/dri from plex completely to stop the freezes. What can we do from here on? As I have read there are some reports that Kernel 5.18 will fix the issues, is this just for Alder Lake or should that be a possible fix for Skylake as well? Best regards,
  10. Yes, syslog logs to a share and is capped to 500MB Tautulli shows a transcoding action within 4 minutes to the last available syslog entry before my hard reset. Also the user was only able to watch 2% of the show, so I guess that was when the crash happened. I see, thank you for the information. If I can provide any additional information just tell me.
  11. No I'm not sure, I'm sure that my GPU was the issue in the past up till the hdmi dummy. I literally changed everything incl. rmaing the memory sticks and memtesting the new ones for 2 days. Most amount of time online until a crash without any log entry where about 3-4 days at max. Then I read your recommendation with the HDMI dummy, added this to the system and instantly reached many days uptime without any crashes. Now I installed rc7 without any changes to my system and it crashed after only 1 day, also without any log entry again. That's why I instantly thought the issues are back.
  12. After having (at least I tought) solved this issue in rc5 (had an uptime since the release of rc5) by adding an hdmi dummy to my i7-6700K setup I had the first crash after only 1 day of uptime on rc7. Did anything change regarding that matter in rc7?