Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,572

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    An ad-don controller in one of the PCie slots that looks like this:
  2. JorgeB
    Always best to start a new one, but since we're here, the problem was the controller: Feb 11 06:55:01 Babs kernel: ahci 0000:01:00.0: AHCI controller unavailable! All connected disks become unavailable, Unraid disables the first one to error on write (with single parity), the other will have read errors. That is a Marvell controller, and we don't recommend those, though not necessarily related to the current issue, try re-seating the controller, power back on and post new diags, note that the disable disk will remain disable.
  3. JorgeB
    No, it means parity got disable first, and then during the sync disk1 also got disable.
  4. JorgeB
    Hopefully yes.
  5. JorgeB
    You can, but your parity is invalid: [name] => parity [device] => sdb [id] => WDC_WD120EMAZ-11BLFA0_8CJX0N9F [size] => 11718885324 [status] => DISK_INVALID There should be a yellow icon next to it.
  6. JorgeB
    Yes.
  7. JorgeB
    I know that, that what I was saying, and if you want to get SMART reports
  8. JorgeB
    There are two invalid disks (parity and disk1), so disk1 can't be correctly emulated, disk itself looks OK, so if you do a new config with all existing disks and re-sync parity all data should come up fine, if it doesn't please post new diags.
  9. JorgeB
    No, they are connected to the HP P420i RAID controller, or you posted the wrong diags.
  10. JorgeB
    Feb 11 09:39:30 UNRAID1 shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed. https://forums.unraid.net/topic/102568-transport-endpoint-is-not-connected-with-mntuser/?do=findComment&comment=946178
  11. JorgeB
    That's still low, still some network issue.
  12. JorgeB
    Try another PCIe NIC if available.
  13. JorgeB
    Ahh.
  14. JorgeB
    Strange, if it mounted with UD it should mount in the array
  15. JorgeB
    That confirms it's a network problem, try different source PC, NICs, switch, cables, etc.
  16. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  17. JorgeB
    Yes.
  18. JorgeB
    Filesystem on the emulated disk is corrupt, best bet is to resync parity with all the original drives.
  19. JorgeB
    Start by doing a single stream iperf test.
  20. JorgeB
    You can boot using GUI mode to reconfigure the LAN, or delete/rename network.cfg and network-rules.cfg both on the config folder then reboot to go back to default settings.
  21. JorgeB
    If it happens again you can enable the syslog server to see if it catches something.
  22. JorgeB
    Well, all the drives are still connected there, so not disabled.
  23. JorgeB
    It's a known issue, though root cause has been somewhat elusive, usually something manipulating files directly on /mnt/user, for some user(s) it was a plugin, but most common are probably dockers, that unpack, move or delete files.
  24. JorgeB
    Diags are after a reboot, if it happens again grab them before.
  25. JorgeB
    Yes, but last boot was: Feb 10 12:06:10 Tower kernel: Linux version 4.19.107-Unraid (root@Develop) (gcc version 9.2.0 (GCC)) #1 SMP Thu Mar 5 13:55:57 PST 2020 So if this is correct: It means it rebooted, possibly a crash or hardware issue.
×
×
  • Create New...