Jump to content

JorgeB

Moderators
  • Posts

    67,565
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. LSISAS2308: FWVersion(20.00.00.00) Upgrade the firmware to 20.00.07.00, previous p20 releases have known issues, including generating CRC errors.
  2. By the screenshot I can't tell if that's a disk share or user share, you can name them whatever you want.
  3. iperf looks OK, if you haven't yet try copying from a disk share instead of user share.
  4. You need v6.9.rc1 for the NIC on that board to be supported.
  5. You can do this: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  6. Because the disk wasn't disabled, any write error Unraid would disable the disk. Just do a standard replacement, as long as no more errors on a different disk it should be rebuilt correctly.
  7. Diags are after rebooting so we can't see what happened, but the disk looks fine, so replace/swap cables to rule them out and rebuild on top.
  8. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601 Not sure it's fully working with v6.9 though.
  9. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  10. 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.
  11. That tunable no longer exists in current Unraid.
  12. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  13. Disk dropped and reconnected again, disk itself looks fine, check/replace cables.
  14. Please post the diagnostics: Tools -> Diagnostics
  15. Data should be fine since Unraid successfully wrote back the failing sectors (assuming parity was valid), disk doesn't look very healthy though.
  16. Stop/start the array, if nothing changes run a filesystem check on disk6.
  17. It's possible, and it should be replaced anyway.
×
×
  • Create New...