Jump to content

JorgeB

Moderators
  • Posts

    61,730
  • Joined

  • Last visited

  • Days Won

    651

Everything posted by JorgeB

  1. If it keeps going up yes, you can run an extended SMART test for now.
  2. With all the config changes you've made the drive was wiped with wipefs, you can try running xfs_repair to see if it can recover from a backup superblock: xfs_repair -v /dev/sdf1 Note the one in the end
  3. Cache disk need to be replaced, the missing shares should come back one you remove that drive and reboot, then restore your appdata backup and re-create the docker image.
  4. Check the board internal connectors, it might still have some USB 2.0 ports, then you just get a header, e.g:
  5. You can by using at least one different NVMe device.
  6. btrfs, the only option for now for multiple device pools, can change raid levels online.
  7. Please don't post multiple times about the same thing, also this would be better posted in the Nvida plugin support thread.
  8. ASM1166 is a 6 port controller, the one you linked has 8 pots, suggesting it has a port multiplier and so not recommended. LSI is a safer bet since they are made by LSI (or Avago/Broadcom now), unless you get a fake one, these Asmedia and JMB controllers are different, the chips themselves are good but a no brand controller based on one might be good or not, when possible suggest buying from known brands, like Startech or Syba for example.
  9. That's a device problem, LT can add a "quirk" so that it works, I've already added it to the list, but it can only be added for a future release.
  10. Device is dropping offline, hence the btrfs errors, this can sometimes help, on the main GUI page click on the 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.
  11. Disk is dropping offline and reconnecting, swap slots with a different disk and see if the issue follows the disk.
  12. That's an USB device dropping offline, if it's the flash drive it's a problem, try a USB 2.0 port, if it's an unassigned external HDD it should not make Unraid crash.
  13. Upgrade should be pretty straight forward, but make a backup of current flash drive before doing it.
  14. There are multiple call traces, but no indication to me on what's causing them, could be hardware related, one thing you can try is to boot the server in safe mode with all docker/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.
  15. Only the cache NVMe device is being detected by Linux, this is not a software issue, try re-seating the other one or using a different PCIe slot.
  16. Enable the syslog server and post that after a crash.
  17. Recommend waiting for v6.12 and then use them in a raidz pool.
  18. That's a good option, also like the MX500, though they have a firmware issue with SMART, you need to disable monitoring the pending sector attribute or will get false results. You can but you'll need more than two to also have some redundancy, depends on the priorities.
  19. Enable the syslog server and post that after a crash.
  20. Enable the syslog server and post that after a crash.
×
×
  • Create New...