JorgeB

Difficult to say if it's some kernel compatibly issue or just a hardware problem, have you been using that hardware for some time, e.g., was it stable with v6.9?

You should also replace the SATA cable for disk2, it's detecting CRC errors.

Like mentioned, it's normal with XFS, especially since it started supporting reflinks.

Constant ATA errors on parity plus disks 4 and 8, check/replace cables, also note that Marvell controllers are not recommended.

You just need to assign the new device as a pool, but feel free to ask if you have any doubts.

This means some writes were lost to the device, and it's usually a fatal error. There are still frequent ATA errors on that device, as warned above link resets can lead to lost writes and fs corruption. Jul 2 12:18:42 mitchsserver kernel: ata5.00: exception Emask 0x50 SAct 0x1000000 SErr 0x30802 action 0xe frozen Jul 2 12:18:42 mitchsserver kernel: ata5.00: irq_stat 0x00400000, PHY RDY changed Jul 2 12:18:42 mitchsserver kernel: ata5: SError: { RecovComm HostInt PHYRdyChg PHYInt } Jul 2 12:18:42 mitchsserver kernel: ata5.00: failed command: READ FPDMA QUEUED Jul 2 12:18:42 mitchsserver kernel: ata5.00: cmd 60/08:c0:40:10:00/00:00:00:00:00/40 tag 24 ncq dma 4096 in Jul 2 12:18:42 mitchsserver kernel: res 40/00:c4:40:10:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Jul 2 12:18:42 mitchsserver kernel: ata5.00: status: { DRDY } Jul 2 12:18:42 mitchsserver kernel: ata5: hard resetting link

Everything looks normal so far, just re-sync both parity drives, you can do both at the same time, hopefully the HBA error was a one time thing, but if it happens again you'll need to troubleshoot, in the meantime make sure it's well seated and sufficiently cooled. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

Most likely. Worth trying, you don't need a HBA BIOS for Unraid.

No problem using NVMe devices with that board, it probably won't support PCIe bifurcation, so if you want to use a dual adapter you'll likely need one with a PLX switch.

Do you mean a parity swap? It's a known issue, sometimes the extra space of the new parity is not correctly zeroed.

Either of the posters above with the issue can you please confirm that booting in safe mode didn't help?

My first one was the ZX Spectrum 48K (with a separate tape deck), this was probably the first affordable computer in Europe, it was released in the early 80s. Load ""

That looks like a board BIOS issue, best bet would be to contact Asrock support.

Problem with the controller: Jul 2 04:16:27 CMNSVR01 kernel: smartpqi 0000:0b:00.0: controller is offline: status code 0x1111 Jul 2 04:16:27 CMNSVR01 kernel: smartpqi 0000:0b:00.0: controller offline Power cycle the server and if the controller comes online, and it should, post new diags after array start.

Try booting in safe mode.

Try dumping the VBIOS.

Enable the syslog server and post that after a crash.

Post the log after a crash.

Configuration looks fine, do you have just a regular router or some more involved configuration, like a firewall, etc?

Command line: BOOT_IMAGE=/bzimage vfio-pci.ids=8086:10c9 initrd=/bzroot They are stubbed to vfio-pci, remove that from syslinux.cfg and reboot.

That's usually caused by an add-on device, after identifying the culprit sometimes switching slots can fix it, if not you can at least inhibit the error to stop spamming the log.

Thanks, network-rules.cfg is not getting created, let me see if I can find out why.

It failed the SMART test, it should not be used.

Try running memtest.

There's no Linux module/driver mentioned in the screenshots, so cannot say if it was a software or hardware issue.