Page 1 of 1

network boot: minimyth configuration file not found

Posted: Thu Feb 01, 2007 11:27 pm
by jmw
I am stuck. I have tried everything I can think of. I have my minimyth.conf at
/var/tftpboot/PXEClient/conf/default/minimyth.conf
(my tftp root dir is /var/tftpboot, and pxelinux.0 is under PXEClient)

What's bizarre is I just upgraded from an old minimyth, and I hadn't updated my minimyth.conf yet, I just linked to my old one. When I did that, I got a different error, something about how the MM_TIMEZONE option was no longer used and that I'd have to update my minimyth.conf (something like that). So it HAS found the configuration file at that location before.

But now it won't. Not the new one or the old one. I've tried copying the conf dir to every level of that path and it doesn't work.

I updated my dhcpd.conf to the following (maybe there's something wrong here):

default-lease-time 604800;
max-lease-time 604800;
ddns-domainname "mydomain.org";
ddns-update-style ad-hoc;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.2.255;
option routers 192.168.2.1;
option domain-name-servers 192.168.0.1, 24.25.5.150, 24.25.5.149;
option domain-name "mydomain.org";

#additional pxelinux params - experimental
#option space pxelinux;
#option pxelinux.magic code 208 = string;
#option pxelinux.configfile code 209 = text;
#option pxelinux.pathprefix code 210 = text;
#option pxelinux.reboottime code 211 = unsigned integer 32;

allow bootp;
allow booting;

subnet 192.168.2.0 netmask 255.255.255.0 {
pool {
range 192.168.2.128 192.168.2.254;
option subnet-mask 255.255.255.0;
deny unknown-clients;
}

host myth1 {
hardware ethernet 00:40:63:c5:4a:67;
next-server 192.168.2.101;
#fixed-address 192.168.0.192;
filename "PXEClient/pxelinux.0";

}


One thing i notice is i get "INIT: no more processes left in this runlevel" immediately after this error, and the telnet service is shut down, so I have no hope of retrieving any log files. Or do I?

any help is much appreciated.
JMW

ugh

Posted: Thu Feb 01, 2007 11:42 pm
by jmw
This is maddening.

I got it to find minimyth.conf by adding this line to the last clause of dhcp.conf (at least I think that's what did it):

option root-path "/var/tftpboot";

The next error i get when booting is "MM_TZ must be set". Ok, i forgot to set it. So I set it to 'America/New_York' and reboot.

What do I get now? "MiniMyth configuration file not found".

W...T...F!

oops hehe

Posted: Fri Feb 02, 2007 12:58 am
by jmw
Solved it.

I have 2 dhcp servers- one on my wireless router that serves ip's to the rest of the house, and one on my backend box just to support the network bootable frontend. My router's dhcp server is not really configurable.

I managed to get the only the backend dhcpd to respond to the frontend on boot, but i think when minimyth goes to get the config file, for some reason my router was responding (and responding first, most of the time).

That would explain the inconsistent results, and the problem went away when i turned off the router's dhcp. Not a permanent solution, though.

Any suggestions how to do this?

One way would be to use static ip's on my network, but that's a real pain for guests who bring their laptops, also for my laptops that I use elsewhere.

Re: oops hehe

Posted: Fri Feb 02, 2007 1:50 pm
by Pablo
jmw wrote:Solved it.

I have 2 dhcp servers- one on my wireless router that serves ip's to the rest of the house, and one on my backend box just to support the network bootable frontend. My router's dhcp server is not really configurable.
Having two DHCP servers on the network can be maddening. Sometimes, it happens at work, causing our floor to lose connectivity and requiring someone to figure out which lab machine is causing the problem.

Can the wireless router's DHCP server be disabled?

My gateway has a DHCP server. While it supports very limited configuration, it can be disabled. Therefore, I disabled it and I use my Linux server as my DHCP server.

Posted: Sat Feb 03, 2007 12:22 pm
by adrian.s
Another option (which I've used successfully) is to flash your router with dd-wrt [1].

This is a really tight linux distro with dhcp, dns etc. all configured on it. You can then make this your one dhcp server and configure it accordingly. I popped it onto a linksys router and it's being going great for the last few months.

HTH,
Adrian.

[1] http://www.dd-wrt.com/dd-wrtv2/index.php

Posted: Tue Feb 06, 2007 10:35 pm
by mipster
Wait, I'm getting the exact same problem and I do NOT have two dhcp servers.

Booting from PXE using the ramdisk image, I get configuration file not found. then INIT: no more processes left at this runlevel (so no telnetting in). Check out the logs from the tftp server:

/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.0 to 10.0.1.28:2070
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.0 to 10.0.1.28:2071
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/01-00-17-31-87-75-56 to 10.0.1.28:57089
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A00011C to 10.0.1.28:57090
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A00011 to 10.0.1.28:57091
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A0001 to 10.0.1.28:57092
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A000 to 10.0.1.28:57093
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A00 to 10.0.1.28:57094
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A0 to 10.0.1.28:57095
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A to 10.0.1.28:57096
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0 to 10.0.1.28:57097
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/default to 10.0.1.28:57098
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/ram-minimyth-0.20-21/kernel to 10.0.1.28:57099
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/ram-minimyth-0.20-21/rootfs to 10.0.1.28:57100
/var/log/syslog.0:Feb 5 21:19:02 saturn atftpd[31916]: atftpd terminating after 300 seconds
/var/log/syslog.0:Feb 5 21:19:02 saturn atftpd[31916]: Main thread exiting

Notice it never asks the server for a config file??

Here's the even wierder part. I did a local boot install on a spare ide drive and booted the frontend off the disk using the ramdisk image, Same error!! I can mount the disk from a Mac or a Linux box and confirm that the FAT32 filesystem was built correctly. I can even see /minimyth/conf/default/minimyth.conf on the disk. WTH?

I've tried 20-21, 20-22b8 and 20-22b12. I've tried booting from an EPIA-M box and a Pentium D box, both with the same error.

BTW, this is my first attempt to boot minimyth. So I am not coming from a working system.

VERY puzzling.

Posted: Tue Feb 06, 2007 11:21 pm
by Pablo
mipster wrote:Wait, I'm getting the exact same problem and I do NOT have two dhcp servers.

Booting from PXE using the ramdisk image, I get configuration file not found. then INIT: no more processes left at this runlevel (so no telnetting in). Check out the logs from the tftp server:

/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.0 to 10.0.1.28:2070
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.0 to 10.0.1.28:2071
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/01-00-17-31-87-75-56 to 10.0.1.28:57089
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A00011C to 10.0.1.28:57090
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A00011 to 10.0.1.28:57091
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A0001 to 10.0.1.28:57092
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A000 to 10.0.1.28:57093
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A00 to 10.0.1.28:57094
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A0 to 10.0.1.28:57095
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0A to 10.0.1.28:57096
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/0 to 10.0.1.28:57097
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/pxelinux.cfg/default to 10.0.1.28:57098
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/ram-minimyth-0.20-21/kernel to 10.0.1.28:57099
/var/log/syslog.0:Feb 5 21:14:02 saturn atftpd[31916]: Serving minimyth/ram-minimyth-0.20-21/rootfs to 10.0.1.28:57100
/var/log/syslog.0:Feb 5 21:19:02 saturn atftpd[31916]: atftpd terminating after 300 seconds
/var/log/syslog.0:Feb 5 21:19:02 saturn atftpd[31916]: Main thread exiting

Notice it never asks the server for a config file??

Here's the even wierder part. I did a local boot install on a spare ide drive and booted the frontend off the disk using the ramdisk image, Same error!! I can mount the disk from a Mac or a Linux box and confirm that the FAT32 filesystem was built correctly. I can even see /minimyth/conf/default/minimyth.conf on the disk. WTH?

I've tried 20-21, 20-22b8 and 20-22b12. I've tried booting from an EPIA-M box and a Pentium D box, both with the same error.

BTW, this is my first attempt to boot minimyth. So I am not coming from a working system.

VERY puzzling.
Telnet is started before fetching 'minimyth.conf'. Therefore, if you cannot telnet into the box, then the problem happened before getting to the point where 'minimyth.conf' is fetched. When this happens, it is usually related to either the lack of the right Ethernet driver in the kernel or an incompatible DHCP configuration. The kernel contains the Ethernet driver for the EPIA M motherboard, so the problem is likely an incompatible DHCP server configuration.

What DHCP server are you using? What is its configuration? Is there anything obvious in the DHCP server logs that might point to the cause?

Posted: Wed Feb 07, 2007 8:37 pm
by mipster
OK, I'm guessing you are correct about the missing eth driver. The onboard eth on my EPIA board is toast so there is a linksys card in there (which is not in the minimyth kernel). Then on the second machine the onboard eth is 88E8001 which is not in the kernel. So I tried an e100 which is not in there either.

I was missing the HUGE point that this is a very targetted release with very specific HW support.

What messed me up was that both machines got quite far in the boot process. So would this explain why it seems to work but then doesn't: When the machine boots using PXE, the PXE loader gets all the files since the onboard NIC is supported by the oboard PXE loader. But I'm assuming the bootloader passes control to the kernel (without the drivers) before the minimyth config file is gotten. Therefore the reason for the minimyth.conf not found message.

I guess I need to build minimyth from source :(

Posted: Wed Feb 07, 2007 8:45 pm
by mipster
Oh, wait, I forgot to ask:

If the above explains why my netbooting doesn't work, why does local booting fail with the same message?

I'm assuming that when local booting, the config file is retrieved from the filesystem. So why would the local boot fail with the same error message as the netboot? I would assume that the lack of a supported eth card would keep the box from working (since it can't talk to the backend), but why would it fail with the same error message (minimyth.conf not found) as the net boot?

Also, I noticed on the local boot setup that the install script uses the entire flash/hard drive (/dev/sda) as the minimyth partition. Is there any reason that a standard partition is not used (/dev/sda1)?

Sorry for all the questions! Trying to learn...

Posted: Thu Feb 08, 2007 1:59 am
by Pablo
mipster wrote:Oh, wait, I forgot to ask:

If the above explains why my netbooting doesn't work, why does local booting fail with the same message?
Yes, your post above does explain why network booting fails. It may indirectly explain why local boot fails as well.

MiniMyth guesses whether it is network boot or local boot based on information returned by the DHCP server. It does this in the script run by the DHCP client. Looking at the script, I can see no reason that it would guess that it is network boot when DHCP fails. Therefore, I suspect that the problem is something else. However, setting MM_BOOT_TYPE='local' on the boot line (the syslinux.cfg APPEND line) should ensure that it is doing local boot.

I suspect that there is some problem with the configuration of the local boot device. In order for MiniMyth to find minimyth.conf on the local boot device, the local boot device needs to be configured just right. The partition must be formated with FAT32 or some other FAT that supports long file names, the partition must have the label 'minimyth', and the 'minimyth.conf' file must be located on the partition in the directory '/conf/<hostname>/' or '/conf/default/'. Since DHCP is failing, MiniMyth will not be able to determine <hostname>. Therefore, 'minimyth.conf' must be located in '/conf/default/'.
Also, I noticed on the local boot setup that the install script uses the entire flash/hard drive (/dev/sda) as the minimyth partition. Is there any reason that a standard partition is not used (/dev/sda1)?
I was lazy. Using a standard partition required figuring out how to script the creation of a partition table.
Sorry for all the questions! Trying to learn...
No need to be sorry about the questions.

Posted: Mon Feb 12, 2007 7:59 pm
by oscarBravo
I'm having the same problem. It's a basic Epia board with onboard Ethernet. It's booting successfully, up to the point of "MiniMyth configuration file not found."

I can telnet into it, but the syslog doesn't tell me much that's useful. Once telnetted in, I can tftp the config file from the server, so I know it's accessible. In the server log I don't see any sign of an attempt to tftp the configuration file.

Completely stuck here - any pointers?

Posted: Mon Feb 12, 2007 9:12 pm
by oscarBravo
Never mind: I had the configuration file name wrong.

Honestly, if I had a brain I'd be dangerous... :roll: