After deploye grub fog 1.2.0
-
hi,
i have a problem
when i restore one image “dell” automatic boot “legacy”
fog boot grub style , after the fog screen pxe i have " [I]launching GRUB begin pxe scan[/I] [I]starting cMain[/I]."
fog 1.2.0 not start windowsneed help please
-
try changing your exit boot type in the boot menu settings
-
hi
3 style pxe :
sanmode : all computer after screen fog white “_”
exite : same san…
grub :all computer perfect boot
grub : bios ----) ipxe —) fog screen — ) Windows 7
after restore one image with fog 1.2.0 = bios —) ipxe —) fog screen --) [I]launching GRUB begin pxe scan[/I] [I]starting cMain[/I]
screen here
[url=http://www.noelshack.com/2014-43-1413907179-img-20141021-165121.jpg][img]http://image.noelshack.com/minis/2014/43/1413907179-img-20141021-165121.png[/img][/url]
-
i have Lenovo computer m72e
-
Maybe there’s a problem with the hdd?
-
computer are new , before resotore : Windows works perfect
i need change kernel for Lenovo m 72e ?
same error this post
[url]http://fogproject.org/forum/threads/stalled-after-imaging-with-1-2-0.11537/#post-35868[/url]
-
in folder images my d1.mbr = 4,0k its ok ?
[url=“/_imported_xf_attachments/1/1442_Capture.PNG?:”]Capture.PNG[/url]
-
and ls -la i have 512
[url=“/_imported_xf_attachments/1/1443_Capture.PNG?:”]Capture.PNG[/url]
-
hi last post .
for this error [I]launching GRUB begin pxe scan[/I] [I]starting cMain[/I]."
make on master computer
boot windows 7 dvd/usb
restore systeme for use cmd
cd /
x : = name usb or dvd w7
x: cd bootx/boot: bootsect /nt60 all
bootrec /fixmbr
bootrec /fixbooti think this error thinkcenter lenovo m 72e/73 use compress mbr for speed boot
fix mbr restore original mbr -
In case it helps someone else, I just had this problem while a USB stick was connected to the computer. Removing it solved the problem.
Buggy? Yes, but at least it makes sense, I guess
-
@Junkhacker This fixed it for me. I changed my exit from the default (Sanboot style) to ‘GRUB Style’. ‘exit style’ didn’t work either. Oddly, this FOG server is a new install post development (in the ‘IT service’ prep sense). During dev on the old test server we didn’t have this issue. Not sure what changed.