Jump to content

JorgeB

Moderators
  • Posts

    67,540
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. This will be the main issue, HBA is caped at 1GB/s theoretical max bandwidth, usable max is around 80% of that, so 800MB/s, on the diags posted you have 25 drives reading at 31MB/s, that's close to the 800MB/s expected limit. Ideally you'd want a PCIe 2.0 ou 3.0 slot for the HBA, and your board should have a couple of x8 PCIe 2.0 slots, if you use one of those it will quadruple current bandwidth.
  2. Any 2 port Asmedia controller should work, as for a specific brand this is a known good one: https://www.sybausa.com/index.php?route=product/product&product_id=151
  3. JorgeB

    Recovery

    You can use the UD plugin to check which disks have data, just by having the option to mount, or my mounting them read-only, do you have single or dual parity?
  4. I get around 300MB/s sustained to my small SSD server with turbo write enable, about 200MB/s without it.
  5. Diags are after rebooting, but by the looks of it one of the cache devices dropped offline, run a scrub and make sure all errors are corrected, see here for more info.
  6. If you haven't yet enable turbo write and performance should be a little better, but don't expect 500MB/s, even if your SSDs can sustain that, and most SSDs can't contrary to popular belief. Also make sure you're writing to a single disk at a time, i.e., don't enable most free allocation mode unless you have a much faster parity device that can cope with the overlapping writes.
  7. I said there's filesystem corruption, not failing devices.
  8. Disk isn't being detected, make sure it's not the 3.3v SATA issue, you can use a Molex to SATA adapter to test.
  9. There's filesystem corruption on the pool, best bet is to backup, re-format and restore data. P.S: next time please post full diags instead.
  10. Diags are after rebooting so we can't see what happened, but disk looks healthy and the emulated disk is mounting, if contents look correct you can rebuild on top: https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive Also a good idea to replace/swap cables to rule those out and if it happens again grab diags before rebooting.
  11. SMART test was successful, this means the pending sectors are false positives and can be ignored, at least for now.
  12. That value is what the UPS is reporting, nothing you can do on the Unraid side even if it's wrong.
  13. Forgot to mention, since you're on the beta downgrading would unassign the cache pool, but just re-assign it or wait to go back to beta and it would be picked up as it was.
  14. It won't break anything with the NAS part, you can just do a quick test after booting, but better to disable docker/VMs before just in case.
  15. See if this helps: https://unraid.net/blog/unraid-6-9-multi-language-support
  16. Run an extended SMART test on the disk, SSD should be fine for now.
  17. https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta30-x86_64.zip
  18. There's no driver for the onboard NIC in v6.8.x, you can use v6.9-beta.
  19. You can run the diskspeed docker to test controller(s) aggregate speed.
  20. You should check current HBA link speed, but assuming that is good and despite CPU not being very fast (parity check is single threaded), and since it's a large array, most likely this is the main issue.
×
×
  • Create New...