G
Guest
Here is my quaint little problem ...
I was having some peripheral issues on my rig , and I scheduled a chkdsk at
restart.
The chkdsk runs, but about half way through the free space portion (part 5
of 5) it simply stops.
(at about 65 Million sectors of some 132 million. I am running 2x320GB
drives in RAID 0)
No errors. Just stops. Disk access light goes out and system just sits there
happily.
The problem is that since the "dirty bit" is not being cleared in the
registry upon a successful completion of chkdsk, the system tries to run
chkdsk each time the system is rebooted and stops at the same place.
Ok, so cancel chkdsk before it runs (it gives you 10 seconds to cancel).
Wont' work. The system will not respond to keyboard input at that time and
the timer just counts down and chkdsk starts..
Upon reboot, the BIOS sees the keyboard fine (I can enter setup), but when
Vista starts to load it seems there is a period of time between when the BIOS
USB drivers work and the windows ones take over.
Of course, it just so happens that this is when chkdsk runs.
I tried both USB and PS2 Keyboards, thinking it may just be that the USB
prots initialize slower or later.
That does not work either.
So ...
Is there a way to "unset" the dirty bit in the registry from the restore
console or some other method ?
Is there some partition size limitation on chkdsk (why does it alsways stop
at the same place) ?
I couldn't find anything definitive googling.
Thanks in advance ...
I was having some peripheral issues on my rig , and I scheduled a chkdsk at
restart.
The chkdsk runs, but about half way through the free space portion (part 5
of 5) it simply stops.
(at about 65 Million sectors of some 132 million. I am running 2x320GB
drives in RAID 0)
No errors. Just stops. Disk access light goes out and system just sits there
happily.
The problem is that since the "dirty bit" is not being cleared in the
registry upon a successful completion of chkdsk, the system tries to run
chkdsk each time the system is rebooted and stops at the same place.
Ok, so cancel chkdsk before it runs (it gives you 10 seconds to cancel).
Wont' work. The system will not respond to keyboard input at that time and
the timer just counts down and chkdsk starts..
Upon reboot, the BIOS sees the keyboard fine (I can enter setup), but when
Vista starts to load it seems there is a period of time between when the BIOS
USB drivers work and the windows ones take over.
Of course, it just so happens that this is when chkdsk runs.
I tried both USB and PS2 Keyboards, thinking it may just be that the USB
prots initialize slower or later.
That does not work either.
So ...
Is there a way to "unset" the dirty bit in the registry from the restore
console or some other method ?
Is there some partition size limitation on chkdsk (why does it alsways stop
at the same place) ?
I couldn't find anything definitive googling.
Thanks in advance ...