No - don't go deleting the MD making up the hybrid core to create a dedicated core.
Just turn off the automatic starting of those services via the LMCE Launch Manager http://wiki.linuxmce.org/index.php/Launch_Manager. Untick the box labeled "Autostart Media Station" and then save settings.

-Coley.

  finally there is an end to this!!
Not so much a resolution but a solution.
I bought a new machine for the core - clean DVD install of 710.
Booted this MD and seems to have gone though generation of machine image.
All seems to have worked first go 

Thanks Zaerc for your input trying to get to the end of this!! in the end this motherboard seems ok so far.
vga only at the moment, need to verify DVI/HDMI operation.
I've added it to the wiki and will update as I progress.

Before I nuke the old LMCE partition on my other dual boot machine is it worth looking at this old install with a view to check why this was failing?

-Coley.

p.s. UI2 overlay looks sweet and has a high WAF

Purps,
A Hybrid core is a core+media director on the one machine.
As you have read in the wiki http://wiki.linuxmce.org/index.php/Core A core can start off life from the install as a hybrid but then you can choose not to start the media station via the LMCE launch manager. This machine can then be left as a headless server.

hope that clears it up
-Coley.

Just to update here - this arrived last Fri, Got to install 710 i386 via DVD on Mon all went without a hitch
will wiki it and update as I play with it some more.

-Coley.

I'm going to get one of these and some extra mem as a dedicated headless core
http://www.elara.ie/products/detailsfull.asp?productcode=ECE1574355

This way I can do a clean install any time if I go tinkering with it.

You think it will be up to the task?

thanks
-Coley.

moved a stage further - MD now announces itself to the router!
I changed the DHCP settings on the core to give out addresses to non-LMCE components, tried rebooting MD and it used the default image to tftp boot!! Any reason why this would spur the pxe boot into action?

Diskless directories get set up on the core - amd64 recognised and see MD via web admin.

But all the joy was short lived, ran into the "mount call failed 13" looping error.

And yes I have the amd64 tarball from the DVD in my /usr/pluto/install directory as the CD install doesn't carry this.

any pointers??

thx
-Coley.

Ok I think my core/hybrid is sick.
I tried network booting a HP laptop I had previously run as an MD with one of the Betas. It comes up and announces itself to the router, runs some scripts and then reboots. Except it re-announces on reboot! When I check the web admin interface I don't see a new MD.
If I set up MD from web interface and then try boot the Laptop I run into the same mount call failed.

Are there any scripts available that can validate a core install? or it it clean install time for me??

-Coley.

I'm still trying!
I've disabled the onboard NIC and put in an n/w card from another PC - still no joy.
MD still fails to get past the "mount call failed" repeating error.

I'm running out of ideas...

-Coley.

I tried adding forcedeth as a module and rebuilding the image.
It doesn't make any difference. Is there any way to log the console output of an MD booting? I do see a reference that forcedeth is loaded as it scrolls past.

After the MD fails to boot and gives up trying to mount I checked what it was trying to do, It attempts to run the scripts in the /scripts/nfs-premount directory in the image. But when I check the dir it is empty! so there is nothing to run, is this correct?

any more pointers appreciated,
-Coley.

[MCP67]

Back to this again, was away for a week. Only got a brief chance this morning to investigate. Seems the chipset in use is MCP67 and the module should be forcedeth Will try these later and report back.

Would it be an idea to add known unrecognised NICs to that wiki page? along with what mobo they appear on?

How do NICs get from unrecognised to recognised? is it the kernel version on which LMCE is based that determines this?

thx
-Coley.

Ok, did that. copied PlutoMD-amd64.tar.bz2 as you said, changed MD arch to amd64 in webadmin, rebuit image and quick reload of router. Now the boot directory has files and looks healthier.
Booted the MD, starts to boot the image provided but fails, gets stuck in a loop:

Code:

Begin: Running /scripts/nfs-premount ...
Done.
Mount call failed: 13
Done.
Begin: Retrying nfs mount ...
<Block of info on IP connection>

until it gives up and drops me out to busybox.
I can ping the moon### from the core but not ssh or telnet to it.

at the very end when the scripts give up I get

Code:

Begin: running /scripts/nfs-bottom
Done.
Done.
Begin: running /scripts/init-bottom

Mount fails trying to mount /root/dev, /sys and /proc as the destinations don't exist.
the last error: target filesystem doesn't have /sbin/init

but /usr/pluto/diskless/###/sbin/init exists on the core?

any other insights?

thx
-Coley.

I originally installed from CD. (machine is dual boot)

MD spec is
AMD M2N-VM HDMI AM2 NF630A MATX VGA+SND+GLN
ATHLON 64 X2 4200+
1GB RAM

-Coley.

The links are laid out as follows
tftpboot/###/initrd.img -> /usr/pluto/diskless/###/boot/initrd.img which itself is a symlink to initrd.img-2.6.22-14-generic in that dir.

and the same for vmlinuz
tftpboot/###/vmlinuz -> /usr/pluto/diskless/###/boot/vmlinuz which itself links to vmlinuz-2.6.22-14-generic.

In both the tftp/###/ and the pluto/diskless/###/ the only files in those dirs are the symlinks.

Also noticed that the MD subdir ### doesn't get created when the MD is added via the webadmin, I have to add the MD MAC address before they get created.

-Coley.

I've been battling on and off trying to get an AMD64 MD going with an i386 hybrid core with no success yet.
I've tried

• adding MD via webadmin, leaving arch type as i386, clicking setup diskless MD, wait for it to finish generating MD, quick reload router. Then tried booting MD. Nothing, MD gets no IP addr.
  Add MD MAC via webadmin, save, reload router, booting MD this time gets ip addr and continues to boot until it loops failing a mount call with error 13. Rebuilding of the image via webadmin doesn't help.
• Delete above MD via webadmin, re-add as above, set its arch type to be amd64, rebuild image and reload router. Less this time, ip addr received by the MD but cannot boot.

After some digging found that the tftboot directory had the initrd image and vmlinuz had broken symlinks. The symbolic link had the right content but the destination file was not present.

Do these files get pulled out of the PlutoMD-archxxx.tar.bz2 files? My amd64 file appears to be corrupt, bunzip decompresses it ok, but tar complains - I can't rember the exact error - " missing '.' " or something to that effect?
Am I digging in the right direction?

thanks
-Coley

I tried a 2CD based upgrade from RC1 to RC2 last night. The install seemed to hang on generating mdadm.conf (I don't have any sort of a raid set-up), I started it last night and it was still stuck on that this morning. I ran dmesg to see if anything had died during the night and it reported too many open files and the system was very sluggish. I've shut it down now but I'll try the install again later.
Anyone any clue what could cause the hang?

btw - should the core and md services be stopped before running the install script? or does it detect them running and handle it itself?

thanks
-Coley.