[Unraid OS version 6.10.0-rc4 available]

7 minutes ago, mdrodge said:

There are a few of us that have reported 2.5gb network issues with RC4 but as yet no one has acknowledged this.

So far it seems tied to the RTL8156, is this your chipset?

 

Mine is detected as RTL8125

 

[10ec:8125] 28:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller

 

[Unraid OS version 6.10.0-rc4 available]

I'm having lot of issues with my PCI-E add-in 2.5GB network card on RC4. It seems to be far worse once I start a VM (Windows 10). Is this a known issue?

 

Apr 12 14:15:24 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
Apr 12 14:15:24 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
Apr 12 14:15:24 bigbird kernel: device eth0 left promiscuous mode
Apr 12 14:15:24 bigbird kernel: bond0: now running without any active interface!
Apr 12 14:15:24 bigbird kernel: br0: port 1(bond0) entered disabled state
Apr 12 14:15:28 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
Apr 12 14:15:28 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
Apr 12 14:15:28 bigbird kernel: bond0: (slave eth0): making interface the new active one
Apr 12 14:15:28 bigbird kernel: device eth0 entered promiscuous mode
Apr 12 14:15:28 bigbird kernel: bond0: active interface up!
Apr 12 14:15:28 bigbird kernel: br0: port 1(bond0) entered blocking state
Apr 12 14:15:28 bigbird kernel: br0: port 1(bond0) entered forwarding state
Apr 12 14:15:40 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
Apr 12 14:15:40 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
Apr 12 14:15:40 bigbird kernel: device eth0 left promiscuous mode
Apr 12 14:15:40 bigbird kernel: bond0: now running without any active interface!
Apr 12 14:15:40 bigbird kernel: br0: port 1(bond0) entered disabled state
Apr 12 14:15:44 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
Apr 12 14:15:44 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
Apr 12 14:15:44 bigbird kernel: bond0: (slave eth0): making interface the new active one
Apr 12 14:15:44 bigbird kernel: device eth0 entered promiscuous mode
Apr 12 14:15:44 bigbird kernel: bond0: active interface up!
Apr 12 14:15:44 bigbird kernel: br0: port 1(bond0) entered blocking state
Apr 12 14:15:44 bigbird kernel: br0: port 1(bond0) entered forwarding state
Apr 12 14:15:46 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
Apr 12 14:15:46 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
Apr 12 14:15:46 bigbird kernel: device eth0 left promiscuous mode
Apr 12 14:15:46 bigbird kernel: bond0: now running without any active interface!
Apr 12 14:15:46 bigbird kernel: br0: port 1(bond0) entered disabled state
Apr 12 14:15:50 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
Apr 12 14:15:50 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
Apr 12 14:15:50 bigbird kernel: bond0: (slave eth0): making interface the new active one
Apr 12 14:15:50 bigbird kernel: device eth0 entered promiscuous mode
Apr 12 14:15:50 bigbird kernel: bond0: active interface up!
Apr 12 14:15:50 bigbird kernel: br0: port 1(bond0) entered blocking state
Apr 12 14:15:50 bigbird kernel: br0: port 1(bond0) entered forwarding state
Apr 12 14:15:52 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
Apr 12 14:15:52 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
Apr 12 14:15:52 bigbird kernel: device eth0 left promiscuous mode
Apr 12 14:15:52 bigbird kernel: bond0: now running without any active interface!
Apr 12 14:15:52 bigbird kernel: br0: port 1(bond0) entered disabled state
Apr 12 14:15:56 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
Apr 12 14:15:56 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
Apr 12 14:15:56 bigbird kernel: bond0: (slave eth0): making interface the new active one
Apr 12 14:15:56 bigbird kernel: device eth0 entered promiscuous mode
Apr 12 14:15:56 bigbird kernel: bond0: active interface up!
Apr 12 14:15:56 bigbird kernel: br0: port 1(bond0) entered blocking state
Apr 12 14:15:56 bigbird kernel: br0: port 1(bond0) entered forwarding state
Apr 12 14:15:57 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
Apr 12 14:15:57 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
Apr 12 14:15:57 bigbird kernel: device eth0 left promiscuous mode
Apr 12 14:15:57 bigbird kernel: bond0: now running without any active interface!
Apr 12 14:15:57 bigbird kernel: br0: port 1(bond0) entered disabled state
Apr 12 14:16:02 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
Apr 12 14:16:02 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
Apr 12 14:16:02 bigbird kernel: bond0: (slave eth0): making interface the new active one
Apr 12 14:16:02 bigbird kernel: device eth0 entered promiscuous mode
Apr 12 14:16:02 bigbird kernel: bond0: active interface up!
Apr 12 14:16:02 bigbird kernel: br0: port 1(bond0) entered blocking state
Apr 12 14:16:02 bigbird kernel: br0: port 1(bond0) entered forwarding state
Apr 12 14:16:03 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
Apr 12 14:16:03 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
Apr 12 14:16:03 bigbird kernel: device eth0 left promiscuous mode
Apr 12 14:16:03 bigbird kernel: bond0: now running without any active interface!
Apr 12 14:16:03 bigbird kernel: br0: port 1(bond0) entered disabled state
Apr 12 14:16:07 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
Apr 12 14:16:07 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
Apr 12 14:16:07 bigbird kernel: bond0: (slave eth0): making interface the new active one
Apr 12 14:16:07 bigbird kernel: device eth0 entered promiscuous mode
Apr 12 14:16:07 bigbird kernel: bond0: active interface up!
Apr 12 14:16:07 bigbird kernel: br0: port 1(bond0) entered blocking state
Apr 12 14:16:07 bigbird kernel: br0: port 1(bond0) entered forwarding state
Apr 12 14:16:09 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
Apr 12 14:16:09 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
Apr 12 14:16:09 bigbird kernel: device eth0 left promiscuous mode
Apr 12 14:16:09 bigbird kernel: bond0: now running without any active interface!
Apr 12 14:16:09 bigbird kernel: br0: port 1(bond0) entered disabled state
Apr 12 14:16:13 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
Apr 12 14:16:13 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
Apr 12 14:16:13 bigbird kernel: bond0: (slave eth0): making interface the new active one
Apr 12 14:16:13 bigbird kernel: device eth0 entered promiscuous mode
Apr 12 14:16:13 bigbird kernel: bond0: active interface up!
Apr 12 14:16:13 bigbird kernel: br0: port 1(bond0) entered blocking state
Apr 12 14:16:13 bigbird kernel: br0: port 1(bond0) entered forwarding state

 

