Storage node IP address change doesn't get applied
-
@gabbas The picture is cut at the right side exactly where there might be some valuable information at the end of where it says
... Tried on interfaces(s): ...
(haha, found a typo). So I can only give you a very general answer. Usually this happens due to spanning tree on the switch being enabled but the port not set as port fast (if you see an interface mentioned in the output) or the driver for this NIC is missing in the Linux kernel (if ther is no interface name printed). -
@Sebastian-Roth Thanks Sebastian, there is no words after Tried on interfaces, please the full image and also what I get after this message and will be very grateful for your assistance:
-
@gabbas Which kernel do you use at the moment? Please run the following commands on your FOG server and post output here:
ls -al /var/www ls -al /var/www/html file /var/www/html/fog/service/ipxe/bzImage
-
@Sebastian-Roth said in Storage node IP address change doesn't get applied:
Thanks, please see below:
-
@gabbas This is because you are still using the 1.5.7 version of FOG. Your bzImage file is out of date (v4.11.0). You can update your kernel to 4.19.143 (or later) using the web gui, but you still should upgrade to 1.5.9 and the updated kernel will come with it.
-
@gabbas Definitely update the kernel! Better if you update FOG altogether when you have some time to properly backup things beforehand.
-
@Sebastian-Roth Many thanks , I have updated the kernal and now the image capture task is stuck at this screen: Any idea how to get this one going? Many thanks
-
@gabbas You updated kernel and init - which is fine. But for the newer init you need to manually adjust the RAMDISK size setting: FOG Configuration -> FOG Settings -> TFTP Server -> KERNEL RAMDISK SIZE set it to
275000
from the original value of 127000. -
@gabbas OK the updated inits need a bit more memory allocated to them.
FOG Configuration -> Fog Settings -> Expand All
In the TFTP Server section set
KERNEL RAMDISK SIZE = 275000That will increase the size of the ram drive in memory.
-
Hi @george1421 and @Sebastian-Roth , thank you very much for your assistance on this issue. Sorry for delay in replying here as I just completed the testing on my side. Yes changing Kernal Ramdisk size to 275000 worked and I was able to capture the image fine. The image is working perfectly okay now. Many thank and much appreciated, you guys are amazing and very helpful.