trurl

Another snippet, the first few lines of your syslog: Dec 6 07:54:30 Tower kernel: microcode: microcode updated early to revision 0x714, date = 2018-05-08 Dec 6 07:54:30 Tower kernel: Linux version 4.18.20-unRAID (root@develop64) (gcc version 8.1.1 20180626 (GCC)) #1 SMP Fri Nov 23 11:38:16 PST 2018 Dec 6 07:54:30 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot So as you can see, your server had rebooted

Why do you think I posted that snippet from your syslog? You didn't know a parity check was underway? You were in a non-correcting parity check due to unclean shutdown, and it found parity errors, so your parity needs correcting. Setup Sylog Server so your syslog can be retained after a crash.

Increase capacity by replacing drives with larger drives.

Locking this thread since the user found the correct support thread.

One thing I notice is your appdata share is cache-only, but has some files on the array. After cleaning things up and rebooting, stop docker service, change appdata to cache-prefer, and run mover to get it moved to cache where it belongs.

Sounds like your problems may be deeper than just this one docker. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

https://forums.unraid.net/bug-reports/prereleases/how-to-install-prereleases-and-report-bugs-r8/

Since the OS runs in RAM and can't make any assumptions about anyones persistent storage there is nothing to keep that history.

Locking this thread since the user has found the support thread.

Since each disk is independent in Unraid, the speed of those disks would only matter if you were reading or writing them, or possibly if you were using "Turbo Write" where all disks are read in order to update parity. I would say don't worry about it. But, I always recommend not installing more disks than you need for capacity. Each additional disk requires an additional port, additional power, at some point more Unraid license, and most importantly, each additional disk is an additional point of failure. Don't install old disks just because you have them.

You can go directly to the correct support thread for any of your Dockers by simply clicking on the icon for the container on the Dashboard or Docker page and selecting Support.

Please don't do this. Pick one thread to receive replies in and post in that one. If you must, post a link to that in the related thread. It is impossible to coordinate replies when you crosspost.

Better but still too full. You have a share anonymized as w---------k which is cache-prefer and all on cache. What is your purpose for this share and keeping it on cache?

yes

And to answer the question in the title, your data should be fine.

Shut down, check all connections, SATA and power, both ends, including any power splitters. Reboot and post new diagnostic.

Put flash in your PC

Delete or rename config/network.cfg on flash to go back to default and reboot.

Except for the CRC errors which usually just indicate a bad connection, drive looks OK. You mention reformatting parity. Parity doesn't have a format. You have a common misunderstanding of the meaning of the word format, a misunderstanding which sometimes gets people in trouble when they mistakenly apply it to a data disk. Go to Tools - Diagnostics and attach the complete Diagnostics zip file to your NEXT post.

I don't understand this part. Are you talking about settings within each specific application, or are you talking about the settings for each container on the Docker page? The settings for each container on the Docker page is exactly what the Previous Apps feature is about.

During bootup, there are 8 hours between consecutive lines in your syslog. Dec 9 04:49:08 Yggdrasil root: Installing perl-5.30.0 package... Dec 9 12:49:22 Yggdrasil nerdpack: Cleaning up packages... I am guessing this is an artifact rather than an actual elapse of 8 hours, possibly your server adjusted its time somehow. Any idea what might have happened there? If we subtract out that apparent gap, syslog only contains a few minutes after booting. Go to Settings - Syslog Server and set that up so your syslog can be saved somewhere you can get it after rebooting from hanging.

You can go directly to the correct support thread for any of your plugins by selecting its Support link on the Plugins page in the webUI.

Go to Tools-diagnostics while problem is happening then attach complete Diagnostics zip file to your NEXT post.

oops! I was looking at the arrow backwards.

Not familiar with that method to backup flash. You can just download a zipped copy of flash from Main - Boot Device - Flash - Flash Backup. Different version of kernel would of course be a different version of Unraid. Usually a new install with the config folder copied from backup should get things going as they were, but let's see what happens without plugins.