Welcome, Guest. Please Login
 
  HomeHelpSearchLogin FAQ Radified Ghost.Classic Ghost.New Bootable CD Blog  
 
Page Index Toggle Pages: 1
Send Topic Print
"Partition not large enough during NTFS load." Ghost boot disk fails (Read 13754 times)
Ranger
N00b
Offline


Carbon14 in coal... fetch
dino, fetch!

Posts: 8
Sydney


Back to top
"Partition not large enough during NTFS load." Ghost boot disk fails
Apr 17th, 2008 at 7:46pm
 
Hi Guys, this is my first post.

I've been using Ghost since before 2003.  According to a .txt file on its diskette, I use "Version: 2003.775...", but, have I been using this diskette to do the impossible? I see it's not suppose to work with SATA HDDs.  Mine does on my older SATA/ PC, but not on the new.  "So what's a gonin' on, eh?"

I have successfully been able to Ghost a 320GB SATA drive with 10 (ten) partitions using this version routinely for a couple years years. The partitions (P) are:  P10 & 9:8GB; P8 & 7:9GB; P6 & 5:10GB; P4 & 1:12GB and P3 & 2:110GB.

I have always found a multiple partition strategy most effective for progressively building (and maintaining) my system.  I add programs and tweaks to the C: drive (P1) and clone each major stage starting with the base OS (Win XP SP2) going to P10, right through to a final customised image of P1 going to P4.  

There's never been a problem, it always work brilliantly, plus, several times a month I might 'refresh' the C: drive (P1) with its squeaky clean image from P4.  My system is always optimised and hopefully free of any hidden hitch-hikers or links to who knows where.  So what's the problem?  

Well, wanting to explore networks at last, I recently built another PC, upgrading from my P4 socket 478 (at last) to a Q6600 on a GA-EX38-DQ6 with a 500GB SATA.  I did my 10 partition (and format) thing using Win XP SP2 immediately after installing it.  Relevant partition sizes are: P10 & 9:10GB; P8 & 7:12GB; etc.

I booted from the Ghost 2003 diskette to clone the base OS from P1 to P10, it went fine. I then restarted the PC from its HDD and loaded the motherboard drivers from the Gigabyte CD.  I restarted using the Ghost diskette intending to clone this iteration from P1 to P9. However, Ghost just frooze.  A title (I think) and the egg-time was all I got to see.

After looking at the Ghost diskette I've been using all these years, I discovered the version along with an "Error Number: (653) Message: Partition not large enough during NTFS load. Operation aborted at user request. Version: 2003.775 (Aug 14 2002, Build=775)"  (10GB not enough? I don't think so.)

Anybody got any ideas how I can get back to using my time honoured routine of booting from a Ghost DOS disk and cloning each incremental installation for my new system build please?   Ranger. Smiley
 
 
IP Logged
 

Rad
Radministrator
*****
Offline


Sufferin' succotash

Posts: 4090
Newport Beach, California


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #1 - Apr 17th, 2008 at 10:29pm
 
Well, first off, I like the way you think.

Quote:
I have always found a multiple partition strategy most effective for progressively building (and maintaining) my system.

Motherboard drivers contain disk controller drivers, so I'm guessing there's the source of the problem (compatibility).

Next, since you have Ghost 2003, you should (try to) update it to v793, which is latest. There are threads here which discuss doing this. See if this helps:

http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1206707882

When you say this:

Ranger wrote on Apr 17th, 2008 at 7:46pm:
I restarted using the Ghost diskette intending to clone this iteration from P1 to P9.

.. does that mean create an image? (I use the term clone specifically for a duplication process, not image creation.)

Then I was reformate the destination partition to FAT32 and see if that does anything .. just as a datapoint.
 
WWW  
IP Logged
 
Ranger
N00b
Offline


Carbon14 in coal... fetch
dino, fetch!

Posts: 8
Sydney


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #2 - Apr 18th, 2008 at 1:31am
 
