Jump to content

JorgeB

Moderators
  • Posts

    67,871
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. You can assign them as individual pools (or multiple disk pools), then set the plots share as cache="only" and select the pool you want to fill up first, once it's full select the next pool and so on.
  2. Like mentioned good overall case airflow is enough, I have a couple like that, but more direct airflow is better.
  3. After you get that error download and post the diagnostics.
  4. Try swapping cables with a different disk, both power and SATA, or slots if that's the case.
  5. Original heatsink if fine if you have overall good airflow in the case, obviously including the zone where the controller is, if using a tower style case a large side fan can also be a good solution.
  6. Issues appear to start with Python errors: Oct 8 06:10:15 mediaserver kernel: python: Corrupted page table at address 1495f93e1260 Try booting in safe mode to rule out plugins.
  7. Finding the server powered down is almost certainly a hardware problem, unless you have something powering it off, you can enable the syslog server to confirm, if it's powering off on its own it could just be temps related or other issues, like PSU or board.
  8. Doesn't look like a disk problem, wait for the parity2 sync to finish then check/replace cables on that disk and if the emulated disk is mounting and contents look correct you can rebuild on top.
  9. Cannot help with the actual issue, but: This is incorrect, any data on cache will still be moved by the mover as long as the share is correctly configured. This is correct.
  10. You can post the diags in case something is visible like in the previous case.
  11. RDIMM and LRDIMM are for server boards, your board will only accept UDIMMs, AKA unbuffered ECC DIMMs.
  12. It's not the same issue: Oct 8 10:50:05 Unraid kernel: nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 Oct 8 10:50:05 Unraid kernel: nvme nvme0: Removing after probe failure status: -19 The device failed to initialize. This also suggests it's not a software problem if it was it would always work or always not work with the same release, please try upgrading to v6.11.1 again to see if it was a one time thing.
  13. Looks more like a hardware issue to me, you can try going back to the previous known good release and see if it still happens, if yes it's likely hardware related.
  14. Does it still run stable if you downgrade to v6.9.2?
  15. Nothing so far suggests a software problem, if anything and since nothing is being logged it suggests a hardware problem, but get the diagnostics after the local Firefox stops working to see if there's something relevant logged, also can you still access the GUI with a browser when that happens?
  16. Permissions look fine, and if the problem is related to "access based share enum" I really cannot help, never used that option nor remember anyone else on the forum using it, possible it's broken or working differently with the new Samba release.
  17. It did it for the array, not for pools until v6.10
  18. Upgrade to v6.11.1 first, v6.9 didn't stop the array from auto starting with a missing pool device, though you could add it later, and don't remember if there were other issues.
  19. Yes that's fine, assuming the current pool is redundant, also make sure you're using the current stable, this didn't always work correctly with older releases.
×
×
  • Create New...