trurl

Not clear there is anything wrong with the original, but if you insist on replacing it, as noted no need to move any data off. Just replace the drive and its data will be rebuilt on the new drive.

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post. Have you done memtest?

Unraid IS NOT RAID. There is no striping. Each data disk is an independent filesystem. Each file is stored completely on a single disk. Folders can span disks (user shares). Because Unraid is not RAID, you can mix different sized disks in the parity array, and you can easily add additional disks without rebuilding the whole array. You can have one or two parity disks, which allows one or two simultaneous drive failures to be recovered. You should keep a backup of flash. With that backup, you can get going again just as before with a new flash by registering the new flash in the webUI.

Diagnostics already includes syslog since the last reboot, so no need to post separate syslog. You should never format a disk with data on it that you want to keep. You should have asked for advice and we probably could have helped you recover the data. Disk2 SMART is OK but it seems to have connection problems. Double check all disk connections, power and SATA, both ends, including power splitters. Are you sure it is a disk making the sounds? Looks like you have some problems with mover and duplicates, which is keeping you from getting your appdata, etc. moved to cache. We can deal with that later.

This is the best way. RAID doesn't really make sense when you are talking about folders (shares). RAID doesn't work that way.

That one is deprecated. See 2 posts above yours for video on how to switch to another plex docker.

There should be a lot more than that in config, including your license .key file. This suggests that your flash drive has disconnected or is corrupt. Post new diagnostics.

Are you sure both aren't trying to use the same host ports?

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post.

Post a screenshot of your User Shares page

Do you have any other symptoms?

Syslog since the last reboot is already part of the diagnostics.

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

Yes

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

Shouldn't need to use command line for that. If repairing a disk in the array be sure to repair the md device and not the sd device, or you will invalidate parity.

I thought you were doing a disk rebuild. Did that ever complete?

Do you mean you have run memtest and it gives errors?

Just thought it might be worthwhile to elaborate on this beyond the answer already given. The data can be recovered from the parity calculation by reading parity and all remaining disks. The parity disk by itself can't recover anything.

Not entirely clear, but you seem to be having problems with cache, and libvirt and docker image on cache. Since you've already done the less extreme measures, you might just reformat it. Disable dockers and VMs in Settings, then backup cache and reformat it. Then run an extended SMART test on it. If it passes, recreate libvirt and docker image.

All disks have dropped. Could be connections, could be controller. Shutdown, check all connections, and restart rebuild. Are you sure the disk even needed replacing? As you can see from this situation, you can have disk errors even if the disks are good.

Tried again and it is working now. Not sure what the problem was before. Thanks a lot for this app!

I get the button now on my Samsung Galaxy S7, but it won't actually connect to my server for some reason. I have tried server name and IP. This phone has no problems connecting to my server for share access. As noted, working on my tablet.

According to your diagnostics flash drive had definitely disconnected. Once that happens it won't come back without reboot.

Possibly you wouldn't even have needed data recovery software for those disks. You might have been able to just mount them with Unassigned Devices and read their files directly with their names intact. It is only if the files were deleted or corrupted that the filenames are likely to be lost.