Jump to content

trurl

Moderators
  • Posts

    44,352
  • Joined

  • Last visited

  • Days Won

    137

Everything posted by trurl

  1. Mostly just wanted to take a look at SMART for the original disk3, which of course isn't in those diagnostics. And since the array isn't started until after the parity copy, many other things can't be known from those, such as whether disks all mount. Let us know if you have any questions or problems.
  2. Post-read verification failed can be caused by bad RAM. Happened to me.
  3. Better yet, Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. It might be worthwhile to consider why exactly you think disk3 has failed instead of something else causing a problem accessing disk3.
  4. Sounds like you missed step 12: This is why it is a "swap". Old parity replaces failed data disk, new larger disk becomes parity. Please read the whole procedure again and ask if you have questions.
  5. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  6. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.
  7. I have merged your topics about this. Please don't post in multiple threads for the same question. It is impossible to coordinate responses when you post in multiple threads. "Crossposting" has been considered bad form on message boards since before the World Wide Web. If you feel your question hasn't received enough attention after a reasonable time, please post again in the original thread. People often will just quote their original question in a new post in the same thread, or simply make a new post in that thread just saying "bump".
  8. Rebuilding to the same disk is the same whether parity or data Stop array Unassign disk to be rebuilt Start array with disk unassigned Stop array Reassign disk to be rebuilt Start array to begin rebuild
  9. docker exec -it <container name> /bin/bash
  10. Might as well try rebuilding parity to the same disk. It doesn't actually have any of your files after all.
  11. Your syslog goes back a few months. Is this new behavior?
  12. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread
  13. On mobile now so can't look at Diagnostics yet Probably other things need some work to get dockers and VM paths optimal
  14. On mobile now so can't look at Diagnostics yet. Safest would be to rebuild disk 5 to a new disk and keep the original as is in case of problems with the rebuild. Are all disks mounting?
  15. Split level has precedence over allocation method
  16. The only acceptable number of sync errors is exactly zero. You must correct sync errors and until you get exactly zero you still have work to do.
  17. Flash drive problem. Put it in your PC and let it checkdisk. While there make a backup. Be sure to boot from a USB2 port.
×
×
  • Create New...