jmbailey2000

I used to use Unbalance a lot, but with the issues creeping up, I've gotten to the point where I just use MC to moves files between disks and haven't had any issues so far. To me, I feel a little better as I have more control over what goes where. Of course, I don't moves tons of files around that often, but I did have to clear off a disk I need to remove from the array and had great luck using MC.

Ah. Got it. Will do and Thanks!!!

The web gui for everything will be down. IS there a command line way to get that info?

Yep all good, but now I have really weird issue trying to install docker apps from CA. The selection of an app usually hangs without actually starting to load. If it does load, the actual install process shows the downloading, extracting, etc. but never seems to finish. I finally refresh the page and I get a 400 Bad Request error. I have to clear my cache in Chrome to regain access to Unraid's interface. Otherwise, everything else seems to work.

Bing, bang boom......BINGO!!!!! I might be able to take a few full breaths now and get everything back to normal. Which has been al over me about the media server being down!!! I followed the docker.img steps (after making sure the docker settings was set to disabled) to avoid an unclean shutdown. Then did a reboot after upgrading to rc2. Rebooted clean. Started array clean. Started docker clean. Looking good so far. THANKS EVERYONE!!!

Holy crap!!! Where was this during my last 2 messes!!! Awesome!!! I'll give this a try and then see if I can upgrade to rc2 (crossing fingers it has been fixed).

Any way to get around the unclean shutdown or do I just have to deal with another parity check?

So any concerns with updating to rc2 with an unclean shutdown in the mix?

NEW EDIT: Well, after waiting 30 hours for a parity rebuild, got everything checked out and reset they I wanted and decided it was time to downgrade. Like I always I have stopped all my dockers and disabled the docker so it wouldn't start up after the downgrade until I was ready. Whoops, forgot to check something and BAM!!!! Can't start the docker service and here we are again, back to 6.12.2 not working. Yeah, yeah, I know, reboot and that should fix it but guess what, it doesn't. I'll have to rebuild parity again. So here is my NEW question..........should I just do the down grade without docker service able to be started (assuming that after downgrade the reboot will fix it)? And if the shutdown doesn't cleanly go down, which it hasn't since I installed 6.12.2 over a week ago (and 5 parity rebuilds) is there any concern that the downgrade was done and it is coming back up to complete the downgrade with an unclean shutdown? PAST EDIT: Never mind. Found stuff that said a reboot is the only way. Well, once again, wouldn't shut down after sitting for an hour and couldn't kill any process to make it complete, so force a reboot and now will sit around and wait 30 hours for a parity check to finish. Then 6.12.2 is gone. I came from 6.9.2 but am going to try and down grade to 6.11.5. ORIGINAL: Well, 6.12.2 has been a total disaster. I can't reboot the server without it failing shutdown, even trying to stop any open processes, etc. So every reboot causes a parity check. Once I let it finish the check, I found the docker.img file corrupt. Got that fixed, and now I find the /mnt/user folder is "missing" or labeled as ?user in MC. When I look at ls-l for the user folder is shows as "d???????" and all other fields for the listing as "?". I can't install any new dockers now even though I was able to install all previous dockers to rebuild the docker.img file. I want to downgrade but this missing /mnt/user file has me concerned because now docker what start because of missing path. What can I do to get it back, just recreate the folder under /mnt or is there something else that needs to be done to fix it. Edited Monday at 09:13 PM by jmbailey2000

EDIT: Never mind. Found stuff that said a reboot is the only way. Well, once again, wouldn't shut down after sitting for an hour and couldn't kill any process to make it complete, so force a reboot and now will sit around and wait 30 hours for a parity check to finish. Then 6.12.2 is gone. I came from 6.9.2 but am going to try and down grade to 6.11.5. Well, 6.12.2 has been a total disaster. I can't reboot the server without it failing shutdown, even trying to stop any open processes, etc. So every reboot causes a parity check. Once I let it finish the check, I found the docker.img file corrupt. Got that fixed, and now I find the /mnt/user folder is "missing" or labeled as ?user in MC. When I look at ls-l for the user folder is shows as "d???????" and all other fields for the listing as "?". I can't install any new dockers now even though I was able to install all previous dockers to rebuild the docker.img file. I want to downgrade but this missing /mnt/user file has me concerned because now docker what start because of missing path. What can I do to get it back, just recreate the folder under /mnt or is there something else that needs to be done to fix it.

Out of 8 shutdown/reboot sequences, only 1 was successful. I have dozens of php and other things that refuse to end and there is no killing them. Twice I let the thing sit for hours with nothing happening. Seriously getting tired of non-stop parity checks due to unclean shutdowns. Guess I'll manually install 6.11.5 since I came from 6.9.2 14 days ago.

With this update, I was able to get o the docker set up screen which I was never able to do before. I'll get it installed tomorrow and let you know if there area any issues. Greatly appreciated!!!! Thanks!!!

I'll post a screen shot when I get a sec. I am still running Unraid 6.9.2 if that happens to matter.

Which logs you looking for. There aren't any logs related to ygg I can find and since it never makes it to the docker install screen from the CA Apps selection screen, not sure where else to look.

Not sure what you mean by "laws".

Every time I try and install this, it crashes Unraid web page and I have to exit Chrome and restart. Anyone else having issues?

Agreed. While I have never needed support or had to update Unraid specifically due to a bug, dockers/plugins is a different story. While 6.9.2 has been so rock solid, the number of dockers/plugins that can't be updated because of 6.9.2 not being supported is the biggest issue now. Thanks!!

What is the most reliable 6.11.?? to upgrade to? I'm seeing lots of issues with 6.11.5, so not sure if that is the best from 6.9.2? Or is there a better, more stable release? Thanks!

I'm traveling at the moment so can't get the logs, but was just curious if this is a known issue.......manual backups WORK, but the automated daily at 5am is not working. I didn't notice it when I swapped v2 for v3 (because I was doing manuals at the time during the switch). All my settings are the same as v2 and everything works as expected except the daily automatic execution. If no one has heard of this I'll grab the logs tomorrow and post them when I get back from traveling. Edit: Well, never mind. I changed the auto backup time settings, saved, then changed them back to the original settings and backup ran fine this morning. All is good. Thanks!

Hmmm...well, set to cache. Totally missed that. I'll set it to user and see what happens. THANKS!!!

I happened to go looking for something in the AppData Backup and found much of my appdata missing. After some research and reading of some messages, it appears the plugin only backs up files for appdata on the cache? Is the assumption if it isn't on the cache is is already protected because it is on the array? Is there a way to force a true full backup of appdata if you don't force appdata to live in the cache? Thanks!

Currently running 6.9.2 Anyone noticed an issue with the Share Allocation Method not saving? I changed several of mine from High-Water to Most-Free and after a reboot, it appears to have reverted back to High-Water. I've seen a couple messages sort of relating to this but that was more an configuration issue from what I gathered. Any thoughts?

If I have questions about the cron schedule, I rely on this...... https://crontab.guru/ Truly a god send.....

This is for Unraid 6.8.3 Got a weird thing happening......had an array drive acting up so moved all data off and excluded it from all shares. Then move the drive to unassigned and pre-cleared it. Everything was clean so for practice (having never done the process before) added it back to the array and the rebuild kicked off. Cool. All worked well and after 12 hours, the drive was rebuilt in the array. Now the quirky part.....most of my shares show the files aren't protected. There is nothing on the cache for the shares and even ran mover to make sure. Looking at the files for each share, none show as residing on the original failing drive. For the life of me, I cannot figure out what isn't protected or why. Thought I'd ask the question before I fire off a normal parity rebuild to see if that clears it. Thanks!