Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Warning MBR.bin could not be created when network boot image was sent from ghost Console 11.5

Created: 26 Sep 2008 • Updated: 21 May 2010 | 31 comments

Hi All. Im trying to boot a desktop from a PXE server, using a boot image that was created with Ghost Console 11.5, in order to see it from this Console, and may be able to restore an image that was previous taken. But, when the PC boots from the NIC, takes ip address, and is trying to install the boot image, we received the following error, in the last line:
-Checking for sysprep process ID:1244 name: Device\RAMDISK\
\GHOST\NGCTW32.EXE.
Warning: MBR.BIN could not be created 127.0.01:1346.
Pooling for Bound Server (here the name of pxe server/Ghost server)( it appears 4 times)
and stay there.

Results: the mac address of this PC didn't appear into the default group at console (although my dhcp server was assign a ip address to it) and we can't manage the pc.


Somebody may help us?


Thanks in advance....


[Mørtï-Mørtï]

Note:
We created the boot image using the TCP/Ip network ghost image, preOS: windows PE (default and 512 too)

Discussion Filed Under:

Comments 31 CommentsJump to latest comment

roger_symantec's picture

Hello S.O.S,

 

I present/display the same problem somebody can help us

 

Thanks........

Eugene Manko's picture

Since you are running in Winpe it is more than possible that you either do not have appropriate driver for your NIC or that driver is not suitable to run under Winpe 2.0. Can you Ctrl+C on the agent window and then type ipconfig in command prompt to see whether you have valid ip address and also to ping anything on your network to make sure NIC driver is working.

 

If it is not - I suggest you donwload latest Vista driver from manufacture website and import this driver to driver database using Ghost boot wizard (GBW) and then add this driver to your Winpe from Winpe editor dialog in GBW.

 

Hope this helps.

Morti_Morti's picture

Thanks Eugene, but...there's something I'm not sure about

