On Fri, Dec 23, 2016 at 11:50 PM, NeilBrown <neilb@xxxxxxxx> wrote: > On Sat, Dec 24 2016, Giuseppe Bilotta wrote: >> >> >> So the array assembles, and raid6check reports no error, but the data >> is actually inaccessible .. am I missing other aspects of the metadata >> that need to be restored? > > Presumably, yes. > > If you provide "mdadm --examine" from devices in both the "working" and > the "not working" case, I might be able to point to the difference. I found the culprit. All disks have bad block lists, and the bad block lists include the initial data sectors (i.e. the sectors pointed at by the data offset in the superblock). This is quite probably a side effect of my stupid idea of trying a re-add of all disks after all of them were kicked out during the JBOD disconnect. One more reason to just stop the array when this situation arises. -- Giuseppe "Oblomov" Bilotta -- 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
