Jump to content

JorgeB

Moderators
  • Posts

    67,556
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. If it's slow from the beginning of the transfer it suggests a network issue, start by running a single stream ipert test.
  2. For some time, since firmware P17 IIRC, that trim doesn't work with LSI SAS2 models, it works with SAS3 models (only on SSDs with DRZAT like you mentioned).
  3. That should fix the problem for now, you'll lose trim support but that's a small price to pay for stability, you can just connect the SSDs to the LSI, Unraid will pick them up without a need to do anything else.
  4. You should also run memtest, bad RAM is the number 1 cause for sync errors.
  5. If there were no unclean shutdowns there's likely a hardware issue, you should post the diags so we can look at the hardware used.
  6. This is a general support issue, one of the cache devices dropped offline: Dec 13 06:56:15 NAS kernel: ata4: softreset failed (1st FIS failed) Dec 13 06:56:15 NAS kernel: ata4: limiting SATA link speed to 3.0 Gbps Dec 13 06:56:15 NAS kernel: ata4: hard resetting link Dec 13 06:56:20 NAS kernel: ata4: softreset failed (1st FIS failed) Dec 13 06:56:20 NAS kernel: ata4: reset failed, giving up Dec 13 06:56:20 NAS kernel: ata4.00: disabled This was caused by a problem with the AMD onboard SATA controller: Dec 13 06:55:14 NAS kernel: ahci 0000:03:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0015 address=0xdef9e000 flags=0x0000] This issue is quite common with Ryzen boards, look for a BIOS update or disable IOMMU if not needed, a newer/different kernel might also help.
  7. 1 sync error is too many, any unclean shutdowns since last check?
  8. It's failing the SMART test, and there are UNC errors, I would replace it.
  9. If the NIC is not detected it suggests a hardware issue, possibly just a compatibility problem, not much you can do on the Unraid side.
  10. Crash appears to be network related, try to simply the network config as much as possible and/or try a different NIC.
  11. Looks more like a connection problem, replace cables and try again.
  12. Try this: Stop the array, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign both cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), start array and post new diags.
  13. But that's not correct, like I mentioned above You can balance to single and remove the other device.
  14. Diags after rebooting are not much help, you can try this.
  15. If so far so good there's not much to see.
  16. Do you mean in UD? You either mount with UD or pass trough to a VM, can't do both.
  17. Unlikely that preclear or any other disk test will help with vibration issues, either live with it or replace it, again very difficult to predict if it's going to cause problems or not.
  18. Settings -> Syslog Server If it helps or not.
  19. Do you have syslog server running? Also try booting in safe mode.
×
×
  • Create New...