Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,681

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    If there was only one data disk parity1 will have the same data, you should be able to mount it in a new array (after a new config) or using UD, note that if the other disk was just formatted it can't be mounted at the same time due to having the same UUID.
  2. JorgeB
    Nothing jumps out regarding the hardware used, see if the mirrored syslog catches anything after a crash.
  3. JorgeB
    That will happen if you do this: Formatting is never part of rebuilding a disk, there's a big warning about that. There are none on the diags posted.
  4. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  5. JorgeB
    There's nothing logged about the crash, this usually points to a hardware issue, start by checking that power supply idle control is correctly set, having 3 DIMMs while supported is not ideal, you can also try just two to see if it makes any difference. P.S. General support forum would be a better place for this.
  6. JorgeB
    Sometime removing the BIOS from the HBA also helps, it's not needed for Unraid.
  7. JorgeB
    https://forums.unraid.net/bug-reports/stable-releases/solved690-691-692-netapp-pmc-sierra-pm8003-rev5-and-adaptec-6805h-hba-controller-didnt-find-the-hdds-r1300/?do=getNewComment&d=2&id=1300
  8. JorgeB
    Usually yes.
  9. JorgeB
    Should be fine.
  10. JorgeB
    Please use the existing docker support thread:
  11. JorgeB
    Yes
  12. JorgeB
    No point, disk is failing and needs to be replaced.
  13. JorgeB
    They were already disabled in this last boot, this means it happened before.
  14. JorgeB
    Try disabling Bluetooth in the BIOS.
  15. JorgeB
    Parity disk need to be replaced, disk5 is also showing some issues, see if it survives the parity sync.
  16. JorgeB
    Still a lot of network related crashes, if you haven't yet try this: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/?do=findComment&comment=14530
  17. JorgeB
    No, you should re-format.
  18. JorgeB
    Diags you posted look normal, I assume they were taken after a restore, post new ones after the problem.
  19. JorgeB
    Those are the Unraid driver errors, they come after the hardware issue, and they will always look similar, the important part is before that.
  20. JorgeB
    I can only speak for this one, but yes, if healthy disks keep dropping it's most likely a connection/power problem.
  21. JorgeB
    Disk dropped offline, this is usually a connection/power problem, but since it's offline there's no SMART report to check.
  22. JorgeB
    Rebooting should bring the shares online.
  23. JorgeB
    Drive looks fine, could still be hardware related, like a RAM or similar issue, not bad idea to run at least one pass of memtest.
  24. JorgeB
    Depends on the controller, if it's onboard SATA/AHCI this usually indicates a disk problem:
  25. JorgeB
    See below for some recovery options: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
×
×
  • Create New...