For future people with these problems - this worked. [URL=‘http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/’][COLOR=#737373]http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/[/COLOR][/URL]
Posts made by Buddy
-
RE: Operation Not supported
-
RE: Adding Images Back in
Restarting NFS didn’t seem to help. Not horribly concerned about this one - it only shows itself to us in IT so waiting for one additional boot cycle isn’t that big of a deal. It looks like we are also getting stuck on the FOG boot menu screen though. If I hit enter on the boot from HD then it just starts the timer over. If I hit escape it blinks a “_” in the top left corner.
-
RE: Adding Images Back in
Ok did it again. Ignore the ctrl-c part … It must have just timed out and rebooted. It errors on first boot and then goes and images once it reboots itself.
-
RE: Adding Images Back in
It is a partimage and new development. When it came up with the original error telling me that it was going to restart - I pressed ctrl -c and it rebooted and went through the entire image process - and successfully. I am going to try it again.
-
RE: Adding Images Back in
Yep.
[url=“/_imported_xf_attachments/0/974_ScreenShot544.png?:”]ScreenShot544.png[/url]
-
RE: Adding Images Back in
Checked Case sensitive and that is fine. Checked and verified that rec.img.000,sys.img.000 are both present and they are. Can root be the owner on the rec and sys?
[url=“/_imported_xf_attachments/0/973_ScreenShot543.png?:”]ScreenShot543.png[/url]
-
RE: Adding Images Back in
I think this is talking about that 100MB partition made in win7 but not 100%.
-
RE: Adding Images Back in
It seems to be all of my windows 7 images. They are single disk re-sizable.
-
Adding Images Back in
After the redo and every thing - I think I am back up for the most part. I am adding the images back in but having an issue with my windows 7 images. I am sure this is something simple, just don’t know what to do.
[url=“/_imported_xf_attachments/0/971_ScreenShot541.png?:”]ScreenShot541.png[/url]
-
RE: 040ee119 error on boot
Thank you I will try this in the morning. Getting late now. I will let you know.
-
RE: 040ee119 error on boot
The above was off a dell 390. Just tested them all on hp 8300 elite:
unidonly.pxe - - puts it into a boot loop
All others = operation not supported.
-
RE: 040ee119 error on boot
Just tested them all as well. undionly.pxe throws it in a boot loop (but still gets error (op not sup)- flashes really fast). ipxe.pxe does something new (see image below). The rest just did the operation not supported. The ipxe.pxe error doesn’t make a lot of sense though as seen in second pic the path is correct.
[url=“/_imported_xf_attachments/0/913_ScreenShot535.png?:”]ScreenShot535.png[/url][url=“/_imported_xf_attachments/0/914_ScreenShot536.png?:”]ScreenShot536.png[/url]
-
RE: 040ee119 error on boot
Will check it against my environment to see if it helps me. Will post back tonight.
-
RE: Operation Not supported
Changed the hyper-v network adapter to legacy thinking that just maybe - but nope.
-
RE: Operation Not supported
Ok something new. It appears that non of them are working. They all say operation not supported, but they move past it pretty quickly. Just the 390 and 990 get stuck on it.
-
RE: Operation Not supported
Opt 66 is set to fog server ip. Opt 67 was not on default.ipxe - I was on undionly.kpxe . If I change over to default.ipxe it hangs after getting gateway ip.
Will check out the boot disk in the AM.
-
RE: Operation Not supported
Found mass erase here [url]http://fogproject.org/forum/threads/mass-delete-hosts.10396/#post-29140[/url] didn’t seem to have an effect.