Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,884

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Please post the diagnostics.
  2. JorgeB
    Cache device dropped offline, this is usually a power/connection problem.
  3. JorgeB
    Check wat was left on cache, mover might not move everything for various reasons, enabling the mover logger and running the mover will usually show the reason.
  4. JorgeB
    It's not logged as a disk problem, and that usually means power/connection issue.
  5. JorgeB
    Do you mean it's not showing the errors in safe mode?
  6. JorgeB
    It's not expected, did you free up some space before converting? Strange, are you still on v6.11.1 or updated to v6.11.4?
  7. JorgeB
    If the container is mapped to /mnt/user it won't be a problem, if it's using /mnt/cache you need to adjust. It shouldn't make any difference. It will only work for the first array start if the array is also set to autostart.
  8. JorgeB
    Syslog is just after rebooting, regular syslog starts over after every reboot, thats why I mentioned enabling the persistent syslog.
  9. JorgeB
    You can make a btrfs pool with both devices by adding them to an Unraid pool and then UD will mount it, you can also have and automatic rsync script run on mount.
  10. JorgeB
    It's not logged as a disk problem, could be power/connection or spin up related, I would start by disabling spin down for that disk.
  11. JorgeB
    Start the array in normal mode and the format button will be next to the stop array button.
  12. JorgeB
    Wouldn't worry about those errors for now, likely harmless, as for the temp warnings you can adjust the temps for that device, SSDs can run hotter, especially during prolonged writes, mas temp is usually around 70C.
  13. JorgeB
    You'll need to consult the board manual or contact Gigabyte.
  14. JorgeB
    Look more like a Mac problem, do you see all the other folders or only the files? Try with a PC or Android device if available.
  15. JorgeB
    Then just reformat and see here for better pool monitoring, so you are warned if there are more issues.
  16. JorgeB
    You are having multiple apps crashing and btrfs is detecting data corruption there's also this: BTRFS error (device dm-3): block=3573797388288 write time tree block corruption detected Which usually means bad RAM, or other kernel memory corruption, start by running memtest.
  17. JorgeB
    Changed Status to Closed Changed Priority to Other
  18. JorgeB
    This is about the UD plugin, please use the existing support thread:
  19. JorgeB
    As you prefer, for some time now that macvaln can crash the server for some users, it usually happens every few days, and macvlan related call traces are usually logged before the server crashes, if you have no problems you can keep using it.
  20. JorgeB
    Start by running memtest.
  21. JorgeB
    You need a keyboard, if it's a wireless RF keyboard will without drivers.
  22. JorgeB
    Forgot to mention, there are macvlan call traces, these can make Unraid crash, switch to ipvlan.
  23. JorgeB
    Parity is not yet synced, let it sync first, only after that will turbo write work correctly.
  24. JorgeB
  25. JorgeB
    Boot using the GUI mode and change the docker network to macvlan, apply, reboot and see if that makes a difference, if it doesn't you can easily downgrade back to v6.11.3 by going to Tools -> Update OS -> Restore
×
×
  • Create New...