JorgeB

Jun 14 10:00:47 172.18.0.1 kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jun 14 10:00:47 172.18.0.1 kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Btrfs is detecting data corruption, more info here, you should set RAM to 1866MT/s as explained here, also check the power supply idle control setting, after RAM is correctly set reset the btrfs stats and keep monitoring, if more corruptions are found run memtest.

I assume you mean MB/s, Mbs is Mbits per second. Also note that without turbo write array writes are considerably slower, again depending on the hardware, but speeds from 40 to 60MB/s are normal, more details about both write modes here:

Let the clear finish then rebuild disk1.

Then I would try with a different flash drive, you can use a trial key to make sure it works before transferring the current one.

If you didn't yet and you're booting CSM it might be worth trying UEFI boot, or vice-versa.

Didn't re-read the entire thread, but if you didn't yet try recreating the flash drive, backup current one, re-do it manually or by using the USB tool, then restore the config folder.

It's been notoriously difficult to reliably boot Unraid with Apple hardware, though some times it works, agree that UEFI is more likely to work.

Click on cancel next to array start/stop.

Write speed with Unraid depends mostly on the hardware used, also if you just want to use the array or can use pools. For the array, and using turbo write, if there are no controller or other bottlenecks write speed will be limited by the slowest disk in the array in that zone, e.g., with fast empty disks write speed will be around 200/250MB/s. For pools, using a multi device SSD pool or a fast NVMe device/pool I get around 1GB/s with 10GbE.

No. No, you can cancel.

You can try.

This error can be a little elusive, sometimes I can't see a reason for it.

Check the link, it only happens with newer kernels, still a device problem, or at best a kernel problem with that device, it happens with different Linux distros.

It's a device problem: https://us.community.samsung.com/t5/Monitors-and-Memory/SSD-980-heat-spikes-to-84-C-183-F/td-p/2002779

That's form mcelog, not Unraid, i.e., it's fine.

The problem is that there's an invalid btrfs filesystem on this disk: Jun 22 22:17:24 NAS emhttpd: shcmd (72): /sbin/btrfs device scan Jun 22 22:17:25 NAS root: ERROR: cannot scan /dev/sdb1: Input/output error Disk is currently unassigned, was this parity and/or where do you want to use it now?

Please use the existing docker support thread/link:

That's because of this pesky "stale configuration" error, array is starting, just not showing in the GUI, make sure there are no other browser windows open in the GUI, including phones or tab, also clear browser cache.

Will be able to rebuild disk1 once the clearing is done, I assume disk2 is really a new disk, because it's getting wiped, and if disk2 was supposed to be used as disk1 he should cancel the clear now and after that will be able to use that disk to rebuild disk1, if the clear finishes can't so easily remove the disk from the array, especially with aa disabled disk.

Jun 21 16:14:51 unRAID-1 kernel: ixgbe: probe of 0000:05:00.0 failed with error -5 Jun 21 16:14:51 unRAID-1 kernel: ixgbe: probe of 0000:05:00.1 failed with error -5 Both NICs are failing to initialize, suggest going back to v6.9 to confirm if it's a driver or NIC issue.

It is, it shows that in the screenshot, good catch.

Please post the diagnostics

It's OK to power down but it will start over from the beginning, might as well see if it finishes. It is, those are a good option.

This suggests Unraid is detecting an unclean shutdown.