nkissick

Members
  • Posts

    16
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

nkissick's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Hi All - just wanted to say thanks to you all for replying. It was indeed the macvlan issue - shouldn't have ignored CA Advisor....
  2. Hi Itimpi - thanks for that. I've been running the syslog for a while now while I try and diagnose. If you'd be able to take a quick look at the attached I'd appreciate it. In the meantime, I ran CA Advisor which reported that something on the file system /dev/mapper is very full. I tried expanding the docker image which didn't seem to do anything - so not sure if this is related or just a random issue. syslog-192.168.1.101(2).log
  3. Hi all - I've been having persistent issues with my server (Unraid version 6.12.6). Basically, the server becomes unresponsive after three to five days and requires a hard reset. Issues/things I know The issue has been going on for a while no - I have no idea whether it was brought on by something or just randomly developed. Oddly, the boot order in my BIOS also gets out of whack - which means that after the reset, it sticks the USB drive with unraid as lowest priority and then the server hangs. This means I have to go into the BIOS to change it back. Note: Only the boot order appears to change - time/date etc remains consistent. Fix common problems reports the maclan thing is an issue and a an issue with the NIC - but these have never caused me problems before. Steps I have already taken Replaced the Cache nmve drive / formatted everything to XFS (I thought this might the issue - but no luck) Replace the CMOS battery (also didn't work) Enabled system logging to try and catch the problem - but i have no idea what im looking for (not attached - will do so on request) Request I'm hoping that someone here can interpret my attached diagnostics and see if it is a software issue / easy fix. The hardware is all old - so it may be time for new gear. But the problem is weird and doesn't seem to be related to failing hardware as far as I can tell. Thanks very much in advance tower-diagnostics-20240128-1244.zip
  4. Can confirm that crenn's solution worked for me. Thanks! Maybe we could pin this to the top or something?
  5. Perfect thanks! For anyone else's info: I had to stop Docker, delete the image, remove the dodgy scripts in the boot folder and start back from scratch!
  6. Thanks for your reply! I get the same error when attempting to install apps using community applications. I agree that I think something has been corrupted. It happened right after I attempted to map a drive in SABNZBD. I suspect the problem is that when the system boots it looks for that XML, but that XML is corrupt. Is it possible to edit the script which is calling SABNZBD.xml?
  7. I forgot to mention that I am able to ping out from the box - and can successfully install plugins. The issue is limited to Docker it appears.
  8. Hi, I'm getting the following error when attempting to install a Docker app I've searched the forums and attempted to set my DNS server manually (both to that of the router and 8.8.8.8 etc.). I would appreciate any advice that can be offered! tower-diagnostics-20161122-1921.zip
  9. Hi all, Was wondering if anyone has successfully used the proprietary eaton software successfully on unraid? Or run a vm which allows controlled shutdown from ups? I have an eaton 5e and need help! Thanks!
  10. Did you ever get a workaround to work? Any ideas why it didn't? I just bought an eaton and am having some issues
  11. If I'm reading this correctly, does this mean that plex needs to be installed on a cache drive to work properly? I'm having an issue whereby Plex works fine but does not automatically update the library. I do not have a cache drive and was wondering if this could be the cause. If this is the case is there a workaround which it allows the library to be updated (requiring all affected drives to spin up) on say a daily basis? Cheers
  12. Hi CHBMB, thanks for your reply. In the process of updating now, cheers for having a look around for me. Unfortunately after posting I saw some comments regarding the DNS issue which seems the likely culprit.
  13. Hi All, I am using the Couch Potato and Sonarr docker images which up until yesterday worked fine. They now refuse to hit the indexers. Also, I am unable to search for new TV Series and Movies (in sonarr and couch potato respectively). This leads me to believe it's a broader connectivity issue rather than an indexer (I am also unable to resolve indexers such as Kick Ass which are free and don't require an API). I have been able to ping from an ssh terminal to external sites. I have unraid six. Any ideas? Thanks