Link to home
Create AccountLog in
Avatar of tjwib29
tjwib29

asked on

Boot Partition is full and therefore cannot boot

I have a Win Server 2003 machine (remote) that will not boot in any form of safe mode or active directory recovery mode.  I believe that the issue has to do with a full c drive, but I can't get it booted to delete any files.  I am working on downloading Active Boot Disk from ntfs.com but my client has to drive to get use of a cd burner.  Will this work?  I have a pair of mirrored SCSI drives and not sure how drivers will get loaded to recognize the drives.  Does anyone have any other options and maybe something to do in the future to prevent this.  Part of my problem is MS Exchange creates 5 MB log files everyday and I schedule a reboot every night to clear up some other issues.  I guess one option is to move the log files to a diff drive.

Thanks

TJ
ASKER CERTIFIED SOLUTION
Avatar of InteraX
InteraX
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
tjwib29,

What error do you get when you try to boot? I had a similar issue about 2 years ago and the server took about 30 mins to boot until I could move the databases off.

InteraX
Avatar of tjwib29
tjwib29

ASKER

You need the server 03 cd to run the recovery console right?  I have the client getting the cd, but the person who has it is out till Monday, so I was trying to see what I could get done today.  We are running Exchange 03 standard and I have moved the exchange db's on other machines, so I guess I need to do it on all my clients.  I do save the log files, because I read somewhere about them being needed until a proper backup was done and they should delete themselves after that happens.  Veritas with the Exchange add on does not cover this apparently.  They are kind of annoying though!  

Do you have any experience with Acitive Boot Disk, I saw it recommended in another post on this site.  The stop number I get is 0xc000007f.

Thanks

TJ
Avatar of tjwib29

ASKER

InteraX

As far as the 30 minute boot, are you saying it might continue to boot after the error message shows up as long as I don't click OK?

Thanks

TJ
tjwib29,

Sorry for the delay in responding. I've been very busy at work.

I presume you have this fixed now. My veritas with exchange plugin cleans out all my log files every night. What type of exchange backup do you run? brick level or store level? Unless you perform a store level backup, the log will not get cleaned out and you will not be backing everything up.

The stop code means inaccesible boot device. This looks bad. Faulty hdd or something similar.

The recovery console is on the OS install CD. Try running a chkdsk from there if you still have this pending.

InteraX
Avatar of tjwib29

ASKER

Thanks for the help!  I ended up using Active Boot Disk and loaded my SCSI drivers and was able to access all drives.  Then I could move stuff around to get it booted.  The program that caused the issue was a Supermicro Monitoring tool that creates a file from some type of memory dump and uses all available space.  I ran into it another time so I knew where to find the file.  Supermicro just says to delete the file so I did and everything is fine.  Now I need to check the memory sticks out though, just in case.  I'll look into the Veritas backup, thanks for the info.

TJ