On Sunday April 16, [EMAIL PROTECTED] wrote: > A system with 6 disks, it was UUUUUU a moment ago, after read errors > on a file now looks like: > > /proc/mdstat: > md1 : active raid5 sdf1[5] sde1[4] sdd1[3] sdc1[2] sdb1[6](F) sda1[7](F) > level 5, 64k chunk, algorithm 2 [6/4] [__UUUU] > > uname: > linux 2.6.11-gentoo-r4 > > What's the recommended approach? > > Compile 2.6.16.5 and mdadm 2.4.1, install both, reboot, then use mdadm > assemble --force (after automatic mount probably fails)?
You shouldn't need to upgrade kernel or mdadm (though you didn't report the version of mdadm, so I cannot be sure, and upgrading won't hurt). But yet, use --assemble --force and be aware that there could be data corruption (without knowing the history it is hard to say how likely). An 'fsck' at least would be recommended. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
