trurl

For future reference, you can always download a zipped copy of flash at Main - Boot Device - Flash - Flash Backup

Everything about your configuration is in the config folder on flash. As long as you have a current copy of that config folder you can use it on a new install and everything should work as before.

Our Docker FAQ is pinned near the top of the Docker Engine subforum. Here is a direct link to it: https://forums.unraid.net/forums/topic/57181-real-docker-faq/

Your docker image is corrupt. And the fact that you have given it 80G makes me suspect you have been filling it or it has been growing. I always recommend only 20G for docker image. Making it larger will not fix anything, it will just make it take longer to fill. Most likely you have one or more of your docker applications writing into the docker image instead of to mapped storage. If any application is writing to any path that is not in a mapped container path, then it will write into the docker image, filling it up. All applications must be configured to use paths that are absolute and correspond to a container path, case-sensitive. Also, your cache disk is completely full, possibly that is corrupt also. Unfortunately, your old version of Unraid doesn't give us all of the useful information about your configuration that more recent versions do. For example, I can't tell what user shares have files on your full cache. I see you have most shares set to not use cache, but I suspect you just changed them to that because you realized you were filling it. And setting them to not use cache won't get anything moved off cache. Go to Settings - Docker, disable docker service and delete the docker image. Leave it disabled until we get room on your cache. Go to Shares - User Shares and click the Compute All button. Wait for the result, it will likely take several minutes. Then post a screenshot of that page.

Post your docker run command as explained at the first link in the Docker FAQ

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

Looks like a flash drive problem. Put it in your PC and checkdisk. While there make a backup. Be sure to boot from a USB2 port.

Could you give more details about this? Did you install the dockers before or after you created the new array?

I suspect you don't have any mountable disks yet. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

Each connected drive counts, whether parity, cache, array, or even unassigned.

I don't remember anything specifically and since I don't mac it's not something I encounter myself. Those are easily deleted in Midnight Commander. They would be located in /mnt/user/<sharename>. Is there something you can do on the mac end to prevent it from creating those hidden files?

So do you have any dockers mapped to an Unassigned Device or anything else that might be trying to use one?

I am not sure what you mean by this. How did you rename the share? Are you sure Plex is able to access the files at the old name, or is it just showing the old name because you haven't changed the plex library.

This is not the place for discussing problems with a plugin. You can always go directly to the correct support thread for any of your plugins by using its Support Thread link on the Plugins page.

If that 14TB doesn't have any data then it goes into the array as disk1 and gets formatted by Unraid. It is never an Unassigned Device.. Nothing you can do with the Unassigned disks until you have an array disk to start. Then you could just leave it as disk1 and after you get some or even all the other disks copied and assigned to the array you could move disk1 contents to those other disks. Then when you are ready for parity, set a New Config with that disk as parity and all the others as data, and begin parity build.

If you take that "future parity drive", and format it as disk1 in the array, then you could copy the data from one of the other drives that is mounted as an Unassigned Device. But then you talk about copying a 14TB drive to the next drive using Unassigned Devices and I or maybe you are confused at that point. If the 14TB you are talking about copying is that disk1 you already have in the array, then it wouldn't be an Unassigned Device. The "Unassigned" in Unassigned Device refers to disks that are not in the array. Once the disks are in the array and formatted by Unraid, then you can copy and move the files around between them as much as you want. But the disks that haven't been formatted by Unraid yet can only have their data accessed as Unassigned Devices.

I assumed you wanted to reuse the drives. If so then you would need one empty drive, perhaps an existing drive if you could move its contents elsewhere. Make an array with that one drive and format it, copy data from another drive, add and format that already copied drive, repeat.

I noticed some FSCK files on flash which means some corruption had been "repaired". You could try preparing flash as a new install then copy the config folder from your flash backup.

You have to copy it yourself. I usually use the builtin Midnight Commander.

All disks mount but user shares don't. I don't think I've ever seen that before. Try stopping and starting the array. Do you have a backup of flash? You can download a zipped copy of flash at Main - Boot Device - Flash - Flash Backup.

This likely won't have anything to do with your crash but you should set domains and system shares to cache-prefer, disable docker and VM services, and either delete docker and libvirt images so they can get recreated on cache, or run mover to get those shares moved to cache where they belong.

Before you even enable docker and VM services. If I understand correctly you have complete backups so leaving parity till after the transfer makes a lot of sense and will make things go faster.

You don't have a parity disk, is that correct? Start the array and post new diagnostics. A started array has a little more to tell us.

See if it will work in SAFE mode and with no dockers or VMs. Also post Diagnostics. It can tell us more about your configuration and hardware than just syslog.

I think he is wondering if your flash drive is still mounted. Go into the console and see if there is anything in /boot.