• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

bobo89's Achievements


Rookie (2/14)



  1. do you have dynamix system temperature? It's a plugin.
  2. Bingo that was it. I am only seeing boosting to 4.15 Ghz. Is that configurable in the bios ?
  3. I can't seem to get the proper driver running for my 3900x cpu on an x470 motherboard. Running the penultimate bios. In tips and tweaks it says no driver, with no performance boost option selectable: Any reasons why this may be ?
  4. Any reason why I don't have a driver or can't select performance boost?
  5. I have a docker only vlan with no IPv4 assignment in the networking tab. On 6.8.3 all containers were happily accessing the right DNS server which is a pihole docker container. However after upgrading to 6.9.2 containers all have /etc/resolv.conf set to Where was the change that is preventing the dockers from accessing the DNS as normal?
  6. Running 6.9.2, 3900x on a x470 board. In tips and tweaks it says "no drivers" and Turbo boost option is blank. Governers are selectable. Do I need to load my own driver ? root@Tower:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1:
  7. My issue is that on server reboot some of my docker containers seem to boot faster than the rclone mount comes up. For example emby keeps giving me can't find media stream errors and from within the docker console no files show up. Rebooting the docker containers picks up the mount properly. Anyone else have this problem ? Any way to delay docker startup on array start ? Sent from my SM-N960W using Tapatalk
  8. Interesting. There was no super.dat, only a super.dat.backup. finding one from an older backup that got me back to normal. Thanks ! Sent from my SM-N960W using Tapatalk
  9. Ryzen 3900x with 128gb of ram at 3600 MHz . Although that is technically an OC 22 hours or memtest ran fine. I realized what my issue was. I wasn't zipping up the files from the usb backup, but the whole usb folder was zipped, so the format or the usb wasn't right. Last question is, I've booted in now, but the drive assignments are all blank, however the config folder contains a disk_assignments.txt file however unraid isn't picking it up. Should I manually reassign or is this indicative of another problem ? Sent from my SM-N960W using Tapatalk
  10. I was still on 6.8.3, so I just created a 6.9.2 USB (same usb key), and tried to copy over just the config files. That booted fine to UNRAID, but the config was all messed up, with drives unassigned and services wonky. Seems that the USB key is good, but the backups are all not. Is there anyway for me to gracefully upgrade from 6.8.3 to 6.9.2 and preserve the config without being able to boot into my last known good config?
  11. I had to uncleanly shutdown my unraid server, however upon restart the USB key was corrupted. No sweat, I have backups, so I take the backed up USB folder from the Backup/Restore plugin and convert it into a zip, then use the unraid usb creator and flash it to the usb. Try to boot from that and I get to the blue Unraid boot screen where you can select memtest, and selecting any of the options, it tries to initiate that option, the screen flickers, and it goes back to the the blue screen with the 5 second countdown timer. I read that could be due to a corrupted bzimage file on the USB stick, so tried replacing them manually on the restored USB. No dice. The thing is I have a few months worth of backups, and have tried restoring those USB backups, and they all have the same symptoms. I have confirmed the MD5 of all the bzimage files are the same across backups. I have rebooted in the past few months multiple times so whatever was getting backed up must have been not corrupted, unless all the backup got corrupted, which I would find unlikely. Any thoughts?
  12. Rebooted 3 times, and everything works as normal. Any ideas as to what caused the intial issue ?
  13. Unraid server has been running well for 56 days however this morning woke up to everything quasi working -Network shares are listable but files can't be opened - Webgui is giving me a "Fatal Flash drive error" - managed to pull diagnostics and take a screenshot of my drive allocations just in case. I have a USB backup from last night that looks OK. Syslog is full of error messages "MEMSTORE:00: can't create shared message for channel /disks Feb 22 04:40:06 Tower nginx: 2021/02/22 04:40:06 [crit] 17219#17219: ngx_slab_alloc() failed: no memory Feb 22 04:40:06 Tower nginx: 2021/02/22 04:40:06 [error] 17219#17219: shpool alloc failed Feb 22 04:40:06 Tower nginx: 2021/02/22 04:40:06 [error] 17219#17219: nchan: Out of shared memory while allocating message of size 10161. Increase nchan_max_reserved_memory. Feb 22 04:40:06 Tower nginx: 2021/02/22 04:40:06 [error] 17219#17219: *20307960 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST" Using Firefox I'd like guidance on what to take a look at before I reboot and we see what comes out the other side.
  14. Google stubbing primary video card unraid. You need to edit your boot file or upgrade to 6.3.9 which just came out and use the built in functionality to prevent unraid from using the video card so you can pass it through. Yes you need to select the video card and vbios file in the vm manager Sent from my SM-N960W using Tapatalk