PXE Boot Goldmemory
-
Ok I’m perplexed…
I tried another client machine and this one did boot Goldmemory 6.92 shareware. Great!
However, I still get a Ramdisk missing error if I try to use our copy of Goldmemory 7.8 full (FLOPPY.IMG).
The second test client also was unable to boot our iso of Netboot disk with the same error (Ramdisk not found). -
What “ramdisk missing” error?
-
“Could not find ramdisk image: fog/GM/FLOPPY.IMG”
-
Can you verify that the file exists on your FOG server.
/tftpboot/fog/GM/FLOPPY.IMG
Keep in mind that Linux is case sensitive.
Running this:
[code]ls -la /tftpboot/fog/GM/FLOPPY.IMG[/code]
Should return something like this:
[code]-rw-r–r-- 1 root root 1474560 2007-03-23 00:00 /tftpboot/fog/GM/FLOPPY.IMG[/code] -
I can’t access the server over the weekend, as it’s on an isolated network where I work. I’m sure the files are all there though.
As it stands, the only one that loads successfully on one client, is GM 6.92. The other versions simply don’t work on any clients.
I copied several different .iso and .img files to the /fog/GM directory to test. I’ll check again Monday though, if there is any doubt the files might not be there.Is it relevant to mention that I made this modification to the server?
[url]http://www.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]It changes the directory structure a little bit, but I otherwise don’t see how it could bork loading any images.
Thanks for all your help!
-
Is this alright?
[CODE]-rw------- 1 root root 1474560 2010-07-20 00:00 /tftpboot/ltsp/i386/fog/GM/FLOPPY.IMG[/CODE]
-
Any other ideas? I’m high and dry
-
Memdisk with a floppy image is pretty particular with things, have you tried booting from the cd iso?
An entry like
[code]LABEL GoldMemory
MENU LABEL GoldMemory
LINUX memdisk
append iso initrd=isos/GoldMemory.iso
[/code]
should work.btw… in this setup I would have the directory isos under /tftpboot (/tftpboot/isos)
-
Thanks Rixter,
As a matter of fact, I have tried isos too. I get the same result.
Just maybe the append line wasn’t exactly the same as yours.
I thought that booting isos with memdisk was relatively a new thing?I am now in the process of completely reinstalling the server on Ubuntu 10.04 (it was running on 11.10).
I’ll give it a try as soon as I’m up and running again (in between other projects).
Thanks again!
-
It is a fairly new thing.
The problem I always had with memdisk and floppy images was that different vendors handled the pxe stacks differently. Many of my intel machines would work fine, some needed other options to work, and some wouldn’t work at all. From all the reading at the time (this has been a few years back) all the problems were because there is no good pxe standard. I haven’t used it much but gPXE (or is it iPXE now?) might be the first thing you want to load, then pass your other pxe options to it, you will probably get better results that way. From my limited knowledge of this you would probably want to chainload it (according to the ipxe.org website),
[SIZE=4][B][FONT=Lucida Grande][SIZE=18px][COLOR=#000000]Chainloading from an existing PXE ROM[/COLOR][/SIZE][/FONT][/B][/SIZE]
[FONT=Lucida Grande][COLOR=#000000][URL=‘http://ipxe.org/_detail/clipart/chain.jpeg?id=download’][COLOR=#436976][RIGHT][IMG]http://ipxe.org/_media/clipart/chain.jpeg?w=200&h=96[/IMG][/RIGHT][/COLOR][/URL]
You can chainload iPXE from an existing PXE ROM. This is useful if you have a large number of machines that you want to be able to boot using iPXE, but you do not want to reflash the network card on each individual machine.
You can build a chainloadable iPXE image using:
[SIZE=12px] make bin/undionly.kpxe[/SIZE][/COLOR][/FONT]Good luck.