Synd

Hi Team, I was trying to add VLANs to replicate smdion's bug and it caused another issue from my side. Been able to add a 3rd VLAN, but each time I try to add a 4th, I get this error, which doesn't seem that it should happen. Thanks, Synd megumin-diagnostics-20250403-1633.zip

Hi, since I upgraded to 7.0 beta 3 (does it still in beta 4). I get the following spam every 5 mins in my logs. Oct 22 14:10:13 Megumin kernel: eth0: entered promiscuous mode Oct 22 14:10:14 Megumin kernel: eth0: left promiscuous mode there's no logs in my switches about port disconnecting, and the network config I currently run hasn't changed since unraid 6.8. including also my switch log to show that Fo1/1/1 (eth0) or Fo1/1/2(eth1) doesn't disconnect at all in those times. The update to beta4 is the only logs i have about those in my logs. It's more of an annoyance as it's not doing anything on my unraid. Thanks, Synd megumin-diagnostics-20241022-1500.zip

Hi, Since 6.11.5 upgrades, each time I run a parity check, write to the array or use the mover, the parities are running at 60-70MB/s, while before the upgrade, it was at 170-180MB/s. The system is all connected on SAS3 equipment, but we've seen the same issues on Discord with others running SAS2, or Direct connect. I included my diagnostics, and others will do as well, as we talked on Discord to give as much data points about this. I don't spindown or anything. I run write reconstruct all the time, but it's almost like the setting doesn't work at all anymore. This is a bug that impacts AMD only. There was a regression in kernel 5.19 about dummy waits that caused to impact AMD CPUs. (https://www.phoronix.com/news/Linux-6.0-AMD-Chipset-WA) Thanks. megumin-diagnostics-20221221-1116.zip

Hi, I was doing tests with the rc3n/o versions and it did this as well. My Nic is getting renamed from either eth1 to eth3 or the opposite each time I reboot the system. I've changed the assignation from eth4/5 to eth0/1 during the RC2 cycle, and once I went on Test versions (n or o) or RC3, it started doing this issue on reboot. I also see the NICs in my network_rules.cfg in double on some reboots. I uploaded diagnostics of 2 different reboots for this to show the issues i'm hitting as well. My config is running the Mellanox Nics in LACP as it's how my switches only allow bonding. Thanks, Synd. megumin-diagnostics-20220310-1650.zip megumin-diagnostics-20220310-1321.zip