On Sat, 14 Jan 2012 15:42:58 -0600 Steve Carlson <stevengcarlson@gmail.com>
wrote:

> On Sat, Dec 31, 2011 at 5:37 PM, Steve Carlson <stevengcarlson@gmail.com> wrote:
> >> On Sat, Dec 31, 2011 at 4:08 AM, Jes Sorensen wrote:
> >> Hi Steve,
> >>
> >> What I meant here is that I would like to see the dmesg output at this
> >> point, to see if there were any read errors reported during the assembly.
> >>
> >>> I also ran extended self tests just to be thorough, and they both came
> >>> back error free.  I'm unsure as to whether that puts them in the clear
> >>> for bad sectors though.
> >>
> >> There were read errors in the dmesg output you posted earlier, which is
> >> why I am wary of it.
> >>
> >> Cheers,
> >> Jes
> >
> > Jes,
> >
> > This is /var/log/messages from boot to stopping and reassembling md2.
> > I think this is what you wanted, I'm not sure what more I can give
> > you.
> > http://dl.dropbox.com/u/2776371/raid/mdadm_stop_dmesg_c_mdadm_assemble_var_log_message.txt
> >
> > -Steve
> 
> 
> 
> Hi all,
> 
> This is still unresolved.  What else could I try short of breaking and
> rebuilding the array?

I don't know how the array could have got in this state.  IO errors on a
RAID0 don't mark the devices as faulty.
You would have to explicitly
   mdadm /dev/md2 --fail /dev/sdb3
or something like that - and I doubt you did that.

Anyway:
 mdadm -S /dev/md2
 mdadm -C /dev/md2 -e 0.90 -c 64 -l 0 -n 2 /dev/sda3 /dev/sdb3

should get you going again.  All the data should be there except for anything
that the hard drive has decided to keep for itself.

NeilBrown