Mageia forum

Hi ,

sorry for my poor english...

I hope that is the correct place for this post, and apologize me if not.
I try to boot Mageia2 on PXE diskless client from lan nfs serveur : (192.168.0.10 in this exemple)

To create testinitrd with nfs support , i run dracut with :

Code: Select all

dracut -f   -d nfs -d network  /home/urg/mageiaOnNfs/mageia2/boot/testinitrd 

(where /home/urg/mageiaOnNfs/mageia2/boot/ point to correct tftp boot place)
and generate directly testinitrd in correct tftp folder.

192.168.0.10:/tftpboot/mageia2/boot/loopbacks is a nfs shared export folder in wich i have copied the mageia file system.

create a new entry in : tftpboot/pxelinux.cfg/default

Code: Select all

LABEL Mageiatest
KERNEL mageia2/boot/vmlinuz-3.3.6-server-2.mga2
APPEND initrd=/mageia2/boot/testinitrd rd.neednet=1 rd.driver.pre=nfs rootfstype=nfs root=nfs:192.168.0.10:/tftpboot/mageia2/boot/loopbacks:-t rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 vga=788

note that some another tftpboot folders entries runs perfectly with other linux distribution (SliTaz, ubuntu) on this server.

when client boot with this entrie i get this error :

Code: Select all

dracut : FATAL: don't know how to handle 'root=nfs:192.168.0.10:/tftpboot/mageia2/boot/loopbacks'

nfs seems not run. I try with a recompiled kernel with nfs direct support and i get the same error.

on fedora forum i see that dractcut-network package must be installed. On Mageia i don't found this package.
some people says me that Mageia2 dracut package contains dractcut-network...

is there some charitable man to help me to boot Mageia2 clients from my nfs server.

By avance many thanks for your help.

Roland
http://medintux.org

this could be your problem, but it is still opened on the fedora side.

https://bugzilla.redhat.com/show_bug.cgi?id=537969

I don't think you'll find some help here in the forum,
it could be better if you open a bug report for that:

https://wiki.mageia.org/en/How_to_report_a_bug_properly

You may want to take a look at: http://colin.guthr.ie/2011/06/network-b ... -goodness/

Please next time use code tags as explained in ftp://ftp.mandrivauser.de/rpm/rpm/extra ... e_tags.ogv

Thanks very much for your help

The problem is not resolved, now

You may want to take a look at:http://colin.guthr.ie/2011/06/network-boot-mageia-pxe-nfs-root-goodness/

May be here is the solution.

Thanks.

Roland.

Execuse me; but I don't understand why do you need to use dracut to boot Mageia through PXE!

I did that a while ago with Mandriva, NFS, HTTP and FTP, and there has been no need to recreate initrd!

If you configure the dhcp and tftp to pick up the right file on the right server you can use Mageia's default initrd and kernel..remember that you can install Mageia on the network so maybe I am missing something in your problem!

I'll try it on the week-end and update again.

Good luck!

Thanks fot your reply,

Execuse me; but I don't understand why do you need to use dracut to boot Mageia through PXE!

I have to deploy OS + specifics applications on fanless diskless clients, from a pxe (ipxe) tftp nfs server. it's work with SliTaz, Ubuntu, but i want mageia kde because it is the best environnement for this specifics applications.

thanks.

medintux wrote:I have to deploy OS + specifics applications on fanless diskless clients, from a pxe (ipxe) tftp nfs server. it's work with SliTaz, Ubuntu, but i want mageia kde because it is the best environnement for this specifics applications.
thanks.

So it is a Linux Terminal Server! Have you checked http://wiki.mandriva.com/en/Docs/SysAdm ... inalServer ?

So it is a Linux Terminal Server! Have you checked http://wiki.mandriva.com/en/Docs/SysAdmin/Server/TerminalServer

As see thereafter this solution shares root server fs not good for me because server is not always with same Os , may be VM machine resolves this ?

Terminal-server is a subsytem of Mandriva Linux that is perhaps less than well publicized. If you are familiar with LTSP, it is very similar, except that it uses the server's root filesytem, rather than having a parallel, client filesystem under a different directory (like /opt). The main benefit to this type of arrangement is that the client software base will automatically be updated along with the server, rather than needing to redo an LTSP type arrangement to agree with the server software base. The negative side may be in sharing the root fileystem with a number of other machines. although in a controlled environment this shouldn't be much worse than having user accounts on the server.

thanks

medintux wrote:As see thereafter this solution shares root server fs not good for me because server is not always with same Os , may be VM machine resolves this ?

Sorry! I seem not to have gotten your problem quite well..!

You have a diskless machine, like a dumb terminal, and you want to boot it using PXE. Then what kind of root file system is this machine going to use?!

Are you trying to share an NFS folder only? What do you mean by "the server OS is not always the same"?

linuxero wrote:

medintux wrote:As see thereafter this solution shares root server fs not good for me because server is not always with same Os , may be VM machine resolves this ?

Sorry! I seem not to have gotten your problem quite well..!

You have a diskless machine, like a dumb terminal, and you want to boot it using PXE. Then what kind of root file system is this machine going to use?!

Are you trying to share an NFS folder only? What do you mean by "the server OS is not always the same"?

Thanks for your help,

I make a litle step forward ...in the abyss.

Now i can boot Mageia2 on a client terminal via PXE/dhcp/tftp. Filesystem is somewhere on a nfs server.
Ok . I go in a root console, lauch X11 Xfce with startx but no keyboard no more mouse in X11 (fortunately i can kill X11 client with ssh from an another PC). X11 config mouse/keyboard seems ok. Curious : when i use keyborad on client all caracters goes in root console ant not in X11 (i see this after killing X11 with ssh).



When the next episode ?. Lots of RTFM to read .....

Good-bye

Bingo here is the solution in /etc/xorg.conf ····

Section "ServerFlags"
Option "AutoAddDevices" "false "
EndSection

thanks and many thanks to all peoples which have help me ....

RESOLVED

Roland

Great! Maybe you can expose the scenario here