Hardware Currently Working with FOG v1.x.x
-
Dell Optiplex 7010 with UEFI enabled, not working.
Lenovo L530 with UEFI enabled, not working.Dell Optiplex 7010 with UEFI disabled, working with undionly.kpxe
Lenovo L530 with UEFI disabled, working with undionly.kpxe -
All working systems UEFI disabled single partition realizable.
Fog 1.3.0 SVN 3263 all systems using the base NIC on the motherboard, and default kernel.
2goPC touchscreen laptop
Dell Latitude 2100
Dell Latitude 2110
Dell Latitude 2120
Dell Latitude 3540
Dell Latitude E5400
Dell Latitude E5410
Dell Latitude E5420
Dell Latitude E5430
Dell Latitude E5500
Dell Latitude E6400
Dell Latitude E6500
Dell Latitude E6530
Dell Optiplex 3020
Dell Optiplex 7010
Dell Optiplex 745
Dell Optiplex 755
Dell Optiplex 760
Dell Optiplex 780
Dell Optiplex 790
Dell Optiplex 990
Dell Precision T5500
HP Compaq 8100 S
HP Compaq 8100 V
HP Compaq Pro 6300 SFF
HP Probook 450
HP Probook 4540s
HP Probook 650
HP Probook 6550b
HP Probook 6570b
HP ProDesk 400
Lenovo MT-M 5048
Lenovo MT-M 5049
Lenovo MT-M 7033 -
[url]http://fogproject.org/wiki/index.php/WorkingDevices[/url] should be up-to-date as reported here. If there is something missing please post and I will add them.
-
Hey Guys,
We have a specific issue with imaging Lenovo P700 Model of Workstations.
We have Fog Server 0.32 hosted on Ubuntu 12.04.
Details Below : -
Make : Lenovo P700 Workstation
Model : 30A8A05900
Procesor : Intel Xeon CPU E5-2640 v3 @ 2.60 Ghz[U]SATA Connectors ( SATA 0 is not available ) :- [/U]
SATA 1
SATA 2
SATA 3
SATA 4
eSATA[U]HDDs : -[/U]
Primary :- 180 GB 2.5" 6Gb/s Intel SSD 520 Series Harddisk
Secondary :- 1000GB 3.5" SATA Harddisk[U]Network Cards : - [/U]
2 NIC(s) Installed
[01]: Intel I210 Gigabit Network Connection
[02]: Intel Ethernet Connection I218-LMPXE Version : GE V1.5.55
More Detials on the Machine on below link
[url]http://shop.lenovo.com/us/en/workstations/thinkstation/p-series/p700/#tab-tech_specs[/url]The host registration and image upload is happening fine. But while deploying the image we get a error as “File Partition Not Found”
I have tried updating so many kernels and lates kernel used is
Latest Fog Kernel Used : bzImage 2015-04-13
Due to this issue we are not able to provide a new lot of 100 machines received. Please help me with the issue.
Thanks in Advance
Rahul S Lal.
[url=“/_imported_xf_attachments/1/1903_Thinkstation-specs » Thinkstation P700.html?:”]Thinkstation-specs » Thinkstation P700.html[/url]
-
Rahul,
I don’t know what the issue is, but what I do know is that no kernel is going to fix a missing file for you.
-
Essentially, I’m looking for details. The “File Partition not found” message you’re seeing is coming from FOG? Is it coming from Windows? Where exactly are you seeing this error being reported?
My guess, is this message is coming from windows. Specifically you have a dual hard drive system where the OS lives on the SSD and the secondary hdd is on your main data storage? I’m going to guess, even further then, that the SSD is either not getting the data written to it as expected, or it’s not being structured properly.
-
[quote=“Tom Elliott, post: 45881, member: 7271”]Essentially, I’m looking for details. The “File Partition not found” message you’re seeing is coming from FOG? Is it coming from Windows? Where exactly are you seeing this error being reported?
My guess, is this message is coming from windows. Specifically you have a dual hard drive system where the OS lives on the SSD and the secondary hdd is on your main data storage? I’m going to guess, even further then, that the SSD is either not getting the data written to it as expected, or it’s not being structured properly.[/quote]
Hello Elliot,
Yes, you are right OS lives on 180 GB SSD and Data on 1000 GB SATA HDDs.
I’m trying to upload a Windows 7 64 bit loaded on Lenovo P700 and deploy the same.
Note : Other models of Lenovo, Dell and HP machines work fine.
Please find the Details BelowFOG version : FOG 0.32
OS version : Ubuntu 12.04I searched a lot in fog forums and google and tried with multiple kernels still no luck
What I’m thinking was SATA 0 is not available in this particular model, other models have the SATA 0 in the motherboard, Is that an issue ?
More details on Lenovo P700 machine in the attached files. Is Lenovo P700 Series on workstation supported in latest Kernel ?
The errors in [SIZE=12px]/var/log/apache2/error.log i as below[/SIZE]
[Tue Apr 21 22:24:15 2015] [error] [client <client IP>] PHP Notice: Undefined index: BPM in /var/www/fog/management/ajax/tasks.active.php on line 90, referer: [url]http://<fog[/url] server ip>/fog/management/index.php?node=tasks&sub=active
[Tue Apr 21 22:24:15 2015] [error] [client <client IP>] PHP Notice: Undefined index: timeElapsed in /var/www/fog/management/ajax/tasks.active.php on line 112, referer: [url]http://<fog[/url] server ip>/fog/management/index.php?node=tasks&sub=active
[Tue Apr 21 22:24:15 2015] [error] [client <client IP>] PHP Notice: Undefined index: timeRemaining in /var/www/fog/management/ajax/tasks.active.php on line 11 3, referer: [url]http://<fog[/url] server ip>/fog/management/index.php?node=tasks&sub=active
root@<fog server>:/var/log/apache2#
Thanks in Advance
Rahul S Lal[url=“/_imported_xf_attachments/1/1904_Thinkstation-specs » Thinkstation P700.html?:”]Thinkstation-specs » Thinkstation P700.html[/url]
-
Would you be willing to try the latest FOG revision to see if this resolves the issue?
You don’t have to bother your production FOG server, just build this on the side, then connect it to a mini switch. -
I have the same problem with Lenovo S20. And it seems that an hidden partition is created by the computer, ghost, fog, and clonezilla don’t work with this machine (SAS, Classical SATA, SSD)
-
dumb Lenovos.
-
Fujitsu - M470 - Workstation - Win7 - 1.3.0 - 11/05/15 - Single - Resizable - No sysprep
Fujitsu - R570-2 - Workstation - Win7 - 1.3.0 - 11/05/15 - Single - Resizable - No sysprep - Work with additionnal card or custom ipxe (no drivers in the actuals) UP/DOWN
Fujitsu - R650 - Workstation - Win7 - 1.3.0 - 11/05/15 - Single - Resizable - No sysprep
Fujitsu - W380 - Workstation - Win7 - 1.3.0 - 11/05/15 - Single - Resizable - No sysprep - Work Down with custom image from virtualisation - Don’t work UP (“corrupted gzip stream”)
Lenovo - S20 - Workstation - 7 - 1.3.0 - 12/05/15 - Single - Resizable - Don’t work before 1.3.0 -
Hello Wayne,
As suggested, I have tried a new fog setup with Ubuntu 14.04 64 bit Server and Fog 1.2.0.
What happens now is, as before, the host registers fine and also image upload is fine as well.
But when deploying the image, it will show all initial steps and simply stuck in between and cursor continues to blink. I thought initially its doing some update and waited for further operations, but nothing happened. Eventually when hitting Enter key on the machine it started to deploy but the second HDD which is normal SATA 1 TB disk where as no imaging deployment happens with first HDD which is 180 GB SDD SATA HDD.
This happens only with Lenovo P700 models and all other models work fine. Request you help and thoughts
Attached is hardware details of Lenovo P700 workstations
Thanks in Advance,
Rahul S Lal[url=“/_imported_xf_attachments/1/1995_LenovoP700.png?:”]LenovoP700.png[/url]
-
Those with lenovo’s please try updating to latest SVN.
I’m attempting to use the same methods as we use for GRUB, but for all MBR’s now. It will always load up the first Megabyte of MBR and reload that. Prior images should work as well. Theoretically it should work for OEM Lenovo’s too. SVN 3396 is the rev number in case you’re all wondering.
If anything else is broken, please let me know.
-
Hi Tom,
Thanks for the update.
I am trying updating to latest SVN. @ [url]http://jbob.io/wiki/index.php/SVN[/url]
I get below error when I run the command “svn checkout [url]https://svn.code.sf.net/p/freeghost/code/trunk[/url]”
svn: E000104: Unable to connect to a repository at URL ‘[url]https://svn.code.sf.net/p/freeghost/code/trunk[/url]’
svn: E000104: Error running context: Connection reset by peer
Also tried with “svn co [url]https://svn.code.sf.net/p/freeghost/code/trunk[/url]”, above error returns.
I found that apt-get update works fine and proxy settings are OK.
Thanks in Advance,
Rahul S Lal -
[quote=“Tom Elliott, post: 47392, member: 7271”]Those with lenovo’s please try updating to latest SVN.
I’m attempting to use the same methods as we use for GRUB, but for all MBR’s now. It will always load up the first Megabyte of MBR and reload that. Prior images should work as well. Theoretically it should work for OEM Lenovo’s too. SVN 3396 is the rev number in case you’re all wondering.
If anything else is broken, please let me know.[/quote]
Look my last post, in 3377 - S20 works !!
-
We’re using DNSMASQ here to keep FOG away from our DHCP server, this highlights machines which, although they may work where FOG is on the DHCP server, don’t work where it’s split.
On the working ones iPXE will try to load default.ipxe from the PROXY IP (FOG server) address.
On the bad ones it will try to load default.ipxe from the DHCP IP address instead.Updating the machine’s BIOS doesn’t seem to update the PXE loader, so doesn’t fix things.
I’ve upgraded to build 3482, which (apart from breaking PXE boot until I recreated the undionly.0 link) hasn’t made a difference. Kernel has been upgraded to 4.0.4, still no difference.
WORKING
Dell Latitude D630 (Broadcom UNDI PXE-2.1 v10.0.9)
Dell Latitude E5500 (Broadcom UNDI PXE-2.1 v11.4.1)
Dell Latitude E5510 (Broadcom UNDI PXE-2.1 v11.4.1)
Dell Optiplex 745 (Broadcom UNDI PXE-2.1 v10.0.9)
Dell Optiplex 755 (Intel Boot Agent GE v1.3.35)
Dell Optiplex 360 (Broadcom UNDI PXE-2.1 v11.4.1)
Dell Optiplex 380 (Broadcom UNDI PXE-2.1 v12.2.2)
HP rp5700 (HP Base Code PXE-2.1 v1.0.6)UNSURE
Compaq 615 (Yukon PXE v6.50.2.3) (imaged OK on older build of FOG, now it drops into Windows instead of bringing up FOG menu)NOT WORKING
Dell Optiplex 390 (Intel Base-Code, PXE-2.1 (build 083))
Dell Optiplex 3010 (Intel Base-Code, PXE-2.1 (build 083))
Dell Optiplex 3020 (Intel Base-Code, PXE-2.1 (build 083))
Fujitsu Esprimo E3521 (Intel UNDI, PXE-2.1 (build 083))
HP 500B MT (Intel UNDI, PXE-2.1 (build 083))There seems to be a common theme amongst the ones that don’t boot properly, but I can’t quite put my finger on it…
-
@mspritch This information is greatly appreciated. I’ll work on updating the hardware lists.
Do you know if you’re using undionly.kkpxe or undionly.kpxe ?? What version of FOG were you using when you verified the working ones?
-
@mspritch Can you try using the SVN included intel.pxe file for those systems, or the undionly.kkpxe file?
-
Up until last week we’ve been using a newer-than-1.2.0 build, but I’m not sure what (and whilst trying to dig out the build number I’ve just managed to update that build’s directory to v3500 so can’t tell what it was now). 3285 rings a bell.
We’re currently on 3484, upgraded when trying to troubleshoot these machines. I’ve just imaged a mix of Latitude D630s and E5500s plus Optiplex 745s, 755s and a 380, all using this build. The other ones listed as working all booted on this build so I suspect they’ll image as well (they imaged on earlier builds).
Been using undionly.kpxe, was also until recently using some mod I found somewhere that forced it to ask for the FOG server address before the menu loaded, but that didn’t work either. Can’t find a link to it now but it was on a FOG-related page, possibly something else by Tom?
Presumably because of the ProxyDHCP setup ours doesn’t work unless there’s an undionly.0 symbolic link set up in the tftpboot folder. I’ve added another entry to the PXE boot menu so I can test other KPXEs without trashing the working one, switching between them by pointing the test symlink (in my case intel.0) at the various kpxe files.
These tests were made on build 3484 using a HP 500B PC.
undionly.pxe: Clears the screen and drops to Reboot and Select proper Boot Device
undionly.kpxe: Picks wrong IP address, connection eventually times out
undionly.kkpxe: Same as undionly.kpxe
intel.efi: Hangs at a cursor (Caps Lock still responsive)
intel.pxe: After PXEXT it drops to Reboot and Select proper Boot Device
intel.kpxe: After PXEXT it drops to Reboot and Select proper Boot Device
intel.kkpxe: After PXEXT it gives a PXE-M0F Exiting PXE ROM.
ipxe.pxe: Same as undionly.kpxe
ipxe.kpxe: After listing the (correct) boot server IP it gives a PXE-E79 NBP is too big to fit in memory, then a PXE-M0F
ipxe.kkpxe: As above
realtek.pxe: Same as undionly.kpxe
realtek.kpxe: Same as undionly.kpxe
realtek.kkpxe: Same as undionly.kpxeThe HP’s supposed to be getting redeployed to a school but I’m happy to hang onto it for testing, there are always Optiplex 3010 and 3020 machines in the storeroom that I can do further testing on if need be.
-
WORKING
Dell Optiplex 760
Intel onboard Gigabit Ethernet
Intel Boot Agent GE v1.3.81
4.0.4 kernel
9th June 2015
Resizeable
