Hello all,
Does anyone know a way of forcing a reboot after a chkdsk? Say... after a crash and a large HPFS/HPFS386 drive being chkdsk'd? I have a couple systems that do just that, and one particular one that does not (which results in it hanging on various other driver loads - most notably NETWKSTA.200... folllowed by a trap, which spawns another reboot, which starts a chkdsk again, which results in errors loading NETWKSTA.200 and such, which is followed by a trap, which is followed by a reboot, which is followed by a chkdsk... you get the point.
I am not sure what the determining criteria is that's used by chkdsk.sys to decide on whether it will trigger a reboot or not; nor can I find any documentation that indicates a switch to always cause a reboot after the chkdsk - but I definitely have one system that needs an "always reboot" enabled.
Best,
Robert
Hi,
well I don't have a faintest clue. But... I can imagine that it perhaps depends on a special flavor of a "dirty flag" of the partition (similar to what causes the actual chkdsk perhaps). I wonder if people who deal with partition stuff (like Jan van Wijk, DFSee) have perhaps info on this?
Or you may be lucky to find more clues if you google for HPFS "specs"?
HTH,
Thomas
Well, I am pretty sure from what I know of the HPFS internals and the files that implement and maintain HPFS partitions, that the system is rebooted to free the memory used and locked by the chkdsk routine.
* The memory will not be available for the system to use in
completing the boot process.
* Errors may occur later in the boot process.
Hence, the CHKDSK.SYS device driver is smart enough to recognize when CHKDSK has used this reserved memory and will reboot the system automatically after all HPFS drives have been checked. Since the drives were checked before the reboot, CHKDSK will not have to check them after the reboot and the system will boot normally.
So... there it is. I apparently have run into a situation where chkdsk.sys is exhausting too much memory from one of the memory arenas, but the reboot is not being triggered.
QuoteI apparently have run into a situation where chkdsk.sys is exhausting too much memory from one of the memory arenas, but the reboot is not being triggered.
It is more likely that it is not using enough memory to trigger the reboot. That can happen if you have lots of memory, and not a lot of files on the drives. However, that situation should not cause problems later. I suppose that it may be a situation where too much memory is used, but the reboot threshold has not been crossed. Try adding a couple of hundred (perhaps thousand) small files to the disk with the most files, and see what happens.