Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,589

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    That's a different issue, please post the diagnostics after upgrading to v6.9
  2. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below:
  3. JorgeB
    Don't forget the 1 in the end, e.g. /dev/sdk1
  4. JorgeB
  5. JorgeB
    No, free space is usually wrong with different size devices, or with an odd number of same size devices, this is a btrfs issue.
  6. JorgeB
    Not seeing any filesystem issues, except for the cache not mounting, also all disks show hight data usage, what was the share name and what disks was it using?
  7. JorgeB
    Used on main should be the correct one, dashboard is still using the old way which was usually wrong for raid1 with different device sizes, if you want post diags to confirm.
  8. JorgeB
    It's disabling disks for some users, so it can cause data loss.
  9. JorgeB
    Unfortunately nothing in the logs I can see about the crashes, this usually points more to a hardware problem, one thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  10. JorgeB
    That should work, try again after rebooting.
  11. JorgeB
    Yes, it started with the v6.9-rcs, likely due to a newer LSI driver.
  12. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  13. JorgeB
    There are knwon issues with LSI + 8TB Ironwolf (possibly other capacities also), one workaround is to use the onboard SATA ports for those, until there's a new LSI driver.
  14. JorgeB
    https://wiki.samba.org/index.php/Server-Side_Copy
  15. JorgeB
    Windows uses Samba server side copy, i.e., local copy doesn't use the network.
  16. JorgeB
    https://wiki.unraid.net/Cache_disk#The_Mover
  17. JorgeB
    Cache replacement is broken in v6.9, add/remove should be OK, but probably best to use v6.8 since it's known to be working there.
  18. JorgeB
    You can but only after balancing the pool to raid1.
  19. JorgeB
    That issue didn't affect the SAS2308 chip, and the other one is working, rather strange.
  20. JorgeB
    The linked FAQ entry has the command you need to use, used it several times myself, though like mentioned ddrescue isn't optimized for flash devices.
  21. JorgeB
    Cache drive is completely full, so the docker image is out of space, free up some space on cache, then re-start array.
  22. JorgeB
    Try this, if it doesn't work post the output: xfs_admin -U generate /dev/sdX1 Replace X with correct letter for the unassigned device.
  23. JorgeB
    Try booting in safe mode.
  24. JorgeB
    Remove the Dynamix sleep plugin.
  25. JorgeB
    Run the mover, shares must be set to cache=yes
×
×
  • Create New...