JorgeB

Try booting in safe mode to rule out any plugin issues.

There's constant crashing on the syslog, looks more like a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480419

Formatted with type 2 protection You need to remove this first, more info below: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078 https://forums.unraid.net/topic/110835-help-with-a-sas-drive/

Problem are these repeating errors: Aug 1 21:22:28 Onibi kernel: pcieport 0000:00:01.1: AER: Corrected error received: 0000:06:00.0 Aug 1 21:22:28 Onibi kernel: mpt3sas 0000:06:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 1 21:22:28 Onibi kernel: mpt3sas 0000:06:00.0: device [1000:0086] error status/mask=00000001/00002000 Aug 1 21:22:28 Onibi kernel: mpt3sas 0000:06:00.0: [ 0] RxErr First try this and/or using the HBA in a different PCIe slot and if that doesn't help see if you can suppress the errors.

Sep 25 06:53:04 UnRAIDServer kernel: ata4: hard resetting link Sep 25 06:53:09 UnRAIDServer kernel: ata4: found unknown device (class 0) Sep 25 06:53:09 UnRAIDServer kernel: ata4: softreset failed (device not ready) Sep 25 06:53:09 UnRAIDServer kernel: ata4: reset failed, giving up Sep 25 06:53:09 UnRAIDServer kernel: ata4.00: disable device Sep 25 06:53:09 UnRAIDServer kernel: ata4: EH complete Device drooped offline, this is usually a power/connection problem, check/replace cables, both power and SATA.

Backup config folder from current flash drive, redo it with v6.11.0 using the USB tool or manually then see if it boots, if yes restore the config folder from the backup.

Agree, there have been other similar reports for that model, according to SMART estimated life is still at 99% left: Percentage Used: 1%

Try with a different NVMe device if that's an option.

Old disk5 appears to have really failed, but keep it intact for now, we can try re-enabling disk2 to rebuild disk5 again, connet new disk5 again, then: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including old disk2 and new disk5, 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 disk5 -Start array (in normal mode now), ideally the emulated disk will now mount and contents look correct, then post new diags

If the diags didn't finish get the syslog: cp /var/log/syslog /boot/syslog.txt

Sorry, no more ideas then other than try a real monitor.

Update to v6.11.0, SAS SMART tests are supported now.

Try without -z, compression should only be used for highly compressible files and when using a very low bandwidth connection, though this usually result in low MB/s, not KB/s, so you might have other things going on, like SMR disks as mentioned.

You must format disk1 before use, below array stop button.

Best would be using a true HBA, like one from the recommended controllers list, but that doesn't mean you cannot use the RAID controller in JBOD mode, but you might run into issues in the future, if for example you need to replace it with a different one as mentioned.

See here for some possible solutions: https://forums.unraid.net/topic/128652-6110-final-edid-block-0-is-all-zeroes-error/

From the release notes:

Disk2 looks healthy so it be easy to re-enable, is the old disk5 completely dead? If not connect it and post new diags.

See here for some things to try:

Did you try blacklisting both the iGPU and the AST GPU?

Please post the diagnostics.

I see you found where, thanks.

No, just boot in safe mode and check if you have the same problem, to rule out any plugin issues.

Try booting in safe mode, also make sure there are no stale browser windows opened on the GUI.