pxe booting unbutu using pexlinux & windows deployment service 2008r2

[dureal99d]

I have been racking my brain for literally 2 days strait; day and night in an attempt to get ubuntu to boot using pexlinux via windows deployment services. I have gotten a little ways in that linux does go thru some of the boot code but then i get this message

Begin: trying netboot from my (servers ip address) "the directory i set" then Begin: trying nfsmount -0 nolock - ro (see attached Pic) nfsmount: can't parse IP address? (see attached pic) i have no idea what this means and why my boot is locking up here

245338

I am stuck at the point of no return please help me i know its something i am lacking and or need to reconfigure i just cant seem to figure it out.

oh and i am using & have successfully configured syslinux version 5.01 so i can install windows vista,7 & 8 just fine from pxe boot

any help would be greatly appreciated!!! thanks

[newbie-user]

The client seems to be getting 0.0.0.0 as its default gateway. Perhaps that's causing the problem?

[dureal99d]

gateway not needed as I am not booting to the internet? I also don't need the second dns (dns1) as my first dns (dns0) 192.168.1.2 is being noticed now.

Also i have gotten a tad bit further in that changing it to boot from nfs in this line (see red)

APPEND boot=nfs netboot=nfs nfsroot=192.168.1.2:/Images/Ubuntu/ubuntu-13.04-desktop-amd64 initrd=/Images/Ubuntu/ubuntu-13.04-desktop-amd64/casper/initrd.lz

used to be:

APPEND boot=casper netboot=nfs nfsroot=192.168.1.2:/Images/Ubuntu/ubuntu-13.04-desktop-amd64 initrd=/Images/Ubuntu/ubuntu-13.04-desktop-amd64/casper/initrd.lz

now i get running /scripts/nfs-premount ... done. (which i consider a step forward) however (see screen shot) the server replies with a no such file or directory. I do not understand why this is the case. I assume I have something configured wrong but I just don't know what I have wrong.

245356

As always any help is greatly appreciated.

[newbie-user]

If your nfsroot=192.168.1.2:/Images/Ubuntu/ubuntu-13.04-desktop-amd64, then shouldn't your initrd=casper/initrd.lz?

I think it might be looking for /Images/Ubuntu/ubuntu-13.04-desktop-amd64/casper/initrd.lz inside of /Images/Ubuntu/ubuntu-13.04-desktop-amd64. As if to say the file in question is /Images/Ubuntu/ubuntu-13.04-desktop-amd64/Images/Ubuntu/ubuntu-13.04-desktop-amd64/casper/initrd.lz

[dureal99d]

Hum excellent thought, following your statement i reviewed the config file and well let me show you

kernel Images/Ubuntu/ubuntu/casper/vmlinuz.efi

APPEND boot=nfs netboot=Server1 nfsroot=server1:/Images/Ubuntu/ubuntu initrd=/Images/Ubuntu/ubuntu/casper/initrd.lz

(note)I have changed the install location to make the name shorter, my boot issues maintain the same.

casper/initrd.lz (see orange) is already a part of the config, that unless i am not understanding what you are saying which is quite possible.

i also tried 1 more thing I changed (see red) boot=nfs to boot=server1 & now I get (see pic)

245385

[dureal99d]

OOOOOh I see what you are saying now, you are saying that somehow it continues to look for the needed boot files in the wrong folder.

Mt question is how do i get it to look in the right folder, what do you recommend?

[newbie-user]

Your line should read:

APPEND boot=nfs netboot=nfs nfsroot=192.168.1.2:/Images/Ubuntu/ubuntu-13.04-desktop-amd64 initrd=casper/initrd.lz

So what this is saying is that the nfsroot folder is on the server 192.168.1.2, at the path /Images/Ubuntu/ubuntu-13.04-desktop-amd64. Then the client mounts that location. So to the client, the folder which it finds itself in is the ubuntu-13.04-desktop-amd64 folder. Then the initrd file (initrd.lz) is within the current folder in a directory called casper.

[dureal99d]

Your line should read:

APPEND boot=nfs netboot=nfs nfsroot=192.168.1.2:/Images/Ubuntu/ubuntu-13.04-desktop-amd64 initrd=casper/initrd.lz

So what this is saying is that the nfsroot folder is on the server 192.168.1.2, at the path /Images/Ubuntu/ubuntu-13.04-desktop-amd64. Then the client mounts that location. So to the client, the folder which it finds itself in is the ubuntu-13.04-desktop-amd64 folder. Then the initrd file (initrd.lz) is within the current folder in a directory called casper.

Ok!! I will try this configuration and let you know how it works out.

[dureal99d]

Not working? :frown:

[newbie-user]

Just checking, have you correctly shared the nfsroot directory via nfs?

[dureal99d]

Yes or at least I think I have, perhaps I should try and check it from a Linux system say Ubuntu or the like ie; mint or something