Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,662

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    If it's still doing that with the latest firmware it's a strong possibility
  2. JorgeB
    Try this: https://forums.unraid.net/topic/76066-vm-settings-change-stuck-at-updating/?do=findComment&comment=705420
  3. JorgeB
    Cache pool is detecting data corruption, that and all those segfaults suggest a hardware issue, start by running memtest.
  4. JorgeB
    Try booting is safe mode, a plugin can cause this.
  5. JorgeB
    This is how cache works with Unraid: https://wiki.unraid.net/Cache_disk
  6. JorgeB
    Copy libvirt.img from the old cache and replace current one (VM service must be disable), obviously also copy the vdisks.
  7. JorgeB
    See if this applies to you: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  8. JorgeB
    Looks like you're passing thought the USB controller where the Unraid flash drive is, and Unraid loses access to it.
  9. JorgeB
    You can bypass the i/o error by using btrfs restore or copying from an user share to another, but it will still be corrupt.
  10. JorgeB
    This suggests a hardware problem, like bad RAM, diagnostics might give more clues.
  11. JorgeB
    With the array stopped on main click on "Add pool".
  12. JorgeB
    Best bet is to post in one of the existing Wireguard support threads.
  13. JorgeB
    Also du isn't reliable with btrfs, df will report correct used/free space for that pool, GUI will report correct free space, since devices are not of the same size.
  14. JorgeB
    It's not, generally RAID controllers don't expose the full disk capacity, they can reserve a few bytes, then Unraid will complain that the partition isn't using the full disk, solution it to rebuild one disk at a time so the new partitions can be recreated (or format them and restore data from backups):
  15. JorgeB
    Still the best place to get help with that.
  16. JorgeB
    Cache is almost full, GUI is correct, you can go to each share, click on "calculate" to see what's using the space.
  17. JorgeB
    This issue is reportedly fixed for next release.
  18. JorgeB
    diagnostics.zip
  19. JorgeB
    Please use the existing docker(s) support thread:
  20. JorgeB
    Nothing should change with a single device cache, it will if using multiple devices of different capacity, since that was wrong before, you should post the diags: Tools -> Diagnostics
  21. JorgeB
    Please post the diags: Tools -> Diagnostics
  22. JorgeB
    Already wrote above, you can enable turbo write for faster transfers to the array, at the expense of all disks spinning up, for smaller transfers, you can enable cache for that share so that data goes to the SSD first, then it's moved to the array by the mover.
  23. JorgeB
    You'll never get anywhere close to 10GbE transferring to the array, you can double or tripe current speed if you enable turbo write, even more than that if you enable cache for that share, but still not 1GB/s with a SATA SSD.
  24. JorgeB
    Do you use CA backup? I believe sometimes it can fail to turn them on after a backup.
  25. JorgeB
    It's normal not mounting with UD because of the same reason, If you want to make sure all is well before wiping parity just disconnect parity from the server and after booting disk1 should now mount.
×
×
  • Create New...