was able to login normally then yesterday was having problems with logging in to unRAID.   locally I can sometimes get to the page sometimes get http 500 error.   but when I get to the page when I try to login nothing happens.   if I enter a wrong password it says invalid but nothing happens if I hit the right one.  I figured it was just a little weird so I rebooted using the terminal and things worked again but today the same thing is happening. Dockers are still going fine and all that. I just can't login on the server main page.  only odd thing that happened lately was I accidentally filled the first drive in the array to the brink but have since fixed that and my client now preallocates the file space so it shouldn't happen again.  any ideas what is wrong and how to fix it?

 

edit my roots was completely filled with tons of stuff in /mnt/none/   any idea why stuff would be put in there?  once I emptied out a bit of space in there I could restart nginx and login.  its copying files I think should be on the original array to this for some reason and I don't know why I can see it increasing in size the longer it runs

 

solved it is the mover putting files in /mnt/none.   why would mover be doing that?  I did install mover tuning a few days ago so I figure I screwed something up there

Edited December 9, 20241 yr by duelistjp
more info

you have a phantom mount from a previous configuration and instead of something writing to a disk it is writing to the unraid root system in ram until it is full and unable to do anything. 

You will need to go though every docker, vm and setting to make sure they have complete disk mounts and paths.

Please post diag file to help troubleshoot.

figured it out I had installed mover tuner then removed it when I realized it wasn't what I wanted I uninstalled it.   had to reinstall it tell it to disable running mover on a schedule then uninstall it and now there is no /mnt/none folder being created.  I don't use a cache so no need for it.