Fribb

Members
  • Posts

    9
  • Joined

Everything posted by Fribb

  1. Interesting, I disabled the UPS Settings and NUT seems to show everything again. Though I am wondering why it worked for a year and just now wants to crap the bed... Thanks for the easy fix.
  2. This morning I got the message "Warning communication lost with UPS". I checked my NUT Settings and the UPS is listed as "On Line" with battery charge and NUT Details. But in the UPS settings it states "Lost communication". I already restarted both services and also switched USB ports without any change. I do see a few warnings in the syslog like "Poll UPS failed - Data stale" or when I restart the NUT service I get "WARNING: send_to_all: write 34 bytes to socket 16 failed (ret=-1), disconnecting: Broken pipe" diagnostics are attached. I have the CyberPower CP1500EPFCLCD for a year now which was running without any issues. fribb-tower-diagnostics-20231119-0502.zip
  3. I would like to make a suggestion. While I like the "container by container" approach of doing the backups to reduce the time a container isn't available, in some instances this could also be a problem. For example, stopping the database of a service will potentially break the service accessing that database. A more specific example, I have a Tautulli container which can monitor the Plex logs which are acessible through a volume mapping to the Plex container config. However, currently the Backup of Tautulli fails because the Plex Logs are changing. I had to now remove that feature and the volume mapping for Tautulli getting backed up correctly. I also see that a ToDo is to "Use Dockerman default order when no order was set before" which is good but doesn't necessarily fix the issue I highlighted above. What I would like to see is that you can "group" Containers so that they are stopped as a whole and then started after they are backed up. So, for example, Plex and Tautulli are in such a group and both are getting stopped, Tautulli is backed-up and started, then Plex is backed-up and started.
  4. Yes, I'm really really sure that I booted into UEFI before. I think I even read somewhere that you should use UEFI because that is the new standard?! I had it on the old board, running 6.8.3 and the new board running 6.8.3 and 6.9-rc2 but on 6.8.3 I had the "old" Nvidia approach which I can't reproduce anymore because of missing drivers etc or I would have tried to see if that is a problem there too and my GPU has some issues. While testing the new components for my DAS I had the old board and even plugged the GPU into it and ran some transcodes without that problem turning up. Whatever the case, running in legacy seems to have fixed that for whatever reason.
  5. I'm pretty sure, yes. So, the transcodes are through, no GUI mode, persistance mode 1 and loaded with Legacy. Seems to run as it should but I will keep and eye/ear on it but hopefully it will stay that way. Still, why did it work before and not now anymore?
  6. So, I booted in legacy mode and with GUI and let some ffmpeg transcodes running, GPU went up to 62°C and stayed there while the fan was at 40%. So far, hopefully I don't jinx it with saying that, the GPU has stayed quiet and at 35% fan speed. What is weird to me is that I didn't had this behaviour the last year and only recently after upgrading to 6.9 (and switching Motherboards), I already have the latest bios on the MB.
  7. I meant a previous driver version because I didn't had this issue a couple of weeks ago. I don't know when the v455.45.01 so this might just me grasping at straws. This is a GPU I use/used for a year now in the same server and only recently when I did my DAS server expansion and upgrade to 6.9 had this problem. I did try it with a different board while testing the DAS hardware and the problem didn't turn up there for some reason (also Unraid 6.9 and v455.45.01). I did run it with GUI mode for a while and it seemed to not happen there but I did not extensively test it as I did today running a few ffmpeg transcodes. I boot with UEFI mode. I already had the persistance mode active and also disabled and enabled it a couple of times trying to figure this out, without any luck. Now that I stopped the array it suddenly stopped and after a couple of minutes it started again. Disabled the 2 docker containers that have the GPU passed through and it dipped shortly but stayed at max fan speed. I rebooted in GUI mode now and the Fan has settled down again, I have to do some tests first to be sure that it is "working". Though I don't know if that should be the solution...
  8. I have some issue with my 1660 Super. When the GPU is is under load it will go up to 60°C and hover around 40% fan power. After a while, after the GPU has a load of 0%, the temperature is back to normal 36°C and it is in P8 power state the fan decides to spin up to 100-110% and stay there for a while. After a short or long while (currently active for 10 minutes) it will settle down again but shortly after will ramp up again. I got the latest drive v455.45.01 installed and am wondering if there is a way to install a previous version just to rule out any issues with the driver itself. I'm running Unraid 6.9.0-rc2, the GPU is at 8 lanes if that makes any difference. I would restart but I have a few pre-clears running which will still take a few hours.
  9. I am really out of ideas here and this behaviour is driving me nuts because it doesn't make any sense but first my systems stats: AMD Ryzen 5 3600, NVIDIA Geforce GTX 1660 Super, Unraid 6.9.0-rc2, NVIDIA Plugin with Driver Version 455.45.01 What happens is that my GPU is cranking up the Fan to 110% while there is no load, the temperature is at 30-ish °C and the GPU is even Idle. Even better is that I had some Transcoding Jobs running an hour ago at which the GPU was at ~35% Fan speed while being at 60°C. But now, half an hour later, it spins up the Fan sounding like a jet engine for no reason (or at least no reason I can find. I have two docker container running that got the GPU passed through, Plex and Tdarr (v2) but even with both disabled the behaviour doesn't change. One thing I couldn't check would be to install a different Nvidia driver version because both, the specific and latest, are the same version. What I also tried was to reseat the GPU, use a different PCI-E Slot on my motherboard but that didn't change anything. I'm out of ideas. I really hope that the GPU isn't broken... Edit: I restarted Unraid, again, to maybe get it settle down again. Now it runs hasn't stopped so far but what I also noticed is that the Monitor I had connected to the HDMI port is completely black and also doesn't even allow me to switch channels until I disconnect the HDMI cable... fribb-tower-diagnostics-20210220-1055.zip