no, everything is running normal. Raid 1 will have to rebuild the array
if you do a hard reboot, i've had realplayer hang on me more than once,
causing me to see my HD lights glowing for about half an hour
afterwards (i've only got 8.4 GB drives). The UU in your mdstat shows that
both drives are functioning in the array, if it showed U_ or _U then you
would have a problem and have to use the raidhotadd command to manually add
it to the array. The howto on Redhat's site explains this pretty good.
BTW, was it much of a slowdown to actually use the system while it was
resyncing?
On 10 Oct 2002, Robert L. Cochran wrote:
> Last night, my machine rebooted (possibly due to Evolution locking up --
> I don't think it is as stable as Mozilla Mail?) and this seemed to have
> caused a problem with my software RAID devices md0 and md1.It started
> "syncing" and the process took hours to do, from around 6:30 p.m. to
> 4:00 a.m. The physical disks are 2 -- 120 GB Western Digital WD1200JB
> drives. An Asus DVD drive is connected as /dev/hdb meaning it is the
> slave drive on one of the IDE busses.
>
> Could the RAID array have started syncing according to some schedule
> that I'm unaware of?
>
> Is it normal for software RAID to take the whole darn night to "sync"
> (reconstruct?) a disk array?
>
> I also got these kernel messages:
>
> Oct 10 16:40:15 bobcp4 kernel: hda: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Oct 10 16:40:15 bobcp4 kernel: hda: drive not ready for command
>
> And /proc/mdstat says:
>
> [root@bobcp4 root]# cat /proc/mdstat
> Personalities : [raid1]
> read_ahead 1024 sectors
> md1 : active raid1 hda2[0] hdc2[1]
> 115860416 blocks [2/2] [UU]
>
> md0 : active raid1 hda1[0] hdc1[1]
> 313152 blocks [2/2] [UU]
>
> unused devices: <none>
> [root@bobcp4 root]#
>
> Do I have a problem with my drives based on the kernel messages? The
> mdstat messages?
>
> Thanks
>
> Bob Cochran
> Greenbelt, Maryland, USA
>
>
>
>
>
