Jump to content

Squid

Community Developer
  • Posts

    28,770
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Googling suggest to make sure that the Turbo clock set in the BIOS doesn't exceed the spec's of the processor. May 1 08:47:44 PatricksNAS root: MCA: Internal parity error
  2. Thanks. I'd guess that you have no docker apps installed at all.
  3. Reason why the containers aren't available is because the array won't start: Apr 30 09:25:01 Serverly emhttpd: cmdStart: too many devices By can't boot via gui do you mean that you're not seeing the gui even when accessing from another server or just locally? Since you've played around with different cards for passthrough, you may have to undo the changes you did to isolate them. Rename /config/vfio.cfg on the flash drive (and reboot) to restore the hardware stubbing back to default.
  4. Harmless mce issued during processor initialization which happens on certain combinations of hardware
  5. They never will if run against a share that contains appdata
  6. Same version as mine, which works fine. The OS (and CA) is tested against Chrome, Safari, Brave, Firefox and Edge and on occasion Opera. (Not that anyone uses it, but IE is not supported)
  7. The "plex" share isn't being excluded from the extended tests (as it looks like it's outside your existing appdata share) Add it to the exclusion list. Can't help with the subtitle thing. BTW, extended tests don't really do much except for checking for issues with sharing over the network, so not much reason to ever run them...
  8. I think (at least in theory) you would create a new VM (with the same settings etc as the old VM), but point it at the existing vdisks. Never had to do it though.
  9. Is this edge legacy or the new edge? Both the dev version and the last release are working fine for me on the new edge
  10. If you were running the appdata backup plugin with the libvirt backup option enabled, there's a copy in your backup share
  11. Apr 30 10:06:28 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down Apr 30 10:06:32 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX Apr 30 10:06:33 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down Apr 30 10:06:36 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX Apr 29 11:37:03 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down Apr 29 11:37:07 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX Apr 29 11:37:08 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down Apr 29 11:37:11 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX Apr 29 11:37:14 fs login[7961]: ROOT LOGIN on '/dev/pts/1' Apr 28 16:59:17 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down Apr 28 16:59:19 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX Apr 28 10:39:54 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down Apr 28 10:39:58 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX Apr 28 10:39:59 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down Apr 28 10:40:02 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX Apr 27 23:34:26 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down Apr 27 23:34:29 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX
  12. Not going to be related, but your network goes down and up a fair amount. Maybe replace the cable or use a different port on the switch?
  13. Stop Krusader and see if the traces stop. After that, I'd run a MemTest and post in the applicable support thread for Krusader
  14. It's there on my system when I click add VM. "Supported OS" doesn't now particularly mean that any given OS isn't supported. It's just a template with some default entries filled out.
  15. If it can't grab it within 45 seconds then it automatically times out. (And, it also does the download compressed, so it's 846K not 8.5M) Glad you got it sorted out.
  16. Restart in safe mode. If it fixes itself, then delete the following from /config/plugins in order with a reboot after each gui.search.plg snmp.plg usbip.plg Followed by any of the remaining ones
  17. That implies a bad plugin (docker folders?) Reboot in safe mode and it should disappear, or from the plugins tab uninstall docker folders and try again (docker folders OTOH is the only thing I can think of that would affect both tabs)
  18. Yup. Tools - Diagnostics Even better would be to boot normally, and if you have access to the local command prompt (or if booting via the GUI mode to hit the "lime" startmenu, then Terminal) and enter in diagnostics Shut down the server, pull the flash drive, and upload the resulting file (logs folder on the flash drive) here
  19. So after uninstalling (and presumably a reboot), the webUI link doesn't appear (or presumably the "edit")?
  20. By design. It's to handle the circumstance where a template gets another port added to it. Most of the authors where the behaviour happens commonly with the users have already modified their templates so that it does not do this. You need to modify the applicable xml within /config/plugins/dockerMan/templates-user and change the line that states <TemplateURL>someURLhere</TemplateURL> to instead be <TemplateURL>false</TemplateURL>
×
×
  • Create New...