Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,505

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Backup current flash, then recreate from scratch (on the same flash) and restore just the key and super.dat, both are on the config folder.
  2. JorgeB
    Install v6.9-beta25, it includes that NIC's driver.
  3. JorgeB
    iperf, included with the nerdpack plugin.
  4. JorgeB
    This.
  5. JorgeB
    Replace/swap both cables, or if using some enclosure swap with another disk, then rebuild the disabled disk, not parity. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  6. JorgeB
    Diags are after rebooting so we can't see what happened, but disk looks fine, suggest replacing/swapping cables first just to rule them out and rebuild on top.
  7. JorgeB
    I agree, and there's already a request for that, in the meantime I recommend having array auto-start disable when using pools, so you can always check everything is correct before starting the array.
  8. JorgeB
    No, but it seems to only happen occasionally.
  9. JorgeB
    I remember other reports of CA stopping the dockers then failing to re-start them.
  10. JorgeB
    Correct, direct replacement is only possible if you can have both the old and new devices connected, more info in the FAQ.
  11. JorgeB
    Not if you do like I mentioned above.
  12. JorgeB
    You can only stop after the balance finishes.
  13. JorgeB
    They aren't, at least not with stock Unraid.
  14. JorgeB
    Please use the existing plugin support thread:
  15. JorgeB
    Try a different flash drive, or recreating that one.
  16. JorgeB
    It's balancing the pool to a single device, you can then add the new one, but the best way of doing this would be a direct replacement, i.e., stop array, select new cache device in the place of the old one, start array.
  17. JorgeB
    You have two failing disks with single parity, copy everything you can from emulated disk4 and disk8 to other disks in the array, then do a new config with the remaining good disk and re-sync parity, alternatively you can use ddrescue on disk8 and actual disk4 then do a new config with the clones.
  18. JorgeB
    Please post the diagnostics instead: Tools -> Diagnostics
  19. JorgeB
    No driver is being loaded for either NIC, @Mistress_Mistietry the latest beta, it should have the driver for both.
  20. JorgeB
    That looks like a correctable memory error, check the event log on the board BIOS, it might have more info and identify the slot, e.g., this is from one of my Supermicro boards:
  21. JorgeB
    Possibly unrelated but you should upgrade the LSI's firmware to latest (20.00.07.00)
  22. JorgeB
    There are some SMART warnings, run an extended SMART test.
  23. JorgeB
    Since they are exactly the same errors on the same blocks it rules out for any transient memory error, are you absolutely sure there wasn't any unclean shutdown? It's what makes more sense, it could be a disk but those cases are extremely rare and the sectors are not all together so even more unlikely, in any case and IMHO you should run a correcting check and as long as there are no more errors in the future you're fine.
  24. JorgeB
    No, it's the new normal for xfs.
  25. JorgeB
    It is, but it's the new normal.
×
×
  • Create New...