JorgeB

No, because raid0 requires that all writes go to at least 2 devices, though I believe this has been/going to be changed in newer kernels, when there's only one device available it starts writing in single mode.

Don't see any LSI being detected, you can try temporarily disabling any vfio-pci bindings, adding hardware usually changes the device IDs and start binding the wrong device(s).

AFAIK it's not Ironwolf models in general but only the ST8000VN004, and there's a fix for it, but if you want a non LSI HBA the Adaptec HBA 1000 and 1100 series are reported to work without issues, though not as used as LSI, so not as well tested.

Run it again without -n or nothing will be done, if it asks for it use -L

Becuase the devices are of different sizes, so the largest one can't be fully used, single mode will use both (but will be slower).

It's a known issue for some, disabling NFS if possible, or at least hard links, sometimes helps.

It's not the syslog server, it auto generates the logs if it can't shutdown cleanly, they are saved in the flash drive logs folder.

Not just helpful, but essential.

Those won't be very useful, you can enable the syslog mirror to flash option on the syslog server then post that after booting with the HBA.

Not installed is the normal status for a disabled disk, you just need to do a standard replacement.

That's normal, missing status is for example when an array disk is missing at array start.

That doesn't help since it starts over after any reboot.

After a disk gets disable only a rebuild will fix it, if you thing the problem is solved and the disk is OK resync parity. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

This means single link, so the speed you're getting is normal, a single SAS2 link theoretical max is 2400MB/s, of those around 2200MB/s are usable, so dividing that by 26 drives (since parity devices also count) you'll get 84.62MB/s max speed, like mentioned you can increase that by connecting a seconds cable from the HBA to the expander, assuming it supports dual link, and it should since it's an LSI.

If you want to try it I'll post the procedure below, but like mentioned almost certainly disk3 will be unmountable, at best there could be some recoverable data using btrfs restore: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including the new disk3, replacement disk should be same size or larger than the old one -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk3 -Start array (in normal mode now), ideally the emulated disk will now mount (unlike in this case) and contents look correct. -If the emulated disk mounts and contents look correct stop the array, re-assign disk3 and start array to begin rebuilding, if it doesn't you can try brtrs restore, on the emulated or rebuilt disk.

You can re-enable disk1, if it's not failing, but due to being out of sync and using btrfs disk3 would be unmountable, also disk6 could no longer be missing.

See if the below applies to you, if yes, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), 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/

Open another ssh session and/or use the keyboard/mouse.

Assuming you mean 85MB/s that's about right for 24 drives on a SAS2 expander with single link, do you have one or two cables connected to the HBA? Or just post the output of: cat /sys/class/sas_host/host7/device/port-7\:0/sas_port/port-7\:0/num_phys With dual link you should be able to get around 110MB/s, bottleneck then would be the PCIe 2.0 slot.

No, parity needs the correct missing disks (the ones that were used to sync it) to be able to rebuild a disk, and with single parity only one disk can be missing/disable.

Copy the syslog to the flash drive in case the diags aren't saved: cp /var/log/syslog /boot/syslog.txt

Oct 27 14:34:08 cronos kernel: ahci 0000:02:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001 address=0x9f400000 flags=0x0000] Problem with the onboard SATA controller, this is quite common with some Ryzen boards, look for a BIOS update or use an add-on controller.

First upgrade to rc1, reboot, then install the plugin.

It's this issue: See that thread for some possible workarounds.

Changed Status to Closed Changed Priority to Other