Topics created by Sebastian Roth

@Sebastian-Roth the only reason I’m thinking that is because it’s the only thing I added that I can think of that could be giving the bad sector. I don’t know if it causes issues or not and I’m leaning more that it likely isn’t. But just seeing if maybe it will work?

Well, let’s hope that fdisk is not doing any unnecessary checks causing us issues then… 😉

The function itself looks pretty straight forward, I like it this way.

@Jean-Jacques-Morda said:

In my case, i have severals DHCP on my network and this script (i suppose) make the ipxe boot taking the wrong dhcp server and trying to boot on it. You can see here the dhcp is swapping between 172.31.43.1 and 172.31.37.252. Each time i restart the fog isc dhcp server, it took the good one but each time i reboot the client, 1/2 chance the iPxe took the wrong one because my other dhcp is responding. Is that strange ?

If you already have another DHCP service, configure that one and turn fog’s DHCP off - or - turn off the other DHCP service, and just use FOG’s DHCP.

If you don’t have split-scope configured correctly, you cannot run two DHCP services on the same broadcast domain anyways. You’ll have IP conflicts like crazy.

@Sebastian-Roth said:

Removed from wiki as I don’t feel like anyone really cares about running FOG on a Mac OS X server…

And I feel free and open work should be run on a free and open operating system. Just my thoughts on the matter.

@TheOverseer Sorry, took me a while to get things sorted. Here you can find the current version on github now (still alpha): https://github.com/FOGProject/node-dhcproxy

Should run on linux and windows after installing node.js. Extract the archive and take a look at README file for some more details. Run as root on linux (needed to listen on port 67).

Would be great if you can give some feedback on how this is working for you.

When I used to try to build with IMAGE_PNG it would seemingly fail quite miserably. It should work now for you.

I’ve readded the option and the efi binaries are now all updated as of SVN Version 4031, GIT Commit: 56601f2, and FOG Version: 4704.

Hopefully this is what you all were looking for.

a very edge case… you will likely need to DIY it.

The developers can not program every single configuration, only the one that fits most use cases.

Here’s the same, albeit slightly modified, patch:

[code]Index: src/buildroot/package/fog/scripts/usr/share/fog/lib/funcs.sh

— src/buildroot/package/fog/scripts/usr/share/fog/lib/funcs.sh (revision 2932)
+++ src/buildroot/package/fog/scripts/usr/share/fog/lib/funcs.sh (working copy)
@@ -106,6 +106,12 @@
fi
}

$1 is the partition

+getPartType()
+{

parttype=`blkid -po udev $1 | grep PART_ENTRY_TYPE | awk -F'=' '{print $2}'`; echo $parttype;

+}
+# $1 is the partition

Returns the size in bytes.

getPartSize()
{
@@ -774,9 +780,9 @@

$1 is the drive

runPartprobe()
{

hdparm -z $1 &>/dev/null; if [ ! -f "${1}1" ]; then partprobe $1 &>/dev/null; partprobe $1 &>/dev/null || hdparm -z $1 &>/dev/null; if [ "$?" != "0" ]; then handleError "Failed to read back partitions"; fi

}

@@ -1023,6 +1029,7 @@
local imgPartitionType=“$6”;
local partNum=“”;
local fstype=“”;

local parttype=""; local imgpart=""; partNum=${part:$diskLength};

@@ -1030,7 +1037,8 @@
mkfifo /tmp/pigz1;
echo " * Processing Partition: $part ($partNum)";
fstype=fsTypeSetting $part;

if [ "$fstype" != "swap" ]; then parttype=`getPartType $part`; if [ "$fstype" != "swap" ] || [ "$parttype" != "0x5" -a "$parttype" != "0xf" ]; then echo -n " * Using partclone."; echo $fstype; sleep 5;

@@ -1042,8 +1050,12 @@
clear;
echo " * Image uploaded";
else

echo " * Not uploading swap partition"; saveSwapUUID "${imagePath}/d${intDisk}.original.swapuuids" "$part"; if [ "$parttype" == "0x5" -o "$parttype" == "0xf" ]; then echo " * Not uploading content of extended partition"; else echo " * Not uploading swap partition"; saveSwapUUID "${imagePath}/d${intDisk}.original.swapuuids" "$part"; fi fi rm /tmp/pigz1; else[/code]