trurl

Do you have Community Applications plugin installed? Take a look at some of the Categories on the Apps page and see if any of them have an app that would suit your purpose.

More likely a hardware issue

^ What he said. There has even been some discussion whether or not some models of SSD might invalidate parity.

I see you had another thread about this. Glad you got it sorted.

What evidence do you have that you have the same issue? The ultimate explanation for his problem was What are your permissions for /mnt/user?

Since you had errors on multiple disks, likely a controller issue. Sounds like you may have fixed it yourself. Let us know how the parity check goes. Exactly zero parity errors is the only acceptable result.

That is not the diagnostics file. Is that all you downloaded? If that is the syslog from before rebooting, it is useful, since the syslog included in diagnostics will not have anything from before reboot. But complete diagnostics will also have a lot more information about your situation and configuration. Tools - Diagnostics, attach complete diagnostics zip file to your NEXT post.

Just make sure you don't assign a data drive to the parity slot, or its data will be overwritten with parity.

Tools - Diagnostics, attach complete zip file to your NEXT post.

Have you seen this "sticky" pinned near the top of this same subforum?

Post it

If you would rather take the approach of learning new ways to do things, we could consider rebuilding parity first without disk1 and disk3. That would get the rest of your array back to a protected state and we could even change the disk assignments so to fill the gap of the missing disk1 and put that new disk in all at the same time. Then we could use Unassigned Devices to get the data off that disk currently assigned as disk3. Something I maybe should have asked before now. Do you have backups of anything important and irreplaceable?

Or is this what you had in mind, using SFTP to also send files to the destination disks? It would be a round trip over the network from the server to your PC and back so it might be slower than doing it directly on the server, but if that is something you are comfortable with then it might be faster than learning another way. The main reason I don't like for people to shuffle data to other disks on the server is because they are usually thinking about a disk that has already failed and is being emulated by all the other disks and all the other disks have to be read to get that data for the failed disk. But, in your case, the "failed" disk is actually the missing disk1, and you aren't trying to get any data from that, so no emulation involved. And since your parity is invalid anyway, it might make things faster if you just unassign parity for now. Sorry for the long delay in responding but life gets in the way sometimes, even for us forum junkies.

Normally I don't recommend this, but how do you propose to move files from disk3 to other disks in the array? I know how I would do it directly on the server but I am wondering if you know how to do that.

Could you elaborate? You can mount SMB network shares using the Unassigned Devices plugin. That will make them available to various things on Unraid, including dockers. I don't have any specific application to recommend. Another thing you might consider is something running on the computer that has the files. There are a lot of things like backup software that can be scheduled.

Maybe just try a different port?

A forum search shows others who are using that hardware. What are you using for a flash drive?

Looks like you don't have any, not even a motherboard header.

Also, have you seen this? https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Your flash drive has disconnected and possibly corrupt. Are you booting from a USB2 port? You may have one of those systems that can't keep a USB3 connection with the flash drive.

Your parity hasn't been valid since you removed that disk1. How much data is on disk3 currently? Instead of trying to move it to other disks in the (already compromised) array, it might be safer to just copy it to your PC over the network. Then we can work on getting your array back to valid parity without the missing disk.

I will be back. Please don't do anything without further advice,

I have to be away for an hour or so.

Just any disk put in for disk1 won't help at all. In order to calculate the correct data for disk3 rebuild, it must have all the data from all the disks the parity was built with.

No, I am just trying to get an idea of the best approach that won't be a big learning curve for you. You can't replace / rebuild disk3 to a new disk because parity plus all other disks are required to calculate the data for the rebuild, and you have another disk missing already. I am not sure how bad disk3 is. Probably it isn't even showing SMART warnings on the Dashboard, but SMART attribute 1 is not monitored by default and it is important for WD Reds. What made you think it needs replacing?