Jump to content

JorgeB

Moderators
  • Posts

    67,667
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Also good to replace/swap power cable just to rule that out.
  2. If there are doubts reset disk stats and disable docker and VM services, leave it like that for a few hours or days enough to confirm that there are no reads on that disk, then enables services one by one and re-check.
  3. Enable syslog mirror to flash then post that log after a crash.
  4. Try again after rebooting in safe mode, a bad behaving plugin can cause that.
  5. Please post the diagnostics: Tools -> Diagnostics
  6. Also a good idea to run memtest, bad RAM is the number one reason for unexpected sync errors.
  7. Looks good, I would just add that when using the second option user should run a correcting parity check ASAP to correct the sync errors.
  8. Didn't noticed, but yeah, IMHO it should men mentioned first as a way to keep parity 100% in sync, just in case a disk fails before it can be corrected if doing the other way.
  9. That will make parity out of sync, maybe using UD and mounting the disks read-only could be added as an option.
  10. Enable syslog mirror to flash then post that log after a crash.
  11. Install the UD plugin and mount all the disks read-only, there should only be one disk that doesn't mount, that would be parity, if yes assign all the disks, data disk order doesn't matter with single parity, check "parity is already valid" and start the array.
  12. There are multiple segfaults and btrfs is detecting data corruption, start by running memtest.
  13. Enable syslog mirror to flash then post that log after a crash, together with the complete diagnostics: Tools -> Diagnostics
  14. These come from an NTFS formatted unassigned disk/volume, run chkdsk on it.
  15. Please post the diagnostics: Tools -> Diagnostics
  16. Not reliably. No, that's a v6.8.3 issue: https://forums.unraid.net/topic/108643-all-docker-containers-lists-version-“not-available”-under-update/?do=findComment&comment=993672
  17. if there are no errors manual trim is the same as the Dynamix trim.
  18. This is an Unraid forum, more likely to get help if you post in a Windows related one.
  19. If it was working before with the same Unraid release it could be, or some other hardware related issue.
  20. Looks more like a hardware problem, or the current kernel doesn't like your board, looks for a BIOS update and/or try with a previous Unraid release, if it's the same it's likely hardware.
  21. If you mean lack of lanes no, or the HBA wouldn't be detected, though the bottom slot is only x4, but that could at most be a performance issue, not a reliability issue.
×
×
  • Create New...