Jump to content

SpuddyUK

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

1 Neutral

About SpuddyUK

  • Rank
    Member

Recent Profile Visitors

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

  1. Same Issue on dashboard, two collumns for docker containers instead of usual 3 with an inability to interact unless I go to specific docker page. My VM section of dashboard is empty but if I go to VM page, my Windows Server VM is running. Google Chrome 86.0.4240.198 unraid 6.9.0 beta35
  2. Noticed Processor is spelled wrong when hovering over the status bar when using Dynamix System Temperature plugin.
  3. Ok, updated to 6.9.0-beta29 and my 9201-16i (based on 2116 chip) seemingly works fine. @limetech @Squid
  4. Running 6.9.0-beta25. Glad I came here to check. Seems my 9201-16i would be one of the affected LSI SAS cards as it's based on the 2116 too.
  5. Will the next nVidia unRAID release use later drivers than 440.100? I'm looking to resolve a Plex Transcoder power C-State issue that nVidia fixed in > 450.36 Thanks,
  6. Is anyone able to assist with a P2000 that seems to want to stay in a P0 power state even when no transcoding in occurring? If I run the command nvidia-smi --persistence-mode=1 Then restart Plex container, it seems to put the card in P8, then P0 when transcoding but the transcoder crashes after about 5 seconds ending the playback? Therefore I have to put back to nvidia-smi --persistence-mode=0 and restart Plex container to get transcoding to work stable again. But stuck at P0 always, transcoding or not.. nvidia unRAID6.9.0 b25 It's not a huge issue, but I note I should be able to get idle card usage down from 17W to around 8W.
  7. Hello, I was wondering if anyone knew of a plugin that could on a schedule output a list of all files/folders on each disk? That way, if I lose more disks than parity covers, I can cross-reference that disks list and know what I need to restore from backup. Thanks in advance,
  8. I am sorry if this has been covered in the topic already, I did search. Found this great app today but am having a few problems with it on an LSI 9300-8i. It seems to benchmark the 2x SSDs (cache and unassigned for plex) that are connected directly to my motherboard but the 8x drives connected to my HBA (LSI 9300-8i) are not scanned. It just seems to hang here. 30 minutes and counting. Incidentally, the controller and drives are accurately represented at the beginning before starting the benchmark. Maybe I'm doing something wrong?
  9. Any ideas why the dashboard widget is showing an active tunnel when I disconnect many minutes beforehand? Android client. I even dropped my device into airplane mode to be sure it wasn't still connected somehow. Is there a way to get it more accurate or poll connection status quicker? Thanks in advance, everything else is working perfectly!
  10. Been on this for the past 2 days and I think I've just got to the bottom of it. I tried with docker disabled but VM Manager enabled, same issue. I tried with VM disabled but docker enabled, same issue. Both turned off and NUT successfully powers down Unraid within 2 mins. Turned both back on and issue starts again. However! My wireless usb/mouse combo, has a little dongle. Unraid was doing it's hanging at "forcing shutdown" (usually 10+ minutes) trick. I unplugged the dongle during this to use elsewhere and immediately unraid completed it's shutdown and powered off, like within 10 seconds. It could be there is an issue between this little dongle and docker/vm manager which is preventing NUT from rebooting in a timely fashion. Could be coincidence but unlikely. I'll hold my judgement for now as I'm just waiting for the UPS to get it's charge up (couple hours) then i'll be testing again with no dongle and both docker and VM manager enabled. I'll report back later! Thanks for help.
  11. Ok. So i'm further along. I shutdown all my docker containers manually and turned docker off under Settings > Docker. I also manually shut down my single Windows Server 2016 VM. Pulled the mains on my UPS and everything shutdown perfectly, INCLUDING Unraid (R210ii). Seems Docker and/or VM are causing the long 12+ minute delays during NUT induced shutdown. Next question is I guess why and what can I do about it? Can I add something to a nut conf somewhere to forcefully kill docker/vm instances?
  12. Thanks for the info. This morning I have tested the following, Unraid (R210ii) as NUT master, Synology as NUT slave, PFsense as NUT slave. Same issue occurs, if not a few minutes worse. Setup NUT on unraid to shutdown after 1 minute on battery. pfsense seems to start it's shutdown sequence at the same time. Synology, I set to after 45 seconds on battery. Synology and pfsense automatically go off nicely within 2 minutes of power being lost to UPS. UnRaid hangs at both the "Waiting up to 90 seconds for graceful shutdown..." and "Forcing Shutdown". For around 12-15 minutes before powering off. If I "Shutdown" in the gui, the R210ii is off within 2 minutes. I can try pfsense being the NUT master, but with similar experiences being had with synology being the NUT master, and now same with unraid server being NUT master, I'm inclined to believe it wont make a difference. Something in the NUT unraid plugin shutdown sequence is causing the delay. Anyway I can troubleshoot this lengthy delay?
  13. Any idea why a NUT shutdown of Unraid would take 10 minutes +, when a normal manually induced shutdown from the GUI takes 1/2 minutes? I have an Eaton 5P plugged into a Synology. UnRaid and PFsense are slaves and getting all the info. Pfsense box shuts down fine before battery dies but Unraid server (R210ii used for VMs and Docker) takes too long loses power ungracefully; meaning parity checks etc. I have tested 8 to 10 times this afternoon and GUI shutdown can be accomplished quickly, NUT induced shutdown takes forever. I have a monitor plugged into the UnRaid server and can see it has begun shutting down 5 seconds after going onto UPS power but still takes too long. "Waiting 90 seconds for graceful shutdown" then shows "Forcing Shutdown" for an eternity before usually losing power. UPS has ~15 minute battery. I'm just trying to work out what happens differently between a GUI shutdown and a NUT slave shutdown to cause this undesirable behaviour? Thanks in advance,