Jump to content

JorgeB

Moderators
  • Posts

    67,616
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Since you started another thread please continue discussion there: https://forums.unraid.net/topic/106667-so-my-nas-that-was-running-unraid-suddenly-has-been-reinfected-with-asmb6-ikvm-anyone-have-a-suggestion/
  2. That is the IPMI function, you can read the manual to find out how it works, and please stop starting multiple threads for the same issue, continue discussion below.
  3. See if you can clone it with ddrescue.
  4. That one is supported by Unraid, diags might show the problem.
  5. Syslog is still full of call traces, this can be a hardware issue or your hardware doesn't get along with current Linux kernel.
  6. Diags are after rebooting so we can't see what happened, but disk looks fine and since it's mounting you can rebuild on top, before doing it you may want to replace/swap cables just to rule them out if it happens again to the same disk.
  7. You can find which ones are the data drives by mounting them with UD, use read only mode to keep parity 100% valid, did you have single or dual parity?
  8. You need to check filesystem on disk6, but there are a lot of other traces, and I have no idea what those are about.
  9. Thanks for this, lost passwordless ssh due to some permission issue, and since it happened right after installing the plugin I suspected it was the problem, just tested now on another server and it happened again, this was the error logged: Apr 20 18:27:30 Tower15 sshd[15259]: Authentication refused: bad ownership or modes for directory / Rebooting solves the problem it but it should be fixed in the plugin install, I can't really help with what's needed to fix it but @Squidshould be able to help you if needed.
  10. Apr 16 02:31:15 UnRAID kernel: md: disk4 write error, sector=5920974112 Apr 16 02:31:15 UnRAID kernel: md: disk3 read error, sector=5920976928 Apr 16 02:31:15 UnRAID kernel: md: disk0 read error, sector=5920976936 Multiple disk errors suggest a controller/power problem, since the controller is Intel I would start with power.
  11. See here first: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=972660
  12. Those are not correct, you can see them on the SMART report: Data Units Written: 114,252,166 [58.4 TB] and Data Units Written: 114,251,764 [58.4 TB]
  13. Please post the diagnostics: Tools -> Diagnostics
  14. No, but much more than the continuous writes reported by iotop would generate, check SSDs TBW then let it run for 24H without any downloading, then check again.
  15. Parity1 is still checked, and corrected if there are errors.
  16. ASM1166 is an Asmedia 6 port controller, and works fine with Unraid.
  17. Any continuous writes should be in there, at least they were for all users with that issue, including myself, do you do any downloading/unpacking to the cache pool?
  18. Not 100% valid. Disk is showing some SMART issues, but these errors look more like a connection problem, replace the cables/slot and try again.
  19. That's from 3 Hours? It shows a total of less than 2GiB. That's very little, something else must be doing most of the writing.
  20. https://forums.unraid.net/bug-reports/stable-releases/691-setting-warningcritical-temperature-in-smart-settings-not-possible-r1376/?do=findComment&comment=13795
  21. 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.
  22. JorgeB

    SAS SSD

    I use normal consumer SSDs for my small array, Samsung 860 EVO for data and a WD Black NVMe device for parity, most other users I've seen using SSDs also use consumer models. Cache device is always optional.
×
×
  • Create New...