Shamsul Kamal
asked on
URGENT! how to bypass Windows Server 2003 scandisk after reboot ?
Hi,
May i know how to bypass Windows Server 2003 scandisk after reboot ?
It seems do not have the option to skip the scandisk .
The scandisk is running for many hours and we would like to skip it.
Appreciates if anybody can help.
Thank you.
May i know how to bypass Windows Server 2003 scandisk after reboot ?
It seems do not have the option to skip the scandisk .
The scandisk is running for many hours and we would like to skip it.
Appreciates if anybody can help.
Thank you.
I think you just restart it and hit any key to skip the disk check when the screen shows up.
ASKER
Hi,
The weird thing is that , there are no option to skip as always after i reboot it ...
The weird thing is that , there are no option to skip as always after i reboot it ...
How about booting into the recovery console or command line and run CHKNTFS /X volume.
I would suggested to wait until the scan of the disks completed (just to be sure the disks are okay) and then make sure that Chkdsk.exe or Autochk.exe are not scheduled or configured for automatic start: http://support.microsoft.com/kb/831426
Hope it helps.
Hope it helps.
you need to reset the dirty flag : https://technet.microsoft.com/en-us/library/cc753059.aspx
If it starts, I think you can hit the ESC key to stop it.
ASKER
Hi nobus ,
May i know how to remove the dirty flag ?
May i know how to remove the dirty flag ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@nobus:
Removing the dirty flag is correct and I didn't want to intrude upon that advice. The dirty flag is usually raised upon a hard reboot of the server.
So, what raised the dirty flag in the first place? Could this be a hard shutdown of the server, (meaning the power switch was toggled off/on without providing an excuse to the server for shutdown)?
We might refer this back to the author to find out what caused the dirty flag, like a power outage of hard boot of the server. Otherwise, they may lower the dirty flag and go back to business as usual. They may toggle the off/on switch and raise the flag again, giving the false impression that it was never resolved by your excellent advice.
Removing the dirty flag is correct and I didn't want to intrude upon that advice. The dirty flag is usually raised upon a hard reboot of the server.
So, what raised the dirty flag in the first place? Could this be a hard shutdown of the server, (meaning the power switch was toggled off/on without providing an excuse to the server for shutdown)?
We might refer this back to the author to find out what caused the dirty flag, like a power outage of hard boot of the server. Otherwise, they may lower the dirty flag and go back to business as usual. They may toggle the off/on switch and raise the flag again, giving the false impression that it was never resolved by your excellent advice.