Jump to content

JorgeB

Moderators
  • Posts

    67,459
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. Start here, you're overclocking the RAM for the installed CPU, and that's a known source of problems with Ryzen.
  2. When bad sectors are re-allocates by the disk's firmware they keep using the old LBA, it's transparent to any OS.
  3. That's one of the worst options to use with Unraid v6, together with the SAS2LP which uses the same driver, they have multiple known issues.
  4. No: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed. -Start array to begin parity sync (alternatively you could select "parity is already valid" before starting the array, since it mostly is, then run a correcting parity check)
  5. Unfortunately there are no errors logged before the crash, most likely a hardware issue.
  6. Assuming the old disk is intact and all disks are healthy you can do a new config and then re-sync parity.
  7. Suggest replacing/swapping cables to rule them out and then re-sync parity.
  8. You can still swap with another disk. SATA + Power cable
  9. Only need to post it after the server crashes, not much point in looking at it before that.
  10. That means the partition is gone, it was either deleted or it could be an SSD problem, despite still appearing healthy on SMART.
  11. If the syslog is after a crash/shutdown there's nothing there, which further suggests a hardware issue.
  12. No, the limit if for all attached devices, including devices not used as part of the array/pool
  13. That won't accomplish much, best to replace or swap the cables with another disk to rule them out. I suppose you mean unassign and re-assign the disk here, if yes that's correct
  14. SSD looks normal, please post output of: mkdir /x mount -v -t xfs /dev/sdh1 /x Also any errors on the syslog after typing the mount command
  15. Disk looks fine, recommend replacing/swapping both cables to rule them out, then rebuild on top.
  16. Rebooting shouldn't be needed for this, but glad it's working now.
  17. SMART test passed so disk fine, at least for now, and those pending sectors are "false positives", replace/swap both cables to rule them out and rebuild on top.
  18. They are, and the most likely problem.
  19. Firefox is again one the worse, have you tried not booting in GUI mode?
  20. It's logged as an actual disk error, but these can be intermittent, run an extended SMART test.
  21. RAM should be fine, try running in safe mode for a couple of days without any docker, if stable start turning on the dockers one by one.
  22. Not seeing any USB device being connected, but since the log is kind of long, reboot, start the array, wait a minute and then plugin the USB device and post new diags.
×
×
  • Create New...