On 12/08/2013 09:17 PM, John Andersen wrote:
On 12/8/2013 6:50 PM, David C. Rankin wrote:
Both drives are fine!! Why is mdadm having problems? Would a newer mdadm be worth a shot? I'd rather figure out why my version (2.6.4) isn't working, but I think I've pretty much tried everything up to the point of having to use the --create mode and risk data loss. JA, all, anybody have any other suggestions?
There seems to be a lot of talk that google dredged up about this problem being related to specific versions. So it might be ok to try a new version, as long as you can get it installed.
Yes, I saw that too, but it mostly had to do with the array outgrowing its space, so I didn't think that was it - but it may be. I have an Arch install disk with mdadm 3.3.2. I should be able to boot that and see if it can assemble the array. If it does, then what? If the assemble/sync succeeds, then the Event Count should be corrected and it should boot and assemble back under the 11.0 version - right? If not, then were are going to have to what? I can't just chroot below one of the / partitions update and then create a single disk array - can I. Then --add the other partition to the raid set and have everything sync? I'll try the newer mdadm and see what happens. I've already rsync'ed the needed data of /dev/sda5 mounted -o ro under the Rescue Console, so at least the config, mail, mysql tables and other data is safe. Any other ideas, let me know. If not, I'll report back after the 3.3.2 test. -- 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