Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,504

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Try booting in safe mode.
  2. JorgeB
    No idea, maybe something visible if you post the diags. For that you'd need to ask for help on the Dynamix File Integrity plugin support thread.
  3. JorgeB
    Parity can't help with filesystem corruption, according to your diags discs 12 and 13 weren't mounting, but they are now, likely the result of running xfs_repair.
  4. JorgeB
    Check the disk's SMART report, like mentioned and unless the correct lifetime is reported there on the SMART self-test history section it's a disk issue.
  5. JorgeB
    Changed Status to Closed Changed Priority to Other
  6. JorgeB
    Disk looks healthy and it passed the extended test, so it should be fine.
  7. JorgeB
    Please user the existing docker support thread:
  8. JorgeB
    It still looks like a cable problem, but try another device if available. You should also update the LSI firmware.
  9. JorgeB
    Btrfs is very sensitive to memory issues, you are overclocking your RAM and that's known to corrupt data with some Ryzen systems, see here, for your current config you should set the RAM speed @ 2666Mhz max, also good to run memtest.
  10. JorgeB
    Since the diags are after rebooting we can't see what happened but parity looks fine, replace/swap cables to rule them out and re-sync parity. Cache filesystem is corrupt, you need to re-format, if there's important data there see here for some recovery options.
  11. JorgeB
    Please post the complete SMART report, of better yet, the diagnostics.
  12. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address:
  13. JorgeB
    Syslog start over after every reboot.
  14. JorgeB
    You can run an extended SMART test.
  15. JorgeB
    We need the diags after the problem happens but before rebooting.
  16. JorgeB
    First thing to do is to upgrade to beta25, if the issue persists post new diags before rebooting.
  17. JorgeB
    Most likely best bet.
  18. JorgeB
    Yes, you can still try btrfs restore. Rebuild is corrupt, no doubt about that, just by how much, but note that the disk was already unmountable before the read errors on parity, so parity wasn't already 100% valid, possibly due to previous errors.
  19. JorgeB
    Shares are using high-water, since disk 1 is larger Unraid will only start writing to other disks once you pass the 3TB mark, more info on high-water here: https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water
  20. JorgeB
    Yep, like mentioned Unraid doesn't do anything special to the flash drive.
  21. JorgeB
    Then you need to check/clean the cooler.
  22. JorgeB
    Yes, though btrfs is not as forgiving, but there are some recovery options here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490 On the plus side, if you can get it to mount you can know whitch files are corrupt by doing a scrub, you can also try btrrfs rescue (also on the link) but that won't check for corruption.
  23. JorgeB
    I did, many times.
  24. JorgeB
    It does, but any read read error on another device during a rebuild will result in a corrupt rebuilt disk, you an still tun xfs_repair on the disk, depending of where and how much corruption there is it might still have some (most) data.
  25. JorgeB
    LSI HBA is the best option, other than Intel SATA ports.
×
×
  • Create New...