[NTLUG:Discuss] RAID recovery help!

[Pat Regan]

On Tue, 4 Nov 2003, Richard Geoffrion wrote:

> Nov  2 12:00:01 gwifs kernel: md: syncing RAID array md1
> Nov  2 12:00:01 gwifs kernel: md: minimum _guaranteed_ reconstruction speed:
> 100 KB/sec/disc.
> Nov  2 12:00:01 gwifs kernel: md: using maximum available idle IO bandwith
> (but not more than 100000 KB/s$
> Nov  2 12:00:01 gwifs kernel: md: using 124k window, over a total of 4000064
> blocks.
> Nov  2 12:00:01 gwifs kernel: md: delaying resync of md2 until md1 has
> finished resync (they share one or$
> Nov  2 12:00:01 gwifs kernel: md: delaying resync of md3 until md1 has
> finished resync (they share one or$
> Nov  2 12:00:58 gwifs kernel: raid1: mirror resync was not fully finished,
> restarting next time.
> Nov  2 12:00:58 gwifs kernel: md: recovery thread got woken up ...
> Nov  2 12:00:58 gwifs kernel: md: updating md1 RAID superblock on device
> Nov  2 12:00:58 gwifs kernel: md: sdb5 [events: 0000006c]<6>(write) sdb5's
> sb offset: 4000064
> Nov  2 12:00:58 gwifs kernel: md: (skipping faulty sda5 )
> Nov  2 12:00:58 gwifs kernel: md: recovery thread finished ...
> Nov  2 12:00:58 gwifs kernel: md: md_do_sync() got signal ... exiting
> Nov  2 12:00:58 gwifs kernel: raid1: mirror resync was not fully finished,
> restarting next time.
> Nov  2 12:00:58 gwifs last message repeated 25 times
> [/another snippet]
>
> so...how can /dev/md1 (sda5) be faulting...but all the other mdXs be
> fine...they are all on the same physical disk!
>

It's actually been a few years since I have used software raid...  But it
looks to me like it is trying to rebuild /dev/md1 but it's failing.  If it
is actually trying to rebuild and it is failing, I would guess that you
have a failing disk and all the bad sectors it has hit so far were within
the boundries of partition 5.

Pat