bilr514

Hi...I'm going through trying to cleanup following a power outage. I have about 53,000 directories in my Lost+Found directory. Many of these directories are empty. Is there a way to mass delete the empty directories or subdirectories to reduce my search time?

I previously had a power outage which caused one of my drives to be unmountable. Through the forums here JorgeB helped me do a repair on the drive that was having the issue and all is now well, with one exception. I'm missing quite a few files (well over 3,000). I've browsed the individual drives to see if I could locate one of the files and I cannot, but the same amount of space seems to be consumed on the drives so I assume the files are still there but appear to be hidden. I looked through the forums and found a post that was similar where it was suggested that the particular user in question had corruption issues on one of his drives that was identified in the SYSLOG. I did the same system diagnostic tests, but don't see that same error message. Not sure what the proper course of action should be. I should also point out that UNRAID just finished an automatic parity check following my repair/reboot. Below is the system diagnostics file. tatooine-diagnostics-20230708-2356.zip Thanks, Bill

The second xfs_repair was successful. Appreciate the help again Jorge. Bill

Here you go Jorge... Thanks, Bill tatooine-diagnostics-20230706-1103.zip

Thanks Jorge...I ran it again, this time with -L as I did last time...Stopped the array and restarted but the disc is still unmountable....Here's the output from the repair. 20230706 - Repair Filesystem Output.txt

Hi...I had this issue about a month ago....that thread is here: Following the steps of the previous correspondence, here are the diagnostics: tatooine-diagnostics-20230705-1951.zip The Check Filesystem output was WAY longer than the last time I ran this...I copied the entire page to a notepad document here: Check Filesystem Output.txt This problem seems slightly different than my previous problem so I hate to take the same action as last time without checking with the experts first. Thanks for your help. Bill

Had an issue with a drive not mounting following a power failure. Was able to get that issue resolved along with an issue with the Docker failing to start...Now I'm left with Plex in an unhealthy state and a message saying that unraid failed to load preferences. Fairly new user and definitely not an expert on trouble-shooting these issues. Thanks for taking the time to look. To see the original thread, go here:

Following along on another post that is related, I pulled the Plex logs: Not sure how to correct this...If anyone has any ideas, I'd much appreciate it. Bill

I recently had a power failure. Upon rebooting my Unraid system, I found one of my drives to have an error and state that it was unmountable. I got some great support for that issue as well as reinstalling Docker...That thread is here: Upon reinstalling Plex, I now have it running but it is in an unhealthy state and I can't access my library. JorgeB suggested I open another thread and ask for support on this side. I've attached a screenshot and the latest diagnostics. Anyone have any ideas? Thanks, Bill tatooine-diagnostics-20230615-0513.zip

That got it JorgeB...Thanks! I wish I could say my troubles are over, however, I can't access Plex. After reinstalling, it says that Plex is unhealthy...In anticipation, I've rerun diagnostics. tatooine-diagnostics-20230615-0513.zip

Here you go...Thanks again! tatooine-diagnostics-20230614-2105.zip

Hi...I had another issue where a drive wouldn't mount. See this thread: Following the advice posted, I was able to get the drive mounted successfully. Unfortunately though, the docker service now fails to start. I had commented about my issue with the docker service, but thought it better to open another topic as my original issue was resolved. Any thoughts?

Thanks for your help! It is now mounted and a parity check kicked off automatically... The problem I'm seeing now is that my docker service failed to start.

Had to use -L