trurl

On mobile now so can't look at Diagnostics. Post a screenshot of Main-Array Operations

Bad RAM is a possible reason for post-read fail. Have you done memtest?

Do you know about this? https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564314

Can you get diagnostics immediately after booting? That would be better than nothing. Also you might try setting up Syslog Server so you can get syslog from before hang: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

User shares are the top level folders on cache and array. When you create a user share Unraid creates a top level folder on cache or array, named for the share, as needed according to settings you make for the share. Conversely, any top level folder created on cache or array is automatically a user share, named for that top level folder. The screenshot you posted earlier showing the settings for that AppData share are just the default settings you would get for any share that gets created when you create a top level folder on cache or array. You have something creating a top level folder on cache or array named AppData. Docker mappings are a common cause of accidentally creating user shares. You will have to figure out what is creating that folder.

I have split your post into its own thread so you can get us more information without cluttering up the thread of that other user. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post. It might not tell us exactly what is happening when it hangs, but it will tell us a lot about your configuration and save a lot of questions. Since syslog resets on reboot, also setup Syslog Server so you can get us the syslog from before rebooting: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601 Have you done memtest?

Your docker settings are in templates on flash and the Previous Apps feature on the Apps page will use those templates to reinstall your dockers exactly as they were.

This is a connection issue. If it only increases a small amount infrequently then I just acknowledge it, otherwise look for the problem causing the connection issue.

Take a look in Settings - Docker and make sure you haven't put it in there as AppData

An emulated disk (disabled) will have a red X next to it on the Main page, and if it is mounting, it will also have a filesystem listed for that disk on that same page. If it is not mounting it will also show that in the place where the filesystem is displayed. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

Are you using a docker for doing downloads?

Use the built in Wireguard VPN instead

Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

You haven't told us if you have followed our recommendation about booting from a USB2 port.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Put flash in PC and let it checkdisk. While there backup config folder. Boot from a USB2 port.

You can go directly to the correct support thread for any of your dockers by clicking on its icon and selecting Support.

Syslog snippets are seldom sufficient. Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post

Thought I would update this now that I have everything going again. I used my Node 304 as a test bed since the parts were coming in over several days and I kept my main server going on the old mobo in the meantime. I had already lost 2 ports going to that old mobo, but one was unassigned and the other was parity2. And the new mobo wasn't going to get me back to 10 ports without using that expansion slot, so parity2 wasn't coming back. I only had 5 data disks anyway. So while I tested the new stuff as it came in, I reconfigured my storage on the still running main server. Since I already had some SSDs reclaimed from other projects, I upgraded my raid1 cache pool from 2x275GB MX300 to 2x500GB 850EVO. Then I thought it might be fun to use the M.2 slot on the new mobo, what with multiple cache pools in our future, but that meant I had to give up another SATA port (and another part to buy). I shuffled files until I could shrink the array, only giving up one 4TB drive in the process (all others are 6TB). Since my former parity2 was 7200RPM instead of 5400, I decided to use it to rebuild one of my remaining data drives. One of the other disks threw 41 pending sectors during that rebuild, but the rebuild seemed to be OK anyway and a filesystem check didn't find anything. I ordered an 8TB disk which I will use for parity swap when it comes in Sunday. That will get me started on upsizing my old drives, now that they are one fewer. So today the last part came in (except that parity swap disk), a 256GB M.2. Everything worked as it was supposed to, including that OCULink cable. The M.2 took one port from that though. I moved all the new stuff into my PC-Q25 case. No problems so far on the new hardware.

Attach to your NEXT post

Don't try to access Unraid that way. Setup the built-in Wireguard VPN

Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post

Go to Tools-diagnostics and attach the complete Diagnostics ZIP file to your NEXT post