Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Problem is disk2, it's failing: === START OF READ SMART DATA SECTION === SMART Health Status: FAILURE PREDICTION THRESHOLD EXCEEDED: ascq=0xfd [asc=5d, ascq=fd] Do you have another spare?
  2. JorgeB

    Lost

    And if you don't have a backup or the original .key contact support to get a replacement: https://unraid.net/contact
  3. Up to date in the sense that now there's a SMART report for disk16, syslog is always lost after a reboot, disk16 SMART looks OK, though it looks like a white label drive, don't really recommend those, run an extended SMART test on disk5 and post new diags.
  4. Cache SSD is dropping offline, SMART looks OK, try swapping cables (both power and SATA) with a different disk, or just replace them.
  5. Diags are after rebooting so we cannot see what happened, for now check filesystem on disks 8 and 10, don't format anything.
  6. Nothing obvious logged, did you set the correct power supply idle control as linked above?
  7. Syslog cuts off August 23 so we can't see the errors, but you should run an extended SMART test on disk5 since it's logged there as a disk problem, there's no SMART for disk16, power cycle the server and post new diags after array start.
  8. We don't recommend RAID controllers for Unraid, they can have various issues.
  9. Check if the container you're using has a support thread/discord, that would be the best place to get help with that.
  10. If all is well you'll get close to line speed with iperf and a single stream, I get around 9.5Gbits
  11. Diags might show something but if it's an Emby problem I cannot help since I've never used it, someone else might.
  12. Nope. File system check should not be needed, but it won't hurt as long as it's in read only mode.
  13. That's good news, just running xfs_repair didn't fix it?
  14. P.S. a single stream iperf test is much better to give an idea of the actual transfer speed, when you copy using one windows explorer session it's a single transfer.
  15. Drop is kind of fast to be the effects of RAM caching, try enabling disk shares and copying directly to the cache share.
  16. Currently only the WD SSD is in the pool, stop the array, unassign the Samsung NVMe, start array, stop array, re-assign the Samsung NVMe, start array and that should fix it, in doubt post new diags.
  17. Does it get responsive if you stop the docker service? If yes try stopping one docker at a time.
  18. If it's working fine let it be, if it happens again try booting legacy.
×
×
  • Create New...