Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,569

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yes, if the old disk still has data, you can't rebuild it since it was removed from the array.
  2. JorgeB
    Just disable pending sector monitoring, they are still good devices.
  3. JorgeB
    In this case it will re-sync parity without disk4. If you want to add disk4 you need to do it before that: See if it mounts with the UD plugin.
  4. JorgeB
    If they are not detected in different computer they are likely dead, not much else you can do.
  5. JorgeB
    https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  6. JorgeB
    Was, not any more. You can re-enable parity but that won't bring back disk4.
  7. JorgeB
    If you wanted to rebuild disk4 you should never have removed it from the array, you can see if the old disk still mounts, and if yes do a new config with it and re-sync parity.
  8. JorgeB
    Array can still start with parity disabled, in fact the last diags you posted have the array started.
  9. JorgeB
    It should work with v6.9, diags might show the problem.
  10. JorgeB
    So you don't want disk4 in the array no more? If so just re-enable parity and re-sync.
  11. JorgeB
    You can download from here, then just replace all the bz* files.
  12. JorgeB
    Diagnostics might help.
  13. JorgeB
    Upgrade to v6.9-rc and the on-board NIC will work.
  14. JorgeB
    What happened to disk4? It's no longer part of the array, did you do a new config?
  15. JorgeB
    You can try asking for help on IRC, see here, might be able to free up some space so that the pool would no go read only on boot and then move some data, if not best bet it to copy all the data and restore from backup, you should never completely fill up a btrfs filesystem (or any COW filesystem), though it should not crash like it's doing.
  16. JorgeB
    Possibly.
  17. JorgeB
    If you already replaced the SATA cables and since both disks are on the same controller that would be the most likely culprit, you can swap one or both of them to another controller to confirm.
  18. JorgeB
    Yes, old parity was 8TB correct? If so first sync error is on sector=15628053064, which is exactly at the 8TB mark, so it was the bug, but like mentioned no harm in running another check to confirm all is well.
  19. JorgeB
    If you noticed that the sync errors only started after the 4TB mark probably not needed, but it can't hurt to run a non correcting check, also correcting checks should only be run if errors are expected.
  20. JorgeB
    Also, you need to correct those errors, in case it was a non correcting check.
  21. JorgeB
    There's a known bug with the parity swap procedure where some times it doesn't correctly zero the remainder of the new parity disk, so it will find sync errors once you pass the old parity size, if it was that your data is fine.
  22. JorgeB
    Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  23. JorgeB
    Please post the diagnostics zip: Tools -> Diagnostics
  24. JorgeB
    Best chance to recover any data from disks 4 and 5 is to let ddrescue finish and then rebuild, though there will always be some data loss on both, possibly a lot due to all those errors, if you just want to bring the array online and forget about those disks you can do a new config. Also in the future consider adding a second parity, small price to pay for the added redundancy, even for small arrays, but still not a substitute for backups.
  25. JorgeB
    Like mentioned above, you need to use the latest beta or the NIC won't work.
×
×
  • Create New...