Hi Rad and thanks for your comment, links and question.
Re your question "... does that mean create an image?"  
From what I understand (and feel free to correct me),  I thought using Ghost to 'Ghost' from one partition to another, copies absolutely everything resulting in some kind of 'mirror image' of the source partition.  
Re differentiation of your terms "duplicate" v "image creation", I'm not sure what you mean.   Please elucidate.
I'll get on with "(try to) update it to v793" via your suggested link and keep an eye out for your reply.
Regards, Ranger   Roll Eyes
 
 
IP Logged
 
Rad
Radministrator
*****
Offline


Sufferin' succotash

Posts: 4090
Newport Beach, California


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #3 - Apr 19th, 2008 at 1:04am
 
partiton to image
or
partition to partition?

do you create a *.gho file (image)

that's usually the best way to back-up.
 
WWW  
IP Logged
 
Ranger
N00b
Offline


Carbon14 in coal... fetch
dino, fetch!

Posts: 8
Sydney


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #4 - Apr 19th, 2008 at 4:09am
 
Hi Rad,
"partition to partition" ... Strangely, I'm not after a back-up, just a complete mirror image of whatever's there.  I thought this might be a better back-up.  I want to keep it dumb-arse simple.  As simple as my horse could do IT.
Ranger. "Yipee Hi Ho."  Wink
 
 
IP Logged
 
Rad
Radministrator
*****
Offline


Sufferin' succotash

Posts: 4090
Newport Beach, California


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #5 - Apr 19th, 2008 at 8:28am
 
partition to partition is what i call a "clone".

if you are using it for a back-up, this method can introduce problems, such as two drives having the same identifiers,, especially when that partition contains an OS.

cloning is usually reserved for those times when you want to REPLACE one drive with a new, bigger, faster one.

otherwise creating a back-up image is actually much simpler, plus saves you space.

is there some reason ..other than back-up .. for which you want to create a clone?

i don't know anyone who uses a clone for back-up purposes. and because we have so little experience with this method, it makes it more difficult to troubleshoot.
 
WWW  
IP Logged
 

Ranger
N00b
Offline


Carbon14 in coal... fetch
dino, fetch!

Posts: 8
Sydney


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #6 - Apr 19th, 2008 at 10:32am
 
I agree.  It's a clone. That's all I've ever done with Ghost, for more than a decade.  Clone.  Works for me.

The process I've used is always very simple.  I reboot with the Ghost PC-DOS diskette, select the source, select the target and clone.  For cloning (stored) data I usually have an identical but slave HDD installed.  The data is cloned from partition 2 to partition 2.  I just overwrite the old with the new.

This second HDD (slave) is partitioned in exactly the same manner as the first (master), except the primary active partition 1, the C: drive has no operating system installed.  The operating system on the slave drive is present as a clone, but only on the E: drive, i.e. partition 3.

I'd still like to know how you upgrade Ghost 2003 from v.775 to 793.

Ranger
 
 
IP Logged
 
Rad
Radministrator
*****
Offline


Sufferin' succotash

Posts: 4090
Newport Beach, California


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #7 - Apr 19th, 2008 at 10:56am
 
have you seen?

http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1201902207

just cuz u have done something a certain way in the past, doesn't make that way better/good.

precedent is a poor justification for methodology.

what about upgrading to ghost 14?
 
WWW  
IP Logged
 
Ranger
N00b
Offline


Carbon14 in coal... fetch
dino, fetch!

Posts: 8
Sydney


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #8 - Apr 19th, 2008 at 11:47pm
 
Hi Rad, you said: "just cuz u have done something a certain way in the past, doesn't make that way better/good."  I couldn't agree more.

However, when you went on to say "precedent is a poor justification for methodology."  With respect mate, that doesn't make sense; here's why.

"Precedent" means "any act, decision, or case that serves as a guide or justification for subsequent situations." Precedent IS justification for doing things a better way.  Even from a legal perspective, "precedence" is actually a form of proceeding (which) serves as an authoritative (usually better/ fairer) rule or pattern in future similar situations.  

"What about upgrading to Ghost 14?"  That sounds like good advice.  But I'll need to check out whether Acronis "clones" from partition to partition on the same HDD?  A read some reviews.

In the meantime, thanks Rad and thanks also to edarnell; Christer and Jer (... jerliz).

And hi Jerry, (Jerliz)

