Hello list! I have found today one bad drive! (Maxtor 200G IDE) I have also lost a lot of data thanks to that drive. The problem: The drive goes to crazy, and "can't remember", but dont say any error! The RAID5 is still used that drive, and wasted the data what the system writes to it... I dont know is there any good trick to detect this error, but I have one idea that can help some people on similar situation.... The job is simple: Recover from RAID5 parity information, but don't write the data to any disk, just verify the original data from drives, and reply the differences! (same on raid1) This helps to detect this light-bug drives. And it is more useful, if the kernel can do that on the working array with low priority... I am lucky, because I have found easy this bad drive, that loses own MBR, and 2 raid superblocks! :-) (raid0 on raid5) Thanks Janos - 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
