JorgeB

Moderators
 View Profile  See their activity

  • Posts

    61553

  • Joined

  • Last visited

  • Days Won

    649

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Unfortunately there's nothing relevant logged, I do see some errors related to a CD/DVD drive, but those should not cause the server to crash, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, 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.
  2. JorgeB
    Btrfs is detecting new data corruption, since memtest is only definitive if it finds errors, and since you have multiple sticks, fix the corrupt files and reset the stats and and try with just one stick of RAM, if the same try with a different one, that will basically rule out bad RAM.
  3. JorgeB
    Looks OK for now, no more ATA errors.
  4. JorgeB
    I thought it was only one of them, in that case much less likely that a disk is the problem, but don't really have other ideas, there's nothing out of the ordinary logged in the syslog, very strange issue.
  5. JorgeB
    If you mean the disk remaining disabled that is expected, SMART looks OK, re-sync parity.
  6. JorgeB
    If the server is restarting on its own, vs. crashing or hanging, that's almost always a hardware problem, but could be caused by different things, like PSU, RAM, board, etc.
  7. JorgeB
    Check filesystem on disk4, run it without -n, and if it asks for it, use -L.
  8. JorgeB
    You can click on the thumbs down to acknowledge the current errors, it will change again if new ones come up.
  9. JorgeB
    That looks more like a disk issue.
  10. JorgeB
    Apr 22 00:57:28 chewbacca kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Apr 22 00:57:28 chewbacca kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually 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)), then reboot.
  11. JorgeB
    Try rebooting and attempt another rebuild, may be a good idea to replace the cables for ATA14 first.
  12. JorgeB
    Enable the syslog server and post that after a crash together with fresh diagnostics.
  13. JorgeB
    Could be this issue:
  14. JorgeB
    Please post the diagnostics.
  15. JorgeB
    Syslog-previous only includes a couple of minutes up time, was the server already crashed? The errors above look more like a HBA issue, make sure it's well seated and sufficiently cooled, you can also try a different PCIe slot.
  16. JorgeB
    Sorry, that should have been -h. The last diags are working, though the syslog is being spammed with syslog server errors, fix that to avoid more spam in the future, then reboot to clear the logs and post new diags if you still have issues.
  17. JorgeB
    Please post the diagnostics.
  18. JorgeB
    Not really at the moment, but once we get to kernel 6.9, FUSE passthrough mode should be available, that's expected to increase performance by a lot, similar to native.
  19. JorgeB
    Constant ATA errors with both disks, looks more like a power/connection issue, replace cables and post new diags.
  20. JorgeB
    You can format the pool using the GUI, change the filesystem to a different one and you can then format, of course you need to backup the pool first.
  21. JorgeB
    I don't think that will make any difference, the HBA is working fine, also no issues with the HBA to enclosure connection, so I think the problem can only be the enclosure, or how the disks are connected there, i.e., if it needs some specific config.
  22. JorgeB
    That's a perfectly valid setup.
  23. JorgeB
    If you have data that needs to be moved you can use this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923
  24. JorgeB
    Still not seeing anything, does it still happen if you leave the Docker service disabled?
  25. JorgeB
    You need to contact support.