using chkdsk in situation where unreadable segment causes reboot

I have installed XP on C drive and chkdsk has found an unreadable file record
segment on the F drive (a Raid array). After chkdsk reports the error, the
system reboots. How do I fix this please? I have read that chkdsk /f can take
days to run on large disks (eg 70GB). My F drive is 240GB. I have the number
of the faulty record segment. TIA .... Greg

"gvm" <gvm@discussions.microsoft.com> wrote in message
news6F6A298-8099-4F97-B342-FBDE1AC6A241@microsoft.com...
>I have installed XP on C drive and chkdsk has found an unreadable file
>record
> segment on the F drive (a Raid array). After chkdsk reports the error, the
> system reboots. How do I fix this please? I have read that chkdsk /f can
> take
> days to run on large disks (eg 70GB). My F drive is 240GB. I have the
> number
> of the faulty record segment. TIA .... Greg

Years ago it may have taken that long, but unless your machine is very old
it should only take a few hours at best.

Are you saying after each and every error chkdsk reboots and starts again?

To the best of my knowledge it will fix what it can , report and then
reboot.

If your array is so degraded it's probablty not worth the hassle and risk. I
would be dumping it.

If the RAID array is not your system drive there shouldn't be a reason you
couldn't run chkdsk while using windows, you just won't be able to access
the F drive in that time.