[SOLVED] Absolute Minimum Netbooting problems

[Akane]

Hi Zendrael!

Thank you very much!

Possibly the Terminal Server is locating all files for network boot(including pxelinux.cfg/*) into '/netboot'.

If it is correct, there is 'default' configuration file in '/netboot/pxelinux.cfg'. (not 'tftpboot')
Please check.

I wish you well!

Regards,
Akane.

[Zendrael]

Hi Akane!

Yes, I was playing with this directory now! Will redo all of my configs then I'll post back here to say whats worked or not!

The tests may take some time, will post again just tomorrow!

Thanks for your help! When everything works, maybe I will update or put some tips in the wiki.

[Zendrael]

Ok!

Now there is a /mnt/nfs directory in the clients after they boot up! The directory contain a tce dir with onboot.lst, ondemand and optional directories - all of them are empty!

I (re)created the /tftpboot/nfs/ws1 directory and inside it  tce directory with some extensions. None is loaded. I have this added to the client boot file:

Code: [Select]


nfsmount=myserver:/tftpboot/nfs/ws1
and, as you can imagine, what is mounted in the clients is not what this directory contain... even if I try to create a file inside /mnt/nfs in the client, it doesn't show up in the server....

Almost there!!!

[Akane]

Hi Zendrael!

Sorry for late because I was sleeping.
Congratulations!

It seems that the client did not mount the NFS share or the client mounted different directory.

So please upload the contents of /etc/exports on the server and the result of running command 'mount' on the client.

Regards,
Akane.

[Zendrael]

Hi Akane!

To sleep is good for your brain! I wish I could do more of it! Hahaha!

Attached are the commands you requested, including the "exportfs -a" which always gave me some messages too.

I have a good feeling about this, we will get there soon!

Thanks!

[Akane]

Hi Zendrael!

Thank you for your pictures.

It seems that NFS daemon on server is not running (because the server could not load nfsd kernel module).

I think the kernel version you showed (3.0.21-tinycore) may be incorrect.
Did you 'tce-load'ed 'filesystems-KERNEL'?

Sorry for my ambiguous opinions (because I do not have any PC on that TC can run).
Please show me the result of the command 'uname -r' (kernel version).

Regards,
Akane.

[Zendrael]

Hi Akane!

uname -r shows

Code: [Select]

3.0.21-tinycore
and I have filesystems-3.0.21-tinycore loaded at boot on the server (confirmed with tce-status -i)

[Akane]

Hi Zendrael!

Oh. I see.

Then, please run the command 'depmod' as root and restart nfs-server.
If there are some errors, please show them.

Regards,
Akane.

[Zendrael]

Hey Akane!

The depmod command returned nothing and when restarting the nfs-server I get some messages (attached)

This is becoming a real challenge! Hahahahah

Thanks!

[Akane]

Hi Zendrael!

Okay. Thank you!

Now you can network boot the client, maybe.
Please try!

Regards,
Akane.

[Zendrael]

Hi Akane!

The client is booting up, just don't load any extensions and don't mount the nfs share in the server (where the extensions are).

[Akane]

Hi Zendrael!

Thank you.
Hmmm... That's strange.

Can you mount the NFS share on the server?
For example,

Code: [Select]

$ mkdir /tmp/nfs-share
$ sudo mount -t nfs myserver:/tftpboot/nfs/ws1 /tmp/nfs-share

Regards,
Akane.

[Zendrael]

Hi Akane!

I agree, really strange... the command gave an error too... attached is what I've got.

Thanks again!

[Akane]

Hi Zendrael!

Hmmm...

First, run the command 'chmod 777 /tftpboot/nfs/ws1', 'exportfs -ra' and retry net booting.

If it fails again, then replace /etc/exportfs like below.

Code: [Select]

/tftpboot/nfs/ws1 (rw,no_root_squash,fsid=0)
Then run the command 'exportfs -ra' and retry net booting.

Regards,
Akane.

[Zendrael]

Hey Akane!

The directory was chmoded as 777 earlier then I did it again and, after adding the fsid on the /etc/exports, the error in the clients changed as follows (attached)

Thanks again!