trurl

Post new diagnostics

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

Your diagnostics show you have /mnt/user0 but not /mnt/user. This would make me suspect a problem with cache, but you do have /mnt/cache also, though cache has little if anything on it. Have you recently reformatted cache or had some problems with cache?

Why have you give 64G to docker image, have you had problems filling it? 20G should be more than enough, but I see you have already used more than that. The most common reason for filling docker image is an application writing to a path that isn't mapped.

I'm pretty sure you should still have user0 if things were working normally. Since the diagnostics aren't telling which disks are used I don't know if any of your cache-prefer shares have files on the array. In fact, it is possible that even cache-only shares would have files on the array. Just setting a share to cache-only will not move any files for the share that are already on the array, for example. Normally, diagnostics shows which disks actually contain files for each user share. This is independent of any settings for the user share. The settings for your shares are in the diagnostics, just not which disks actually contain files for the share. Something is broken. Have you ?

Personally I don't bother with split level. I just use the "Included disks" setting for each of my user shares. I have 2 disks filling with Movies, another with Backups, etc. When I need more space for a share, I either upsize one of the included disks, or add a disk and include it in the share. The main purpose of split level is to keep things like music albums, or tv series, together so another disk won't have to spin up during playback. Just keep different things in different shares and include specific disks for each.

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

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

Why are all your array disks still on ReiserFS? My guess is some sort of filesystem corruption on one or more disks. Even though you have cache, you have no /mnt/user0, and diagnostics doesn't even show which disks each user share is using. Check filesystem on each disk.

Don't cache the initial data load.

Unraid doesn't run from the Flash, it unpacks the OS archive from Flash into RAM at boot and it runs in RAM. You may get better reliability from a USB2 Flash (and port).

Post your docker run command for plex as explained at this very first link in the Docker FAQ:

Try the manual method here: https://wiki.unraid.net/UnRAID_6/Changing_The_Flash_Device#Legacy_method_-_Windows_and_MacOS

I also noticed many of your array disks are very full, and you have no cache. Dockers/VMs will perform better and not keep array disks spinning if appdata, domains, system shares are not on the array. Likely all your disks stay spinning since you have those shares all over the array.

Do you have a root password on this server?

Change the "Peer Type of Access" selection.

Are all your plugins up-to-date? One of the plugins I was trying to avoid with SAFE mode is Unassigned Devices since it looked like something might have hung there. Did you have any Unassigned Device set to Auto-mount?

Don't even think of using anything except NAS functionality till you get more RAM. If you want to use dockers you should consider 4G to be minimum and more is better. If you want to use VMs then you would need enough RAM to give the VMs what they need plus more for Unraid and dockers to use. Even with strictly NAS, there are some things that may not work without more RAM, because those things use RAM for temp storage. Upgrading from the webUI will download to RAM before writing the upgrade to flash, and getting Diagnostics will compile those diagnostics in RAM before downloading them. And Diagnostics are very important for letting us troubleshoot.

How old was that appdata backup your restored? Have you reconfigured the CA Backup plugin recently? The last appdata backup with the CA Backup plugin in the syslog of your earlier diagnostics looks like this: Jul 16 03:00:05 Tower CA Backup/Restore: Backing Up appData from /mnt/user/appdata/ to /[email protected] Jul 16 03:00:05 Tower CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar -cvaf '/[email protected]' --exclude 'docker.img' * >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress Jul 16 03:00:05 Tower CA Backup/Restore: Backup Complete Jul 16 03:00:05 Tower CA Backup/Restore: Verifying backup Jul 16 03:00:05 Tower CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar --diff -C '/mnt/user/appdata/' -af '/[email protected]' > /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log & echo $! > /tmp/ca.backup2/tempFiles/verifyInProgress Jul 16 03:00:06 Tower CA Backup/Restore: ####################### Jul 16 03:00:06 Tower CA Backup/Restore: appData Backup complete Jul 16 03:00:06 Tower CA Backup/Restore: ####################### As you can see it completed almost instantly, so that seems to indicate appdata was already gone at that point. I also notice your version of that plugin is out-of-date (as are some others) Unfortunately, diagnostics has anonymized some things in that portion of the log so it isn't clear what the destination of the backup was. It makes me wonder if maybe you haven't misconfigured that plugin so that it was using the appdata folder as the destination of the backup and so wiped it out before beginning the copy.

Have you tried booting in SAFE mode?

Do you have any unassigned devices?

Looks like a memory problem. Do you really have 165G RAM?

Do you actually plan to use the NAS capability of Unraid?

Still not going to be enough to get the full benefits of V6, and even if you stick strictly to NAS functionality, you may still have some problems, such as upgrading from the GUI.

Why get duckdns involved if you have your own domain?