B
Bill
I've got an Asus A7V133 MB with both an ATA100 IDE and a
Promise IDE controller with RAID support (all on the MB).
For a while, I was running two 30G drives in a RAID 0
configuration (striping) on the Promise controller, and
one 80G drive along with 3 CDR/CDRW drives on the standard
IDE controller for a total of 6 drives connected to the MB.
I don't know when it started, but at some point the PC
started to want to run chkdsk quite often during bootups.
I didn't reboot that often, but when I did, more often
than not, it wanted to run chkdsk.
I had chalked it up to it being a "cheap" RAID controller,
and figured the problem would go away when I stopped using
the Promise controller and only used the standard IDE
controller.
About 2 to 3 weeks ago, I rebuilt the OS after negating
use of the Promise controller. This was instigated by the
fact that I had a drive go bad. When I did a clean
install of the OS, I had two 30G drives installed on the
standard IDE channel, and two optical drives. I'd removed
the 80G, and a couple CDRW's.
The problem didn't go away. I've now removed one of the
30G drives and replaced it with the original 80G drive
because I needed more drive space. The problem is still
here. At this point, it's given me "errors" on multiple
drives, on multiple controllers, and under different
installs of WinXP. Note that it's not always the boot
drive it complains about.
After doing some searching, I found a MS kb article that
mentions Win2k wanting to run chkdsk after every reboot.
That's not quite the problem I'm having, since mine
doesn't want to run it everytime, but it's close.
The last couple days I've noticed that I can't run
Diskeeper as it wants me to run chkdsk, but a reboot
doesn't pop up asking me to run one. The WinXP defrag
utility says there are drive inconsistencies as well and
won't run either. This makes sense since it's a stripped
down version of diskeeper. I know that I can force chkdsk
to run, but it's odd that WinXP isn't noticing that it
needs to run.
I downloaded a utility called Drive Fitness Test. I
believe it's made by Fujitsu and/or IBM. It didn't find
any problems with the drive at all.
Also, when the OS reboots and wants to run chkdsk, it
often finds errors, and on occassion has created filechk
files.
Looking back, I don't think I had any of these problems
when running Fat32. However, I have to run at least one
drive using NTFS as video editing (pulling files from my
camcorder) creates files much bigger than 4G.
Is anyone else having this problem? I suspect either
WinXP or the new version of NTFS is at fault.
Any help would be greatly appreciated.
Thank you.
Promise IDE controller with RAID support (all on the MB).
For a while, I was running two 30G drives in a RAID 0
configuration (striping) on the Promise controller, and
one 80G drive along with 3 CDR/CDRW drives on the standard
IDE controller for a total of 6 drives connected to the MB.
I don't know when it started, but at some point the PC
started to want to run chkdsk quite often during bootups.
I didn't reboot that often, but when I did, more often
than not, it wanted to run chkdsk.
I had chalked it up to it being a "cheap" RAID controller,
and figured the problem would go away when I stopped using
the Promise controller and only used the standard IDE
controller.
About 2 to 3 weeks ago, I rebuilt the OS after negating
use of the Promise controller. This was instigated by the
fact that I had a drive go bad. When I did a clean
install of the OS, I had two 30G drives installed on the
standard IDE channel, and two optical drives. I'd removed
the 80G, and a couple CDRW's.
The problem didn't go away. I've now removed one of the
30G drives and replaced it with the original 80G drive
because I needed more drive space. The problem is still
here. At this point, it's given me "errors" on multiple
drives, on multiple controllers, and under different
installs of WinXP. Note that it's not always the boot
drive it complains about.
After doing some searching, I found a MS kb article that
mentions Win2k wanting to run chkdsk after every reboot.
That's not quite the problem I'm having, since mine
doesn't want to run it everytime, but it's close.
The last couple days I've noticed that I can't run
Diskeeper as it wants me to run chkdsk, but a reboot
doesn't pop up asking me to run one. The WinXP defrag
utility says there are drive inconsistencies as well and
won't run either. This makes sense since it's a stripped
down version of diskeeper. I know that I can force chkdsk
to run, but it's odd that WinXP isn't noticing that it
needs to run.
I downloaded a utility called Drive Fitness Test. I
believe it's made by Fujitsu and/or IBM. It didn't find
any problems with the drive at all.
Also, when the OS reboots and wants to run chkdsk, it
often finds errors, and on occassion has created filechk
files.
Looking back, I don't think I had any of these problems
when running Fat32. However, I have to run at least one
drive using NTFS as video editing (pulling files from my
camcorder) creates files much bigger than 4G.
Is anyone else having this problem? I suspect either
WinXP or the new version of NTFS is at fault.
Any help would be greatly appreciated.
Thank you.