Jump to content

JorgeB

Moderators
  • Posts

    67,582
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. You don't need that with updated firmware.
  2. Are both disks from the same model?
  3. Try this then post that log after a crash.
  4. This will delete all data on that device like the warning says, there's a way to re-add a device without deleting data, but it's likely to late for that, please post the diagnostics: Tools -> Diagnostics
  5. Yes, but you can easily add them back, see the link.
  6. Yes, and it will improve once the current writes are flushed to the disks.
  7. loop2 is the docker image, try deleting and recreating.
  8. Power down, replace cables on disk5, power back up, start array and post new syslog.
  9. Yes, but load average is very high, likely i/o wait and that's what you're seeing in the dash, diags might give more clues.
  10. Would recommend replacing/swapping cables before the re-sync to rule them out if it happens again.
  11. Forgot to mention, v6.9-rc has a bug and cache replacement doesn't work, it does with v6.8.
  12. Check filesystem on disk1: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Remove -n or nothing will be done.
  13. Yes, it will never be faster than the slowest device in the array.
  14. Please use the existing plugin support thread:
  15. Disk dropped offline, check/replace cables then run a SMART test.
  16. Not much point in running memtest with ECC RAM unless there's an option to disable ECC in the BIOS.
  17. That would only happen if you also lost the appdata folder.
  18. Rebuild was successful, because you have dual parity, and disk8 appears to be really failing so it needs replacing. It's ratter common since all drives are read during a rebuild, including parity, dual parity saved your butt here.
  19. The dual in the table refers to the rank, but yes, since your dimms are dual rank max speed is 2400Mhz. Parity check is also a pretty good test, only acceptable result is 0 errors, note that it's normal for the first check after the problem is solved to still find errors.
  20. Not sure, but it suggests the backup wasn't OK, you'll likely need to re-create the VM, you can use the existing vdisk if you use the same configuration.
  21. Libvirt if for VMs, for dockers you can just restore them: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  22. Ryzen with above spec RAM is known to corrupt data, see here, if just lowering to max supported speeds doesn't solve it run memtest.
×
×
  • Create New...