Jump to content

JorgeB

Moderators
  • Posts

    67,540
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. No disks are failing SMART, so can't comment about the boot issue, as for the ATA2 errors it looks like a bad SATA cable, replace the cable on disk2.
  2. Please post the complete diagnostics: Tools -> Diagnostics
  3. Just that the disks look fine, so likely a controller or power/connection problem, my money would be on a controller issue, since it's quite common with Ryzen boards and v6.8.
  4. Issue again started with Macvlan call traces, if you're not using custom IP it's still likely network related, try simplifying your lan config as much as possible to test.
  5. Those diags are after rebooting, and the syslog you posted before is incomplete and doesn't show the beginning of the problem, did you save the complete diags before rebooting?
  6. I get normal speeds with Windows 10 and Mellanox, so likely an OS issue.
  7. It's normal with current xfs, it uses more space for metadata, only option would be to format manually or with and older Unraid release.
  8. There won't be a driver for that NIC in v6.8, you need to use the latest beta: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta30-x86_64.zip
  9. No need for all those options, especially since something is incorrect, just: iperf3 -s iperf3 -c IP
  10. Parity can't help with filesystem corruption.
  11. It's possible, even likely: Nov 9 05:07:22 Teletran kernel: ata7.15: limiting SATA link speed to 3.0 Gbps Nov 9 05:07:27 Teletran kernel: ata7.15: softreset failed (1st FIS failed) Nov 9 05:07:27 Teletran kernel: ata7.15: failed to reset PMP, giving up Nov 9 05:07:27 Teletran kernel: ata7.15: Port Multiplier detaching Nov 9 05:07:27 Teletran kernel: ata7.00: disabled Nov 9 05:07:27 Teletran kernel: ata7.02: disabled Nov 9 05:07:27 Teletran kernel: ata7.00: disabled But can also be a cable issue.
  12. That controller uses a SATA port multiplier and is not recommended.
  13. Both should work, but the 9200-8i is not a standard retail model, could be OEM, should be fine if it's genuine.
  14. This error is fatal, it means there are some missing writes, you'll need to reformat that disk, some recovery options here if needed.
  15. Swap cables with another disk and see if the issue follows the cables or the disk.
  16. You changed the array config (by doing a new config) but didn't resync parity (you must have clicked "parity is already valid"), and since it wasn't the rebuild disk is corrupt.
  17. Macvlan call traces are usually caused by having dockers with a custom IP, see here:
  18. Run a single stream iperf test.
  19. Please post the diagnostics: Tools -> Diagnostics
  20. Check connections on disk3.
  21. JorgeB

    Errors

    Disk dropped offline so there's no SMART report, check/replace cables and post new diags.
  22. Disk3 is failing and needs to be replaced, if still issues after that post new diags.
  23. Nov 8 05:00:15 ramiii kernel: XFS (md5): Corruption detected! Free inode 0x185c407dc not marked free! (mode 0x41ed) Check filesystem on disk5.
×
×
  • Create New...