RAID5 data rebuilding by mdadm results in corrupted data!
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This was also true for another device that was part of a RAID1 array (/dev/sda1)
the status of these devices, when checked using `mdadm -D /dev/md*` was "removed".
also `mdadm -E /dev/sd[a-d]3|grep Event` showed that sda3 had a different Events number (0.4647) than sdc3 and sdd3 (0.8721011). (Note: sdb3 also had a slightly different Events number, 0.8721010 but did not give any error message in /var/log/messages or any bad status when mdadm -E /dev/sdb3 was done)
I tried to rebuild my data by simply removing and readding the faulty devices, by
However, this resulted in an error and sda3 could not be added. The status, which was "Not active, degraded" before doing this, now changed to "Active, not started".
So, to start the device I ran the command
mdadm --run /dev/md2
which started the rebuilding process of /dev/sda3
At this point I thought that I was going to save my data, but as it turned out the data that was rebuilt is highly corrupt. A lot of files have garbage and a lot of files/directories don't have any timestamps etc. Some of the original filenames are listed when I do an ls, but I can't open them. there are entries like
?--------- ? ? ? ? ? filename
when I do ls -l
Does this mean that I have lost my data entirely now? Or is there a way to let mdadm know how exactly it should go about regenerating this device so that it gets the data correctly. as of now, mdadm thinks that all the RAID devices are clean.
Thanks in advance to anyone who can point me to any solution to this