Jump to content

JorgeB

Moderators
  • Posts

    67,589
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Try this then post that log after a crash.
  2. No valid btrfs filesystem is being detected on the cache device, assuming you are sure the filesystem was btrfs it was wiped or similar, best to restore from backups.
  3. Run an extended SMART test on all, parity check is also a good test once parity is valid.
  4. Then and assuming the emulated disk is mounting correctly you can rebuild on top, keep monitoring the disk, especially this one: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 187 Reported_Uncorrect -O--CK 098 098 000 - 2
  5. Diags are after rebooting, but the disk looks fine, likely a connection/power problem. Those are normal for Seagate drives.
  6. Yes, just re-create like explained in the link.
  7. Please post the diagnostics: Tools -> Diagnostics (after array is started)
  8. Try redoing the flash drive, backup current flash, redo it using the USB tool, restore the config folder from the backup.
  9. Yes, but the spin down errors are likely unrelated to the crashing, but it will at least stop spamming the log.
  10. Should be. If you only have issues after spin up it should work.
  11. Start by removing the Dynamix sleep plugin, if that doesn't help try booting in safe mode.
  12. Parity can't reliably rebuild any disk since there were errors during the sync, disk5 appears to be failing, there's no SMART report for disk9 in the disgs posted, please post one.
  13. There appear to be some issues since v6.9-rc with the LSI driver and 8TB Ironwolfs, possible different capacities also, not sure if it's any different with v6.9 final, but likely not.
  14. You can use the existing plugin support tread, see a couple of posts above.
  15. You can use rsync over SSH, enable turbo write in Unraid and make sure to bypass cache if there's one.
  16. Doesn't look like a disk problem, I would start by updating LSI firmware to latest.
  17. Parity isn't 100% valid because of the errors, you should remove those disks and re-sync parity.
  18. Did you have 1 or 2 parity drives?
  19. This would be the first thing to try.
  20. Please post the diagnostics: Tools -> Diagnostics
  21. If you're using SAS disks disable spin down to get rid of those errors.
  22. Try getting the diags on the console by typing "diagnostics"
  23. There's no syslog in your diags, try again or post just the syslog.
×
×
  • Create New...