Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,540

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Maybe a firmware glitch? It should never go up.
  2. JorgeB
    Though most likely you have another issue, but since I don't see errors on the syslog don't know what it is.
  3. JorgeB
    Disk shares are still Samba shares, but bypass FUSE, so worth trying.
  4. JorgeB
    Settings -> Global Share Settings -> Enable disk shares Then transfer to a disk share, e.g. \\tower\cache or \\tower\disk1
  5. JorgeB
    You can compare files between the disks, though if there are any read errors on the old disk you won't be able to compare those. Yes, some data on disk3 might be corrupt but parity would be valid.
  6. JorgeB
    Yep, some corruption is expected, unless by luck the failed blocks did not contain any data on the rebuilt disk. Disk is failing and needs to be replaced.
  7. JorgeB
    Looks like a disk problem, run an extended SMART test on parity.
  8. JorgeB
    Don't see any issues in the log, does it happen it any transfer, array or cache? What if you use a disk share?
  9. JorgeB
    Please post the diagnostics (after a transfer attempt): Tools -> Diagnostcis
  10. JorgeB
    New alignment will also help, but that needs v6.9*, these were my results: https://forums.unraid.net/bug-reports/stable-releases/683-docker-image-huge-amount-of-unnecessary-writes-on-cache-r733/?do=findComment&comment=10142 * I found out recently that pools (and only pools) with the new alignment still mount correctly in previous versions, but it's unsupported, i.e., use at own risk.
  11. JorgeB
    https://forums.unraid.net/bug-reports/stable-releases/683-docker-image-huge-amount-of-unnecessary-writes-on-cache-r733/?do=findComment&comment=9579
  12. JorgeB
    You can remount the pool with space_cache=v2, it should reduce writes by a lot, but to take advantage of all the mitigations you'd need to update to 6.9
  13. JorgeB
    In the syslog, though I should have said continuous blocks, parity is checked on a standard 4k Linux block, each block has 8 sectors (for standard 512E drives), so when the errors error are logged for every 8th sector, they are on continuous blocks.
  14. JorgeB
    Try this and post that log after a crash.
  15. JorgeB
    Parity sync will only read the data disks, it can't be the reason for any missing files.
  16. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  17. JorgeB
    Not going to help with the helium level, if it keeps dropping the disk is going to stop working.
  18. JorgeB
    Backup and then recreate the flash drive.
  19. JorgeB
    No valid btrfs filesystem is being detected, was that the filesystem in use for the cache device?
  20. JorgeB
    It's not disabling it, it's being passed-through, adding/removing new hardware can make the hardware IDs change, so if for example you were passing-through a GPU you can now be doing it to the NIC.
  21. JorgeB
    Changed Status to Closed Changed Priority to Other
  22. JorgeB
    It's qemu-img resize --shrink
  23. JorgeB
    https://unraid.net/blog/top-support-and-forum-questions-answered
  24. JorgeB
    Try recreating the docker image, then restore all the apps, assuming you still have the original appdata.
  25. JorgeB
    NIC is being passed-through/bound to a VM.
×
×
  • Create New...