I like to way you build a system.  I have multiple partitions with clones of each progressive build so I also (hopefully) don't have to go right back to the start if something goes wrong.

Unfortunately it's what I'm contemplating after trying to follow 'instructions' re "How to obtain program updates that are archived on Symantec LiveUpdate server."  http://service1.symantec.com/Support/sharedtech.nsf/docid/2007010219171513.  Despite what others report, for me it's been a dead loss.

Be careful with the 'instructions' you find at this link!  From what I see unfolding as I work with Win Ghost 2003, the symantics just don't line up.  From my perspective, it's seems like more of the usual 'Ghost writer' who seemingly doesn't understand the process or have the skills to explain what they are doing. The program itself is probably fine, it's just that good instructional writing is such a specialised process and seemingly rarely employed by Symantec for Ghost 2003... (It's what I've found, for other's, maybe it's very different.)

Here's how I got myself into trouble:

Using my Norton System Works Pro Edition CD, I installed Ghost 2003 to both my old and new PCs.  The older one has a decent Gigabyte mobo, a P4 CPU & Seagate (ST3320620AS, 7200.10) 320GB SATA HDD.  The new one has a GA-EX38-DQ6, Q6600 & Seagate (ST3500320AS, 7200.11) 500GB SATA HDD.

Using Ghost 2003 v775, despite some alleged impossibilities of this, I have not had a problem using Ghost 2003 (PC-DOS diskette method) to clone any partition to another on the same HDD with the 320GB SATA.  However, I have had a problem attempting the same on a 500GB SATA with a newer mobo.

Regarding my trusty P4 system.  Until yesterday, I had always loaded Ghost 2003 from a PC-DOS diskette, however, last night I installed Ghost 2003 Win XP I have now cloned a partition initiating Ghost 2003 from within a Win XP SP2 installation. I also installed Ghost 2003 to my newer Q6600 system.  Everything seemed to go fine until it automatically restarted with Ghost 2003's DOS based screen.  All I saw of the first screen was a title and frozen egg-timer. When I rebooted all I got was:

Verifying DMI Pool Data
Boot from CD/ DVD
Starting PC-DOS

PC-DOS 7.1 Startup Menu - 1) Run Norton Ghost DOS Operation, 2) Retun to Windows without running Norton ghost.  Enter a choice. [1]"  after listing the Microsoft specs for the mouse driver, etc., the screen continued to read, "The previous operation has failed.  Please enter the number of the action you wish to take:  1) Exit to DOS 2) Return to Windows 3) Retry the operation.  If no action is selected the computer will return to DOS within x seconds."

But it didn't and frooze at this point.
Even if I chose the option to reboot to Windows by typing "ghreboot" and hitting enter (as instructed) it was still dead.  I atempted to scoll down with the down arrow and a new message appeared

"Internal stack overflow.  
System halted."  

So now I have a new system that's locked into doing something that Ghost initiates on reboot - regardless. Great, that's the main reason I didn't want to installing Ghost to my hard disk drive, preferring instead to use a bootup disk.  That's precisly why I want to optimise the boot disk method.  Can anyone help please?

So how do I get this thing that died, aka 'the Ghost' out of my new system? When I boot up I'd like to be able access Win XP again?  Any suggestions (with instructions) I can follow?

Regards, Ranger.  
 
 
IP Logged
 
Rad
Radministrator
*****
Offline


Sufferin' succotash

Posts: 4090
Newport Beach, California


Back to top
Re: "Partition not large enough during NTFS load." Ghost boot disk fails
Reply #9 - Apr 20th, 2008 at 12:07am
 
Just read the first part, but I think you're waxing semantically. My intention was for the two statements to be synonymous. Maybe I choose a poor word, but you get the gist.

If it works for you, you're obviously doing something right.

But I've been doing wedsite stuff since 2000. Just recently have I delved into web design on professional level. Easy to see that, altho I have been able to accomplish much, I've been doing things the hard way. So much easier when you know the technology.

http://blogs.radified.com/2008/01/andy_budd_css_mastery_book_cascading_style_she...

That's what I'm saying.
 
WWW  
IP Logged
 
Page Index Toggle Pages: 1
Send Topic Print