Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,871

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Reboot first, then run blkdiscard on the device: blkdiscard -f /dev/nvme#n1 And try again
  2. JorgeB
    Don't think probably just a failing disk.
  3. JorgeB
    Looks more like a power/connection problem, check/replace cables on disk5.
  4. JorgeB
    I meant the parity sync, it cannot be completed successfully with all the errors on disk10, any errors are skipped.
  5. JorgeB
    Which share?
  6. JorgeB
    And that is correct and the first step, then you'd need to upgrade disk1 to a larger one.
  7. JorgeB
    Please post the diagnostics.
  8. JorgeB
    Yes.
  9. JorgeB
  10. JorgeB
    Is this some kind of USB enclosure? I see issues detecting some USB disks, nothing much you can do on the Unraid side, try connecting the disks to a different USB controller or using a different bridge/enclosure, or better yet don't use USB and connect them to a SATA controller.
  11. JorgeB
    Don't think so, and if you are not using custom IPs you can still change to ipvlan.
  12. JorgeB
    If there are macvlan crashes something is still using it, and like mentioned they will end up crashing the server.
  13. JorgeB
    Strange that the permanent syslog didn't show this but the current syslog does: Oct 20 00:43:49 server kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Oct 20 00:43:49 server kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] But that's good news since Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  14. JorgeB
    6.11.1 fixed that issue for some but not for everyone, hopefully it it be fixed for all in the next release, but in case it's not that try a different browser and make sure there ar no ad blockers or a firewall blocking the GUI.
  15. JorgeB
    Oct 17 04:45:37 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Oct 17 04:45:37 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, upgrading to v6.10 or later and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  16. JorgeB
    Please do it on a new thread, if not it gets confusing.
  17. JorgeB
    Parity swap will use the old parity for the disabled disk, but that won't work in this case since it will be the same size as the previous one, you'd need to then rebuild again to a new larger disk.
  18. JorgeB
    Did you try manually creating the flash drive? https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method
  19. JorgeB
    Nothing relevant logged, please post the diagnostics mostly to see the hardware used.
  20. JorgeB
    750W should be enough, assuming the PSU is OK and decent quality, syslog should save the log wherever you configured it to, but enable the syslog mirror to flash option, that will save it to the logs folder.
  21. JorgeB
    Yes, it's a bug, if you click on "shares" you also see the old pool in the name, but if you click on a specific share you see the new pool in the drop down, it is a corner case but I will report it to see if it's fixed when possible.
  22. JorgeB
    Did you try booting without the GUI mode and then accessing the webGUI?
  23. JorgeB
    That suggests a hardware problem, PSU or board would be the main suspects.
  24. JorgeB
    Both cache devices dropped offline, one at a time, replace cables and run a scrub, see here for more info.
  25. JorgeB
    There's no cache assigned, was there supposed to be one?
×
×
  • Create New...