trurl

You can go directly to the correct support thread for any of your plugins by using its support link on the plugins page

Let us know when parity rebuild completes.

Unraid requires one data disk in the array before you can start services to use dockers or VMs. You could access shares from a separate freenas server over the network using Unassigned Devices plugin. Not sure if this would perform any better for transcoding than what you have now since the files would have to come over the network before they could be transcoded. Why not just get your data onto Unraid NAS and leave freenas out of it?

Yes. No.

Do you have a link?

Unraid IS NOT RAID. Do you mean that is your current system, or do you mean you require freenas as the data pool on your new system? Some of your questions make me wonder if you know what Unraid is. Unraid is a NAS OS that hosts VMs and Dockers. The NAS part of Unraid isn't exactly RAID, but it does allow for up to 2 parity disks. Each data disk is an independent filesystem, no striping. This allow mixing disk sizes in the array.

It isn't necessary to login to know when you have a problem. You must setup Notifications to alert you immediately by email or other agent as soon as a problem is detected. SMART attribute for parity2 look OK. Syslogs in diagnostics don't seem to include the events of the disk getting disabled. Possibly there are even older syslogs in /var/log that might show what happened. Run an extended SMART test on parity2. If it passes you can rebuild to the same disk. To rebuild to same disk (whether parity or data): Stop array Unassign disabled disk Start array with disabled disk unassigned Stop array Reassign disabled disk Start array to begin rebuild.

Parity is always updated simultaneously with each write to a data disk. Diagnostics?

Delete docker.img, change size to 20G, recreate, reinstall your dockers using the Previous Apps feature on the Apps page.

Peer type of access is set to only allow connections to the server.

Pretty sure 60G should not be needed for that many. As I said: Making it larger won't fix anything, it will just make it take longer to fill. Do you understand what I mean by this? Linux is case-sensitive, for example, so if an application is writing to a path that doesn't match a container path re: upper/lower case then it is writing into docker.img

Sounds like you may be on the right track now, but just thought I would comment on your original proposal. This is often asked, but "Clean install" is a common "solution" in Windows folklore, but I've never needed it in Windows. In the case of Unraid, if you boot in SAFE mode (which results in no plugins loaded) and also don't load any VMs or dockers, then that is effectively a "clean install" of whatever release you are running, because Unraid runs in RAM. It installs itself fresh from the archives on flash into RAM at each boot. So, if you are keeping your data I don't see how "starting over" can have any effect that couldn't be more simply accomplished by removing addons.

I can access everything on my LAN thru Wireguard on Unraid. Post a screenshot

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

Seems a little drastic though and not clear how it could help. Maybe Diagnostics would give us a better idea what the problem is. Go to Tools-diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Do you have the problem with stock Unraid build?

The usual reason for filling docker.img is an app writing to a path that isn't mapped.

Why not run headless?

The usual reason for filling docker.img is an app writing to a path that isn't mapped. Docker.img is mounted but not clear if it has corruption since no useful info in syslog due to all that other stuff. How many containers do you have?

Did you figure out why and fix it?

Why do you have 60G allocated to docker.img? Have you had problems filling it? 20G is usually more than enough. I have 17 containers and they are using less than half of 20G docker.img. Also, your system share has files on the array, possibly that docker.img Your syslog is spammed with these messages, any idea what that is about? Oct 10 04:42:12 Tower kernel: br0: topology change detected, propagating Oct 10 04:42:16 Tower kernel: br0: port 1(eth1) received tcn bpdu

Windows only allows one login between computers. Once it has already established credentials it won't use others even if it asks you to login. Go to Windows Control Panel-Credential Manager and delete Unraid credentials so it will renegotiate. See Windows Issues thread pinned near the top of this same subforum for more.

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

Did you have cache?

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