Raid 0 question

  • Thread starter Thread starter David Wells
  • Start date Start date
D

David Wells

I have a computer set up with the KV8 moter board with 2 WD drives set
up in a raid0 . When I try to use the scan disk built into XP I get
this message


Windows was unable to complete the disk check. I kind of suspect this
due to my raiid 0 set up. It is a NTFS file system will the defrag
tool work or is it also going to have the same problem due to the raid
0 set up
 
David Wells said:
I have a computer set up with the KV8 moter board with 2 WD drives set
up in a raid0 . When I try to use the scan disk built into XP I get
this message


Windows was unable to complete the disk check. I kind of suspect this
due to my raiid 0 set up. It is a NTFS file system will the defrag
tool work or is it also going to have the same problem due to the raid
0 set up
Click to expand...

Does this get back to me at shae fuuny no answers to this question
 
Does this get back to me at shae fuuny no answers to this question
Click to expand...

I have Raid-0 (two 120s) on a A7V8X and have no problems with defrag.
Thats Win2003 though. On an MSI board I have two 120s in Raid-0 with
XP Pro and have no problem with defrag.

I would guess that you have a background process that is writing to
the disc while windows is trying to check it.
 
Is it defrag or scan disk (chkdsk) that the OP is concerned about??

I too am having the same problem running chkdsk on boot. I would be
interested in finding the cause and remedy to this. Defrag however, runs
fine.

There is only one way around it and that is to run chkdsk from the command
console.
 
Is it defrag or scan disk (chkdsk) that the OP is concerned about??

I too am having the same problem running chkdsk on boot. I would be
interested in finding the cause and remedy to this. Defrag however, runs
fine.

There is only one way around it and that is to run chkdsk from the command
console.


"dgk" <[email protected]> wrote in message
Click to expand...

Try using task manager, see what processes you have running, and start
knocking anything that isn't critical. How do you know what is
critical? If you can look at another machine, assume anything running
on yours and not on the other machine is not critical.

Otherwise, if you knock out something and the system crashes, don't
knock that out the next time.

Try the chkdsk (or scandisk?) after knocking some out.

There is a program called HijackThis (just google) that has an option
to show you everything that starts up with your system. Very cool.
 
Try using task manager, see what processes you have running, and start
knocking anything that isn't critical. How do you know what is
critical? If you can look at another machine, assume anything running
on yours and not on the other machine is not critical.

Otherwise, if you knock out something and the system crashes, don't
knock that out the next time.

Try the chkdsk (or scandisk?) after knocking some out.

There is a program called HijackThis (just google) that has an option
to show you everything that starts up with your system. Very cool.
Click to expand...
Even from the promp I tried chkdsk and it stops saying cannot check
read only disk. Defrag works fine and when I use the raid tool to
check disk it says they are ok. Who knows
 
Back
Top