Upload only works in DD mode. Please Help!
-
Indeed, I can assign a blank image. That is how I am specifying the dd copy method.
If I assign it to simply upload (with any method) after the pxe boot to the menu the system will loop back to the menu regardless of option chosen. If I do debug upload, the task management works, and it will report to the server that it ran the task then loop back to the shell. If I do debug upload with the dd method selected for the image it will actually do something. It starts uploading.
This is the first image I am uploading.
Some more info on configuration:
Client and server are on a dedicated switch behind a firewall. Communication between client and server goes straight through the switch, management traffic goes across the firewall.Thank you in advance for the help.
Ey3
-
Below are the only config options that actually do anything.
Ey3
[url=“/_imported_xf_attachments/1/1521_Screen Shot 2014-11-26 at 11.33.02 AM.png?:”]Screen Shot 2014-11-26 at 11.33.02 AM.png[/url][url=“/_imported_xf_attachments/1/1522_Screen Shot 2014-11-26 at 11.33.24 AM.png?:”]Screen Shot 2014-11-26 at 11.33.24 AM.png[/url][url=“/_imported_xf_attachments/1/1523_Screen Shot 2014-11-26 at 11.33.56 AM.png?:”]Screen Shot 2014-11-26 at 11.33.56 AM.png[/url]
-
Can you get us videos of the “other imaging types” that are failing?
-
Sure, I will take a video of all the failure scenarios after the holidays. I have it uploading now, and need to get an image up and show some progress.
Ey3
-
I have another step for you to try.
Put the image type back to how you want it: (resizable, multipart, whatever)
Recreate your tasking, but make it a debug task. In the Basic Tasks Options click Advanced Options. Look for Upload - Debug.
When the system boots, it will get you to a terminal. Run the command fixparts /dev/sda
It should ask you a few questions. My suspicion is it’s trying to create a “legacy - mbr” file, but there’s still GPT structures on the disk. So it can’t structure the partition prepared for this.
This is just my guess, I really don’t know at this point. If nothing else, would you be willing to try imaging using SVN?
-
[quote=“Tom Elliott, post: 39408, member: 7271”]I have another step for you to try.
Put the image type back to how you want it: (resizable, multipart, whatever)
Recreate your tasking, but make it a debug task. In the Basic Tasks Options click Advanced Options. Look for Upload - Debug.
When the system boots, it will get you to a terminal. Run the command fixparts /dev/sda
It should ask you a few questions. My suspicion is it’s trying to create a “legacy - mbr” file, but there’s still GPT structures on the disk. So it can’t structure the partition prepared for this.
This is just my guess, I really don’t know at this point. If nothing else, would you be willing to try imaging using SVN?[/quote]
That sounds like a very likely cause given the behavior I have seen.
I will test after the holidays and include the results with the other tests you requested.
I’d be down for testing with SVN, do you have any instructions?
Ey3
-
[url]http://fogproject.org/wiki/index.php/SVN[/url]
this is the developer’s work in progress. it is pre-release. it might be buggy. it is not recommended for a production environment.
use at your own risk. you have been warned.
if you choose to use it, please report any problems, and thank you for beta-testing. -
So I attempted to download the image I took last week and the system is now saying:
BootDevice not found
please install an operating system on your hard disk.
hard disk -(3f0)
f2 system diagnostics
for more information, please visit: [url=“http://www.hp.com\go\techcenter\startup”]www.hp.com\go\techcenter\startup[/url]
Running the diagnostics the hard drive is seen by the bios.
Configuration for download:
host management --> list all hosts --> click on down arrow --> select “[COLOR=#333333][FONT=Trebuchet MS][/FONT][/COLOR][FONT=Ubuntu][COLOR=#555555]Schedule [U]Instant Deployment”[/U] --> reboot box[/COLOR][/FONT]client comes up and goes through PXE then pulls down the linux image and runs the imaging.
client reboots and complains that it cannot see an OS on the hard drive
I am pulling down a linux image right now to take a look at the disk and make sure that something was actually written. Any ideas would be greatly helpful.
Ey3
-
Results of fixparts /dev/sda:
loading MBR data from /dev/sda
unable to read MBR data from ‘/dev/sda’! exiting!
This was on an image download task (On the client I just imaged from the dd image taken in the OP)
Ey3
-
are you still running the same version of fog, or did you upgrade to the SVN version?
if you installed an SVN version, please report exactly what one. it will be in the cloud on the fog web gui in place of the version number. -
I did not attempt an update to the SVN version. I can if you think that will work better.
I was thinking about trying to use a rescue disk to write the MBR. Any thoughts?
Ey3
-
Update. Client will now boot successfully after running the startup repair utility from the windows 7 install disk.
o_O
Ey3
