trurl

Looks like disk5 disconnected and is now an Unassigned Device. SMART for that disk P86N looks OK. Emulated disk5 is mounted and shows plenty of data. I assume that is the disk you are referring to as failed, but looks like a connection problem and not a disk problem. Check connections on disk5, SATA and power, both ends, including splitters. Then post new diagnostics.

If some of those Unassigned Devices are permanent, you might consider making them pools instead.

Feb 17 22:05:20 Backup kernel: I/O error, dev sdj, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Feb 17 22:05:20 Backup kernel: sd 7:0:6:0: Power-on or device reset occurred Some of this on disk2. Post new diagnostics.

Parity swap might be what you need. But please attach diagnostics to your NEXT post in this thread and wait for further advice.

SMART for all disks looks fine. You haven't completed extended self-test on any but no reason to think they wouldn't pass. RAID controllers are not recommended for many reasons, and this may be one of them: Feb 14 18:01:31 Tower kernel: sd 1:1:17:0: [sdc] tag#643 access beyond end of device You are getting these on multiple disks. Syslog had lots of macvlan traces, don't know if you fixed that yet. See release notes: https://docs.unraid.net/unraid-os/release-notes/6.12.6/#call-traces-and-crashes-related-to-macvlan Also some out-of-date plugins. Filesystem corruption on disk5. Not clear if that is still the case, or if emulated disk5 is mountable, since these diagnostics were taken without the array started. Can you start the array and post new diagnostics?

Attach Diagnostics to your NEXT post in this thread. Do you have a current backup of flash drive?

Really wish you had asked before doing anything. Bad connections are much more common than bad disks. Can you put all the disks back in your server and Attach Diagnostics to your NEXT post in this thread.

Try this at the command line /usr/local/emhttp/webGui/scripts/notify

Fastest way to get back to dual parity would be to go ahead and rebuild parity2 and disk3 at the same time. And once it has gotten to the end of disk3 rebuild you will again be protected by single parity, and it can continue with the rest of parity2 rebuild.

You have a large number of plugins, and for some reason checking plugin version is blocked or something, so can't easily tell if any are out-of-date. Updating all plugins was mentioned in the release notes. In fact, booting in SAFE mode is mentioned in the Report Guidelines I linked above. And, you have a lot of stuff in the extra folder on your flash drive, probably put there by NerdTools. Not sure if extra folder will be loaded if you boot in SAFE mode or not.

Might be worth seeing diagnostics with the array started in normal (not maintenance) mode so we can see if rebuilds are mountable and how to proceed.

Probably unrelated, but you were supposed to update all plugins.

You can only move it to another USB stick. Are you booting USB2 port (recommended)?

Probably the problem you are having in this thread is just a consequence of not fixing the problem in your other thread.

Default shares are not created until Docker and/or VM Manager are enabled. And those paths are actually determined by the Docker and VM Manager settings made. So not everyone will have appdata. Flash drive is the only persistent storage guaranteed to exist.

Post diagnostics https://forums.unraid.net/bug-reports/stable-releases/report-guidelines-r68/

You can't mean simply running memtest fixed your pool, so what do you mean?

The link you posted is "legacy" as it says. https://docs.unraid.net/unraid-os/getting-started/ 2GB is probably bare minimum now, and may be too small in some circumstances. Update can't be in RAM since it has to reboot.

You didn't really finish this earlier thread by telling us what you did, just marked it solved. Did you actually fix it?

How long did you let it run?

Have you tried non-GUI boot in SAFE mode and getting diagnostics from the command line?

You want docker related appdata and system shares all on fast pool so get cache fixed first.

https://docs.unraid.net/unraid-os/manual/tools/#new-config