jmbailey2000

Members
  • Posts

    61
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jmbailey2000's Achievements

Rookie

Rookie (2/14)

8

Reputation

  1. Any idea why the Backblaze Personal Backup just gives me a black screen with 'Server Disconnected (code 1006)"? No matter what I try, that is all I get. Let is sit for 2 hours, refreshed and nothing.
  2. Hmmm.....could be....I'll take a look. Thanks!!
  3. Has anyone run in to issues with 6.12.2 or 6.12.3 throwing 400 Bad Request web page error? This all started after I upgraded from 6.9 to 6.12 to 6.12.3-rc2 and now in stable 6.12.3. Unraid works fine for a few days after an array shutdown and reboot, but after that I pretty much can't load anything from from CA (or follow any links through CA for support, info, etc.) and have have a couple of dockers that start throwing the same error when I try and run them. I couldn't update any plugins or containers before the 6.12.3 upgrade because of this error. Now after the reboot, is working fine, but will only last a few days then start up again with the error. I can regain control of the main page by clearing cache stuff in Chrome and the main page will work, but nothing else in CA or these couple of dockers. Thanks!
  4. Anyone have any ideas. It started working out of the blue a week later and worked fine until 3 days ago. Now, not working again and no matter what I do, can't get it to run.
  5. Anyone having issues where out of the blue, nzbhydra2 just throws a "http 400 bad status" error? I used it 2 days ago, no problem and now today, this pops up within 1 second of trying to connect to the web gui. I forced an update and even deleted the docker and reinstalled with no luck.
  6. Has anyone had issues with dockers starting up after the backup but not actually working? In my specific case, qBittorrent gets turned back on after the backup, and everything appears to be working, yet, no uploads/downloads are happening. After a few days troubleshooting, I found that every morning, I have to (in the app itself) log out of qBittorrent, then exit qBittorrent, then restart the docker container. Once I do that, qBittorrent starts and whatever was uploading/downloading when the backup was executed, starts up automatically again. Thanks!
  7. 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.
  8. The web gui for everything will be down. IS there a command line way to get that info?
  9. 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.
  10. 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!!!
  11. 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).
  12. Any way to get around the unclean shutdown or do I just have to deal with another parity check?
  13. So any concerns with updating to rc2 with an unclean shutdown in the mix?
  14. 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