On 12/08/2013 10:35 PM, David C. Rankin wrote:
Now it is more "what happened?" As JA and the folks on the mdraid list think it is probably the old version of mdadm not handling the error right.
We shall see. mdraid really isn't magic. It either works or it doesn't, if it doesn't, then there is either a glaring reason seen using --examine or --detail or it is just a bug with mdadm. Most everything is handled automatically after you issue --assemble, there are not a lot of user screw-ups you can make :-)
(that's a good thing)
After 2 days pulling my hair out, the answer was as simple as popping in the Arch install CD and rebooting!! Nothing special about which disk you use, you just have to use one with a newer version of mdadm. The 11.0 Rescue disk had mdadm 2.6.4, the Arch disk had 3.3.2. After it booted, I checked cat /proc/mdstat and /dev/md1 (md126) under mdadm 3.3.2 and the array is labeled status "resync pending". Perfect. All I had to do was: # mkdir /mnt/mdmnt # mount /dev/md126 /mnt/mdmnt BINGO! The drive mounted flawlessly and a quick check of cat /proc/mdstat showed the drive to be re-syncing just fine. That was a whole lot of work to find out that it was an old mdadm causing all the problems -- live and learn... That is also a good lesson for all who have older versions of mdadm. If anything happens to cause a problem, the FIRST thing you do is to get the latest version of mdadm and boot with that! Thanks to all that helps. this problem is SOLVED! -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org