Jump to content

JorgeB

Moderators
  • Posts

    67,880
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Run another test, if it fails replace the disk, if it passes keep monitoring, especially these SMART attributes: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 18 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 1 If they keep climbing you will likely get new errors.
  2. You are getting read errors on many different disks, you should see those errors on the main GUI page (and be notified about it if notifications are enabled), errors on so many disks suggest power/connection problems, you must fix that first.
  3. Yellow color in the dashboard means cache only shares, only on the "Shares" tab it means unprotected.
  4. It's logged as a disk error, there's a recent SMART extended test, if it was before the error run another one, if not keep monitoring, but SMART is showing some issues, so probably going to get more errors in the future.
  5. Disk looks OK but run a long SMART test to confirm, for the VM issue best to start a new thread in the KVM section.
  6. There's something writing to the array during rebuild, disks 2 and 3 are being rebuilt while there are writes to disks 1, 6, 7, 8 and 9, this will make the rebuild (and writes) extremely slow.
  7. There are called traced logged that suggest macvlan is the problem, and it is a known problem, ipvlan should have no impact on CPU usage.
  8. We need the syslog at least to confirm if it's the same issue or not.
  9. Look more like a power/connection problem, check/replace/swap cables and re-sync parity.
  10. Almost all disks disconnected and reconnected at the same time, including both parity drives which are using a different controller, so most likely a power problem, even if you do anything else for now you should at least reboot.
  11. Number of reads/writes is basically meaningless, it can vary a lot, even for similar devices, monitor read/write speed instead.
  12. Yes, USB 2.0 is best, and you are having flash drive issues, so try that first.
  13. Basically yes, SMART looks good for both.
  14. The mover starting and ending should be logged if it really ran at that time, though it won't help much with this issue.
  15. Start by checking the LAN link speed and/or running iperf.
  16. Enable the syslog server and post that after a crash.
  17. You can use this procedure: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
  18. I assume there's nothing relevant before the call trace?
  19. This has been reported to help: https://forums.unraid.net/bug-reports/stable-releases/6103-samsung-980-temp-warning-r2007/?do=findComment&comment=20180
  20. Oct 30 02:00:01 thebox kernel: md: recovery thread: check P ... Oct 30 03:00:01 thebox kernel: mdcmd (63): nocheck pause This suggests parity is set to pause after 1H, try re-applying the scheduled parity check settings.
  21. modprobe i915 chmod -R 777 /dev/dri Did you add this now or was it added to an older release? Try removing those lines from your go file.
×
×
  • Create New...