Jump to content

JorgeB

Moderators
  • Posts

    67,598
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Replace/swap cables on parity and try again, but note that SAS2LP controllers are not recommended for Unraid v6. You also need to check filesystem on disk3.
  2. Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  3. Then please post the diagnostics: Tools -> Diagnostics
  4. If you're sure assignments are correct check "parity is already valid" and start the array.
  5. Try enabling one docker at a time and let it run for a while to see if you can find the culprit.
  6. You can't rebuild to a new filesystem, basically you need an extra disk formatted xfs to move all the data from another disk and then re-format the source and repeat, more info here:
  7. Minor issue, was looking for NUT UPS tools But clicking on the suggestion doesn't give any results, looks like a few spaces are added Just searching for nut worked though.
  8. Some things to try in this thread:
  9. Yep, unfortunately there's nothing about the crash.
  10. This is also happening to me while trying to uncheck a SMART attribute from notifications, strangely it works in another server also running v6.9.1 using the same browser (chrome), for this one had to manully add the lines for all the devices to smart-one.cfg, or it would only save the last one applied.
  11. There have now been a handful of reports of this issue, so I now believe it's likely a bug: https://forums.unraid.net/topic/76732-parity-check-running-when-starting-array-every-time/?do=findComment&comment=957539 Good if LT can fix this in a future update.
  12. 5TB drives are SMR, still 2MB/s is stupid slow, if you have a spare non SMR disk or SSD add it as cache device and see what speed you get transferring to cache, if still slow do a single stream iperf test.
  13. Is the flash drive bootable in another computer? Like mentioned there are a lot of users with that board and never heard of any issues booting.
  14. Those are normal, syslog server might help if it catches anything.
  15. Remove two DIMMs and reacreate the docker image, if it corrupts again try with just the other two, if still issues unlikely to be RAM related.
  16. You're having issues with the disks on the HBA: Mar 14 07:32:02 Unraid kernel: md: disk3 read error, sector=4395399968 Mar 14 07:32:02 Unraid kernel: md: disk1 read error, sector=4395399944 Mar 14 07:32:02 Unraid kernel: md: disk0 read error, sector=4395399944 Make sure it's well seated or try a different slot, you should also update the LSI firmware to latest.
  17. https://forums.unraid.net/topic/103938-69x-lsi-controllers-ironwolf-disks-summary-fix/
  18. Anyone having issues using custom a IP address for docker(s)? That's a known issue and it can crash Unraid, more info below:
  19. Samsung SSD and some Asmedia controllers don't always go well together, use the onboard Intel SATA ports if possible, but first change controller from IDE to AHCI.
  20. I would now agree, since it happened to at least a handful of users.
  21. You can't run SMART tests on NVMe devices. Let it run for 24H but if it didn't find any issues so far it likely won't, also note that memtest sometimes can't find issues even when there are some, but the problem can come from somewhere else.
  22. Without seeing the actual error difficultly to say, but you can reset the cache pool by starting Unraid without any cache devices assigned, then stop the array and you can assign just one device, if a valid btrfs filesystem is detected it will be imported.
×
×
  • Create New...