Jump to content

JorgeB

Moderators
  • Posts

    67,760
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. I've been asking for better pool error reporting for over 5 years, but LT decides which features/fixes are more important, for the last few years they seem to prioritize VM and Docker related issues, leaving array/pool issues for later, which IMHO is a shame.
  2. There are some recovery options here, might be worth updating to v6.10-rc and try the rescue=all options as mentioned in the link above if the options for v6.9.2 don't work.
  3. Logs is spammed with Bluetooth related errors, look for a BIOS update for the board, the below also helps sometimes. Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.
  4. Please post the diagnostics to see the complete error.
  5. See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: 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/
  6. According to the listing it comes with both, and usually when there's only one included it's the standard profile bracket as shown in the photos.
  7. This is supposedly getting fix for next release.
  8. First upgrade parity, when that's done upgrade disk2.
  9. Known issue, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582
  10. AFAIK there are no limits, but this would be a better question to post in the UD plugin support thread:
  11. Flash drive dropped offline, make sure it's using a USB 2.0 port, if it keeps dropping try a different one.
  12. Looks like a device problem, it's not even giving a complete SMART report.
  13. Yes, you can enable the syslog server, but before that check this.
  14. Some time ago there was some logic implemented where it wasn't possible to change the number of pool slots after making any change to a pool, like after unassigning one of the devices, this still worked correctly with v6.10-rc1 but it doesn't with rc2 or newer, this can easily cause problems with the pool after some changes, just like recently a couple of users posted in the forums, example: Start with a two device cache pool in default raid1, user decided to split the devices for use in two pools, with the array stopped: -unassign one of the pool devices -change that pool to just 1 slot -leave the removed device unassigned or assign it to a new pool and start the array, device won't be deleted from the original pool, so if left unassigned it will still be part of the pool despite of what the GUI shows, if assigned to a new pool there will only be one filesystem of the two devices showing in duplicat in both pools. In previous release after unassigning one device user can't change the number of slots, so after starting the array, with the removed device unassigned or assigned it will be deleted from the original pool making it available for use in a new one.
  15. It's correct, since allocation method is set to fill up and minimum free space is set to 100GB, until there's less than 100GB free any new writes to that share will go to that disk, you'd need to adjust the minimum free space or set a different allocation method, like high water.
  16. Same issue as this recent post, same solution: https://forums.unraid.net/topic/119965-split-two-disk-cache-pool-data-still-mirrored/?do=findComment&comment=1096682
  17. If you want a desktop board look for a board with SLI support, those will have two slots that can be configured as x16/x0 or x8/x8, with server boards from for example Supermicro they usually always come with two slots configured for x8/x8, and usually one of them can be bifurcated to x4/x4.
  18. I missed before that you ran an extended test on the new parity, problem appears to be the old parity, now disk1, which appears to be failing, an extended SMART test will confirm.
  19. Could be this issue: https://forums.unraid.net/bug-reports/prereleases/69x-610x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-r1674/?do=getNewComment&d=2&id=1674
  20. You can try posting in the UD support thread to see if there's anything that can be done, simple solution is to not use RAID controllers.
  21. Yep, Unraid requires all devices to have a unique s/n.
  22. It's affecting multiple disks, so depending on how they are connected could be cable/splitter, bad PSU or just how the load is distributed.
×
×
  • Create New...