Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,674

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    All disks are failing to read sector 0, see if they have some kind of protection/encryption enable.
  2. JorgeB
    No
  3. JorgeB
    That basically confirms it was a hardware issue, since your cache is a single device errors can't be corrected, and they were detected before, see here to reset btrfs stats and to enable better monitoring so you are notified if more appear.
  4. JorgeB
    Unlikely, looks more like a hardware problem, and you still need to run a scrub on the pool, if there are any uncorrecteblr errors look for the file name(s) in the syslog and delete/restore them from backup.
  5. JorgeB
    Didn't notice before since I usually use a disk as destination, not an image, for an image you need to clone only the partition, as Linux will fail to read the partition table from a regular file, there might be a way of doing it by passing the partition offsets in the mount command, but can't help with that, alternatively clone to a disk or if cloning to an image again use /dev/sdX1 as source.
  6. JorgeB
    SMART reads happen after the disks spin up, but there are some known spin up issues with v6.9.2, try downgrading to v6.9.1
  7. JorgeB
    It's possible, you basically have to try different things involved one at a time until you find the culprit.
  8. JorgeB
    Sync errors are an unclean shutdown are expected.
  9. JorgeB
    Also good to replace/swap power cable just to rule that out.
  10. JorgeB
    If there are doubts reset disk stats and disable docker and VM services, leave it like that for a few hours or days enough to confirm that there are no reads on that disk, then enables services one by one and re-check.
  11. JorgeB
    Enable syslog mirror to flash then post that log after a crash.
  12. JorgeB
    Try again after rebooting in safe mode, a bad behaving plugin can cause that.
  13. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  14. JorgeB
    This only shows flash drive issues, Is this after the crash?
  15. JorgeB
    Also a good idea to run memtest, bad RAM is the number one reason for unexpected sync errors.
  16. JorgeB
    If it's an option use only SMB instead of NFS, to see if it's related to that.
  17. JorgeB
    Looks good, I would just add that when using the second option user should run a correcting parity check ASAP to correct the sync errors.
  18. JorgeB
    Didn't noticed, but yeah, IMHO it should men mentioned first as a way to keep parity 100% in sync, just in case a disk fails before it can be corrected if doing the other way.
  19. JorgeB
    That will make parity out of sync, maybe using UD and mounting the disks read-only could be added as an option.
  20. JorgeB
    Enable syslog mirror to flash then post that log after a crash.
  21. JorgeB
    Install the UD plugin and mount all the disks read-only, there should only be one disk that doesn't mount, that would be parity, if yes assign all the disks, data disk order doesn't matter with single parity, check "parity is already valid" and start the array.
  22. JorgeB
    There are multiple segfaults and btrfs is detecting data corruption, start by running memtest.
  23. JorgeB
    Enable syslog mirror to flash then post that log after a crash, together with the complete diagnostics: Tools -> Diagnostics
  24. JorgeB
    These come from an NTFS formatted unassigned disk/volume, run chkdsk on it.
  25. JorgeB
    That's good, everything should be fine.
×
×
  • Create New...