internal stack overflow system halted

[Migration User]

Hi
Ive recently upgraded from gss 1 to 2.01 and im getting theis error:
internal stack overflow system halted
whenever an image restore starts.
I kick off the restore from the console - The client boots into dos starts ghost fine, then this error comes up as it starts to restore the MFT.
Tried in on a few pc's and its the same every time.
Never had the issue on the older version.
Any ideas?
The drive in the pc is a SATA drive, do i have to add any extra switches to my task ?
Cheers

[Migration User]

Hi mgtra,

 

it looks like general protection fault error.

I believe we fixed most of the situations with liveupdate.

however, since you are already using 2.01, it might be something else.

does this also happen when you try to create an image?

also you mentioned that this happens on a few pcs.

what kind of machines are these?

 

also if you can try to use the boot floppy or cd, does it make any difference?

thanks.

 

regards,

James Lee

[Migration User]

Hi James,

It works fine if i use a boot cd. Its only through a ghost cast session this happens.
The painful thing is the drive is then corrupt and i have to pull a drive from another machine boot from cd and ghost disk to disk.
We have two domains/ subnets, the ghost server sits on a machine that can see both subnets. The ghost cast restore works fine in one subnet, in the other i get this message. The PC's are identical in both networks.Could it be some kind of tcp/ip issue ? Im probably barking up the wrong tree, but .... ?
Has anyone else reported this ?

Cheers

[Migration User]

Ive done some more testing on this.
Im pretty sure that theres a bug with ghost.
I have the ghost console installed on a machine a 192.168.0.1 network.
This machine is also connected to a 200.10.10.0 network (2nd card).
Images ghostcast fine to the 192.168.0.1 network
identical machines fail with the stack overflow to the 200.10.10.0  network even though the session starts, so theres no network connectivity issue.
Can anyone please shed light on this for me ?

[Migration User]

Ive sorted this one out .

It was a parameter of the marvell yukon dos driver.
The change was FIX=2 to FIX=1

Hope this can help someone out in future and save them the frustration i endured !