Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,386

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Not sure what you are asking exactly, for that purpose a COW filesystem works as any other, once a file is modified any user will only see the new version of that file, only if you have snaphosts (or reflinks) you can access previous versions.
  2. JorgeB
    Yes, until there are less than 2TB free, then it will start filling the other disks.
  3. JorgeB
    Rebuilding a disk won't fix filesystem corruption, you need to run xfs_repair without -n.
  4. JorgeB
    Post the output of xfs_repair.
  5. JorgeB
    Cache. You can use this.
  6. JorgeB
    Changed Status to Open Changed Priority to Other
  7. JorgeB
    This looks more like a general support issue and should be posted on the general support forum, and also please post the diagnostics: Tools -> Diagnostics
  8. JorgeB
    This looks more like a general support issue and should be posted on the general support forum, and also please post the diagnostics: Tools -> Diagnostics
  9. JorgeB
    That's far from normal, you should get 40/50MB/s with default writing mode and line speed with turbo write, post the diagnostics, might provide some clues.
  10. JorgeB
    This
  11. JorgeB
    I wouldn't say it happens more with SSDs, just that read/write errors with SSDs are most likely a connection problem, with HDDs sometimes there are actual bad sectors.
  12. JorgeB
    If you want to run a parity check run with no correct, but it will take a wile because of disk3, and it can even get disabled, I would probably wait until disk3 is replaced. You could also unassign disk3 and work with the emulated disk for now, with dual parity it still protects you if another disk fails before disk3 gets replaced.
  13. JorgeB
    Correct, it will work with any currently available capacity and for any larger disk coming in the few next years, at least.
  14. JorgeB
    Yes, will likely need crossflashing to LSI IT mode, unless it comes pre-flashed. It doesn't say anywhere if it's forward breakout or reverse breakout, they look the same and only forward breakout will work in this case. Yes, with the right cable.
  15. JorgeB
    Write errors to an SSD usually means it dropped offline, but without the syslog can never say for sure. Scrub only checks the data, it doesn't check files system consistency, you can leave it as is for now and see if it doesn't happen again, just make sure backups are current. You can also run btrfs check --readonly, but if errors are detected best to format instead of trying to fix them, btrfs fsck is still very fragile, and can even make things worse when trying to fix a corrupt file system.
  16. JorgeB
    Should be fine, a few sync errors are normal after an unclean shutdown, other than that every time there should be 0 errors, see how it goes for the next checks.
  17. JorgeB
    Cache file system is corrupt, best way forward is to backup, re-format, restore data.
  18. JorgeB
    You have the mover logging enable, and that's spamming the log, might be a good idea to disable it unless you need that enable.
  19. JorgeB
    We need new diags after a reboot then.
  20. JorgeB
    That's normal for high-water. https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water
  21. JorgeB
    Syslog rotated so we can't see the beginning, but those are likely remnants of previously used UD devices, reboot will clear the errors.
  22. JorgeB
    Still using my first two Unraid flash drives which just turned 12 yeas old.
  23. JorgeB
    You can then update to v6.8 final, just don't update to v6.9-rc until that issue is fixed.
  24. JorgeB
    Don't understand German but 1st one looks correct based on the pics.
  25. JorgeB
    Try redoing the flash drive first, it it keeps happening you likely need a new one.
×
×
  • Create New...