Jump to content

JorgeB

Moderators
  • Posts

    67,871
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Nothing obvious but would really need the before to compare.
  2. Check filesystem on the emulated disk3.
  3. Added to the list, should work on the next release.
  4. Nope, that's a different issue. Difficult to say, one thing you can try is to boot the server in safe mode with all docker/VMs disable, 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.
  5. That's just to keep the assignments, select all then reassign the two unassigned disks and start the array to begin a parity sync.
  6. You could also use the 10GbE NIC just for direct connection between the server and the PC for data transfer, and use separate gigabit for internet access on both.
  7. First you need to be able to identify the drives, and probably will still need to rebuild them all, and there's no guarantee it will work until you try the first one.
  8. For array devices you'll only get a notification when Unraid tries to read or write to the disk and it can't.
  9. Boot with a different flash drive using a new stock Unraid install, no key needed, just to rule out any config issue.
  10. Device is dropping offline so that part is normal, question is why is it dropping with just a kernel change, since we know it's not a device problem I suspect some board compatibility/BIOS issue.
  11. The diags only show the HBA not being detected on a hardware level, like if it's not installed, not much we can do with that, try a different PCIe slot if available or try the HBA in a different computer to make sure it's working.
  12. Nothing wrong the I can see, are you sure the router is correctly configured? Make sure the connection is a simple as it can be to start, no firewall, etc, just the server connected directly to the router.
  13. Those are the minimum you need, it's the key and the array/pool assignments.
  14. You can create a new pool, just for testing, then set a coupe of shares to use the new pool as cache=yes.
  15. OK, in that you case there are basically to options, copy the bare minimum from the the backup (key file, super.dat and pools folder) and reconfigure the rest, or start by copying the minium and then add the other config files, one or a few at a time, until you find the problem.
  16. Oct 16 20:06:56 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Oct 16 20:06:56 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, upgrading to v6.10 or later and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  17. Connect the gbit NIC to a router, set it as eth0 and see if that one works.
  18. Do you have another client computer you could test with? If not you can even test with an Android phone.
  19. Highwater is the a compromise to use all disks (once the first one gets past half used), the other options are fill up which does the opposite and most free that like mentioned is the worst for performance, so not recommended.
  20. The kernel is a lot newer, look for a BIOS update for the board, it might help.
×
×
  • Create New...