Someone changed my C: no paging file config..

Microsoft Windows server 2003 enterprise
June 9, 2010 at 07:58:41
Specs: Windows 2003
...On my clustered box. I've tried to set it back to
"No paging file", but it reboots itself repeatedly. I
can boot it in safe mode, but don't know what to
do after that... thanks, edi

See More: Someone changed my C: no paging file config..

Report •

#1
June 9, 2010 at 09:08:03
why would you set your server to no paging?
that is not a recommended setting.

Report •

#2
June 9, 2010 at 09:11:27
It was the requirements for this configuration, and our
application... "System managed" is set for the rest of the disk
space for the application... I was wondering if it was rescue-
able..

Report •

#3
June 9, 2010 at 10:34:10
Sorry but you are not making much sense to me.

You only need one pagefile. System managed is just fine. System managed means you have a pagefile.

Why do you think you specifically need a pagefile on c:?
What disk is the system managed pagefile on?

Specifically can you tell me the "required configuration" for the pagefile? i.e. what was recommeneded.


Report •

Related Solutions

#4
June 10, 2010 at 02:26:46
You are right, but due to the limited size of the C: Drive, these servers it was deemed that "No Paging File" was set, and a D: drive was created and was set to "System Managed".
This is a standard configuration for applications that deal with Realtime data and hefty logging...
In testing a live failure, another team changed the C: drive to a custom size (2000 to 4000) and rebooted the server. That's when the server could no longer boot properly. I was asked to fix it, so I booted the server into safe mode and reset the C: drive back to "no paging".
What I'm really asking is, is there anything else I can do to stabilise the server, or will it mean a rebuild.

Report •

#5
June 10, 2010 at 08:01:15
Before they set c: for pagefile did they defrag the drive?
It is a sop to defrag before making the pagefile.
There also has to be sufficent available disk space on c:

You may want to run chkdsk /f on the drive before defragging.

Once you have created a pagefile on c: make sure to delete the one on the d: partition.

The paging rule is one pagefile on a disk. There is only wasted space having a pagefile on multiple partitions on the same disk. Ideally you put the page file on a disk that is not being used for OS operations [system and boot].


Report •

#6
June 10, 2010 at 09:23:55
Hi Wanderer
Thank you for your help. Unfortunately chkdsk /F and defragging didn't work, but I have learnt a great deal about why servers are configured the way they are.
After I had tried your suggestions, I enabled boot logging to try to see if a driver was failing, and the boot was crashing when the crcdisk.sys driver was the last one to be loaded. I reloaded the ntdetect.com and ntldr (from advice off other sites), but this did not fix the issue. Due to time constraints I will probably rebuild the server from scratch in the morning (BST). If you have a further suggestion, then I'm quite prepared to try it, though I won't be able to take too long.
Either way, Thanks again for your help.
edi

Report •

#7
June 10, 2010 at 09:36:31
You would do a repair install of server 2003 before you do a wipe and reinstall.

post the results of a chkdsk from c: for review. Thx


Report •

#8
June 10, 2010 at 15:31:45
sure will... I've got pressures to get this back to normal, but of course can send you the results.

Report •

Ask Question