Installing Diskless MDs

[phenigma]

I am on lmce 14.04

I'll try to setup a test.  My ion is in use so I may not be able to completely replicate things.

Sent from my Nexus 5 using Tapatalk

[phenigma]

I cannot re-create this issue here.  I'm getting flawless initial boots, announce to router & device creation.

You should try re-creating the default diskless image.

Code: [Select]

/usr/pluto/bin/Diskless_BuildDefaultImage.sh
and try initial booting again.

It's all I can think of without knowing what is specifically causing the issue.

J.

[maverick0815]

I tried and this is what happens

dcerouter_1047595:/home/linuxmce# /usr/pluto/bin/Diskless_BuildDefaultImage.sh
cp: cannot stat ‘/boot/vmlinuz-3.13.0-116-generic’: No such file or directory
grep: /boot/config-3.13.0-116-generic: No such file or directory
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
depmod: WARNING: could not open /tmp/mkinitramfs_IjVlgf/lib/modules/3.13.0-116-generic/modules.order: No such file or directory
depmod: WARNING: could not open /tmp/mkinitramfs_IjVlgf/lib/modules/3.13.0-116-generic/modules.builtin: No such file or directory
dcerouter_1047595:/home/linuxmce#

what I don't understand is, why it wants 3.13.0.116, when the kernel that's installed is actually 3.13.0.119

[phenigma]

I think I've got that sorted.  I'm going to push an update to the default image script that should pick the most recent kernel, which it is currently not doing. 

J.

[Marie.O]

We are coming full circle :-D - about 8-9 years ago the script already used the latest available kernel.

[phenigma]

Heh.  It did. It's back the way it was now. 

[maverick0815]

So far so good..thanks, but i am still having an issue woth avwizard...trying 1080p at 60hz the picture is garbled...improper setting of the frequency

[phenigma]

Lets start a new thread for that one.  Have you tried using the number/letter keys to choose the output prior to selecting resolution?

[maverick0815]

As you suggested, I opened a new thread...I hope I am beeing verbose enough

[Aarontraum]

Now i have tried installing ubuntu the same way and i got the same error. So it is definetly the computer and it is not fixed by the chromebooks powerwash. How do i reset it even further?