JorgeB

Not really Your are mentioning both Windows and DOS, you just use one or another, try DOS first since if it works it's faster (assuming you know the basics of DOS, like changing dir etc, if not this will be difficult to explain for me, you might need to use google: Create a DOS flash drive with rufus unzip the correct firmware package to the flash drive leave only the HBA you're updating this time, remove the other one navigate to correct folder where you extracted the firmware and the sas2flsh utility, then type sas2flsh -o -f 2118it.bin replace 2118it.bin with correct firmware name

You only formatted the cache now... That is done by running the mover, but shares need to be correctly configured, see here for more info (or turn the GUI help on).

Then I suspect some HBA issue, still worth to try the beta, if the normal update isn't working you install it manually, download the zip: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta25-x86_64.zip Then extract it and copy all the bz* files to the flash drive overwriting existing ones, then reboot.

Should work fine, but note that you can only connect one or two minSAS cables, since it's an expander backplane.

It should work correctly with any Supermicro backplane, what model backplane do you have?

If cache is now mounted please post new diags.

Should work as long as you pass trough the HBA to the VM, but it wouldn't be available for Unriad, so you couldn't start the array. Not sure X8 boards already had UEFI support, I know X9 have, if they don't it's easy to do it with DOS.

Download the Package_P20_IT_Firmware_BIOS_for_MSDOS_Windows for the correct models you have, then the easiest way to update is with Windows, by either installing the HBA on a Windows desktop or installing Windows on the server on a spare SSD or something, then just follow the instructions but basically is opening a command prompt windows and typing from where the package folder was unzipped: sas2flash -o -f blahblah.bin You can also boot form a dos flash drive an the update is the same, just using the DOS executable, though it only work wit older boards, newer ones will require the UEFI utility, sas2flsh -o - f blahblah.bin P.S. since you have two HBAs you'd need to specify the correct number, or just remove the other one and do it one at a time. I'm sure it's also possible to do it on Linux, but likely more complicated.

It's easier to update with a DOS boot flash or even Windows, you can download the latest firmware from Broadcom's support site, those HBAs will be under legacy, then HBA.

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.