On Thu, Jan 14 2021, Nathan Brown wrote: > Scenario: > > I had a 4 by 10TB raid 5 array and was adding 5 more disks and > reshaping it to a raid6. This was working just fine until I got a > little too aggressive with perf tuning and caused `mdadm` to > completely hang. I froze the rebuild and rebooted the server to wipe > away my tuning mess. The raid didn't automatically assemble so I did > `mdadm --assemble` but really screwed up and put the 5 new disks in a > different array. Not sure why the superblock on those disks didn't > stop `mdadm` from putting them into service but the end result was the > superblock on those 5 new drives got wiped. That array was missing a What does this mean "the superblock on those 5 new drives got wiped"? How do you think that happened. Can you please report the current super blocks (mdadm --examine) anyway please. NeilBrown
Attachment:
signature.asc
Description: PGP signature
