Jump to content

JorgeB

Moderators
  • Posts

    67,485
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. There was a recent change on how free space is reported with btrfs, unfortunately it doesn't appear to work correctly for a 3 device raid1 pool, I wonder if df reports correctly, please post the output of: df -hH | grep cache
  2. Diags are after rebooting so we can't see what happened but SMART looks fine, most likely not a disk problem, you can replace/swap cables to rule them out in case it happens again.
  3. Since the extended SMART test passed drive is OK for now.
  4. You have filesystem corruption on disk1, you need to check filesystem and since that was spamming the logs it's difficult to look for other issues, post new diags after fixing that when the issue re-occurs.
  5. Those messages end up filling the syslog. If by external you mean USB disks we don't recommend those used for pools/array devices, but it's not necessarily a problem, impossible to say if there are issues with this without the diags, ones posted just have the NFS spam.
  6. du is not reliable with btrfs, GUI will show the correct used/free space (with equal size devices), if you have Windows VMs this should help to recover some space.
  7. Sorry, no, but if you search the forum you should find some recommendations.
  8. So many errors could be explained for example by writing to the emulated disk once it got disabled before doing the new config, there could be other explanations, but again would need the previous diags,
  9. Whatever name you choose for the pool, pool name cache will still be at /mnt/cache, pool named newpool will be at /mnt/newpool
  10. That alone doesn't explain 500K sync errors, a few errors yes, but not that much, something is missing.
  11. Sop this wasn't correct: And again:
  12. Best bet is to backup any cache data, re-format and restore the data.
  13. Would need the diags to confirm but based on the screenshot the disk is likely being detected with a small capacity difference, and if that's the case this would be a controller issue.
  14. These errors sometimes happen with some hardware, no one knows exactly why, unfortunately can't suggest anything other than trying different flash drives and/or a different board.
  15. The SAS expander shouldn't cause this, as it's a model widely used with Unraid, including by myself, though it could be the expander + those specific disks.
  16. Impossible to know without the previous diags showing everything what happened before the check, you did do a new config, so some (or a lot) of sync errors can happen, depending on the array status before.
  17. Log is completely spammed with errors from an external 4TB disk, can't see anything else, disconnect that disk, reboot and post new diags if/when there are more issues. That is the docker image.
  18. Unfortunately there's nothing in the log that gives a clue about the crash, it could be a hardware issue.
×
×
  • Create New...