Leen de Braal wrote: > > Update Time : Tue Mar 6 13:22:40 2007 > State : clean, degraded > Active Devices : 1 > Working Devices : 1 > Failed Devices : 0 > Spare Devices : 0 > > UUID : aed4ffaa:f90aa9b6:be5af158:c22c8924 > Events : 0.9596839 > > Number Major Minor RaidDevice State > 0 0 0 - removed > 1 3 67 1 active sync /dev/hdb3 > linux:~ # > > You should look for a message from mdadm in your syslog which may give you some ideas. Since it looks like it is still working, I would lean toward either controller or possibly cable problems. > It seems, that resyncing is going on now. > > Update Time : Tue Mar 6 13:26:30 2007 > State : clean, degraded, recovering > Active Devices : 1 > Working Devices : 2 > Failed Devices : 0 > Spare Devices : 1 > > Rebuild Status : 3% complete > > UUID : aed4ffaa:f90aa9b6:be5af158:c22c8924 > Events : 0.9596970 > > Number Major Minor RaidDevice State > 0 0 0 - removed > 1 3 67 1 active sync /dev/hdb3 > > 2 3 3 0 spare rebuilding /dev/hda3 > linux:~ # > > Check it every once in a while till you can see it has finished resyncing. > Still asking myself how this could have happened? Any idea? > > Perhaps a loose cable, a controller going bad, or perhaps a drive getting ready to go.
-- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
