News:

Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com

Main Menu

Reboot Media Director (diskless) - Found problem, but how to fix??

Started by tamix, July 31, 2009, 01:49:50 AM

Previous topic - Next topic

tamix

I have a diskless media director that boots up only right after a core reboot, and once only.    If I try restarting this MD it stops dead after saying which nic it's using (just prior to the spinning slashes :-) )

Anyone any idea how to sort this?   I can't leave the MD on, but can also not restart the core every day.


tamix

#1
Further to the above - I figured that there must be some serious issue in my setting up of the MDs.  Every time a new one is added or rebuilt two things happen - first the symlinks go awry and I have to repair it:
in /usr/pluto/diskless/99/ both the initrd.img and vmlinuz symlinks get stuffed for some reason, and fixing it gets everything humming along again.

and secondly /etc/exports get changed and I have to modify it -

From:
/usr/pluto/diskless/99  192.168.80/255.255.255.0 eth0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
To
/usr/pluto/diskless/99  192.168.80.3/255.255.255.0 eth1(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

If anyone can offer some intelligence here I'll be very happy!

pigdog


tamix


tamix

I "solved" the "reboot" problem by reinstalling - somehow the above problems disappeared.... Must have been some finger troubles my side.

The new brick wall is The Media Director.    I added a MD device, entered the MAC address and voila!   It found the files and started the (rather long) boot process.   The last lines that came up were:
* Starting anac(h)ronistic blah
* Starting periodic command scheduler
[ 704.581176] hci_cmd_task: hcio command tx timeout

And there we get stuck - seemingly forever

HELP!    ???

pigdog

Hi,

You should not have to manually add a MD,

Quoteentered the MAC address and voila!

the device is self-discovered.  You plug it in to your Core internal network and let it find itself.

I would suggest using webadmin to delete the MD, shutdown the MD, reboot the Core - when it's finished power up the MD.

If there is problems then it will probably be easier to figure out because we've followed the 'typical' install.

Cheers.