JorgeB

But you also need to fix these.

I would, since it won't be valid anyway, then try again.

There were already some read errors on disk10, this means parity won't be 100% correct, doesn't look like a disk problem, I would start by updating both LSIs firmware: Sep 8 10:13:56 Tower kernel: mpt2sas_cm0: LSISAS2008: FWVersion(10.00.08.00) Very old, current release is 20.00.07.00 Sep 8 10:13:56 Tower kernel: mpt2sas_cm1: LSISAS2116: FWVersion(20.00.06.00) All p20 releases except 20.00.07.00 have known issues. It could also be a power/cable problem.

You'll need to rebuilt it anyway, not sure what script you're using, but you can decide if it's worth running it also.

Please post the diagnostics, you can grab the on the console by typing "diagnostics".

Though doubt it will help, still won't hurt to try, and if it's still the same it's likely a HBA problem.

If find it very odd that it shows up on the BIOS and then it's like it's not present as far as Linux is concerned, but again, can't see how this issue could be fixed on the Unraid side.

Replace as soon as you can.

Yep.

Replace cables and try a different port, if still not detected you need a new cache drive.

Controller is failing to initialize: Sep 8 07:48:49 Unraid kernel: mpt3sas_cm0: Scatter Gather Elements per IO(128) Sep 8 07:48:49 Unraid kernel: mpt3sas_cm0: _base_wait_for_doorbell_int: failed due to timeout count(5000), int_status(40000000)! Sep 8 07:48:49 Unraid kernel: mpt3sas_cm0: doorbell handshake int failed (line=5253) Sep 8 07:48:49 Unraid kernel: mpt3sas_cm0: _base_send_ioc_init: handshake failed (r=-14) Sep 8 07:48:49 Unraid kernel: mpt3sas_cm0: fault_state(0x2669)! Sep 8 07:48:49 Unraid kernel: mpt3sas_cm0: sending diag reset !! Sep 8 07:48:49 Unraid kernel: mpt3sas_cm0: diag reset: SUCCESS Sep 8 07:48:49 Unraid kernel: mpt3sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:10684/_scsih_probe()! Make sure it's using the latest firmware, you can also try the latest Unraid beta, there might be some driver difference.

oops, I meant nerdtools, poor Ned.

Diags look fine, but it's without cache assigned, if the 500GB was your cache disk it should be replaced, it has a failing now SMART attribute, one that means data can't be trusted on that disk.

Run a non correcting check now and post the diags if there are more errors.

Looks like the cache dropped offline, reboot/check cables to see if it comes back.

That's what it looks like.

Those messages mean the docker image is already corrupted, you need to recreate it.

Nothing jumps out, is it still going slow? Maybe a disk getting some slow sector zones, you could run the speedtest docker to see if the disks are performing normally.

You have a flash drive problem, filesystem is read-only, so Unraid can't update super.dat with the new disk info, run chkdsk on the flash drive.

See here: https://forums.unraid.net/bug-reports/stable-releases/680-r787/?tab=comments#comment-7711

Yes, 5 minutes should be fine, it's what I use also for a long time.

You can change that on Settings -> Disk Settings -> Tunable (poll_attributes): Default is 1800s (30 minutes)

That's a good idea but IIRC it had 0 downloads when I downloaded it, and I immediately removed it.

I edited your post to remove the attachment since it looks like by mistake you attached a txt file with some of your passwords.