kaleb112494

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by kaleb112494

  1. Thank you for this. I have been experiencing this issue since 6.10.X, as I am notorious for leaving browser sessions open. Back before unraid-api, I was able to just restart rc.nginx without issue, but that solution stopped working after 6.11.3. Similar resolution, different methodology. EDIT: I suppose we can't really call it a solution until the problem ceases to occur in the first place.
  2. Thanks for creating a quick replacement for NerdPack! I second ctop, great little program to keep Docker containers in check.
  3. Following, as I am experiencing a similar issue. Removed some lines, as it's ~22 lines long. For my system, I'm using an R9 5900 (non-x), which is not listed as supported by my board, but this issue has only recently started for me. I was getting >4 month uptime until about 2 months ago. Nothing has changed since then, other than updating plugins and whatnot. Based on "SB.PCI0" in the error, it looks like it's related to a PCIe device? PCI0 is where my X520-DA2 is located currently. When my server goes offline, I am unable to reach it via the network. I haven't been home when this occurs to see if it is responsive other than network. Like other posts, there doesn't appear to be anything in /var/log/syslog (and by extension, /boot/logs) that states anything about a kernel issue, and the ACPI issue only reads during boot. If nothing else, I hope that my diagnostics have similarities to OP's so that we can find a solution. unraid-diagnostics-20230316-1819.zip
  4. Hey guys, haven't ran into this one before. Wish I knew docker a little better, but hopefully someone can help educate me on what to look for. Had an issue with an NVME pool in BTRFS RAID 10 where one of the drives went AWOL for a few hours. The pool reestablished itself automagically into a 2TB pool instead of 1TB, so I'm not sure what happened there. Removed power, waited for caps to dissolve power, then started back up, where NVME returned from it's vacation. Already balanced the pool and rebooted, which did not resolve the issue. Any help would be appreciated. I've already created a backup of the important data on the pool, so I can start from scratch if necessary - but I'm really, really, REALLY trying to avoid that if possible. TIA for any assistance. liteserver-diagnostics-20220402-1541.zip
  5. I can confirm that this was the solution for my system hanging at "Starting Samba"
  6. Thanks for the reply. I reached out, and they've been maintaining the package in nightly rolling releases, as opposed to commiting to the master image on GH, which then causes the Docker image to not get these nightly updates. Or so I'm told 😅
  7. I second VanDAM, this would be awesome!
  8. Is TaskCafe still maintained? I see that there have been commits and updates pushed, but the docker container doesn't ever have new updates. TIA