Unable to boot to some PXE ROM
-
It sounds like you are trying to do MBR style image setup, but there’s likely still GPT structures on the disk.
If you would, you could recreate the upload task, but enable it as a Debug task. If you’re on the Latest SVN (sorry I forget which specific rev that I added this feature) it’s as simple as clicking the checkbox for Schedule task as a debug task. Then you can boot the client and be brought to a prompt. You would then run fixparts /dev/sda. Confirm the settings as needed and then run the command: fog. It should go through the processes although you will have to press enter a whole bunch of times.
If you’re running a released version (i.e. FOG 1.2.0, FOG 1.10, etc…) you can do the same type of thing, but you have a few extra steps rather than just clicking a checkbox. You would select the host, choose Basic Tasks, then click on Advanced Tasks. You will see a tasking in that area that displays Upload - Debug.
Hopefully this part helps.
-
If you’re able to, can you please upgrade to trunk? I know this isn’t recommended as “production quality” but I’ve attempted to add in an auto-fixparts capable system. While I don’t know 100% it will work, I do need some testers. The information I gave above is still valid should the init fail to do it directly, but I’m hoping for a miracle that might help Many more users including yourself.
-
[quote=“Tom Elliott, post: 40980, member: 7271”]
If you would, you could recreate the upload task, but enable it as a Debug task. If you’re on the Latest SVN (sorry I forget which specific rev that I added this feature).Hopefully this part helps.[/quote]
Here is probably where I am going to need lots of help. I am not sure what is the SVN or how to even download/install it on the system. If you can kindly provide me with a brief on how to I will be more than glad to proceed so. I am using FOG 1.2.0 so far.
The other thing that comes to mind is to rebuild the machine again from scratch and see if it will upload the file. I don’t think I have tried that route and as you mention I might have some GPT. I will low format the drive and do it all over again just to make sure it is doing it from scratch.
-
-
[quote=“Tom Elliott, post: 40985, member: 7271”]If you’re able to, can you please upgrade to trunk?[/quote]
Absolutely!!! I can do anything with the system but, how? What do I need to do to upgrade the trunk? I think this is part also of the SVN which I know nothing about it. Any help appreciated.
-
[quote=“DarkEnergy, post: 41015, member: 26785”]Absolutely!!! I can do anything with the system but, how? What do I need to do to upgrade the trunk? I think this is part also of the SVN which I know nothing about it. Any help appreciated.[/quote]
[url]http://fogproject.org/wiki/index.php/Upgrade_to_trunk[/url]
-
I have this issue occuring again but only on laptops and only when they are not on my domain. It’s really weird. If I push an inventory request or an image deploy pxe will work perfectly fine. If I just want to boot into windows it gives me an input/output error. My apache error log references line 774 in BootMenu.Class.php file[($StorageNode = $StorageGroup->getOptimalStorageNode();]. If my laptop is on the domain this error does not occur.
-
Are you on the latest SVN?
-
I’m on SVN 2873.
-
Can you update to the latest SVN? We’re nearly 100 commits ahead.
-
Sorry for the long break; many things going at work. I finally was able to do the update but I haven’t test the upload yet.
Tom:
Do you want me to do the BTSync too? I will be testing it fully tomorrow or the day after. Please let me know if there is anything else you want me to do. -
Update after updating the trunk as requested.
Since I got a new laptop with too much bloatware it was very much given to install Windows from scratch. Here is the procedure that was follow:
Created an original image from the original installation = Success
Configure Legacy
Disabled secure boot
Enabled PXE
Installed Windows 8.1 from scratch by:
Booting from USB bootable stick
Deleted all the partitions
Installed Windows 8.1
Created an image from the new installation = FailedThe error is the same, invalid partition table. I am starting to wondering if it has something to do with the installation type. Both systems having the issue, Acer Veriton M2611G and the Lenovo Touch B50-30 are experiencing the same issue if a Windows 8.1 clean install is perform or is it just the FOG does not recognize the new partition table? In either case the image creation failed.
Hopes this help to find a solution to this issue.
-
i’m betting there are leftover GPT bits that are confusing fog. windows doesn’t do a very good job cleaning things up.
run a debug task then run
fixparts /dev/sda
y
w -
Update:
I was persuaded by Junkhacker about the GPT table left over so, using gparted all the partition were removed from the disk and reinstalled windows from scratch and surprise! It did not work! I am beginning to think it has something to do the way FOG handle the partition table when Windows is installed from the original CD/DVD/USB image. To make this even more clear, a Lenovo Touch B50-30 with the original image was able to be image from FOG and the image was uploaded to the server, however, after destroying the partition and installing Windows 8.1 from scratch and retried to upload an image, the problem presented itself again with the same error; invalid partition table blah, blah, blah.
-
The disk you’re attempting to image, is it smaller than the original source disk?
-
[quote=“DarkEnergy, post: 42451, member: 26785”]
I was persuaded by Junkhacker about the GPT table left over so, using gparted all the partition were removed from the disk and reinstalled windows from scratch and surprise! It did not work![/quote]
What?!
i asked you to follow a very specific set of instructions, and expected you to report back the results. This would not have required you to rebuild the image from scratch. -
[quote=“Junkhacker, post: 42474, member: 21583”]What?!
i asked you to follow a very specific set of instructions, and expected you to report back the results. This would not have required you to rebuild the image from scratch.[/quote]I don’t care doing the extra work as long as it is working correctly. The point I was trying to make in the update was: By writing zeros to the drive there is nothing left and the drive was restored to factory default eliminating any other guesses.
-
[quote=“Tom Elliott, post: 42452, member: 7271”]The disk you’re attempting to image, is it smaller than the original source disk?[/quote]
I am not sure what are you asking. These are two new systems that I blew away. I removed the image from factory and performed a clean install to remove all the nasty bloatware that comes from the factory (i.e. Lenovo, HP, Dell, Acer, eMachine, etc.). Then an image is made out of the new install for further deployments.
I am not sure if I actually answered your question.
-
[quote=“DarkEnergy, post: 42520, member: 26785”]I don’t care doing the extra work as long as it is working correctly. The point I was trying to make in the update was: By writing zeros to the drive there is nothing left and the drive was restored to factory default eliminating any other guesses.[/quote]
Yes and no.
Have you tried running fixparts on the drive? Is the size of the drive smaller than the size of the drive you were originally creating the image from (if this is a non-resizable image)?
-
[quote=“Tom Elliott, post: 42522, member: 7271”]Yes and no.
Have you tried running fixparts on the drive? Is the size of the drive smaller than the size of the drive you were originally creating the image from (if this is a non-resizable image)?[/quote]
I think you are asking wrong question. I am not downloading and image, I an creating a new image from scratch. Meaning, got the systems, destroyed all the partitions, installed windows 8.1 directly from disk, then create a new image into FOG. I think you might be in the wrong track as I am not downloading and image into the HDD but uploading a new one into FOG.
I haven’t use fixparts in the past so, I am not familiar with it. I will have to investigate to find out what it does. However the point I was trying to make was that two different systems having the same exact issue. What are the odds? One Lenovo and one Acer. I can do the same in a third computer and see what I get. Most likely the same issue. In every system that was blew away and installed from scratch the image failed.
