Jump to content

JorgeB

Moderators
  • Posts

    67,871
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Unraid is not RAID, data is not stripped between the disks, there's a most free allocation option but that one is the worse for performance since parity writes will overlap, you can use pools for faster performance if suitable for your use case.
  2. Sorry, missed that part, if that doesn't help could be a board/BIOS/kernel issue, I use the same device with v6.11.1 without any issues, and didn't need to disable the low power options.
  3. Don't see how that is possible but if it happens again grab the diags.
  4. Like mentioned by the kernel try adding that to syslinux.cfg, on the main GUI page click on flash drive, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 pcie_aspm=off e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 pcie_aspm=off Reboot and see if it makes a difference.
  5. Yes, I misread the config, looks like you have a vlan, suggest renaming network.cfg to go back to defaults just to test if makes any difference.
  6. Remove the gateway from eth1, also eth0 should be you main NIC, does the 10GbE NIC have internet access?
  7. This is not easy to diagnose based on the diags, best bet is to disable all the services and then start enabling them one by one to see if you can find the culprit, more RAM might also help.
  8. That doesn't look very good but the only option is to run it again without -n to repair the filesystem.
  9. If you've used a new flash drive first try the original with a new install to confirm it's not a flash problem.
  10. Try with a different flash drive with a new stock install, no key needed, just to see if it boots.
  11. Note that virtualizing Unraid is not supported and if you are going to do that you should at least pass-trough a controller with all the devices, but for now check filesystem on disk1.
  12. AFAIK not directly, but rename one of them from *.key to*.bak then go to Tools -> Registration, if it's still registered you've renamed the correct one, if not swap.
  13. Unfortunately there's nothing relevant logged, this usually points to a hardware problem, if you haven't yet run memtest.
  14. It's still trying to remove the device and it's stuck, AFAIK there's no option to cancel that, since the pool is accessible make sure backups are up to date and then reboot by typing "reboot" in the console, if it reboots post new diags after array start.
  15. You'll still need to run reserfsck to rebuild the superblock then scan the filesystem.
  16. Log is spammed with Nvidia related issues but looks like the btrfs balance is stuck, and there still a device missing, type in the console: btrfs dev del missing /mnt/cache and post the output
  17. If you mean the console froze enable the syslog server and post that after array start.
  18. Those look OK, can you write if you change the share to public?
×
×
  • Create New...