trurl

If you have rebooted then it won't be full anymore.

https://wiki.unraid.net/UnRAID_6/Storage_Management#Replacing_disks

From backups may be the simplest. The problem is those files will have lost anything that tells their name or folder. How much is there?

syslog and docker.log in those diagnostics aren't very large but /var/log is full. What do you get from the command line with this? du -h /var/log

Do you know if docker.img is getting full? You can see on the Dashboard how much is getting used. You can also use the Container Size button at the bottom of the Docker page to see how much each is using.

Also, the version of Unraid you are running is over a year old. Why haven't you upgraded?

I have replied on your thread.

docker.img corrupt. Why have you allocated 40G to docker.img? Have you had problems filling it? 20G should be more than enough and making it larger won't fix anything, it will just take longer to fill. I am running 17 dockers and they are using less than half of 20G. You will have to delete and recreate docker.img. Previous Apps on the Apps page will reinstall your dockers just as they were. Some of your appdata is on the array. You should set that share to cache-prefer so it can be moved to cache. While you have docker disabled you can run mover to get the rest of appdata moved back to cache. Mover can't move open files so you will have to do that before installing your dockers again.

docker.img corrupt. You will have to delete and recreate it. Previous Apps on the Apps page will reinstall your dockers just as they were. Some of your appdata is on the array even though cache isn't full. Have you had problems filling cache? While you have docker disabled you can run mover to get the rest of appdata moved back to cache. Mover can't move open files so you will have to do that before installing your dockers again.

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

SMART for disk11 still looks OK. Stop, shutdown, check connections, SATA and power, both ends, including any splitters. Change SATA cable if you have another. Then reboot and Start parity sync again.

That is a lot of read errors on disk 11. Maybe the disk is failing. Go ahead and post those Diagnostics since that is the easiest way to get me everything else including SMART for all disks.

That isn't diagnostics, that is only syslog. Diagnostics contains syslog and many other things. But syslog probably has most of what we need now so I will take a look. You did manage to post diagnostics in the first post. It is on the Tools page.

Post diagnostics

Unmount that Unassigned Device. Stop the array. Go to Tools - New Config and keep all assignments. Before starting the array, reassign disk11. Make sure you do NOT check the box saying parity is valid, because it needs to be rebuilt. It may only be a little out-of-sync but it should be rebuilt anyway. Then Start the array to begin parity sync. If there are any problems during parity sync, post your diagnostics but let it continue pending further advice. What you should see during parity sync is a lot of Reads on all data disks, a lot of Writes to parity, and zeros in the Errors column. Parity sync errors are expected, be interesting to see how many.

No that is correct, just being cautious. Go ahead and start the array. Disk 11 should be missing, disabled, and unmountable but you should be able to look at the Unassigned disk on the network.

Probably should have been posted to General Support instead of Bug Report. I may copy it there eventually.

Just to make sure. On Main - Array Devices, does it show disk 11 as No Device or similar? I guess you will have to start the array to get SMB started so you can look at that UD on the network. Or you could examine the files from the server itself if you know how to use Midnight Commander (mc from the command line) or just how to work from the command line.

The slider under "Share" will let you share it on the network so you can look at it from your PC. Maybe you will have to unmount it before it will let you change that, I'm not sure.

Post a screenshot of Main - Unassigned Devices

Just thought I should warn you that you don't want to reassign that disk without doing New Config first. Reassigning a disk is the way you get it to rebuild, and you don't want to rebuild it.

That looks good. Have you checked the files on the disk with it mounted Unassigned?

It is good because you still have the files. It is bad because we don't know the cause of the disk becoming disabled nor the reason the emulated disk was unmountable. Since you rebooted after you began to have problems, syslog from your diagnostics don't tell us anything about what may have happened. Do you have any ideas about this? Do you have any reason to think your parity was invalid? Your screenshot didn't show all disks. Were any of them showing anything other than zero in the Errors column? To get that disk back into the array will require New Config / Parity Sync. But before we proceed with that lets see if we can figure out what went wrong, or at least make sure there isn't something currently wrong that would prevent parity rebuild. You have a lot of disks, and I haven't examined SMART for each of them. Do any of the disks show SMART warnings on the Dashboard? Post a screenshot of the Array section on the Dashboard page.

I will probably copy this to General Support after we get the syslog and diagnostics since this thread doesn't really conform to Report Guidelines:

I will probably copy this to General Support after we get the syslog and diagnostics since this thread doesn't really conform to Report Guidelines: