On 03/11/17 10:44, John Crisp wrote: > On 03/11/17 00:47, Wols Lists wrote: >> On 31/10/17 18:11, Wols Lists wrote: >>> It's possible - I wouldn't know - that the existence of the MBR stops >>> mdadm looking for a superblock that applies to the whole drive, which >>> could explain why those drives have disappeared. >> >> Just been digging in the code - function check_raid - I think if you >> pass a drive to mdadm it checks the drive for a superblock, and doesn't >> look for whether a partition table exists. So I think that's that >> explanation blown out the water ... :-( >> > > :-) Thanks for looking. > > As I mentioned, I think I created the array via Xubuntu. > > As far as I remember I didn't partition any of the drives - just added > them to the array and I think it effectively created one partition > across the whole array (which would make sense why you can't see > partitions on individual drives) > > I am pretty sure that is trashed, but I like to try and understand these > things ! > More for Neil, this, but I've had a nasty thought. Did you reboot at all (as in clean shutdown, not crash and restart) at any point during this? I get the impression you might not have. Because that *could* explain the missing superblocks! I think raid updates the superblock every time it moves the rebuild window, so it should get rewritten to disk regularly. BUT. Is it possible that it was sitting in the disk cache when the system crashed? I find it hard to believe that's the case, but it could explain at least some of it (doesn't explain why those drives had mbr's, though). Cheers, Wol -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
