Jump to content

JorgeB

Moderators
  • Posts

    67,662
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Disk dropped offline, SMART looks fine, most likely a connection/power issue.
  2. You can use the highlighted toggle to get real time disks speeds:
  3. Should be, but not by much.
  4. Read check like the name implies only reads the data disks, it will report any read errors.
  5. Disk2 is failing, copy whatever you can manually or using ddrescue and then rebuild parity with a new disk.
  6. Docker image is going read-only because of lack of space, due to cache being completely full.
  7. If the server shutdown on its own it suggests a hardware problem, start by checking cooling and temperatures, could also be the power supply.
  8. You'd need to do a new config and re-sync parity. It's showing a pending sector, you should run an extended SMART test.
  9. Cache filesystem is corrupt, you should backup and re-format.
  10. Problem is with disk1: Jun 24 07:22:43 Tower kernel: XFS (md1): Corruption detected. Unmount and run xfs_repair
  11. Filesystem corruption on cache and it went read-only, it will likely happen again, make sure backups are up to date or preemptively backup and re-format.
  12. Based on the syslog disk4 appears to be failing, post a SMART report for that disk, or update to v6 and post the diags, you should also change the onboard SATA controller from IDE to AHCI.
  13. Disk errors look more like a connection/power problem, for the reboots see here, also next time please post the full diagnostics instead.
  14. Nothing there crash related, full syslog might show more.
  15. I assume the backplane uses miniSAS, if yes you need a reverse breakout cable, forward breakout looks the same but it only works the other way around, miniSAS to host and SATA to target, you need SATA to host and miniSAS to target.
  16. I would think a few like 2 or 3 shouldn't make much difference, but if you do like 10 in a month, that could have an impact.
  17. There's a lot of data corruption detected, first thing is to respect the max officially supported RAM speed for your CPU, since that's a known source of data corruption with Ryzen, also not a bad idea to run memtest after that, once it's fixed restore files from backup.
  18. If it finishes replace after, if it errors out again replace before another attempt.
  19. Disk dropped offline again, this is usually a connection/power problem, if you already replaced the SATA cable replace the power cable.
  20. Don't see anything out of the ordinary logged, you should probably post on the OpenVPN docker support thread.
  21. Disk looks OK, you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
×
×
  • Create New...