Chkdsk keeps running at boot on new drive!

Joined
Aug 22, 2004
Messages
5
Personal home computer.
Installed new Western Digital WD1200JBRTL 1.2 Gbyte drive w/8 Mbyte cache as new primary master, moved my existing Toshiba 40 Gbyte (still loaded with WIN98) as secondary slave. Installed XP on new drive. CHKDSK keeps self-executing at boot, and scary thing it sometimes reports corruption. I checked registery, and CHKDSK is NOT enabled to auto-run. Mortherboard is an Abit RAID BX-133, 800 Mhz, 393 K Ram, and I flashed the latest BIOS to it (2001 is last update). Disk passes diagnostics test from Western Digital.

It appears that the "dirty bit" flag is getting set while running under XP, thus forcing CHKDSK to run. Coudl this be a cache/timing error? Within BIOS, ultra DMA is enabled. I'm terrified of having corruption occur, I need a STABLE system, does anyone have specific reccomendations/comments regarding compatability of this board with this drive, and/or BIOS settings that should be used?

Thank you in advance for any assistance.
 
I ran "chkntfs /D" to force values to default. I also removed my 40 Gbyte secondary drive, so now I'm only looking at only the Western Digital drive. Powered off and on and used XP two times without any errors, but on third cycle Chkdsk came back on, on my root partition I had 50 or so "corrupt attribute records", went on to repair and rebuild index for a couple hundred orphan files. Event log shows instance of ID#55, NTFS reporting corrupt/unstable hard drive discovered during boot.

I should add since installing XP I routinely receive errors (in the System Log) on every boot, "ACPI BIOS Attempts to read and write from IO $ 0x71, protected address...." - I'm told this has to do with outdated power management features on the RAID motherboard that are incompatible with XP but this is suppossed to be only a minor annoyance. But could this be causing an NTFS file corruption issue?

I need help, this is getting beyound me....
 
and its passed several loops of memtest86+ ?
and its passed the manufacturers diagnostic?
and youve reloaded the busmaster drivers?

and the HDDs primarily uses the +12V rail not the +5V
and modern CPUs the more powerful P4s, A64s
and Graphics cards use the +12V as well
while many a supply is geared towards the +5V rail
leading to anemic +12V power delivery, and serious instability on that rail
 
Have run memory tests, RAID tests and Western Digital drive tests several times with no trouble. I think I've updated all the drivers I could find. I'm not sure about the 12V power, although the voltage levels are reading fine there might be sub-transient dips that are difficult to measure. If no one is aware of any specific BX-133 problems interfacing with XP and this drive then the power supply is a likely suspect. I will investigate and if need be, upgrade. I may also run this drive under WIN98 to see if this is at all XP related.
 
well thats not a +12V powered mobo the VRM (Voltage Regulation Modual(s) are drawing off the +5V, so its less likely that rail is overtaxed, but the supply might still have issues
(poor power being among the hardest intermittent problem to isolate)

try running ATACT (AT Attachment Command Test)

for just the individual drives and cables on the IDE Channels (omitting the RAID)
 
Ice - Thanks for your help, it appears that all trouble was stemming from my power supply. Although I measured a steady 12.87 V on the rail, after borrowing an oscilliscope I discovered there was all kinds of noise and who knows what bleeding across into the disk drive. Replaced the power suply with more watts to boot (locally, 400W units priced from $9.99 to $139, I chose a $49 model). Amazing that this trouble has probably existed since day one, but this new drive was a lot more suspectible to transients/harmonics than the older one. I would also swear that XP is running faster, maybe clock/data xfer speeds are improved without having to recycle through so many bad read/write cycles.

I should've heeded your original advice, Corruption 101 was right.
 
Back
Top