Veah

numlock on some keyboards can swap a character for a letter you think you are typing

I'm a Seagate guy, Exos more specifically. Beyond Itimpi's example of a problem batch, I see no reason to vary the drive manufacturers or models.

Only other thing I can think is to disable bonding. Hope you isolate this and then share the fix.

I did not experience the amd c-state issue on a trx4 3960 cpu. Have a look here to see what's what.

I've moved my array a few times between 3 different systems. The only tedium I run into sometimes is reconfiguring the containers.

Yep. After it boots up, you will need to assign the array drives. That's where the pic comes handy for me.

Take a pic of your 'main' page and use it to assign all your drives in the new PC in the same array spots as the old. If you are using USB attached drives, things could be more complicated. Edit:. And make a flash backup first.

Yes

Good reading about jumbo frames here courtesy of @MAM59

Do the troubles stop if roll back to 7.2.0? If so, suggest keep it there.

This is strange, but I have had issues using the cable style adapters on these. My fix was to use the firm chip type like this.

That's how mine is connected

Mac addresses in my containers have kept since 6.12 so not sure about that. Sometimes I need to do the ping to make the connection show green (in pfsense). It's been kind of peculiar and sometimes I question what I am actually trying to accomplish by messing with it. It's like losing sight of the forest through all the trees.

Have you tried clocking down your memory?

Have a look around here: https://forums.unraid.net/forum/35-unraid-compulsive-design/ Edit link

I get the mac address by console into the container and ifconfig. With the mac from there, create your dhcp entry which is more of a placeholder than anything else. After thats done, you can ping from within the router and then a status should show the connection up. I emphasize that the dhcp is mostly fluff unless you have a completely open ip assignment range. As for mac/ipvlan, I have done it with both.

Docker does not properly receive DHCP addresses right so I just work around by manual assign on both DHCP end and the eth1 assignment. Silly but works in my case. Also assign your IP to eth2. I imagine things should start talking after that.

If the other drive is already empty, yes. Remove the empty drive and use 'New Config'. That will start like fresh with your remaining drives and start a parity build. Be sure to preserve the assignments you want.

Have you tried assigning the desired addresses to the containers for eth2? The eth1 for vm sounds like something to vfio and should not show up under your network interface at all. I presume eth0 is functioning as desired already. Edit: corrected eth#s

Well with 2 parity drives.... I'd shut it down, unplug the drive you are zeroing, then start up. The drive will emulate and you should be able to move your data to the disks you plan to keep. After that, shrink the array.

The worst case is the button reset you mentioned. Going that route won't be too bad especially if you stop all the containers and vm you may be running.

Stop the array should do it.

Can you clarify what this means?

A crappy little 40mm fan screwed janky style into the hba heatsink is a pretty easy fix for these overheating buggers.

I realize you swapped cables already but those symptoms sure sound like a badly crimped connector. I do not think unraid is causing the problem.