trurl

According to those 6.8.3 Diagnostics in OP, you seem to have 3 SSDs, one an NVMe different in size than the other 2. Were these all in cache pool or was one of them Unassigned?

yes

Did you read the link I gave you? It tells you how to get us more information even when there is a network issue.

Diagnostics?

Working for me. Sounds like a browser issue. Have you tried clearing cache, other browsers, etc?

This suggests you have not succeeded in telling the BIOS to boot from the flash drive.

Have you read the release thread?

Have you tried setting this in your router?

Probably can't work with XFS filesystem in your desktop. Unassigned Devices is what I had in mind, but doing it in or out of the array won't matter much as far as the repair goes, you just don't have valid parity until parity is rebuilt. Any progress with finding a superblock?

That thread you linked is pretty old, but go ahead and let it continue for a while to see if anything works out.

I don't think there is any point in trying to repair the disk in the parity array when parity is invalid. Either rebuild parity then try to repair the disk after parity is rebuilt, or New Config without that disk, rebuild parity, and try to repair it outside the array.

Really wish you had asked for advice before doing anything. Pretty much everything you did was wrong. NEVER format a disk you think should have data on it. Format is a write operation. Unraid treats that write operation exactly as it does any other, by updating parity. So after you format a disk in the parity array it is empty and rebuilding an empty disk can only result in an empty disk. Would have been better if you had tried to work with the original disk as an Unassigned Device. Not sure what state it is in now since you put it back in the array. Maybe too late for anything and since you must have rebooted a lot of what you did will not be in syslog anymore. But we will know more about your situation if you post your diagnostics. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Looking at that syslog you already gave us disk4 was unmountable and disabled so it will have to be repaired before or after rebuilding it.

Since you can't easily get us anything else get us a new syslog.

Do you mean none of your shares are working, or just shares that are on disk2? According to your diagnostics, user shares are mounted as are all disks except disk2, including the emulated disk3.

Whether you repair disk2 before or after rebuilding disk3 would have no effect on the rebuild. The SMART warnings you are already getting on disks 2 and 5 might be a problem though and nothing you can do about that except replace them one at a time after you get disk3 rebuilt. It is also possible that the SMART warnings you have on disk2 might cause problems repairing disk2. Just take things one at a time and see where we get. Do you know how to replace a disk? Do you know what to expect during rebuild?

In order to reliably rebuild every bit of a failed disk, Unraid must be able to reliably read every bit of parity PLUS every bit of ALL other disks. Parity by itself can recover nothing. So obviously you don't want to wait until a disk completely fails to consider if any disks have problems since problems with any other disks that might not have completely failed yet can compromise any attempt to rebuild the failed disk. If nothing on the server is important or irreplaceable then I guess we will just go ahead and see what happens. Currently, you have no parity protection since you already have a failed disk. Rebuilding to a new disk would at least get you back to a place where you had some redundancy so I would start with that.

Disk3 doesn't even appear in those diagnostics. Emulated disk3 is mounted though so you should be able to rebuild it and it shouldn't need repair. Except... Looks like disk2 and disk5 are beginning to have problems also. How did you get to a point where you had multiple disks with SMART warnings? Do you have Notifications setup to alert you immediately by email or other agent as soon as a problem is detected?

You rebooted before getting those diagnostics so can't see what may have happened before that. Disk3 isn't giving SMART, check connections and post new diagnostics.

But you probably can't achieve that writing directly to the parity array, so you configure it to write to cache instead.

There are several things to consider with cache and speed. Cache (or additional pools with 6.9), your Dockers and VMs are usually configured to use that space for performance, and so array disks can spin down. Cache is also used to cache user share writes to be moved to the slower array later. Often people will disturb connections when replacing a disk and dual parity can sometimes help with that. And, sometimes another disk will actually begin to have problems while rebuilding another disk. Be sure to setup Notifications to alert you immediately by email or other agent as soon as a problem is detected. Unraid monitors SMART for all disks (unless you try to use RAID controller, don't).

There is a parity2 slot you can assign 2nd parity disk to. Each parity disk must be at least as large as the largest single data disk.

Don't install disks just because you happen to have them. Only add what you need for capacity. Each additional disk is an additional point of failure, requires more hardware to support and more power. Older smaller disks often aren't worth bothering with, fewer and newer larger disks perform better and don't require as much hardware and power. If you plan to have many disks be sure to setup dual parity.

https://wiki.unraid.net/index.php/Replace_A_Cache_Drive

Then you should be able to just boot up and use blank password.