Cannot add replacement drive (mdadm) not large enough to join array
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.
interesting note, i just used pvcreate on the drive and it had not problems, I then used vgcreate and created a test volume no problems, I am really at a loss for what problem mdadm sees with the drive.....
I haven't tried hot plugging, but I did run blockdev against the drive and the partition and they match exactly
I did see a note about mdadm and not using the last 256 blocks, however I am not seeing the problems they were seeing...
Is there a way to just copy the GPT label off one drive to another, if it is a corrupt partition or some such I should be able to copy the data off the "failed" drive... Perhaps side stepping whatever the actual problem is.
If you think hot plugging the drive has a genuine chance of giving s different result I will try it. I am only leary because I could accidentally affect one of the 2 remaining drives.
Sounds like exactly what I am seeing... My version 2.6.4 which I believe is older than the listed bug version (2.6.7 I am guessing) on that bug report. I am stuck with openfiler, and I am a very LIGHT user of linux... I cannot see a way to update mdadm to a newer version... can you help me with updating this or perhaps there is a work around?
If you can get your hands on a later version of mdadm, compiled against the same library versions as found in Openfiler, you can just copy it with scp to basically any directory on your system and run it from there.
Another option would be to boot the system from a Live CD, use the mdadm tool on that CD to add /dev/sdb1 to the array, and then reboot back to Openfiler.
the kernel is 188.8.131.52-0.24.smp.gcc3.4.x86.i686 , I believe it is version 2.3, but now that I go looking for the version, I can't seem to find it anywhere that makes sense. Based on the update log, the system updated from 2.2 to 2.3 in december 2012. When I do a "update" it tells me that it has nothing to update.