JorgeB

Moderators
 View Profile  See their activity

  • Posts

    61539

  • Joined

  • Last visited

  • Days Won

    648

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It's also logged in the syslog as a disk problem, though the UNC @ LBA 0 doesn't make much sense, I would run an extended test on the disk.
  2. JorgeB
    Memtest is only definitive if it finds errors, if you have multiple sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.
  3. JorgeB
    Please post the complete diagnostics.
  4. JorgeB
    Parity will not be accessed for any array reads, it will be access during a parity check or any array writes.
  5. JorgeB
    Don't really think so, controller is using the stock AHCI driver, I guess it could be a controller/board problem.
  6. JorgeB
    Server rebooting on its own, vs. crashing/hanging, is almost always a hardware problem, but it can be caused by different things, like PSU, RAM, board, etc.
  7. JorgeB
    It can start happening by just using a different Unraid release, or the same release with different hardware, several users had that issue come up after a change.
  8. JorgeB
    Yep.
  9. JorgeB
    Those should be OK, looks like result of macOS, but there is a problem with the flash drive: Apr 21 14:36:50 Tower emhttpd: Unregistered Flash device error (ENOFLASH4). There were similar reports before that were fixed by plying with the USB settings in the board BIOS, IIRC last one was fixed after enabling USB power delivery in S5 State, or something similar.
  10. JorgeB
    I would replace/swap the cables, if not done yet, but for now don't see a reason to suspect a device problem.
  11. JorgeB
    If you have multiple RAM sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.
  12. 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.
  13. 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.
  14. JorgeB
    Looks OK for now, no more ATA errors.
  15. 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.
  16. JorgeB
    If you mean the disk remaining disabled that is expected, SMART looks OK, re-sync parity.
  17. 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.
  18. JorgeB
    Check filesystem on disk4, run it without -n, and if it asks for it, use -L.
  19. JorgeB
    You can click on the thumbs down to acknowledge the current errors, it will change again if new ones come up.
  20. JorgeB
    That looks more like a disk issue.
  21. 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.
  22. JorgeB
    Try rebooting and attempt another rebuild, may be a good idea to replace the cables for ATA14 first.
  23. JorgeB
    Enable the syslog server and post that after a crash together with fresh diagnostics.
  24. JorgeB
    Could be this issue:
  25. JorgeB
    Please post the diagnostics.