Jump to content

Squid

Community Developer
  • Posts

    28,769
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Yes, just delete the file on the flash drive. You WILL NOT lose anything on the array. After rebooting, just set up the share settings back how you want it.
  2. I make a conscious decision to not investigate that completely as I probably don't want to know. I estimate though that between the servers and my desktop it costs me a couple hundred a year. Just the cost of doing business IMO
  3. Enable the syslog server (mirror to flash) and wait for the crash. Diagnostics will also help
  4. You have a docker container referencing "CamelCase" in it's path mappings
  5. Tools - System Devices. You were isolating some hardware device for passthrough to a VM, but when you added a new controller, the ID's changed (outside of the OS control) and now your controller is isolated. Adjust the checkmarks accordingly
  6. You grabbed the diagnostics within 2 minutes of the system starting up, and presumably formatting the disks etc. Let the system level out a bit...
  7. Can't be done. If it's using :latest (which everything does that any update is going to be used for) the "date" is the time of the last update, and even if it could be discerned, the update would wind up installing the latest version since that's how the container is tagged. I'll still think about implementing. Netdata and some others would never actually wind up updating because they are constantly updated.
  8. It's not currently anywhere near full. But, I'd surmise that you have mover logging enabled. Disable it (This get's complicated by using the Mover Tuning Plugin -> I have no idea if the plugin respects that setting)
  9. Follow the link in @itimpi's post Odds on you've got a poor connection to a drive
  10. It's hard to discern why the drive(s) failed without diagnostics before a reboot when they were listed as being disabled. Cabling is always the go-to as hard drives are actually one of the most reliable components in any random system, whereas SATA connections since day 1 have not been.
  11. Is what you're selecting via F8 the same as what you've got listed in the boot order? If you've got an LSI controller and say more than 12 drives total, then you should disable Int13H in the controller's BIOS to prevent them from being available in the boot order -> Many (most?) BIOS's have a limitation where after 12 hard drives things become wonky for selecting a non hard drive for the boot
  12. I don't believe that RC5 is that far away. It's a display aberration that doesn't affect any functionality at all.
  13. Still something wrong with corefreq. CA won't install it from the sidebar, and installing from the card there's nothing in "Settings" for me
  14. Kernel Helper is no longer available, and not to be used at all and should be uninstalled
  15. You need to use either WireGuard, or set up a small VM (which is accessible via remote access) and then from it go to the webUI's of the container.
  16. It was clean, which removes all of the usual suspects for reboots. Basically, it implies that you initiated the reboot somehow BTW, you've got some plugin issues: preclear.disk.plg - 2021.04.11 (Up to date) (Incompatible) statistics.sender.plg - 2017.09.22 (Up to date) (Incompatible) These should be removed and replaced with Unassigned Devices Preclear Unraid-Kernel-Helper.plg - 2021.03.17 (Unknown to Community Applications) This should be removed completely.
  17. From the bootup menu. (If you're booting via UEFI though you'll have to switch to boot "legacy" in order for memtest to work)
  18. Diagnostics (even though after a reboot) would be helpful, especially if its a Ryzen system Run MemTest. Do you have a UPS? Power issues?
  19. Docker containers effectively run at full speed. All else being equal you shouldn't be seeing any real noticeable difference. Diagnostics may help us here
  20. Not sure about the problem, but why are you unplugging the cable (on a seemingly semi-regular basis)?
×
×
  • Create New...