trurl

All your array data disks are mounted and no I/O errors logged. Your docker.img has corruption so you will probably have to recreate and reinstall, but that isn't related to parity. Since parity has none of your data, might as well let it finish correcting sync errors.

Do you have another copy of anything important and irreplaceable?

Is this assigned to the array? SSDs in the array cannot be trimmed.

UPS should only be on battery long enough to get past brief outage, then if power doesn't come back very soon, shutdown. You don't want to run on UPS, only shutdown on UPS.

Those small laptop HDDs probably don't perform well. And your parity disk is SMR which might be the reason a pause helps it out.

syslog says it is correcting, but I think unclean shutdown parity check is supposed to be non-correcting. I don't know if plugin affects that or not. Seems like more sync errors than I would expect from unclean shutdown. Were previous parity checks zero sync errors?

Check filesystem on disk2 from the webUI. Capture the output and post it.

First post in thread 😉

Probably because of your split level setting

I see that setting now.

What does this refer to? Doesn't seem to be anything related to the Unraid OS itself. If you are asking about a docker container you should go to its support thread or page. You can usually get there by clicking its icon in your Unraid webUI and selecting Support. For future reference

You're right, it only lets me set it to a user share path. Which is probably better anyway since UD devices may not be mounted. And in the more general case where you are really sending syslog to a remote server, it has to be a shared path. Does it work with both NFS and SMB? Or does it do it some other way?

You should be able to see your CPU temps in the BIOS. And Dynamix System Temps plugin shows this for me in Unraid.

The flash drive is the only device that is guaranteed to exist. You can configure syslog server to use a path on an Unassigned Device with the other settings, but flash is the only thing that makes sense for "mirror" since it doesn't require you to set any path.

Not clear there is anything wrong with disk1, and replacing/rebuilding it won't fix its filesystem.

Probably better to start a new thread with your diagnostics than post to a 5 year old thread about a version you don't have.

I often recommend not even using parity with USB since if something disconnects, the array won't be out-of-sync since there is nothing to be in-sync with. So nothing to rebuild. But nothing can be rebuilt.

Each data disk in the Unraid array is an independent filesystem that can be read all by itself on any Linux. You could just New Config disk7 back into the array and rebuild both parity. Maybe physical disk7 is actually mountable and not corrupted. And then live with whatever results from repairing disk1 and possibly disk7 (until the next time). Even if parity rebuild won't succeed, parity contains none of your data as mentioned. Your earlier diagnostics seemed to indicate there was a lost+found share, which would have been the result of an earlier check filesystem. It doesn't show as currently existing, possibly it is on the unmountable disk7 so can't be seen until repaired (again).

Maybe because they had empty mappings, which is technically a syntax error. Previous versions allowed this. You can get rid of the empty mappings, or install Docker Patch plugin.

Diagnostics after reboot can't tell us what happened before. Setup syslog server. You have some out-of-date plugins. This one in particular has caused problems recently: disklocation-master.plg - 2024.03.10 (Update available: 2024.03.22) This might be related:

When you add a disk to a new slot in an array that already has valid parity, Unraid will clear the disk unless it has been precleared so parity will remain valid. All those zeros on a clear disk has no effect on parity. This is the only scenario where Unraid requires a clear disk. After the disk has been cleared and added to the array, you can format it so it can be used for files. A disk that hasn't yet been formatted will appear as unmountable. In Main - Array Operation, it will list all unmountable disks and give you a checkbox to enable the format button and allow you to format them. You can see this in the screenshot you posted above. NEVER format a disk that should contain your data. An unmountable disk that should have data on it needs to have its filesystem repaired. That is what check filesystem is for. Or, as suggested above, maybe its partition needs to be fixed. DO NOT FORMAT!!!

I don't know what you mean by that. Parity is not a substitute for backup, whether Unraid or some other system. Parity contains none of your data. Parity is just an extra bit that allows a missing bit to be calculated from all the other bits. That is basically how parity works in any system, Unraid or otherwise. Parity contains parity bits that allow the contents of a failed/missing/disabled/emulated/rebuilding disk to be calculated from the bits on all the other disks. https://docs.unraid.net/unraid-os/manual/what-is-unraid/#parity-protected-array Parity by itself can recover nothing. All bits of all other disks must be reliably read to reliably rebuild all bits of a disk. And as we have seen, it doesn't appear that your current setup can reliably read all other disks.

Doesn't look like there were any problems communicating with disk1 during that. Do you have another copy of anything important and irreplaceable?