trurl

Doesn't look like you're getting DHCP. Can you see your server on your router? Check ports, plugs, cables on server, switch, router.

Did you test it?

I assume you mean Dynamix File Manager.

You really shouldn't overclock a server anyway. Data is more important than any marginal speed improvements, and I/O is going to be the limiting factor anyway, not the CPU.

The linux 'file' command might be able to tell you what kind of data is in each file, then you can try to open it with an appropriate application to see if you can identify it. If you drill down into those folders you might find some things that still have the correct names. You can move them to their correct folder on disk4. Each user share with files on disk4 will have a top level folder named for the share. Looks like the only user share you have besides the defaults and that newly created lost+found share is M---a shareUseCache="no" # Share exists on disk2, disk3, disk4, disk5, disk6, disk7 I'm guessing that is Media.

I don't use zfs, are there separate cron files for each pool? I have one for my btrfs pool named cache, and it is named for that pool, but its contents also specify the scrub command to scrub that particular pool.

You should go ahead and post diagnostics now since we don't have it yet in this thread.

Check in config/plugins/dynamix on the flash drive for those cron entries. I don't use zfs but I know others are there.

I know you have lost+found. That command will tell you the size of that share and its subfolders. On the main bar of your Unraid webUI, mouseover the >_ You will see that it is Terminal Click it to get a browser window at the command line.

Looks like you changed it to mirror to flash. That will do for now but you don't want to do that all the time. The other settings setup your Unraid server to receive syslogs from other servers and specifies where it will store them. You have to specify a remote server to send your Unraid logs to. You can use your own Unraid server itself as the remote, just put its IP for remote syslog server. All of this is discussed at the syslog server link. Or you can just let it mirror to flash and get the syslogs from there. Do you know how to get the logs from your flash drive the next time you experience the issue?

Have you got some sort of custom theme installed? Why doesn't that screenshot have any labels for any of the fields? Have you read the syslog server link?

That appears to be mostly the same as the syslog in your diagnostics. Do you know where syslog server is saving the syslog? Post a screenshot of your settings for syslog server.

That shouldn't be a problem. Probably most things except plugins should be fine. All the rest is just .cfg files, settings from the webUI. They are all text so you can examine them. If any look corrupt don't copy. If you had anything in the extra folder on flash leave that out too.

https://docs.unraid.net/unraid-os/manual/docker-management/#configuring-a-container

If you have many dockers, you are going to need to know how to map ports, because many applications will want to use the same port.

We always want the complete diagnostics zip.

Why do you want to change that port?

Do you have a syslog from syslog server?

Unrelated, your system share has files on the array. We can deal with that later. The timestamp on these latest diagnostics says 20240212-1534 Last syslog entry about 30 seconds before that. Feb 12 15:15:04 Is that not the correct time for you?

Disk1 is mounted and has plenty of data. Also, filesystem repair didn't result in any lost+found. Disk2 appears to be empty, or nearly so. Is that expected?

Please help us help you. Start the array in normal (not maintenance) mode and post new diagnostics.

And post new diagnostics

Almost everyone you encounter on the forum, including moderators, are your fellow Unraid users, just trying to help each other. Free support is on the forum from your fellow Unraid users. Paid support is available but not included in the purchase of Unraid. And, you already have multiple people on this thread, some of the most knowledgeable people on the forum. Also, if you post about the same thing in multiple places, it makes it impossible to coordinate responses. Not hijacking and not crossposting has been basic etiquette in internet discussions since before the World Wide Web. Please cooperate.

Filesystem corruption and parity sync are also unrelated. What do you get from command line with this? du -h -d 1 /mnt/disk4/lost+found

Read the documentation I linked.