Hi,
I think this bit is the crucial one (and identical to my problem):
Sep 6 13:10:01 yfs kernel: md: recovery thread got woken up ...
Sep 6 13:10:01 yfs kernel: md0: no spare disk to reconstruct array! --
continuing in degraded mode
Sep 6 13:10:01 yfs kernel: md: recovery thread finished ...
Sep 6 13:10:01 yfs kernel: md: updating md0 RAID superblock on device
Sep 6 13:10:01 yfs kernel: sdi1 [events: 00000009](write) sdi1's sb
offset: 17775808
Sep 6 13:10:01 yfs kernel: (skipping faulty sdh1 )
Sep 6 13:10:01 yfs kernel: sdg1 [events: 00000009](write) sdg1's sb
offset: 17775808
Sep 6 13:10:01 yfs kernel: sdf1 [events: 00000009](write) sdf1's sb
offset: 17775808
Sep 6 13:10:01 yfs kernel: sde1 [events: 00000009](write) sde1's sb
offset: 17775808
Sep 6 13:10:01 yfs kernel: sdd1 [events: 00000009](write) sdd1's sb
offset: 17775808
Sep 6 13:10:01 yfs kernel: (skipping faulty sdc1 )
Sep 6 13:10:01 yfs kernel: sdb1 [events: 00000009](write) sdb1's sb
offset: 17775808
Sep 6 13:10:01 yfs kernel: sda1 [events: 00000009](write) sda1's sb
offset: 17775808
i.e., a disk fails, recovery kicks in, and produces a hopefully correct
array in degraded mode. Then when writing the superblock something goes
wrong? Does the algorithm that recreates the superblock expect all disks
to be there?
Groeten, David.
________________________________________________________________________
Dr. David van der Spoel Biomedical center, Dept. of Biochemistry
s-mail: Husargatan 3, Box 576, 75123 Uppsala, Sweden
e-mail: [EMAIL PROTECTED] www: http://zorn.bmc.uu.se/~spoel
phone: 46 18 471 4205 fax: 46 18 511 755
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
