Author
Topic: Remote Boot failure (Read 6127 times)

We did a standard install from the CD Iso image and are trying to get a PC to remote boot from DCErouter. The process begins ok on the booting PC then we see a DHCP prompt line with an animated progress cursor. After about a minute or so we get the following error displayed;

"No Boot Filename Received"

Then the PC commences to boot from the local Windows XP installation.

Any advice as to what could be causing this to happen. We expected remote boot to be much simpler than this.

It seems that the computer you are trying to boot from the network isn't registered as a Media Director or it's MAC address isn't correctly registered. The Core can't give a bootable image to regular computers since it builds the boot image when it sees a Media Director in the database, for each machine in part.

I'm seeing the same thing. After adding a machine as a Media Director and configuring the settings for IP & Mac, I go to boot it. "No Boot Image found"

I did notice that the /usr/pluto/diskless directory still has only one entry for the machine I entered during the Core install. Is there a way to verify or request that the Core generated the proper boot image for the added Media Directors?

I'm seeing the same thing. After adding a machine as a Media Director and configuring the settings for IP & Mac, I go to boot it. "No Boot Image found"

Adding new diskless Media Directors from the local pluto admin website doesn't currently work. It's on my "To Do" list.

If you add a new diskless Media Director to the installation using the installation wizard on plutohome.com, that doesn't get propagated to the existing install unless you reinstall.

Quote from: "anonymous"

I did notice that the /usr/pluto/diskless directory still has only one entry for the machine I entered during the Core install. Is there a way to verify or request that the Core generated the proper boot image for the added Media Directors?

Each diskless Media Director gets its own directory in /usr/pluto/diskless and some boot files in /tftpboot when the Core boots. Currently it doesn't do that on the fly. But the above "To Do" still applies.

I'm seeing the same thing. After adding a machine as a Media Director and configuring the settings for IP & Mac, I go to boot it. "No Boot Image found"

Adding new diskless Media Directors from the local pluto admin website doesn't currently work. It's on my "To Do" list.

If you add a new diskless Media Director to the installation using the installation wizard on plutohome.com, that doesn't get propagated to the existing install unless you reinstall.

Quote from: "anonymous"

I did notice that the /usr/pluto/diskless directory still has only one entry for the machine I entered during the Core install. Is there a way to verify or request that the Core generated the proper boot image for the added Media Directors?

Each diskless Media Director gets its own directory in /usr/pluto/diskless and some boot files in /tftpboot when the Core boots. Currently it doesn't do that on the fly. But the above "To Do" still applies.

Ok that would explain it!

I noticed that /usr/pluto/diskless did not seem to have as many sub directories in it as i was expecting. Any idea how long it will be before the local Pluto Admin Website will support configuring diskless Media Directors?

By the way we are incredibly impressed by what you guys have done with Pluto.

Adding new diskless Media Directors from the local pluto admin website doesn't currently work. It's on my "To Do" list.

Any chance this is going to make it into 2.0.0.13, or is creating a new KickStart disc a better solution for now?

I put this into the current source tree, but I still need to test and confirm it works for all people. I don't know what the schedule for 2.0.0.13 is, but this should get into it. The KickStart CD also gets updated each release, because I make changes now and then.

Adding new diskless Media Directors from the local pluto admin website doesn't currently work. It's on my "To Do" list.

Any chance this is going to make it into 2.0.0.13, or is creating a new KickStart disc a better solution for now?

I put this into the current source tree, but I still need to test and confirm it works for all people. I don't know what the schedule for 2.0.0.13 is, but this should get into it. The KickStart CD also gets updated each release, because I make changes now and then.

Hi,

I also have empty MAC in original install for Media director. Now I'd like to try that but if I understood right, there is currently no chance to add MAC via web interfaces (either local or Pluto site). But I be there is a workaround.... I have pluto_main database opened, can you point me where to add MAC address....

What is the correct format for entering the MAC address on the Media Directors screen? I cannot seem to get Pluto to hand out the boot image. I have a folder /usr/pluto/diskless/192.168.80.2 with an image in it.

However, after changing it, be sure to either reboot (or faster) run /usr/pluto/bin/Diskless_Setup.sh. That causes the dhcp configuration to be re-written, and the dhcp server to be reset. When that's done, you can confirm what the ip address of the m/d is, and then: tail -f /var/log/syslogand you should see a system log about a dhcp request from the pc, and that it gave it the ip in the database.

Sorry, I'm confused about the use of VMWare.... You have 2 PC's, the core and the m/d. I assume you used the kick-start to setup Pluto on the Core, right? So, it's just a vanilla core, and it created a network boot image for the other PC, which is now booting over the net. So the M/D too is also vanilla Pluto Linux, right? Where is VMWare running? Can you explain the configuration?

The M/D at the moment always boots up with 800x600 resolution. It's one of the more pressing things on our todo list to fix that so you can pick the correct resolution, but at the moment you have to alter the XConfig manually.

Sorry! I didn't mean to confuse you. I have a regular x86 PC that I have built from the kick-start cd this is working fine (well until a few minutes ago when the IDE subsystem died and corrupted my disk - but that's another story). I have a Windows XP PC running VMWare Workstation. In VMWare I have a Virtual PC set to network boot from the Core as an MD. This now works fine except that when the X session starts the panel is too big for the screen. How do I configure X to set the resolution high enough to display the full panel. VMware may have been a red herring it is just that VMWare provides tools for Linux that help describe the capabilities of the emulated hardware a bit better and I thought that it may appear to give the MD OS the impression that the default screen resolution was higher than it is currently using.