JorgeB

It's logged as a device problem, and SMART confirms it, you will nee to replace the device.

That's not possible since parity2 is calculated in a different way, they are not interchangeble, but you can add parity2, remove parity1 and use only parity2.

Check the config for all VMs, the USB flash drive/controller may be passed-through to one of them.

No AMD GPU is being detected by Linux, this is not a software problem, I see only a Nvidia GPU, try re-seating it or using a different PCIe slot.

Yes, should be plug and play.

If the disk is still missing there won't be SMART, try using a different slot/cable, if still not detected it can be dead.

The syslog starts over after every boot, so can only see that it's doing it now.

Is it still missing or can you see it now?

You can try force enabling disk1 to try and rebuild disk3 again, but the diags shows the SATA link going up and down for multiple disks, you need to try and solve that first, are you using any power splitters? You can also try a different PSU if available.

Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller This is a PCIe 1.0 controller, with two devices it will be limited to around 80MB/s, would recommend getting a PCIe 2.0 controller from the list on the 1st post, like an Asmedia 1062.

A second drive should not slow down the parity check, assuming the controller is working at PCIe 2.0, for a better idea you can post the diags.

Nope, but there are a few NIC related threads in the hardware forum that should show up in a search, you can ask there for a recommended model, mention what you are looking for, e.g. gigabit or 10GbE, UTP or fiber.

Those would be old since there's no disk1 at the moment.

You can starting enabling the containers one by one and re-testing until you find the culprit.

Yes.

Basically yes, since you have more than one RAM stick, you can try using just one, if the same try a different one, that will basically rule out the RAM.

Should be fine, and any issues would be easily found on the first couple of parity checks.

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, 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.

It's an option on the boot menu:

If you are using different SATA ports it could be the board, if you just swapped them it could still be cables.

Docker image is corrupt, delete and recreate: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

You can just swap them, nothing else needed.

I can suggest a slightly easier way with UD, it would not require using UD to format a disk or doing a new config, but it would involve a little more risk, since until disk1 is copied back top the array, it would exist only outside, and unprotected: Replace disk1 with the new disk and rebuild, you can install the new disk in the old disk1 physical location now Once the rebuild is done change the filesystem on disk1 to xfs and format it Connect old disk1 to the server Mount old disk1 with UD Copy data from old disk1 to new disk1 Disconnect old disk1 and you're done

If creating the standard partition layout doesn't help, the only other way I know how to fix it would be to rebuild each disk one at a time as already mentioned, alternatively, if you have a spare disk, you can format the new disk and use UD to copy the data from an old one, then repeat for the other disks.

If you don't have one or IPMI, yes.