Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


johnnie.black last won the day on December 6

johnnie.black had the most liked content!

Community Reputation

2137 Hero

About johnnie.black

  • Rank
    ti-ti jorge


  • Gender

Recent Profile Visitors

6139 profile views
  1. Check filesystem on disk2: https://wiki.unraid.net/Check_Disk_Filesystems Full log is the result of the filesystem corruption.
  2. Yep, that's the one used by the 9300-8i and similar HBAs. The Intel ports on the Asus should be rock solid, unless the board has a problem, even the Asmedia ports usually work without any issues, Marvell controllers on the other hand you should stay away from.
  3. Yes. Would be fine, but you could also use the onboard ports for all SSDs.
  4. Format again, it still the same grab and post new diags.
  5. That issue should be gone with v6.8, it's about to go final, though rcs are perfectly safe to use.
  6. Ohh, I missed this, format is never part of a rebuild, it deletes all data on the disk and updates parity. The correct way to fix your problem would be to check filesystem, not rebuild. Now, only option is to restore from backup or use a file recovery util like UFS explorer.
  7. Disk looks fine, just check file system.
  8. Check file system on disk6 https://wiki.unraid.net/Check_Disk_Filesystems Next time please post complete diags (tools -> diagnostics)
  9. Yes, you can also use the onboard SATA ports for any SSD, LSI SAS3 models, like the 9300-8i support trim, but only on the devices with determinist trim, you can check with: OK for LSI hdparm -I /dev/sdc | grep TRIM * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM Not OK for LSI hdparm -I /dev/sdb | grep TRIM * Data Set Management TRIM supported (limit 8 blocks)
  10. There's a known issue with LSI SAS2 models and trim with latest firmwares (>p16), the only strange thing here is that trim it is working on the cache devices, more so since it should never work on the 850 EVO as LSI requires deterministic read zeros after trim for trim to work, 860 EVO would be OK, maybe the mixed pool is confusing it?
  11. Disk3 is failing, but like mentioned if you can get disk2 back it will allow you to replace disk3, try connecting disk2 using different cables, swap with disk3 for example, both power and SATA cables.
  12. SMART test failed = failed disk, you should replace it.
  13. Ryzen on Linux can lock up due to issues with c-states, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), or completely disable C-sates. More info here: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/
  14. Disks won't mount in maintenance mode.