Jump to content

Squid

Community Developer
  • Posts

    28,769
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. The MCE is nothing and can be ignored Have you already set the Typical Idle Power in the BIOS to be "typical"?
  2. Squid

    [6.10RC5]

    CA on dockerHub conversions was putting the entry into the Icon. This is fixed next rev You'll have to edit the template and remove that line EDIT: The next release of the OS (rc6?) will ignore this particular entry
  3. Squid

    [6.10RC5]

    Is that what the Icon URL actually is on the template??? for next_pvr? /plugins/dynamix.docker.manager/images/question.png Technically, that's not a valid URL and should be blank instead The Hotio one is valid, as that's not a good URL and needs to be changed
  4. You're stubbing the HBA to isolate it from a VM 24:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: Dell SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1028:1f4f] Kernel driver in use: vfio-pci Kernel modules: mpt3sas Since it doesn't look like you're doing this through Tools - System Devices, is one of your VM's referencing this card in "Other Devices" or the like?
  5. From the command prompt, diagnostics The file will get saved onto the flash drive (logs folder). Powerdown powerdown Pull the flash, and upload the zip file to your next post.
  6. Did you start the array in Maintenance Mode?
  7. Yes. You can flip back and forth as much as you want.
  8. If it's Windows, you should hibernate the VM instead of doing a shutdown. (VM Settings - change shutdown to be "Hibernate" and install the QEMU Guest Tools on the VM
  9. Not everything that is "forced" is an unclean shutdown. Certain versions of the OS were too aggressive in what they called an unclean shutdown and the resulting parity check, and this may be what you were used to seeing. An unclean shutdown is where the system cannot unmount the drives, and has to force them to unmount. So long as the drives can be unmounted correctly, the shutdown is "clean" regardless if a process(es) had to be forcibly terminated.
  10. Column to column has never been implemented
  11. You can always see if this fixes you up
  12. Primary support venue for SelfHosted's apps would be via the discord (click the icon, select Discord)
  13. Long story behind the evolution of <Overview> vs <Description> which TBH I'm still annoyed about (although it's currently 7:51 am and I'm now considering having a beer before work to calm down now that this has come up again ) If Overview is present, then Description is completely ignored
  14. Ignore it or rename the file to something other than .cfg which triggers this issue
  15. PCIe slot disabled due to forcing another slot to be x16 instead of "auto" or x8 which has the effect of disabling another slot that has shared bandwidth?
  16. Technically you don't. But if you look at the wording, nowhere does it say "sync" It says "Check", and is simply a check (usually run monthly during off hours) to make sure that if need be that everything is good to go and can rebuild a drive if the need arises.
  17. probably via the docker run command which tells you everything on most errors you need to know
  18. Don't you have to click the checkbox for formatting and then there is also a further popup stating that "Formatting is never part of a recovery"?
×
×
  • Create New...