Jump to content

JorgeB

Moderators
  • Posts

    67,411
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. Run a couple of non correcting parity checks and post new diags after that (before rebooting) but first check/replace cables on disk2.
  2. Looking at the syslog the cache devices were wiped, you can't just start the array multiple times while trying various configs, there should have been a red warning "data os this device will be deleted at array start" or similar for one or more devices, not even btrfs restore will work now since the superblocks were deleted, only option would be a file recovery util like UFS explorer, but not sure if it would work for this case, there's a trial if you want to give a shot.
  3. There are several segfaults and btrfs checksum errors, which suggests a hardware issue, like RAM errors, start by reading this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  4. Please post the complete syslog.
  5. Is is the same if you boot in safe mode?
  6. Go to: Settings -> Global Share settings -> Included disks And unselect all disks, or also select disk8, but first option recommended.
  7. I would recommend doing that, as it's likely to happen again soon.
  8. Difficult to say for sure, if it happens regularly it's likely a hardware problem, like bad RAM.
  9. Yes, don't try to backup the docker image, it's easy to recreate, also see here if the fs goes unmountable before the backup is done.
  10. Cache filesystem is corrupt, best to backup, re-format and restore the data.
  11. If it's crashing between logs nothing is being logged, most likely a hardware problem.
  12. Any LSI with a SAS2008/2308/3008/3408 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.
  13. The errors are likely harmless, and if the new firmware doesn't fix them try with 16.00.01, which is the one most commonly used with those models and known to work without issues.
  14. Run xfs_repair without -n or nothing will be done, if it asks for -L use it.
  15. Try that flash drive on another computer to confirm it's booting, if yes it's likely a board problem.
  16. If you get those low speeds writing to cache and array (with or without turbo write) it suggest a problem outside Unraid, like network or source computer, see what you get running iperf test.
  17. Then it's most likely device related, do you have a different NVMe device you could test with?
  18. Since the extended test passed the disk is currently fine, and the pending sectors are "false positives", though it's never a good sign especially on a new disk.
  19. That's a known issue with newer kernels, and why v6.8 reverted to using kernel 4.19.x
  20. Yep, then post the syslog, it might catch something.
  21. You should start by posting the diagnostics, there are some known issues with some hardware, e.g. Ryzen, besides that see this.
  22. This is an English speaking forum, please post in English.
  23. Post a screenshot of the page main showing that.
×
×
  • Create New...