Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,475

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Not yet, v6.9 should be very similar to 6.8, my tests show very small differences (checks with single parity are a little slower faster, with dual parity a little faster slower) but those are very small differences +/- 5MB/s to 10MB/s and likely just because it's using a different kernel, but basically it will be the same, I would guess that understandably LT is looking at more important issues first, but do hope this will be eventually fixed. Edit: slower/faster corrected, it's the other way around
  2. JorgeB
    Also, regular Memtest can still be used if there's an option on the BIOS to disable ECC.
  3. JorgeB
    👍 You're welcome.
  4. JorgeB
    On top of tweak you can also try this, and see if there are further decrease, it's perfectly safe to use.
  5. JorgeB
    And looking at the data units written it was more like 332GB (considering the last stats you posted, though they were posted about 20H ago, so still around 400GB per day)
  6. JorgeB
    So that's still a good result, was close to 1TB a day before, correct?
  7. JorgeB
    Cache filesystem detected checksum errors, aka data corruption, this is usually cased by bad RAM, start by running memtest.
  8. JorgeB
    The use cache setting that controls the Mover can only be set to one pool, though a share can still exist on different pools, you'd need to use the disk shares directly or change the use cache setting before use to use the "pool" you want.
  9. JorgeB
    Yes. Every pool is an independent filesystem, and xfs "pools" can only be single device, if a share exists on different pools data will be merged together by shfs when accessing that share.
  10. JorgeB
    Best bet is to use the existing docker support thread:
  11. JorgeB
    It should, but it's not a capacity issue, there was a problem using some recent devices on that controller, it also affected some small SSDs, please test and report back.
  12. JorgeB
    This.
  13. JorgeB
    Try swapping both cables with another disk, if still not detected it might be dead.
  14. JorgeB
    Did you see this thread? Unfortunately there's not a one-size-fits-all fix for this issue, but there are several things you can try there.
  15. JorgeB
    Cache filesystem is corrupt, best bet it to backup, re-format and restore the data, this post might help if needed.
  16. JorgeB
    Nothing jumps out, most likely it's related to the earlier parity swap, for some yet unknown reason some users then have sync errors in the extra parity section, run a correcting check, then a non correcting one, as long as no more errors are detected you should be fine.
  17. JorgeB
    Just the SATA cable.
  18. JorgeB
    Possibly, if you post the diagnostics.
  19. JorgeB
    Unraid can't protect against filesystem corruption, if corruption keeps happening always on the same disk it might be a good idea to re-format and create a new filesystem, but you'd need to backup all data there first, if corruption is happening on multiple disks without an apparent reason there's likely some hardware problem, like bad RAM, controller, etc.
  20. JorgeB
    raid1c3/c4 will only work on the v.6.9 betas.
  21. JorgeB
    You can try this.
  22. JorgeB
    Lots of UDMA_CRC errors, replace the SATA cable and rebuild on top, assuming the emulated disk shows the correct data.
  23. JorgeB
    Disk looks OK but it's not good that it can't complete a SMART test, if it's in warranty replace it, if not run a parity check or preclear read test to see if there are any read errors.
  24. JorgeB
    There's no risk trying to mount the emulated disk, and whatever is there is what there will be on the rebuilt disk, parity was already updated during the filesystem check to reflect that.
  25. JorgeB
    This means you have more connected devices than your license allows.
×
×
  • Create New...