Jump to content

JorgeB

Moderators
  • Posts

    67,696
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. SMART for SSDs is not so easy to analyze, one of them is getting close to predicted maximum life and showing some issues, but it could still last for a while, pool is correctly configured for redundancy, also see here for better pool monitoring so you're warned immediately if there's a problem.
  2. I would recommend backing up and re-formatting the pool, if issues persist you should run memtest.
  3. Error was after spin up, some combinations of drives/controller can cause this, you should update the LSI firmware to latest, it might help, if it doesn't you can try reporting the issue in the SAS spin sown plugin support thread, or disable spin down for that drive.
  4. You should post in the existing plugin support thread:
  5. That's normal since the auto check is non correct, as log as the next check doesn't find any errors you're fine.
  6. Driver for the NIC isn't loading: Oct 3 04:05:23 Tower kernel: e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid Oct 3 04:05:23 Tower kernel: e1000e: probe of 0000:00:1f.6 failed with error -5 Try googling the error, might need a firmware update.
  7. Don't recommend Marvell, also don't know of any 6 port Marvell controller without using SATA port multipliers and those are not good, Asmedia is available in the various Amazon and Ebay stores, if you can't get that look for an LSI HBA, there are various non RAID models referenced here:
  8. Yes, you should keep disks under 40C, 45C tops, though not always possible if the disk is inside a USB case, but still not good for long term health.
  9. Disk has pending sectors and failed the SMART tests, needs to be replaced.
  10. Please use the existing docker support thread:
  11. Not without anything relevant logged before the crash like mentioned this is usually a hardware problem, one 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.
  12. SMART test passed so disk is OK for now, keep monitoring.
  13. Default mode is raid1, only 128GB can be used, you can change to single profile to use both.
  14. Please use the existing docker support thread:
  15. That's the maximum usable speed when using that controller with 6 devices at the same time, since current disks can't reach 300MB/s it still won't be much of a bottleneck for the 2 SSD's, you can also connect the SSDs to onboard SATA, it will have a little more bandwidth, and connect only HDDs on the add-on controller.
  16. It's good for 6 x 300MB/s, that's enough for 6 HDDs, but not for 6 SSDs, if you plan to use them simultaneously.
  17. This part here sounds more like a UD plugin issue, do you still have problems without the UD plugin installed?
  18. Could be some compatibility issues with those disks and that Intel chipset, or that board model in particular, you'd need to test the same disks in a different identical board and/or a different board with the same chipset to compare.
  19. SMART looks good, but if it keeps failing on a different bay it could still be a bad disk, or like trurl mentioned caused by not enough power or some voltage drop when running a parity check.
  20. Yes, not going to help, sorry, that was a typo before.
  21. Look for an Asmedia ASM1166, only PCIe 3.0 x2 but that's enough for 6 HDDs, even if they are used simultaneously.
  22. Parity check won't affect a cache device, try a different bay, if it keeps dropping try a new disk.
  23. Oct 1 00:00:31 Tower kernel: ata6: SATA link down (SStatus 0 SControl 300) Oct 1 00:00:31 Tower kernel: ata6.00: link offline, clearing class 1 to NONE Oct 1 00:00:31 Tower kernel: ata6.00: disabled Cache device dropped offline, because of that there's no SMART, check/replace cables and post new diags.
×
×
  • Create New...