JorgeB

e.g. /mnt/ramdisk should work

IIRC anything mounted under /mnt/disks/ is limited to 1MB, except actual UD mount points, this was done on purpose, don't use /mnt/disks/ for that.

You can also try updating the LSI firmware, you're using a release I've never seen before (16.00.08), latest stable was 16.00.01, I see now there's 16.00.10.

That's on the slow side, is that writing to cache or array? Your cache device is likely slower than you expect, you also have a slow disk1, still try with turbo write enable and write directly to the array, it should be considerably faster.

Should be fine.

👍

Try enabling the syslog server/mirror then start a parity check and post the syslog after it crashes.

Looks more like a kernel/compatibility issue, you try v6.9-beta1 which includes a much newer kernel.

Iperf tests the actual LAN bandwidth, you're unlikely to get significantly more speed during a single transfer than that result, it's usually the hardware used limiting that, NIC, cable, switch, even board/CPU combo.

On the diags posted libvirt started correctly at first array start: Mar 14 10:01:57 TOWER emhttpd: shcmd (463): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 2 Mar 14 10:01:57 TOWER kernel: BTRFS: device fsid 473e1a30-4df5-4093-9659-11deafd49e06 devid 1 transid 1987 /dev/loop3 Mar 14 10:01:57 TOWER kernel: BTRFS info (device loop3): disk space caching is enabled Mar 14 10:01:57 TOWER kernel: BTRFS info (device loop3): has skinny extents Mar 14 10:01:57 TOWER root: Resize '/etc/libvirt' of 'max' Mar 14 10:01:57 TOWER kernel: BTRFS info (device loop3): new size for /dev/loop3 is 2147483648 Mar 14 10:01:57 TOWER emhttpd: shcmd (465): /etc/rc.d/rc.libvirt start Mar 14 10:01:57 TOWER root: Starting virtlockd... Mar 14 10:01:57 TOWER root: Starting virtlogd... Mar 14 10:01:57 TOWER root: Starting libvirtd... Then for some reason it tried to start again a few minutes later: Mar 14 10:18:28 TOWER emhttpd: shcmd (552): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 2 Mar 14 10:18:28 TOWER root: /mnt/user/system/libvirt/libvirt.img is in-use, cannot mount Mar 14 10:18:28 TOWER emhttpd: shcmd (552): exit status: 1 Try rebooting in safe mode and post new diags.

Weird error, and one I've never seen before: Mar 14 07:35:01 Hoofs emhttpd: unmountable_mask not found Mar 14 07:35:01 Hoofs kernel: emhttpd[28803]: segfault at 0 ip 000014cff73c7006 sp 000014cff7148e70 error 4 in libc-2.30.so[14cff73a2000+16b000] Mar 14 07:35:01 Hoofs kernel: Code: 41 54 45 31 e4 55 53 48 83 ec 28 48 89 74 24 08 85 c9 0f 85 e4 02 00 00 83 fa 01 0f 84 83 01 00 00 83 fa 24 0f 87 7a 01 00 00 <49> 0f be 45 00 49 8b 70 68 4c 89 eb 48 89 c1 f6 44 46 01 20 74 17 Try booting in safe mode to rule out any plugin interference..

Newer kernel would come with a newer Unraid release, e.g. you could try v6.9-beta1 which comes with kernel 5.5

Rebooting should fix it.

There are some options here that might help with data recovery: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490 For the dockers you only need the appdata, the docker image can be easily recreated.

You could try that to at least get the array stable. If you need VM hardware pass-trough and those errors keep happening, and like mentioned it's not that unusual with AMD boards, you might need a new board, bios update/newer kernel might also help, also note that I believe that on at least one case the user was still having issues even with IOMMU disable.

Problem with the onboard SATA controller: Mar 14 02:52:18 Unraid kernel: ahci 0000:01:00.1: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000100000000000 flags=0x0010] Mar 14 02:52:18 Unraid kernel: ahci 0000:01:00.1: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000100000000880 flags=0x0010] Mar 14 02:52:18 Unraid kernel: ahci 0000:01:00.1: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000100000000d80 flags=0x0010] Seen it several times before on the forums with AMD boards, disabling IOMMU might help.

Best to use 4x/4x/4x/4x, or both devices could get assigned to the same x8 link, depending on the slots used.

It should work, that or the Supermicro AOC-SLG3-2M2

Yes, if the motherboard supports PCIe bifurcation, there's also a Supermicro model for two NVMe devices, but again it requires PCIe bifurcation for both devices to work.

No, it says it support NVMe and SATA devices, one of each: NVMe on the left (M-Key) and SATA on the right (B-Key)

The adapter should work but only one device can be NVMe, the other is SATA (and needs to connect to an available SATA port)

I didn't see the video, but iperf is very simple to use, if you can't follow the video try google.

You don't need to preclear, just add it to the array, it will be cleared in the background, when done it needs to be formatted.

The cache filesystem is corrupt and will need to be re-created, also make sure to check this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

You should post on the appropriate docker support thread: