Jump to content

JorgeB

Moderators
  • Posts

    67,432
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. Not as a single array, but you could use the larger ones as array devices and the smaller ones as a cache pool.
  2. You likely have other issues as that would reset all network settings.
  3. Since there were errors on disks connected to both controllers it suggests more a power problem, though LSIs should still be upgraded to latest firmware. This is expected, once a disk gets disabled it needs to be rebuilt: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive P.S. the CPU is overheating and throttling down, check cooling.
  4. Everything looks normal to me, no idea what the problem is, you might want to wait a while to see if someone else has an idea, if not try recreating the flash drive: backup current flash, re-create it with the USB tool, only restore super.dat and your key, both are on the config folder.
  5. Very weird, post new diags after starting in safe mode.
  6. More importantly It makes it difficult for LT to fix if they can't reproduce it.
  7. And no difference accessing/using the dockers during those i/o waits?
  8. Did you format disk3 any any point during this? This suggests it was formatted, but if you don't known we'd need the diags from this time to see what happened.
  9. Anyone having this issue check if the docker image is on the array, if yes move it to cache or just outside the array, there are reports this can help, though probably mostly if the i/o wait is copying to the array, e.g:
  10. Docker image is on the array, there are similar reports when this is the case, try moving it to cache.
  11. Try booting in safe mode and leave docker service disable, see if that makes a difference.
  12. Cache2 failed to add to the pool, this sometimes happens for whatever reason, can't say why without the diags from when it was first added, but it's usually fixed by adding it again, stop array, unassign cache2, start array, stop array, re-assign cache2, start array, look for activity on cache2 or just post new diags. Note: this is considered a safe procedure but still make sure cache backups are up to date before doing it.
  13. You reset the network settings by deleting/renaming network.cfg and network-rules.cfg (if it exists), both will be on flash/config.
  14. Then it's not VM related, but not seeing the reason in the diags, try booting in safe mode, you can also try resetting network settings by deleting/renaming network.cgf (flash/config).
  15. Every storage devices counts except the Unraid flash drive, optical drives and unused card readers.
  16. Disable array auto start, VMs won't auto start if the array is started manually.
  17. Yes, they likely share the same miniSAS cable, also check power if shared, e.g. a SATA splitter.
  18. Please post the diagnostics: Tools -> Diagnostics
  19. There's a chance that after the move all data disks will be unmountable due to an invalid partition, if that happens you can rebuild one by one, like this:
  20. Possibly the NIC is being pass-through to a VM, please post the diagnostics: Tools -> Diagnostics
  21. Then either rebuild the disk or shrink the array.
  22. First thing to do is to update LSI firmware to 20.00.07.00, all p20 firmwares before that one have known issues, and it's on 20.00.02.00
×
×
  • Create New...