Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,557

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601 Not sure it's fully working with v6.9 though.
  2. JorgeB
    https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  3. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  4. JorgeB
    One more thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  5. JorgeB
    Yes.
  6. JorgeB
    Did you ? If yes, replace the drive.
  7. JorgeB
    That tunable no longer exists in current Unraid.
  8. JorgeB
    https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  9. JorgeB
    Disk dropped and reconnected again, disk itself looks fine, check/replace cables.
  10. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  11. JorgeB
    Replace cables on that disk and try again.
  12. JorgeB
    Data should be fine since Unraid successfully wrote back the failing sectors (assuming parity was valid), disk doesn't look very healthy though.
  13. JorgeB
    Run an iperf single stream test to check lan bandwidth.
  14. JorgeB
    Stop/start the array, if nothing changes run a filesystem check on disk6.
  15. JorgeB
    It's possible, and it should be replaced anyway.
  16. JorgeB
    Only if you have IPMI.
  17. JorgeB
    That suggests a hardware problem.
  18. JorgeB
    The mover should work now, but data corruption is not a good sign, start by running memtest.
  19. JorgeB
    All the call traces I see are Macvlan related, this is usually the result of having dockers with a custom IP address, more info below:
  20. JorgeB
    Checksum failed means corrupt data, run a scrub and post the diagnostics.
  21. JorgeB
    SMART test failed, so the disk should be replaced.
  22. JorgeB
    Yes, you can have a script doing that after every reboot. This, 2.5" drives are usually much more aggressive with power saving features, WD black are usually a exception since they are optimized for performance.
  23. JorgeB
    No idea. Probably nothing to worry about.
  24. JorgeB
    That's nothing to worry about. The trim issue is a known issue with SAS2 LSI controllers and current firmware/driver, some users found that downgrading to firmware p16 allows trim to work, and while I don't personally recommend using an old firmware it might be an option, more info below: https://forums.unraid.net/topic/74493-samsung-ssd-hba-trim/page/4/
  25. JorgeB
    No, it's the worst setting for write speed. Whichever you prefer from the other ones, high water is the usually the best compromise. Read speeds won't be affected, unless you plan on reading multiple files at the same time, in that case if they were dispersed speed could be better, but you'd need a way of only reading multiple files from different disks. No, but it won't make any difference for reads.
×
×
  • Create New...