xplicitsomebody

Members
  • Posts

    7
  • Joined

  • Last visited

xplicitsomebody's Achievements

Noob

Noob (1/14)

0

Reputation

  1. My server has been acting pretty strange for a couple of days. First a few containers have been having stability problems. Then yesterday I got another report that one was down (Minecraft again). Typically I have been able to just restart whatever the offending container was. Well when I tried that it failed to start and I noticed that my memory was at 100% usage, the log was taking up 30GB. My second parity drive also had several read errors. It is a warranty replacement from Seagate that just went about two weeks ago after preclearing. Wish I had gotten a diagnostic then but here we are. After a reboot I started getting the error that Docker service failed to start. Read errors were gone though. I went ahead and removed the drive. No dice, I know that the parity should not have much to do with the docker service but if it is a failing drive why leave it. My research into the main issue here points to either a corrupted docker image or something with the cache. I do wonder though if it has something to do with having the extra parity and second cache drives on a PCIe Sata card though. But even with that uninstalled the issue persists. System description Unraid: 6.9.2 Hardware Ryzen 7 1700 Asrock Taiichi x370 32GB memory GTX770 usb Pcie card sata expansion pcie card BlueRay drive Parity 2x Seagate 8TB Cache 2x Samsung evo 860 500TB 5x WD 4TB Seagate 2TB Toshiba 500GB If I have left anything important out let me know. Thanks for looking at this any help is greatly appreciated. ares-diagnostics-20211008-0833.zip
  2. Okay this is resolved, I am back up and running. Thank you so much for your assistance trurl.
  3. Yes! Okay, so I got it spun up and yes the R2E1 was not assigned and i'm pretty sure that sr0 is in fact the DVD drive. Throughs me a bit that it would have an entry in the smart folder though. Found the backup as well now just figuring out how to properly recover with it.
  4. Okay, so I actually found the license key file! So one thing goes right.
  5. Thank you for your help. So I think that older diagnostic is from right after (ish) I upgraded my parity to an 8TB. Found the drive assignments in the folder, there are two there though that aren't numbered. Not supper sure about those. I have a couple of places to look for the license file will check but not high hopes.
  6. So a few days ago I was over at a friends house playing some Minecraft off a server hosted on my Unraid server. We started getting disconnected, so I went home figuring the internet equipment just needed to be restarted. Roommate confirmed that it had been acting up. Reboot network equipment, and it still kicks my friend off after about 45 seconds. The network does seem to be stable now though, so I rebooted Unraid from the web UI. It did not come back. After reboot it showed just a terminal interface (should be a VM with GPU passthrough.) Could not connect to Web UI, boot in GUI mode can't connect to localhost.. So I pulled the flashdrive and took a look from my desktop. Chdsk repaired some errors (crap) but things look off. It has renamed itself back to tower and there seem to be a lot of missing files. Just got my new drive in and loaded up a fresh install and oh are there things missing from the old one. So rebuild great just what I want to do. I can't seem to find a backup of the old flash drive, but there may be one somewhere on either the array or the cache drive. Can any of you much more intelligent people than me help find a way to get things booted back without loosing my array? I did find an old diagnostics folder from before so maybe that can help here? Including the diagnostics that I got off just recently and an older one that seems to still have some configuration in it. TLDR: I think my flash drive died and I can't find a backup, but there might be one on the array. tower-diagnostics-20210728-1741.zip ares-diagnostics-20210321-2150.zip
  7. My problem seems to be more with Minecraft than with the docker itself. Didn't see this anywhere else around though. So I am trying to get this running with a world that my friends and I have been on for about a year and a half. I have had it set up on a VM with an extra account just hosting basically. (I know jank but it's what made it work.) Whenever I upload the world and change the name in properties over to the world I get an error Unable to join world. It works just fine letting it generate it's own world or uploading smaller more recent worlds. My thought currently is some kind of size limit to the world this can run. Is that a thing? Can I change it if so? Or do I have some other thing going on here?