Issue Imaging Optiplex 780
-
That’s nothing. Does the system boot past this?
-
I just mentioned the tsc part because when I image the 7010 model (which works fine), that failure isn’t listed.
Anyway…
It gets up to what is shown in the attached image. After that, the machine reboots and just boots to the hard drive, but at this point, the mbr has been modified and it says “Operating System Not Found”…[url=“/_imported_xf_attachments/0/573_20140306_124538_resized.jpg?:”]20140306_124538_resized.jpg[/url]
-
Any ideas on this? I’m trying to get Ghost off of our network, but I need to get the 780’s working first.
-
I guess I don’t understand the issue.
The tsc error you reported is a non-issue. The e2aso error you have on the screen isn’t an issue. Sometimes a takes a minute or two for the kernel to load everything, so there is a wait time. Is it not booting at all?
-
The screenshot I posted above is roughly what I see right before partclone starts up. But, on the 780 it just reboots the machine. In FOG, the task doesn’t show up in the list anymore, and once the machine reboots, it passes right through all of the PXE stuff, like the machine is normally booting to the HD, but it then gets an error as it tries to boot the OS, that says “Error Loading Operating System”.
-
try wiping the partitions and putting a basic NTFS partition on the drive and try to image it again.
if you run the fog compatibility checker what does it say about the drive?
-
Where do I run this from?
-
[FONT=Tahoma]To [/FONT]Run a compatibility test.
[FONT=Tahoma]From the fog PXE boot menu, you will see:[/FONT]
[FONT=Tahoma]Boot from hard disk[/FONT]
[FONT=Tahoma]Run memtest86[/FONT]
[FONT=Tahoma]Quick host registration and Inventroy[/FONT]
[FONT=Tahoma]Perform full host registration and Inventory[/FONT]
[FONT=Tahoma]Quick Image[/FONT]
[FONT=Tahoma]Client system information[/FONT]
[FONT=Tahoma]Debug Mode[/FONT][FONT=Tahoma]A. Choose Client System Information[/FONT]
[FONT=Tahoma]B. Your computer will load another menu and it will look like this:[/FONT]
[FONT=Tahoma]1.) Reboot[/FONT]
[FONT=Tahoma]2.) IP Information[/FONT]
[FONT=Tahoma]3.) Partition Information[/FONT]
[FONT=Tahoma]4.) Check FOG compatability[/FONT]
[FONT=Tahoma]5.) Ping a Host[/FONT]
[FONT=Tahoma]6.) Display MAC Address[/FONT]
[FONT=Tahoma]7.) Show DMI Information[/FONT][FONT=Tahoma]C. Type 4 and press Enter[/FONT]
-
I don’t have the “Client System Information” option… All I see is:
Boot from hard disk
Run Memtest86+
Quick Image
Quick Host Deletion
Debug Mode -
So I had attempted to image through Full Registration originally, that’s why I had that list. I just removed the host and rebooted, and now I have everything that is in your list… EXCEPT… Client system information…
-
What version of FOG do you have?
-
0.33b Revision 1291 (The most up to date as of right now)
-
I know… I’m getting cut by the “bleeding edge” right now…
-
One moment. There may be a typo where the sysinfo isn’t appearing. That’s a simple fix. However you can do the compatibility thing real easy.
Go into debug mode from the option menu.
Once in run the command:
fog.sysinfo
You should be good.
-
I think you’re right Tom, I’m not sure what my revision is on this server right off the top of my head but I know it’s atleast a month old running 0.33b and I have the option but this is before the switch to iPXE and all that.
-
I found the culprit. The value wasn’t set for some reason. It got deleted. Sorry. It’s back in. r1292 released for this issue.
It also updated the TomElliott.config files (32 and 64) for 3.13.6 kernel and the init_32.xz file is truly included now.
Thanks.
-
The bootlooping you’re seeing in the other forum should be fixed now as well.
Sorry, I forgot to check if the tasking was all snapin or single snapin. Basically it found the tasking and sent you into an “imaging” type of task. Sorry about that. It should be good now.
r1293 released to fix this issue.
-
Ok, Thanks Tom!
I ran the Compatibility Check and it says it appears to be compatible with FOG, but at the top, just under the Title, it says “Error: Can’t have a partition outside the disk!”. I’m a little confused on that one.
-
are you trying to image a system that had a larger drive than the system you’re working on?
-
The original image was on a machine that had a 500GB drive. The older has a 250GB, but the actual partition is only 23GB…