The warning that we`ve received is about MBR.bin (master boot record...we think that it must be related with an HDD -real or virtual)....

Does it really some relation with the NIC driver anyway?


Thanks in advance....

Morti

Eugene Manko's picture

No - mbr.bin is a copy of your real MBR that ghost client saves before it goes to preos (Winpe or DOS). When your boot to Winpe machine executes ghost MBR code and first thing it does is reverts your old MBR back so that no matter what happened in Winpe you can still boot back to your main OS. Complaining about mbr.bin may be not directly related to mbr.bin (it may be that client was still checking for this file in one place when in fact this file was saved in a different location but it didnt matter anyhow since your MBR was already reverted) but to network connectivity hence why I was asking to check whether you have correct NIC.

 

Thanks.

Morti_Morti's picture

Let us explain something more...
We are working in a lab...for a client who want to deploy images 10-15000 machines (with or without operating system)...
The test machine has no Operating System (and obviously, no Ghost Agent). Of course, we got an image of this machine. But, by now, we only want to start up it from network , in order to see and manage it from Ghost Console...then, later, we will send via multicast the image previously taken..(thinking in the real client environment)....
In your answer we understood (or missunderstood) that it is no possible because (...)mbr is a copy of your real MBR that ghost client saves before it goes to preos.. When your boot to Winpe machine executes ghost MBR code and first thing it does is reverts your old MBR back so that no matter what happened in Winpe you can still boot back to your main OS (...)

¿Does it means that we have to send an image previously taken at the same time that we start up the machine from the network....in order to install the original mbr.bin...?

We made a test in a virtual environment and the test was ok...but in the real not (yet)....

May you help us to clarify it..?

Thanks again



 

Eugene Manko's picture

Let me also clarify some bits and correct me along the way if am wrong.

 

You have test machine that is bare metal. You want to boot it, see it appear in Console and push an image from Console to it. This image contains at least 2 partitions:  Windows and Linux, image MBR contains grub so you can boot either OS. Once image is deployed you want to be able to have it dual boot. Anything mistaken?

 

I specifically ignored having GBP for now because it will just confuse your issue. And also having GBP has no advantage for you anyhow.

 

If everything I recaptured is correct this is what you can do: you create your model machine with two partitions, grub etc. Verify it is dual boot alright. Capture that machine as your model image. Then you boot your test bare metal machine from PXE. This you can create "TCP/IP boot package with ghost client" from Ghost boot wizard. Once this machine is booted into PXE, ghost client agent will run and it will automatically connect to Console. Execute image clone task on this machine with your model image. Once complete your test machine should be identical to your model machine (assuming their hardware is identical).

 

Hope this helps.

Morti_Morti's picture

Here our answer to your questions; please check it.... and thanks for help us.

You have test machine that is bare metal: YES.
You want to boot it, see it appear in Console and push an image from Console to it: YES.
This image contains at least 2 partitions: Windows and Linux: MBR contains grub so you can boot either OS. Once image is deployed you want to be able to have it dual boot. Anything mistaken? Yes: A little mistake: the image MBR contains 4 partitions from a HP desktop : 1st: windows vista 2nd:restore 3rd:ntfs(data) 4th:fat.

If everything I recaptured is correct this is what you can do:
1-you create your model machine with two partitions, grub etc. Verify it is dual boot alright. Capture that machine as your model image. Ready (the four partitions image was taken; and then we formatted the machine and created only one partitions in order to test)
2-Then you boot your test bare metal machine from PXE. Ready. The machine takes Ip address from PXE server and DHCP server.
3-this you can create "TCP/IP boot package with ghost client" from Ghost boot wizard. mmmm: We created using the following method: 1-pre os version: winpe; 2-TCP/IP network boot ghost client image (the last option); and specified the tftp directory..etc.
4-Once this machine is booted into PXE, ghost client agent will run and it will automatically connect to Console:This is the point...here appears the mentioned error: Warning MBR.bin could not be created ....for that reason this machines never appears in ghost console. >This error stills .

5-Execute image clone task on this machine with your model image. Once complete your test machine should be identical to your model machine (assuming their hardware is identical: is identical).: Pending (but we know that we have to do it, because i made it in a virtual environment)...




 

Eugene Manko's picture

Thanks for clarification! Unless I'm mistaken you were saying that you have created master image under Winpe and I believe you are deploying it using DOS package of some sort because this error message is related to DOS only. I will ask our ghost client agent expert to comment on your problem but he is away today so it'll be Monday NZ time. In the meantime can you try using Winpe to restore your image?

 

Thanks.

Eugene Manko's picture

I have asked him to have a look at your post - I dont know when he gets a chance thou. Have you tried Winpe as I suggested to see whether it helps?

Thanks.

Morti_Morti's picture

Eugene....let me explain again...
I`d tried with Win Pe for restore since i`d begin this lab...
(we can not restore the image, because the machine never did appear at console)...
Thanks and regards

Eugene Manko's picture

Hi,

Do you know why it didnt appear? The only reason I can think of was because you didnt have correct Vista driver for your NIC card. Have you tried adding this driver via GBW and re-compiling Winpe?

Thanks.

Morti_Morti's picture

Sorry, but if i know what may be the reason, im not posting here.
Please verify with the ghost specialist as soon possible.....

Thanks

Eugene Manko's picture

We are all ghost developers here :) We are not paid to do this but we just like helping our users. Person I was referring to was responsible for ghost client agent software.

 

You still havent given me the answer - have you tried using Vista (not XP) driver for your NIC in Winpe? This could be your problem - device ID could match and it will allow your machine to go to Winpe, but certain XP drivers do not work under Vista. Winpe 2.0 that GSS 2.5 is using is Vista-based.

 

Cheers.

Morti_Morti's picture

And we apreciate your help very much.
We tried with Windows Vista NIC Driver...but the results were the same.
The nic model is Intel 82566.
Thanks...

SN's picture

Hello,

 

I was wondering if anyone had come up with a solution to this problem?  We are experiencing it also, with exactly the same error message.

 

I am trying to boot from a Dell Vostro 1510 laptop.  I have added Dell's 32bit Vista driver "Realtek RTL-8100C Ethernet Controller" to the WinPE-512 PreOS.  This driver was obtained from:

 

 http://support.ap.dell.com/support/downloads/download.aspx?c=nz&l=en&s=lca&releaseid=R179542&SystemID=VOS_N_1510&servicetag=C1WSX1S&os=WLH&osl=en&deviceid=15607&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=1&libid=5&fileid=244439

 

The Dell download is an exe, so it needed to be expanded, and the .sys file location used when adding the driver to WinPE-512.

 

As suggested earlier in this post, I did try an ipconfig, and no IP address was listed.  I am also unable to net use to network locations, so it does indeed appear that the network driver is not loading or not working.  However, when the laptop first boots, it does obtain an IP address from the DHCP server.

 

As with the original poster, the laptop does boot to the Windows Boot Manager menu, and from there I am able to select the boot image previously created using Ghost Solution Centre's Ghost Boot Wizard.  Windows then boots from the network, until after about two minutes, I recieve the error as stipulated in this post.

 

I have successfully take an image from the a laptop of the same model, and that process worked ok.

 

Many Thanks in advance.

 

Regards,

 

Simon

Krish Jayaratne's picture

Hi SN,

 

The MBR related message is not an error when booting from PXE. This is only used in Virtual Partition.

 

The real issue is not getting an IP address. When you start boot from PXE, it obtains an IP address by contacting the DHCP using PXE driver. However, this is not transferred to WinPE. It completes the load of WinPE image and boot to it. At that point, WinPE again obtains an IP address from DHCP server by contacting it using WinPE driver. Now, if the WinPE driver is not loaded successfully, you will end up with the loopback address.

 

Not getting anything from ipconfig is a sign of not having a driver too. 

 

After installing the Realtech driver to WinPE-512, did you recreate the PXE boot package? You need to do it since the wim image used is not dynamically updated. I suspect this could be the case since the drivers from the vendor usually works.

 

If you have already done it and still having the same issue, could you let me know the PCI ID of the network card? You can get this by selecting details tab in driver properties from device manager. There is a possibility that Windows using a different driver for this due to some reason, we can find out more from PCI ID.

 

Krish

 

Simba's picture

THIS IS GREAT!

Had EXACT same issue ,added the NIC drivers to Image in GBW and now error is gone.

 

Client now continues but now says "sending status to..." and "acknowledged by ..." but still doesnt show in Ghost Console. Ive waited 5 minutes now but excited got past error mentioned in this post.

 

One issue down, lets tackle the next one:-)

Simba's picture

The client shows up in the Ghost Console now, just wasnt in the right group I'd defined while creating the boot image.

mattypeterson's picture

Simba and Krish,

I am having the same problem. I boot to WinPE and then I also get the "MBR.BIN could not be created" error message. But then it continues after that. I get to the "sending status to" and "acknowledged by" messages and it just keeps looping over and over. What did you do to resolve the issue? Thanks.

Krish Jayaratne's picture

Hi Simba,

 

If the machine was in Console before, it will not add the machine again but activates the previous machine in Console. In that case, machine will not go to the intended folder. Did you have the machine in Console before?

 

Krish

 

Simba's picture

Hi Krish,

you're right, was a test machine which had the Console client before.

I unpacked a brand new out-of-the-box machine and this one showed up in consolewith name=mac addr.

I created a clone task (using .gho image saved on server) including rename computer, ghost walker and join domain.

All in all worked fine but now have some othe questions:

1) How does rename computer configuration work? I aim to have an incremental naming e.g. asset001,asset002,asset003 etc. In test I simply used computer name asset001 but result asset00100000008

2)How do I "install Ghost executable" as documentation says to a model image?

When I run the clone (restore image to bare-metal client) task from ghost console I need to see status of new machine in the ghost console.

Krish Jayaratne's picture

Hi Simba,

 

For the computer name, you can specify a prefix and * characters. Stars will be replaced by the unique ID of the computer. ID is the number Console allocates when the machine is added to the Console. This remains the same unless you delete the machine and re-add it. In your last test, did you specify lot of stars? It will use leading zeros in ID to match the number of stars.

 

Do you mean installing Ghost Client to the Model machine? You need to install the client in the model machine before creating the image. This will allow you to remotely create the image as well as make the new clients communicate with Console once image is deployed.

 

You can get a step level progress by double clicking the task in the task pane.

 

 

Krish

 

 

Simba's picture

Thanks Krish,

I'm looking into using answer file right now as I've seen the way GC names computers is not really satisfactory for us. You"re rights about the stars, I did specify a lot of them by mistake but still I would prefer an "incremental" count.

I will also install the ghost console to the Model machine.

Krish Jayaratne's picture

Hi Simba, 

Probably it is a typo - you have to install the Ghost Client in the model machine, not the Console. 

The way it allocates numbers are kind of incremental. Console increments the ID when it finds a new client. It is difficult to use an incremental number per task since there is no way to find out if the number is already used by a different task. So it uses the ID, which is an incremental number for the whole Console. 


Krish


Simba's picture

Hi Krish,

it was a typo. I've got it pretty well figured out now and moving on.

I'm now using sysprep for the computer name and joining domain. We need to have the pc name equal asset tag thats why.

Krish Jayaratne's picture

Hi Simba,

 

There is another way to apply arbitrary names computers using a script. I have published an article in Juice, have a look at http://www.symantec.com/community/download/6550/applying-computer-names-based-mac-using-gss-tool-ghconfig and give a try if you like.

 

Krish

 

 

Dnice808's picture

Thank you for responding to these forums as they seem to be our only resource while trialing!
For the past 2 weeks I have been slaving on this "MBR.BIN could not be created" error without resolution!  I have tried basically everything and cannot understand what could be wrong at this point.  Please let me explain what I have done to try to get past this issue.

I am running GSS 2.5 trial
With WinPE, I create a custom WinPE-512 and add the Vista nic drivers for both the Ghost Console/Server and the client machine (I am not taking any chances!).  The WinPE recompiles I am ready to create the client.  This went through fine without errors after I used Live Update to patch the main apps to build 2165.  at first when I ran the updates, the files never changed, but I found a folder in the Ghost folder called patch that had a batch file that allowed me to apply it from there and I did.  So far so good!  I create the boot image and it seems that I am ready to go.  I use PXE and it finds the machine and begins loading WinPE on the macihne.  Once it is there it begins loading what it is supposed to and then the MBR.BIN error message come up and the machine begins polling again.  Based on your advice you say it is a problem with the nic driver and WinPE.  I have changed the nic drivers to older, to newer, and even have switched to 3 different PC's that all have different nics!  After WinPE connects and the MBR.BIN error pops up and it begins to poll, I cancel out using Ctrl + C and I find that I still have an IP address.  I am at a loss...

808     

Krish Jayaratne's picture

Hi,

Not being able to create mbr.bin is not an issue when booting from PXE. What happens after that is not related to the message.
In your case, it is polling for the server. What is the IP address it uses? Is it the local host address (127.0.0.1)? If that's the case, NIC driver is not correct. However, if you have a different address and actually you can access the network, it looks like it cannot find the server for some other reason.

Is the server running correctly? Can you run other tasks on Windows clients if you have any?

Krish 

Dnice808's picture

Whether the server is running correctly could very well be the case.  Is there some special best practice for configuring the GSS?  I have the machine (GSS is running on a Desktop) set as a static IP and the server and the host are both on the same vlan, though with the main project I am trying to prepare for, all of the machines will not be on the same vlan.

Krish Jayaratne's picture

Hi,

This setup should be sufficient, but have you configured all the services (WINS, subnetmask, Gateway etc.) when setting up the static IP? Could you install a client in a windows machine and see if it works?

Krish