Thread (9 messages) 9 messages, 2 authors, 2017-11-05

Re: Raid 6 recovery

From: Wols Lists <hidden>
Date: 2017-11-04 12:46:58

On 03/11/17 10:44, John Crisp wrote:
On 03/11/17 00:47, Wols Lists wrote:
quoted
On 31/10/17 18:11, Wols Lists wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help