Jump to content

JorgeB

Moderators
  • Posts

    67,530
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Disk dropped offline so there's no SMART report, unless the disk died it's like a connection problem, check cables and post a SMART report.
  2. Nope, anything except 0 is not normal, or good.
  3. If there was no unclean shutdown it's a hardware problem, RAM, board, controller, disk, etc. It only shows the sync errors, not the reason for them, though it can help diagnosing, by comparing with previous errors. Yes, but array will perform slower.
  4. Marvell controller, this works for some, though any Marvell controller is not recommended.
  5. https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606
  6. Then you should try to find out what caused the sync errors, only acceptable result is 0 sync errors, run a non correcting check, and scheduled checks should also be non correcting.
  7. Mover logging is spamming the log and because of that there's time missing, cache filesystem is read only, so likely a problem with that, but would need to see the begging of the problem to confirm, re-format cache and/or disable mover logging and post new diags if it happens again.
  8. That's not a normal SMART report, I would suggest getting a replacement.
  9. SMART report is missing a lot of stuff, and there are some errors, possibly a device problem. BTW, what is a Mercury Elite Pro Elite Pro? Is it a white label drive?
  10. It usually happens during high i/o load, like a parity check.
  11. Just to expand a little, LT has not been posting direct links for betas for some time.
  12. This sometimes helps: 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" and before "initrd=/bzroot" nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference, if it doesn't best bet is to get a different model NVMe or board.
  13. It's a problem with the SATA controller, quite common on Ryzen boards, there are reports that the newer kernel on the latest betas help with those, or disable IOMMU if not needed.
  14. Yep, those CPUs only have 6 PCIe lanes total coming from the CPU.
  15. No: It's only x1, should be on an x8 slot (x4 minimum)
  16. For example: Supermicro MiniSAS to 4x SATA 51/51cm Cable (CBL-0097L-03)
  17. Speedtest docker should show it, if not run lspci -vv
  18. You need to confirm if they are forwarded or reverse breakout cables, only forward breakout will work for this.
  19. Use the diskspeed docker to run a benchmark on the controller, also check its link speed.
  20. You have user shares set to use only disks 1 through 5, and since the newly added disks are not part of the user shares and disk shares are set to auto they appear as disk shares, unselect those disks from user shares so Unraid uses them all.
  21. No, you can add a new drive and sync parity at the same time.
  22. Any unexplained sync errors a reason to worry about, any unclean shutdown before this last check?
  23. Don't see any errors logged, you can try running the server in safe mode without dockers/VMs for a few days, if it crashes like that it's likely a hardware problem, if it doesn't start turning the services on one by one.
×
×
  • Create New...