Bug#446323: mdadm: recovery in infinite loop

[Neil Brown]

On Friday October 12, szybalski at gmail.com wrote:
> yes I have.
> Then I tried booting in knoppix to see if maybe there are hdd problems
> so I run e2fsck on both drives to see if there are any issues.
> reboot and it still does the same thing.

Ok, it must be caused by some persistent state.
Could you send
  mdadm -E /dev/hda2
  mdadm -E /dev/hdb2

and the exact partition layouts of /dev/hda and /dev/hdb

> 
> Is mdadm able to sync in init 1?

The array will start resync as soon as it is assembled.  So I think
the answer to your question is 'yes'.

> Is there a debug mode so I could get more logs for the mdadm?

It isn't 'mdadm', it is the kernel.  And no, there is no debug mode.

> If this seems as a kernel problem, how could I find out that is the
> case? Where would I start?

I can't tell what you mean by this question.

My current guess is that hda2 might be slightly smaller than hdb2 -
though that is really justd clutching at straws.

I suggest you 
 mdadm /dev/md2 -f /dev/hda2
so that it doesn't keep trying to rebuild all the time.

NeilBrown