I forgot, in case it's of any help.
mdadm -D gives after reassembly:
/dev/md3:
Version : 00.90.03
Creation Time : Sun Jan 14 21:17:53 2007
Raid Level : raid5
Array Size : 20980736 (20.01 GiB 21.48 GB)
Device Size : 10490368 (10.00 GiB 10.74 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 3
Persistence : Superblock is persistent
Update Time : Tue Jul 3 21:21:53 2007
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 4K
UUID : 36bbe21d:f49e8b5d:f504154c:a6f12a51
Events : 0.6995604
Number Major Minor RaidDevice State
0 3 3 0 active sync /dev/hda3
1 3 67 1 active sync /dev/hdb3
2 22 3 2 active sync /dev/hdc3
and after the next boot:
/dev/md3:
Version : 00.90.03
Creation Time : Sun Jan 14 21:17:53 2007
Raid Level : raid5
Array Size : 20980736 (20.01 GiB 21.48 GB)
Device Size : 10490368 (10.00 GiB 10.74 GB)
Raid Devices : 3
Total Devices : 2
Preferred Minor : 3
Persistence : Superblock is persistent
Update Time : Tue Jul 3 21:27:08 2007
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 4K
UUID : 36bbe21d:f49e8b5d:f504154c:a6f12a51
Events : 0.6995718
Number Major Minor RaidDevice State
0 3 3 0 active sync /dev/hda3
1 3 67 1 active sync /dev/hdb3
2 0 0 2 removed
Any ideas on why the drive keeps being removed?
--
YT,
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
