"Unmountable: No file system" During parity build

[Daft]

I had my array running for about 9 months now with 3 external hard drives connected via usb, one of them as the parity drive (only one parity drive). I recently shucked them all one by one, starting with the data drives, rebuilding their data, then moving to the next. Now after shucking the parity drive and some time into the parity rebuild, another older drive started to throw errors and the build was paused. I foolishly tried to reboot the system and bring up the array, not seeing the drive wasn't mounted, and it looks like parity building restarted. I quickly paused it and stopped the array.

 

Is there any chance for recovering the data from the older drive?

 

Diagnostics: https://drive.google.com/file/d/1vZzIs1Qj7zwDJcgLpkZp4tFSmOx58Dim/view?usp=sharing

[JonathanM]

Attach the diagnostics zip file to your next post in this thread. As a general rule we won't access files not attached here.

[Daft]

Sorry, didn't see the option to attach files.

tower-diagnostics-20210603-1522.zip

[JorgeB]

There are two invalid disks with single parity, so the disable disk can't be emulated, disk itself looks healthy so you can try doing a new config and re-sync parity, probably good idea to replace/swap cables/slots on disk6 to rule that out.

[Daft]

Thank you. New config worked fine and parity build completed without errors. I did lose my docker containers and VMs, but shouldn't take much to rebuild them.