Search
Member List
Calendar
Help
iPXE discussion forum
/
iPXE user forums
/
General 
/
No space left on device (http://ipxe.org/34182006)
/
No space left on device (http://ipxe.org/34182006)
|
No space left on device (http://ipxe.org/34182006)
|
|
2018-07-02, 12:05
Post: #1
|
|||
|
|||
|
No space left on device (http://ipxe.org/34182006)
Hey guys,
I'm new in the world of ipxe and was pushed into this topic by a colleague leaving, so please be gentle. I'm dealing with an issue right now that only appears on on newer machines. We are running many HPE G7 nodes and one HPE G9 node. The G7 nodes boot up just fine, but the G9 node runs into an error as soon as it starts to load the initramfs. Quote:nfs://... No space left on Device (http://ipxe.org/34182006) My IPXE script loos the following: Code: #!ipxeAll nodes are equipped with a minimum of 96GB of RAM and boot in legacy boot mode, as the old G7 nodes don't support any UEFI boot. I hope we can figure out whats wrong |
|||
|
|
2018-07-02, 20:16
Post: #2
|
|||
|
|||
|
RE: No space left on device (http://ipxe.org/34182006)
Which of the nfs:// chain lines (kernel / initrd) is it that fails?
iPXE can be built in a few different ways, and for different platforms, so it would be relevant to include the filename of the iPXE binary, or how you built it. I'm guessing that you are using ipxe.lkrn or undionly.kpxe ? (and that it is built for 32 bit and not 64 bit) please note that imgargs will replace what was given on the kernel line, you might want to change that and only use arguments on kernel or imgargs do you also have the filesize of the 2 files being downloaded? Use GitHub Discussions VRAM bin |
|||
|
|
2018-07-02, 20:47
Post: #3
|
|||
|
|||
|
RE: No space left on device (http://ipxe.org/34182006)
Thank you for your fast reply.
The file that breaks is the initramfs. The filename is undionly.kpxe and it is basically build with this command: Code: make bin/undionly.kpxe EMBED=../../boot-datev-node-centos-from-datev01-via-nfs.ipxeI will remove the arguments from the kernel command line, but as all these commands are included in the imgargs line as well, I don't expect any changes. The initramfs.img file is 1.7GB in size, the kernel is only 6MB big. We are handing over the undionly.kpxe by out tftp server. |
|||
|
|
|
2018-07-02, 20:57
Post: #4
|
|||
|
|||
|
RE: No space left on device (http://ipxe.org/34182006)
So it seams that you are simply running out of (available) RAM here,
I would say that what you are seeing is similar if not the same as described at http://lists.ipxe.org/pipermail/ipxe-dev...04793.html To verify what is going on you could build your undionly.kpxe with DEBUG=memmap added to the make line that should print out the memory map of the system and hopefully which segment it is trying to use. There is also the option of building 64 bit images for pcbios, I would not recommend this unless you really need it, but might be worth a try: Code: make bin-x86_64-pcbios/undionly.kpxeIt would any case be interesting if you could post the full output when enabling the memmap debug, and maybe also if there is any difference between 32bit and 64bit builds of iPXE Use GitHub Discussions VRAM bin |
|||
|
|
|
2018-07-04, 21:17
Post: #5
|
|||
|
|||
|
RE: No space left on device (http://ipxe.org/34182006)
Hey,
sadly, the 64-bit version did not help. Here is the debug output: Code: CLIENT MAC ADDR: 94 18 82 0A FC 1C GUID: 30393137-3436-5A43-4A36-333836573946 Sadly this output is a little bit messed up, as the Mellanox Flexboot, which starts right after the normal netboot, fucks up the VSP output. I hope the important information is still visible. I thought about testing UEFI boot, but I need some time to do the research on this, so this will probably happen over the weekend. The nodes failing on the ipxe boot are all UEFI capable. |
|||
|
|
|
2018-07-05, 10:13
Post: #6
|
|||
|
|||
|
RE: No space left on device (http://ipxe.org/34182006)
So, just a short update:
I managed to build and deploy a UEFI version. This works from the ipxe perspective! But sadly, it does not work for me. We are running a Centos 7 which provides a 3.10 Kernel. This kernel version seems to have a bug on UEFI Ramdisk booting: https://forum.ipxe.org/printthread.php?tid=8195 So I still need to figure out what is wrong with my IPXE - node combination in bios mode. But for everyone running into the same problem and using a newer kernel (>3.16) here is a solution which should work: This is my IPXE script: Code: #!ipxeNote the initrd=<name> option in the kernel line. This is required for a UEFI boot system. building this image works with: Code: make bin-x86_64-efi/ipxe.efi EMBED=../../boot-datev-node-centos-from-datev01-via-nfs-efi.ipxeI additionally configured my dnsmasq to send the uefi file only to uefi nodes: Code: # Test for the architecture of a netboot client. PXE clients are |
|||
|
|
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)