Jump to content

JorgeB

Moderators
  • Posts

    67,877
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. If possible test Duplicati with disk shares instead to see if there's any difference.
  2. You can try but unlikely to help, and if it does it will probably be a coincidence.
  3. Look for a way to disable SMBus over PCIe, Supermicro boards usually have jumpers for this, and after doing no need to tape the pins, but unlikely a desktop board will have that option.
  4. Nothing in the logs, you can try recreating the docker image and/or that specif docker container.
  5. You have firmware 16.00.10.00, current one is 16.00.12.00 IIRC, the one on the guide is to show how to update, not to show the latest firmware.
  6. Yes, I agree, false alarm was being able to reproduce it on demand, this would help a lot with troubleshooting.
  7. False alarm, turns out the server has bad RAM, strange that one time the call trace was exactly the same as these.
  8. Please post the complete diagnostics instead.
  9. A new libvirt.img file was created on disk7, system share is set to use pool "cache" but there's no pool named "cache", change that to the pool you want to use and try again.
  10. AFAIK only 9400 series or newer support NVMe devices.
  11. Not seeing the same call trace with v6.10.3, I do see a lot of segfaulting, run memtest to rule out any obvious RAM issues.
  12. There's one user with the same issue that can apparently make it crash on demand with high i/o, so it does point to that being the problem, of course some servers might be more susceptible than others.
  13. This is the same issue some users are seeing after updating to v6.11, not yet clear the root cause but we think it's high i/o related, two things please: -What exactly are you doing to make it crash to see if other users can replcate -try downgrading to v6.10.3 to see if it doesn't happen there doing the same
  14. Create a new VM using that libvir.img, can be a test VM with a new vdisk, reboot and post new diags.
  15. It happens if there's a lot of spam.
  16. Not seeing any attempt to start the VM service, disable then re-enable the service and post new diags.
  17. Sorry, don't understand the question.
  18. It will delete the BIOS, then see if it helps or not, it won't hurt.
  19. Where are you doing this? Controller must be detected for it to work.
×
×
  • Create New...