running out of room

[Guest]

I have a MS WIN2003 Server with no room in C: Drive
the Physical dirve 0 is 36 gig and in is partition in C: 5 gig and D: 31 gig.
off course it is part of Raid 1 on Adaptec CARD
running out of room on C: drive. I have try to ghost the C: to External USB
and Ghost if back to biger drive But does not work.
Do I need to backup and restore? or do I have any options.

Thanks
Freddie

 

[Pegasus \(MVP\)]

I have a MS WIN2003 Server with no room in C: Drive
the Physical dirve 0 is 36 gig and in is partition in C: 5 gig and D: 31 gig.
off course it is part of Raid 1 on Adaptec CARD
running out of room on C: drive. I have try to ghost the C: to External USB
and Ghost if back to biger drive But does not work.
Do I need to backup and restore? or do I have any options.

Thanks
Freddie

Ghosting sounds like a good idea. What exactly happened?

 

[Guest]

server boots
as soon as it starts the windows logo, goes to screen that looks like when
you
start the scan disk. and complains about the files have errors.
goes on for about 15 mins to fix all the files. and when it reboots it does
not boot and goes to Blue Screen.
does window 2003 or 2000 server keeps track of any changes on the amount of
space it has?
Thanks
Freddie

 

[Pegasus \(MVP\)]

This sounds very much like an imaging process that's gone
wrong. Perhaps your copy of Ghost is defective. Here are
a few options:
a) Try Ghost a second time.
b) Try another imaging product (Acronis, PowerQuest)
c) Temporarily install the disks in some Win2000/XP PC, then
use xcopy with the appropriate switches to create the clone.
d) Boot the machine with a Bart PE boot CD, then use xcopy
as above.

Options c) and d) require an understanding of the Windows
boot process so that you can restore the boot environment.

 

[Guest]

so windows does not care if the only is partition has gotten bigger.?
if so, can I backup everything change the drive or make the C: partition
bigger and restore?
thanks
What did we used to do when you guys were not around.
Freddie

 

[Pegasus \(MVP\)]

No, Windows does not care if its system partition gets
bigger or smaller. It will detect a changed disk and
sort things out by itself in most cases. In some cases
it may need a little help but your case is not one of them.

AFAIK, you should be able to use ntbackup to back
up the whole installation, including the System state,
to a file or tape, then restore it to your new disk.
The problem is that I've never tried it - I prefer to use
imaging programs. If I find the time then I will try the
backup process within the next 24 hours.

 

[Pegasus \(MVP\)]

Well, it did not work, for two reasons:

- When I tried to restore the backup data to a location other
than where the files came from, ntbackup informed me
that the System State would not be restored.
- ntbackup subsequently ran around in circles, prompting
me time and again for the name and location of the .bkf
file, which it knew full well. I was unable to break out of
this loop.

I suggest you use one of the alternatives I gave you in my
first response.

 

[Colon Terminus]

Just how big is the new drive? Greater than 127GB?
Could be a BigLBA problem.
The symptoms are very much as you describe.

 

[Gary Chanson]

so windows does not care if the only is partition has gotten bigger.?
if so, can I backup everything change the drive or make the C: partition
bigger and restore?
thanks
What did we used to do when you guys were not around.
Freddie

You can change the size of partitions without saving and restoring the
data. I do it all the time. I don't know what went wrong in your situation
but I do the equivalent often. Possibly Ghost did something it shouldn't
have done. I usually use either Partition Magic or Drive Image Pro for this
type of operation.

 

[Gary Chanson]

No, Windows does not care if its system partition gets
bigger or smaller. It will detect a changed disk and
sort things out by itself in most cases. In some cases
it may need a little help but your case is not one of them.

AFAIK, you should be able to use ntbackup to back
up the whole installation, including the System state,
to a file or tape, then restore it to your new disk.
The problem is that I've never tried it - I prefer to use
imaging programs. If I find the time then I will try the
backup process within the next 24 hours.

I do the equivalent of what NTBackup does and it does work.

 

[Gary Chanson]

Well, it did not work, for two reasons:

- When I tried to restore the backup data to a location other
than where the files came from, ntbackup informed me
that the System State would not be restored.
- ntbackup subsequently ran around in circles, prompting
me time and again for the name and location of the .bkf
file, which it knew full well. I was unable to break out of
this loop.

I suggest you use one of the alternatives I gave you in my
first response.

Good to know. I'll stick with my own backup program which I know does
work in similar situations. If the final configuration is enough different
from the original, it sometimes takes a repair operation to get it running.

 

[Dan Seur]

I have used various versions of Partition Magic over the years to resize
and move/reorganize partitions on NT351, NT4, and W2k - many SP levels -
and never had a problem.

It is possible, however, to mess up a system with tools like this.
Carelessness will do it every time. Power outages will do it
occasionally. And don't try this on a drive/partition that's already
corrupt.

 

[Gary Chanson]

I have used various versions of Partition Magic over the years to resize
and move/reorganize partitions on NT351, NT4, and W2k - many SP levels -
and never had a problem.

It is possible, however, to mess up a system with tools like this.
Carelessness will do it every time. Power outages will do it
occasionally. And don't try this on a drive/partition that's already
corrupt.

Partition Magic won't let you work on a system with any kind of file
system error.

I did just run into a weird one on one of my own machines where I tried
to move the boot partition from the first partition position to the second
and couldn't get it to work, even after a full restore from the backup.
Putting it back in the first position worked fine though. I still haven't
figured out why that one failed. I've done the same thing before on other
machines and in this case, it was Win2K I couldn't move but I was easily
able to make the same change to XP.

 

[Pegasus \(MVP\)]

Partition Magic won't let you work on a system with any kind of file
system error.

Indeed. This is why I often use my Bart PE boot CD. As long
as the file system is readable, it will work.

 

[Gary Chanson]

Indeed. This is why I often use my Bart PE boot CD. As long
as the file system is readable, it will work.

Bart PE is definitely a valuable resource.

 

[Guest]

no
36gig on both C and D
Thanks
Freddie

Just how big is the new drive? Greater than 127GB?
Could be a BigLBA problem.
The symptoms are very much as you describe.

 

[Guest]

no only 80 gig
thanks

Just how big is the new drive? Greater than 127GB?
Could be a BigLBA problem.
The symptoms are very much as you describe.

 

[Guest]

I have created a Bart PE Boot CD but how do you use it. You just copy
everything from one prtition to another partition? just like the DOS days?
thanks
Freedie

 

[Gary Chanson]

Yes. As long as the files are visible, this will work when other
approaches fail.