trurl

Start your own thread with your Diagnostics.

Attach Diagnostics to your NEXT post in this thread.

Don't overclock your server unless your data isn't important to you.

The boot partition is still at /boot, so that plugin should still work. Better method would probably be Unraid Connect to backup to Unraid cloud.

Replace SATA cable. How is this drive connected to power? Any splitters?

then post new diagnostics

Is your Unraid Connect plugin up-to-date?

Login to unraid.net and try again.

Stop the array and start it in Maintenance mode so you can check filesystem on emulated disk2 from the webUI and post the output.

Your screenshot is clipped on the right where it is telling you the important information. Emulated disk2 is unmountable, so we can't access its filesystem (yet). Unfortunately, it doesn't know what filesystem disk2 is supposed to be. Default for array disks is XFS, and that is what disks 1, 3 are. Unless you know differently we will assume disk2 is also supposed to be XFS. Stop the array, click on emulated (missing) disk2 to get to its page, set File system type to xfs, start the array with nothing assigned as disk2, and post new diagnostics.

Assuming you mean this part the warning is incorrect since the parity valid box is checked. If that is not what you mean, explain further.

new disk 2

Probably parity was already disabled when the other disk failed. So likely it isn't valid. But maybe we could try to trust parity and see if we could get anywhere trying to emulate the missing disk. Go to Tools - New Config - Retain All - Apply. Assign disk2. Very important. Check BOTH the Parity Valid box and the Maintenance Mode box, then start the array. Stop the array, unassign disk2, then start the array in normal (not maintenance) mode, with nothing assigned as disk2. Then post diagnostics

Those diagnostics are a few days old. Looks like you were having connection problems with disk1, but that would not be the reason for your stated problem. Have you done memtest? Setup Syslog Server

SMART for parity looks OK, looks like connection problems. USB not recommended for assigned disks for many reasons. Also ntfs (disks 1,2) not recommended for assigned disks.

Don't know what happened for you. I just did all this on my main server and it all worked. It did take some work to get it done since I needed to move all the data from the mirrored "fast" pool (docker and other things) to my mirrored "cache" pool, so I could repartition the "fast" nvme s for a mirrored "boot" partition and a mirrored "fast" partition. Then move all the "fast" data back from cache. "boot" partition only takes 16GB of my 256GB And TPM license transfer also worked. I did hit a glitch in the license transfer but that fixed itself after I logged in to unraid.net. What "tutorial" were you using?

See if check filesystem from the command line will show anything. Make sure the device is still sdac xfs_repair -n /dev/sdac

Do you have a current flash backup?

What do you get from command line with this? fdisk -l /dev/sdac

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

How is this connected? Can you try to mount it as an Unassigned Device?

I just look at the RAW_VALUE, which is 0.

I don't see that in either of those reports

Probably not directly related to your problems, but in case you weren't aware, SSDs in the array cannot be trimmed.

The onboarding wizard is new for 7.3. There is another wizard for setting up internal boot. https://docs.unraid.net/unraid-os/release-notes/7.3.0/#onboarding-and-internal-boot