> -----Original Message-----
> From: Bruno Prior [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 17, 1999 7:14 AM
> To: Linux-Raid; Michel Pelletier
> Subject: RE: errors on boot
>
>
> > At boot time, I have the following error messages in
> /var/log/messages:
> >
> > kernel: raid1: md2, not all disks are operational --
> trying to recover
> > array
> > kernel: raid1: raid set md2 active with 1 out of 2 mirrors
> > kernel: md: updating md2 RAID superblock on device
> > kernel: sda4 [events: 0000001a](write) sda4's sb offset: 2602432
> > kernel: md: recovery thread got woken up ...
> > kernel: md2: no spare disk to reconstruct array! -- continuing in
> > degraded mode
>
> The messages just before these messages probably gave some
> indication why sdb4
> is considered to be not operational. Can we see them, please?
Ok, there are three groups of messages for each of the three md devices.
Here is the group for the failed device:
<========================================
Nov 16 13:36:28 korak kernel: (read) sda4's sb offset: 2602432 [events:
00000017
]
Nov 16 13:36:28 korak kernel: (read) sdb4's sb offset: 2602432 [events:
00000016
]
Nov 16 13:36:28 korak kernel: autorun ...
Nov 16 13:36:28 korak kernel: considering sdb4 ...
Nov 16 13:36:28 korak kernel: adding sdb4 ...
Nov 16 13:36:28 korak kernel: adding sda4 ...
Nov 16 13:36:28 korak kernel: created md2
Nov 16 13:36:28 korak kernel: bind<sda4,1>
Nov 16 13:36:28 korak kernel: bind<sdb4,2>
Nov 16 13:36:29 korak lpd: lpd startup succeeded
Nov 16 13:36:28 korak kernel: running: <sdb4><sda4>
Nov 16 13:36:28 korak kernel: now!
Nov 16 13:36:28 korak kernel: sdb4's event counter: 00000016
Nov 16 13:36:28 korak kernel: sda4's event counter: 00000017
Nov 16 13:36:28 korak kernel: md: superblock update time inconsistency
-- using
the most recent one
Nov 16 13:36:28 korak kernel: freshest: sda4
Nov 16 13:36:28 korak kernel: md2: kicking faulty sdb4!
Nov 16 13:36:28 korak kernel: unbind<sdb4,1>
Nov 16 13:36:28 korak kernel: export_rdev(sdb4)
Nov 16 13:36:28 korak kernel: md: md2: raid array is not clean --
starting backg
round reconstruction
Nov 16 13:36:28 korak kernel: md2: max total readahead window set to
128k
Nov 16 13:36:28 korak kernel: md2: 1 data-disks, max readahead per
data-disk: 12
8k
Nov 16 13:36:28 korak kernel: raid1: device sda4 operational as mirror 0
Nov 16 13:36:28 korak kernel: raid1: md2, not all disks are operational
-- tryin
g to recover array
Nov 16 13:36:28 korak kernel: raid1: raid set md2 active with 1 out of 2
mirrors
Nov 16 13:36:28 korak kernel: md: updating md2 RAID superblock on device
Nov 16 13:36:28 korak kernel: sda4 [events: 00000018](write) sda4's sb
offset: 2
602432
Nov 16 13:36:28 korak kernel: md: recovery thread got woken up ...
Nov 16 13:36:28 korak kernel: md2: no spare disk to reconstruct array!
-- contin
uing in degraded mode
Nov 16 13:36:28 korak kernel: md: recovery thread finished ...
Nov 16 13:36:28 korak kernel: .
Nov 16 13:36:28 korak kernel: ... autorun DONE.
<=====================================
Thanks for your help folks, if you ever have a Zope questions, let me
know! ;)
-Michel
