Posts made by Tom Elliott

@george1421 The driver is already compiled with this item. That said, ipxe might not have the driver for it. So Kernel is not the problem here, it’s the iPXE Drivers that’s the issue.

@hugo this is the same node that you access the GUI from? Or is GUI different? I ask because I added code that switched from always using http to access node information. If the nodes are all setup without https but you access the GUI with https it would have won’t even display the node in the list. Otherwise I don’t quite now for the moment.

iPXE Developers finally got to look and hopefully have fixed this.

I’ve updated the ipxe binaries directly after pushing 1.5.0-RC-6. Both working and dev-branch have the updates though.

Please re-test and let us know if things are “still” working or if it breaks anything again.

Thank you.

I have been keeping up to date, but leaving my “reversion” code that seemed to fix the problem for users so hyperv gen 2 could still work. Hopefully it now works using iPXE’s own native source code.

See here:
https://git.ipxe.org/ipxe.git/commit/936657832f2262ad04bdf16b9229ce0b1d1c174f

https://news.fogproject.org/fog-1-5-0-rc-6/

@george1421 There’s already functions in place for the hopeful integration of LVM extending through fog (as well as imaging) though I’ve not made any major effort in actually getting this working. You’re more than welcome to have a go at it. The same resizing functions should work similarly. Would you be willing to re-update your init’s to the absolute latest using the same wget commands and seeing if things are a bit better for you?

Just ask, one of the moderators or myself can do so.

@pegasuspc It tells you what file you need TFTP to look at in the installer. The.

Your bootfile is no longer pxedefault.cfg or anything it’s a whole new layout since 1.0.0

https://wiki.fogproject.org/wiki/index.php?title=Advanced_Boot_Menu_Configuration_options

https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu (when you get the bootfile working).

@pegasuspc What does adding ISO’s have to do with it not finding the right pxe boot file?

WOuld you mind looking over: https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq? The article you referenced is for legacy FOG, which with the right changes can still work. This article is newer and more applicable to more modern versions of fog.

@pegasuspc Can you follow the installer’s instructions? Your dhcpd.conf file doesn’t look right. 1.4.4 is NOT 0.32.

@pegasuspc No, the installer tells you so too.

@pegasuspc Did you configure your PXE information for your DHCP server?

Based on what I’m seeing, it has no idea what file to use.

@sebastian-roth I agree, but data is hard to come by, and I don’t think we can come up with every case potential.

@sebastian-roth said in Failure to expand shrunken resizeable image from Linux machines:

./procsfdisk.awk -v SECTOR_SIZE=512 -v CHUNK_SIZE=512 -v MIN_START=2048 -v action=filldisk -v target=/dev/sda -v sizePos=146800640 -v diskSize=146800640 -v fixedList=1:5 in1.txt

Based on the most current this is what I see:

./procsfdisk.awk -v SECTOR_SIZE=512 -v CHUNK_SIZE=512 -v MIN_START=2048 -v action=filldisk -v target=/dev/sda -v sizePos=146800640 -v diskSize=146800640 -v fixedList=1:5 in1.txt
# Partition table is consistent.
label: dos
label-id: 0x77265efa
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     3940352, type=82, bootable
/dev/sda2 : start=     3944446, size=    71485442, type=5
/dev/sda5 : start=     3944448, size=     3940352, type=83
/dev/sda6 : start=     7884800, size=    67425792, type=83

@george1421 It only expands partitions that are “expandable” and not “fixed”. Meaning, if you have 1 ext4 partition, and it shrinks, (say boot here), it will try to expand the partitions somewhat evenly. However, this is not a perfect system, nor has it ever really been. I’ve tried for all I’m worth, but I’m only one man, sorry.

Also, you did update the init first? No need to rerun installer for these tests as it will write the “bad” inits if done.

@xipher what do you mean identical? Of course my test boxes are using the default layout of linux mint, but all are appropriately resizing where my tests yesterday before changes failed in almost the exact same way you described.