JorgeB

Sometimes when adding a new NIC it becomes eth0, the main NIC, if you want you can swap them back in Settings -> Network Settings -> Interface Rules (reboot required)

On the diags posted there's a link on eth1, eth0 has no link, swap the cable to the other NIC.

Several users using those, possibly a bad CPU.

No, it's true, my mistake, the problem is that the filesystem is fully allocated, you need to run balance, see here for more details: https://forums.unraid.net/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551

Are you going to replace an existing disk with the 6TB or add it as a new disk? If it's to replace an existing disk no need to preclear, even as a new disk Unraid can now clear it in the background, but you can use preclear.

Iperf looks good, enable disk shares and transfer directly to cache (\\tower\cache), see if that makes any difference.

Any NVMe adapter should work fine, they are transparent to the server/OS.

First upgrade parity, then the data disk.

Have you done an iperf test? See what you get for a single stream.

Without a disable disk there's no real need to use the parity swap procedure, but it can still be used if you disable the data disk first, like mentioned here: https://wiki.unraid.net/The_parity_swap_procedure

And parity was re-synced?

Then is should still be disabled, or did you do a new config?

Tom might have a better answer, but likely yeah, wait for a newer beta with a more recent driver.

That's not how parity swap works, it only works when you have a disable data disk. And that still doesn't answer what happened to disk6, if parity was valid with it it's not without it.

Is the shfs direct_io option still relevant? I don't see it in the log when enable and it appears to make no difference on or off.

Original parity swap was with disk6: Oct 10 00:04:40 Zeus emhttpd: copy: disk6 to disk0 running How come now it's disk3? What happened to disk6?

Yes, use raid1 for 3 devices and raid1 or raid10 for 4.

Driver is crashing while initializing the device: Oct 11 17:45:47 Ryzen3700X kernel: r8152 2-1:1.0 (unnamed net_device) (uninitialized): netif_napi_add() called with weight 256 Oct 11 17:45:47 Ryzen3700X kernel: ------------[ cut here ]------------ ... Oct 11 17:45:47 Ryzen3700X kernel: r8152 2-1:1.0: couldn't register the device Oct 11 17:45:47 Ryzen3700X kernel: r8152: probe of 2-1:1.0 failed with error -22 Likely a driver issue, assuming the NIC works correctly for example in a Windows machine.

https://unraid.net/contact

Disk5 looks OK, you can use the invalid slot command to re-enable it and rebuild disk2, assuming it's really fine and parity is still valid. Follow the instructions below carefully and ask if there's any doubt. -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed. -Important - After checking the assignments leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters): mdcmd set invalidslot 2 29 -Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk2 will start rebuilding, disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check

You can try testdisk, it might be able to recover the deleted partition.

It will depend on the current data tree, split level always overrides allocation method.

Yes, luks errors start immediately, no idea why, please try booting in safe mode.

Cache pool is completely full, errors are caused by the docker image running out of usable space, free up some space.

Best bet is to use the appropriate docker support thread: