Ok, got a strange one here, where I PXEBOOT a pc and everything goes Haywire. I'm at a loss to why.

Here's the situation: I deleted one of my MDs because I kept on getting a video error message with the Nvidia drivers. I went into webadmin and deleted the MD from the system. Then I PXEbooted and the pc did the usual thing about announcing itself to the Core. Next it runs the DHCP_?.sh script, then the NFS? script. Immediately after that it reboots and repeats these steps over again and again and again.

Meanwhile on the Core/Hybrid I get a message saying "this seems to be a new orbiter, shall I set it up for you?" Next the LMCE babe video starts up. Then I go into the LMCE webadmin tool and notice there is a new orbiter listed there, and also a new Media Director device created. The room listed for the new MD is same room my Core is in. Well I already have a MD at that location. So it appears that LMCE is trying to create another one there. This seems to confuse everything including me. I tried changing the room location for it to where I wanted it to be but it won't stick. I also get messages telling me such and such device #183 is invalid, shall I delete it. Hell yea, delete it for me. Then once I delete the rabid Media director and the wayward orbiter in webadmin, things seeem to settle back down.

So I'm wondering what has happened. Did I screw something up when I deleted the MD? I'm now unable to re-establish the MD I wanted to put back in the system.

I think with 0710 that using the "Setup Diskless Media Director" is no longer used??? Not sure. I tried that but it didn't work. Also the /home/diskless/XX filesystem for that device # is not there, so I'm assuming it's gone. I think the key to my problem is with the Media Director and it's continuous rebooting. It starts the PXE boot fine, announces itself to the Core, starts running the installation shell scripts, and then reboots, and starts this whole process over again. I noticed that it doesn't even create the /home/diskless/XX filesystem at all, even though a device # is assigned to it when the Core detects the new MD. However, in LMCE admin the new MD is listed. Some might say just rebuild the Core, but I've got too much time invested in getting the Core running to do this (only as a last resort anyway).

finsdown - long shot, but when you PXE boot to start building your MD (after you have deleted the old one) what is the first IP address it gets from the core? Is it getting one from your "unknown" devices range (I think this is the higher range) or the lower "MD" range of IP addresses?

If it is the lower one, this could be the problem - the Core maybe remembering the MD from its MAC address and putting it straight into the MD range which in turn may be screwing up the auto discovery scripts in some way I don't understand. Normally, it should get a high IP address as it doesn't recognise the device, builds itself, then reboots and gets a lower address.

colinjones - yes it is getting the lower ip address 1(92.168.80.2) and I think your are right on about the core remembering the mac address from the previous MD. Now how I wonder if I can tell the core to not do this? I thought maybe I could use a different network card, since I do have some spares, and that would be get around it. But I'd rather fix the problem than work around it. Ideas?

It may not be causing the problem... but if you look in /etc/dhcp3 you should find the config file and that contains the leases against MACs. You can delete it from there. Now in my experience this doesn't always stop it from remembering.... don't know why cos it is definitely related to it. But sometimes I have had to dick around a bit before it "forgot" but that was with PC shares where the DHCP client actively requests the old address. With PXE I doubt very much if this is stored in CMOS so maybe it will be easier for you...

Wow, this is the EXACT thing that is happening to me - only I have never tried to install another media director before (I only have a core/hybrid right now, and never attempted to install any other md's). THis was the first media director I was going to PXE boot - and on the first attempt onward, I get the same behavior - Announces itsself to the router, then I can quickly see a DHCP...sh and NFS script, the word Rebooting.. than pow, it reboots and the process starts over. Mine was also assigned an IP of .80.2

Good to know I'm not alone in the wilderness. I haven't had time to try these ideas yet. I've been busy with other issues on my other MD's. I have a Core/Hybrid in the LR and a MD in the MBR that are working fairly well, except the frequent lockups with MythTV.

Can you see the MD's files under /usr/pluto/diskless/# and/or /tfptboot on the core? Does it have an entry in the web-admin? If so you can try letting it rebuild or if not you could try adding it manually and specify the MAC and IP addresses.

linuxmce@dcerouter:~$ :/tftpboot/pxelinux.cfg$ more 01-00-19-de-ad-be-ef -bash: :/tftpboot/pxelinux.cfg$: No such file or directorylinuxmce@dcerouter:~$ :/tftpboot/pxelinux.cfg more 01-00-19-de-ad-be-ef -bash: :/tftpboot/pxelinux.cfg: No such file or directorylinuxmce@dcerouter:~$

Also, there are no MD's listed on the web admin (other than my Core/Hybrid)

Something just hit me.....The computer I am trying to network boot is the computer I normally use for my personal computing. It is running Ubuntu 7.10. I installed the XP version of the orbiter on it, and I run it through wine. The device ID listed on the orbiter page is 60. Is this what is causing the problem?What about the HP Photosmart printer appearing in the PXE boot text - what is that all about?