JorgeB

Moderators
  • Posts

    61540
  • Joined

  • Last visited

  • Days Won

    648

Everything posted by JorgeB

  1. Usually the key is named for the license type, i.e.: Basic.key, Plus.key or Pro.key.
  2. It means supporting zfs pools with cache, logs, dedup, special and/or spare vdevs.
  3. Enable the syslog server and post that after a crash.
  4. Run an extended SMART test on the disk, if it passes it's OK for now, if it fails it should be replaced, but it should be OK.
  5. You may have a network problem, you can try deleting/renmaming /boot/config/network.cfg to go back to default DHCP and re-rest, it may also be a good idea to re-start your router, if the same it basically can only be a router or network/internet problem.
  6. Check filesystem on disk1, run it without -n and if it asks for -L use it.
  7. Try changing your DNS server to 208.67.222.222 and 208.67.220.220
  8. Still don't understand what you mean, each array device uses the full capacity of the drive as an independent filesystem, please post the diagnostics and identify which drive you think is the problem.
  9. Balance is aborting because it's finding some corrupt data, if you don't have ECC RAM it may be a good idea to run memtest first, then scrub the pool and look at the syslog for the list of corrupt files, delete/restore those from a backup, then run another scrub to confirm there are no more errors and try to convert again.
  10. Since this is a plugin recommend reporting it in the existing plugin support thread instead: https://forums.unraid.net/topic/38582-plug-in-community-applications/
  11. Asmedia SATA controllers won't require fleshing to IT mode, the model you've linked should work fine.
  12. This unassigned disk is causing constant errors: Apr 1 04:39:24 Tower emhttpd: HUH721212ALE601_8DHU1VAH (sdk) 512 23437770752 Disconnect it and post new diags.
  13. If you removed an array drive parity should be resynced instead, a parity check will be much slower due to all the errors.
  14. Don't recommend that as it's known to sometimes cause data corruption and/or stability issues.
  15. I don't think that's related to the failure, but you should not do it, as it will keep spamming the log.
  16. Not sure what you mean, parity doesn't work with mirrors, every disk you add will use the full capacity.
  17. Yep, this would be the problem, not the board SATA controller. 6.12.10 should be out soon with a fix.
  18. Should be plug and play, don't know about ASPM.
  19. Typicall SATA controllers are limited to 5 or 6 ports without SATA port multipliers, LSI SAS/SATA HBAs exist with 16 or even 24 ports.