[Search of SMB shares not working (MacOS client)]

Thanks Maxrad, the 45 drives link offers valuable insights.

[Unraid OS version 6.10.0-rc2 available]

Was any progress made regards samba and access from Monterey based Macs?

 

I was hoping a Samba extra configuration change could address the issue(s).

[Unraid OS version 6.10.0-rc2 available]

21 hours ago, JonathanM said:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-819173

"stock" speeds can be too fast, depending on which specific processor and the number and type of sticks.

 

Also, some brands of sticks just don't like some motherboards, are your sticks specifically validated by your motherboard manufacturer?

 

I've checked and the RAM is not overclocked with XMP / AMP, I've also completed a 12 hour Memtest successfully.

 

I feel like this is side tracking from the reported issue - why is unRAID allowing the array to start with an "unmountable unsupported disk"? Why is that disk not being emulated? How is party still valid in this situation? And why would a further 2 reboots suddenly fix it (and maintain a valid parity)?

 

So far as I am aware the screenshot that I posted (earlier in this thread) should not be possible in unRAID.

[Unraid OS version 6.10.0-rc2 available]

8 hours ago, JonathanM said:

Are you by any chance running a Ryzen CPU? If so, make sure your memory is not running over the CPU spec. Typically the RAM chips speed rating is WAY higher than what the CPU can manage.

 

I am using a Ryzen CPU, I have 32GB of DDR4-2666 running at stock speeds. It passed a 24 hour memtest a couple of months ago but I'm happy to re-test it if you think that could explain this issue.

[Unraid OS version 6.10.0-rc2 available]

11 minutes ago, trurl said:

In General Support subforum since it is very unlikely to be related to this (or any other) release.

 

Two more reboots and it suddenly returned to normal!

 

I'm assuming that parity is not valid even though it's reported as such - I'll rebuild it over night and keep an eye on it.

[Unraid OS version 6.10.0-rc2 available]

I'm not sure if this is a bug / a quirk or a coincidence. After upgraded from RC1 (which ran fine) one of my drives has been marked 'unmountable unsupported partition layout'. But it's still in it's slot (Disk 1 - see attached) and is not being emulated which is what I would have expected. Also the array isn't showing as degraded - is that normal?