Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,756

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yep, that was the problem.
  2. JorgeB
    Nothing jumps out in the hardware used, enable the syslog server and post that after a crash.
  3. JorgeB
    Disk6 is failing, since parity isn't valid you can do a standard rebuild, you can try to manually copy everything you can from that disk or use for example ddrescue.
  4. JorgeB
    Enable the syslog server and post that after a crash.
  5. JorgeB
    Diags is showing issues with two devices at the same time, so most likely some backplane related issue, or the SATA controller.
  6. JorgeB
    Reboot.
  7. JorgeB
    Parity check is for the array, you can run a scrub on the pool.
  8. JorgeB
    Since it's happening with all the disks connected to the Intel SATA controller there could be a power/connection problem, or the board/controller is going bad, the former is much more likely.
  9. JorgeB
    Feb 15 18:04:11 TheSentinel kernel: nvme nvme0: pci function 0000:04:00.0 Feb 15 18:04:11 TheSentinel kernel: nvme 0000:04:00.0: can't change power state from D3hot to D0 (config space inaccessible) Feb 15 18:04:11 TheSentinel kernel: nvme nvme0: Removing after probe failure status: -19 Device is failing to initialize, don't think there's much you can do other than trying a different NVMe device (or a different board), you can also try v6.10-rc2 but doubt that it would help.
  10. JorgeB
    Nothing about the crash in the syslog, this usually points to a hardware issue, and not saying that is the problem but RAM is still overclocked.
  11. JorgeB
    Yes, just delete and re-create the docker image, can't help with the VM issues.
  12. JorgeB
    Device sdg was successfully removed from the pool, any mentions of it should stop once you reboot, possibly after an array re-start.
  13. JorgeB
    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/
  14. JorgeB
    Could be this: 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
  15. JorgeB
    This is a different problem, post new diags. See if there's an option to disable the Bluetooth module in the BIOS.
  16. JorgeB
    You can still use the data in all the other data drives, and depending on how bad the data drive failed you might still be able to recover some/most data there with for example ddrescue.
  17. JorgeB
    On main click on the disk, then scroll down to the self-test section and click on extended SMART test, make sure disk spin down is disable for that disk at least.
  18. JorgeB
    I don't like to keep bumping threads, also did that a couple of times for this pool bug which is a basic functionality and didn't help much, though last I heard it's finally being looked at.
  19. JorgeB
    Yes, it pauses for a few seconds (couple minutes max) or the format would take a long time, and disk will be available after the format is done.
  20. JorgeB
    It's logged as a disk problem, you can run an extended SMART test to confirm.
  21. JorgeB
    Yes.
  22. JorgeB
    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.
  23. JorgeB
    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.
  24. JorgeB
    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.
  25. JorgeB
    Please post the diagnostics to see the complete error.
×
×
  • Create New...