Radified Community Forums - Why Does Norton Ghost 2003 Balk At Partition Sizes

Radified Community Forums › Rad Community Technical Discussion Boards (Computer Hardware + PC Software) › Norton Ghost 2003, Ghost v8.x + Ghost Solution Suite (GSS) Discussion Board › Why Does Norton Ghost 2003 Balk At Partition Sizes

(Moderators: Rad, Christer, NightOwl, Pleonasm, MrMagoo, El_Pescador)

‹ Previous Topic | Next Topic ›

Pages: 1

Why Does Norton Ghost 2003 Balk At Partition Sizes (Read 10957 times)

Big_Al

Gnarly

Offline

I love YaBB 1G - SP1!

Posts: 48
Los Angeles

Why Does Norton Ghost 2003 Balk At Partition Sizes
Jun 3^rd, 2006 at 1:54am

June 2, 2006

Dear Forum,

I just installed a bigger Hard Drive and FDisked it to

make some, not all, partitions bigger than my old drive.

I used my Ghost 2003 DOS Batch File to automatically do

all the partition cloning but when it hit the F: Drive, I

got the "Target Partition Is Not Big Enough" screen.

Loading Ghost 2003 manually, I checked the old F: Drive's

occupied size and the new F: Drives empty size. The

occupied size was 1100 MB smaller than the empty space on

the new HD.

The only way around this was to boot the old HD, move

some files to reduce the size down by 1500 MB's and THEN

Ghost cloned it OK. I then went back in and moved those

"extra" files back to the new F: Drive.

When this happened AGAIN to the J: Drive, I decided to

try and use the "Data Lifeguard Tools" that came with my

Western Digital Hard Drive. I selected the old J: Drive as

source and the new J: Drive as target. It performed the

clone without one glitch. However, it took about TEN times

LONGER than Ghost would have!!!

Does anyone have any idea why Ghost 2003 DOS behaved

as it did? AND is there a fix for it?

Thanks in advance.

Big Al

IP Logged

NightOwl

Radministrator

Offline

"I tought I saw a puddy
tat..."

Posts: 5826
Olympia, WA--Puget Sound--USA

Re: Why Does Norton Ghost 2003 Balk At Partition S
Reply #1 - Jun 3^rd, 2006 at 9:13am

Big_Al

I've never run across the issue you have listed--and can not recall anyone else reporting that exact issue either--

Quote:

I used my Ghost 2003 DOS Batch File to automatically do all the partition cloning

That statement could mean so many different things, that it would be hard to know from it what you did! You should post the contents of the *config.sys*, and *autoexec.bat* boot files, and a list of files on the boot disk (? floppy disk ?).

Was this a *disk-to-disk* clone or a *image-to-disk* clone?

It's possible that the partition structure created by Fdisk somehow did not *sit right* with Ghost for some reason--especially if the partition size was *too close* to the limit of what Ghost needed to transfer the data to that partition--Ghost needs/has some overhead requirements for doing a transfer--don't know what those are, but if you are cloning from an image to a new larger HDD and you let Ghost create the partition structure instead of manually doing it with Fdisk, you get a screen where it shows the *proposed* new partition sizes that Ghost has chosen--and you can make adjustments to the sizes at that point before proceeding--but Ghost will not allow just any and all changes you might want--it will dis-allow any changes it doesn't seem to like--and when you change one partition, it may *automatically* change one or more other partitions based on the initial change you want--again, there's no explanation of what those limitations are, that I have found.

____________________________________________________________________________________________

No question is stupid ... but, possibly the answers are Wink

IP Logged

Big_Al

Gnarly

Offline

I love YaBB 1G - SP1!

Posts: 48
Los Angeles

Re: Why Does Norton Ghost 2003 Balk At Partition S
Reply #2 - Jun 4^th, 2006 at 4:26am

Night,

Good typing to y'all again. My auto-clone floppy has:

Autoexec.bat

Command.com

Ghost.exe

Io.sys

Msdos.sys

For Cloning Partitions (Except C & E) From One HD to another

my Autoexec.bat file is:

@echo off
Ghost.exe -clone,mode=pcopy,src=2:2,dst=1:2 -sure
Ghost.exe -clone,mode=pcopy,src=2:4,dst=1:4 -sure
Ghost.exe -clone,mode=pcopy,src=2:5,dst=1:5 -sure
Ghost.exe -clone,mode=pcopy,src=2:6,dst=1:6 -sure
Ghost.exe -clone,mode=pcopy,src=2:7,dst=1:7 -sure
Ghost.exe -clone,mode=pcopy,src=2:8,dst=1:8 -sure
Ghost.exe -clone,mode=pcopy,src=2:9,dst=1:9 -sure
Ghost.exe -clone,mode=pcopy,src=2:10,dst=1:10 -sure
Ghost.exe -clone,mode=pcopy,src=2:11,dst=1:11 -sure

The C: Drive will have already had my latest Ghost Image

put on it right after I FDisked the HDD and the E: Drive

is left empty, as that is where I put all of my files that

I'm going to burn to CD/DVD so I can defrag them before

burning.

>Ghost needs/has some overhead
>requirements for doing a transfer

Wouldn't the Data Lifeguard Tools have the same

requirements?

And don't forget, the F: Drive was already almost 2 Gigs

smaller on the source drive. To be exact, the total size of

the F: was 7830 MBs with 6180 MBs of files and 1650 MBs

of empty space. The target HDD's F: was 7300 MBs of empty

space. I had to move another 500 MBs (to bring it down to

about 5700 MBs) before Ghost stopped bitchin' and did the

clone.

Could adding a config.sys file end this problem? If yes,

do you have any idea of what should be in it?

Thanks again.

Big Al

IP Logged

NightOwl

Radministrator

Offline

"I tought I saw a puddy
tat..."

Posts: 5826
Olympia, WA--Puget Sound--USA

Re: Why Does Norton Ghost 2003 Balk At Partition S
Reply #3 - Jun 4^th, 2006 at 12:16pm

Big_Al

Looks like you are using direct cloning--*partition-to-partition*--you could try creating images of the partitions, and then doing *image-to-partition* cloning to see if that solves the error state.

Quote:

"Target Partition Is Not Big Enough"

I'm guessing that it's not really a *partition size is not big enough* issue--that's probably an *inappropriate* error message in response to Ghost having some other problem with the partition structure on the new HDD--but does not have an *appropriate* error message--i.e. Ghost is *mis-handling* the error state.

You used the work-around of reducing the size of the data on the source partition by approx 500 MB, and that allowed the automated command line to work successfully--could you possibly make the *destination HDD partition* slightly bigger (?--by 500 MB?)--does that work?

____________________________________________________________________________________________

No question is stupid ... but, possibly the answers are Wink

IP Logged

Pages: 1

‹ Previous Topic | Next Topic ›

« Home

‹ Board

Top of this page

	Welcome, Guest. Please Login