trurl

A very bad strategy. You can only rebuild as many disks as you have parity. And parity by itself cannot recover anything. In order to reliably rebuild a disk, every bit of parity PLUS every bit of ALL remaining disks must be reliably read.

Might be better to rebuild disk3 without parity1 involved. Then you can either replace or remove parity1. Let's see if there are any other opinions. None of these are new disks. Did you test any of these disks before trusting them in your server?

Looking at other disks, your parity1 also needs to be replaced. You should be getting SMART warnings for parity and disk3 on the Dashboard. Do you have Notifications setup to alert you immediately by email or other agent when a problem is detected? Probably had some of these issues before you actually noticed anything wrong.

Disk3 is disabled, but the emulated disk is mounted. Your cache is not mounted though and that is probably the reason for the other problems. You should be able to see these things on the Main page but you did not mention it. Post a screenshot. Do you have another copy of anything important and irreplaceable? Looks like you have CA Backup installed. Do you have backups of the important cache stuff from that? SMART for disk3 has some issues. Do you have another disk to rebuild disk3? You may have to reformat cache. Let's see if @johnnie.black has any ideas about that.

Unclear what you mean here, since ignoring and fixing are different things. If you ignore something, the "ignore" will remain even if the problem isn't currently occurring, and it will continue to ignore if the problem occurs again.

Do you have .FSCK files on your flash?

Read the replies to that post

I guess you could try the NUT plugin:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Probably on a motherboard header. Don't know if it would help or not. Is Synology using APCUPSD?

You can go directly to the correct support thread for any of your dockers by clicking on its icon in the webUI and selecting Support.

Have you tried another port?

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post. Also go to Settings, syslog server and configure it so you can get syslog from before reboot.

You shouldn't preclear SSDs

The case is just a case. It has places to mount a motherboard, power supply and disks. You may not need a graphic card for what you want. You will need a CPU, most motherboards don't include one. And a power supply and RAM of course. And you need the CPU, motherboard, and RAM to be compatible. PCPartPicker can help you choose components: https://pcpartpicker.com/

Don't do this. It may not be working for you for some unknown reason but it might be working for someone else you don't want.

You should set your Unassigned Devices to rw/slave mode.

Can your server reach the internet?

I don't see anything in that. When did the problem start? Is anything different from when it was working?

Are you sure the port is forwarded to your server and not to your Windows?

Post your docker run command as explained at the first link in the Docker FAQ pinned near the top of the Docker Engine subforum.

Are you booting from a USB2 port? Recommended. Have you done memtest?

If you don't boot in GUI mode then you get the command line on an attached monitor, so that might be normal.

The 169 address is what happens when it doesn't get an address from DHCP. Can your router see your server?

Can you get diagnostics with the array started?