I am running a single 1404 hybrid, which I installed over the Internet. I now want to install a diskless MD. Previously, in 810, I needed to run the following prior to connecting the MD to the network:
/usr/pluto/bin/Diskless_CreateTBZ.sh
Is this still the case? Does running it hurt anything if the system is already configured to boot diskless clients?
Thanks,
CDM
You will need to run that script to generate the initial diskless image. It will hurt nothing to re-run the script.
J.
OK. I ran the script and it completed without error.
Then, I turned on my new MD, which is a Core i3 with an Intel motherboard, configured to boot from the network and use an nVidia 7300 graphics card rather than the on board graphics. The diskless installation progressed, also without error. Toward the end there was a message saying that a reboot was required in order to complete the nVidia setup. The system reset and began the PXE boot but stalled, with an error:
"Could not find ramdisk image: 82/initrd.img"
A find search indicates that the files seem to exist:
root@dcerouter:~# find / -name initrd.img -print
/tftpboot/82/initrd.img
/usr/pluto/diskless/82/boot/initrd.img
/usr/pluto/diskless/82/initrd.img
/initrd.img
Advice??
Thanks,
CDM
Follow the symlinks to ensure the files are all pointing to real files eventually. Make sure the files are not zero byte. Try rebuilding the md from webadmin if you continue to have issues. I wonder if it somehow rebooted while running update on the initrd files.
Sent from my Nexus 5 using Tapatalk
Further investigation shows that the file seems to be there. The boot message says:
"TFTP prefix: /tftpboot/"
It finds vmlinux but not initrd.img. Why? Both are there:
root@dcerouter:/tftpboot/82# ls -la
total 8
drwxr-xr-x 2 root root 4096 Feb 10 14:19 .
drwxr-xr-x 6 root root 4096 Feb 10 14:19 ..
lrwxrwxrwx 1 root root 33 Feb 10 14:19 initrd.img -> /usr/pluto/diskless/82/initrd.img
lrwxrwxrwx 1 root root 30 Feb 10 14:19 vmlinuz -> /usr/pluto/diskless/82/vmlinuz
root@dcerouter:/tftpboot/82#
Again, any help would be appreciated.
CDM
PS: Just saw Phenigma's reply as I was typing this. I will follow the symlinks.
Make sure the files have read permissions as well. I haven't heard of this happening like this before.
Sent from my Nexus 5 using Tapatalk
It appears that the correct boot files were never created. Look at the version numbers on the initrd.img and vmlinuz files:
root@dcerouter:/usr/pluto/diskless/82/boot# ls -la
total 4632
drwxr-xr-x 2 root root 4096 Feb 10 14:28 .
drwxr-xr-x 20 root root 4096 Feb 10 14:19 ..
-rw-r--r-- 1 root root 1214709 Jun 28 2016 abi-3.16.0-77-generic
-rw-r--r-- 1 root root 176220 Jun 28 2016 config-3.16.0-77-generic
lrwxrwxrwx 1 root root 55 Feb 10 14:19 initrd.img -> /usr/pluto/diskless/8 2/boot/initrd.img-4.2.0-27-generic
-rw-r--r-- 1 root root 0 Feb 10 14:45 initrd.img-3.16.0-77-generic
-rw-r--r-- 1 root root 176500 Mar 12 2014 memtest86+.bin
-rw-r--r-- 1 root root 178176 Mar 12 2014 memtest86+.elf
-rw-r--r-- 1 root root 178680 Mar 12 2014 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 2795312 Jun 28 2016 System.map-3.16.0-77-generic
lrwxrwxrwx 1 root root 52 Feb 10 14:19 vmlinuz -> /usr/pluto/diskless/82/b oot/vmlinuz-4.2.0-27-generic
-rw-r--r-- 1 root root 0 Feb 10 14:45 vmlinuz-3.16.0-77-generic
root@dcerouter:/usr/pluto/diskless/82/boot#
The symlinks point to files that do not exist.
The new MD appears in webadmin. If I click on the button that says "Rebuild image" will that do the trick? Any other steps?
Thanks for the instant response.
CDM
They must have been created for it to boot the first time. Rebuild button is for this exact purpose. Hit rebuild, wait, then bit the md after rebuild competes.
Sent from my Nexus 5 using Tapatalk
I have had progress, and failure.
I clicked the button, waited, and the browser responded with a popup saying that the rebuild had completed successfully. Then, I reset the MD and the diskless boot proceeded successfully, running for what seemed like 10 minutes until the next automatic reboot. Then it failed again, as before, not being able to find initrd.img.
Looking in /usr/pluto/diskless/82/boot, the 4.2.0-27 files do not exist, as before. Further, the timestamps indicate that they do not seem to have been touched in the last half hour, as though they had been rebuilt as part of the webadmin fix.
Another observation: watching the messages scroll by during the second reboot, I saw lots of references to 3.16.0 but none to 4.2.0.
Help.
CDM
Here is the current state:
root@dcerouter:/usr/pluto/diskless/82/boot# ls -la
total 43884
drwxr-xr-x 2 root root 4096 Feb 10 15:19 .
drwxr-xr-x 20 root root 4096 Feb 10 15:07 ..
-rw-r--r-- 1 root root 1214709 Jun 28 2016 abi-3.16.0-77-generic
-rw-r--r-- 1 root root 176220 Jun 28 2016 config-3.16.0-77-generic
lrwxrwxrwx 1 root root 55 Feb 10 15:07 initrd.img -> /usr/pluto/diskless/82/boot/initrd.img-4.2.0-27-generic
-rw-r--r-- 1 root root 34156419 Feb 10 15:18 initrd.img-3.16.0-77-generic
-rw-r--r-- 1 root root 176500 Mar 12 2014 memtest86+.bin
-rw-r--r-- 1 root root 178176 Mar 12 2014 memtest86+.elf
-rw-r--r-- 1 root root 178680 Mar 12 2014 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 2795312 Jun 28 2016 System.map-3.16.0-77-generic
lrwxrwxrwx 1 root root 52 Feb 10 15:07 vmlinuz -> /usr/pluto/diskless/82/boot/vmlinuz-4.2.0-27-generic
-rw-r--r-- 1 root root 6034368 Jun 28 2016 vmlinuz-3.16.0-77-generic
root@dcerouter:/usr/pluto/diskless/82/boot#
My theory is that the build scripts are building targets with the wrong filenames. Thoughts?
Something strange is up there. I've not seen this before. I will try an md at home when i get a chance. Let me know if you find anything out.
Sent from my Nexus 5 using Tapatalk
Not likely, is all Ubuntu stuff that deals with the kernels. The Nvidia install would trigger an initrd rebuild... which may be failing.
Sent from my Nexus 5 using Tapatalk
Pull the Nvidia card out. Try with the Intel drivers on the i3. That's my best suggestion atm.
Sent from my Nexus 5 using Tapatalk
Success. I pulled the nNvidia card and pressed the rebuild button in webadmin. The system booted through to the AV Wizard and Sarah's setup screens. I completed the installation and can now watch movies hosted on my core.
The problem definitely had to do with creating the images specific to nVidia.
Please advise next steps. You may recall from my earlier posts that I am using CRT televisions. I want to use the old GeForce 7300 card because it has a component output. I would like to avoid using an HDMI to component converter box, as I am with my hybrid. Lets please get the nVidia install working.
Also, I setup the diskless MD with analog sound. As on my hybrid, volume and mute controls don't work. I think there was mention in relation to my earlier posts that the linkages to Xine or ALSA are broken. This pretty much means that I have to use a receiver. Luckly I have two Denons and may do this, but was not planning on it. Will internal volume/mute control ever work again? What is the status of integrating VLC? An update would be great.
Thanks for the help.
CDM
The Nvidia install works perfectly with modern cards (no issues here). It's not the image, the image boots fine. It's the Nvidia driver install that is breaking things (as best i can tell). You might try editing the nvidia-install.sh script and tell it to use an older version of the drivers. If that works then a permanent workaround could be made.
Sent from my Nexus 5 using Tapatalk
OK. I had a look at the script and there is a variable defined as follows:
LogFile="/var/log/pluto/nvidia-install.log";
The script apples logic based on the kind of nvidia card that is detected so, I need to know which version code is associated with my card. I am assuming that it would be logged in the log file. However, the log file does not exist in /var/log/pluto. I am guessing that it may have been nuked when I rebuilt the MD without the nvidia card in the machine.
I am happy to put the card back in and have a look to see if the file is created. Is that the right approach? Is there another way to figure out which code would be returned by my card so that I can discern the right part of the script.
Sorry for the newbie question.
CDM
I wouldn't worry about the id for your card yet. Find the bit where it determines the driver and set them all to nvidia-340.
Sent from my Nexus 5 using Tapatalk
Which one should I edit? There are two options:
/usr/pluto/diskless/82/usr/pluto/bin/nvidia-install.sh
/usr/pluto/bin/nvidia-install.sh
I am guessing that the diskless one will get nuked if I rebuild the MD again.
The one on the MD, under the diskless directory. Moon 82.
Sent from my Nexus 5 using Tapatalk
No luck. I made the change to the file, reinstalled the card, and rebuilt the MD in webadmin. The system failed to boot the second time during the install process. Then, I pulled the card, rebuilt again and got to the AV wizard, as before. At this point, I'll just use the HDMI to component converter box.
Thanks for the help nonetheless.
CDM
guys, I have quite a similar problem. After performing an update on my md (asrock ion330) it wouldn't boot anymore. So I too rebuilt the image, which resultet in "45/initrd.img" not being found.
So I rans "usr/pluto/bin/Diskless_CreateTBZ.sh", which ran without detecting any issues, but it seemed quite fast...usually it takes around an hour- this was done after 25 Minutes
I deleted the MD and let it create a new one, which gave me "77/initrd.img" not found.
So what do I do now? Please advise.
Running on 12.04
Cheers
Mario
-------------
I found out that initrd.img points to initrd.img-3.13.0-105-generic and vmlinuz to vmlinuz-3.13.0-105-generic
for both files there ias however a 3.16.0-77 present
Looks like you had a kernel mismatch happen. The easiest ways to resolve this are:
* Delete the MD in the web admin, and let it reinstall.
* symlink the default initrd and vmlinuz image to your media director's image.
-Thom
Unfortunately its not that easy. I tried deleting the orbiter and reinstall it. It boots up fine the first time, but then installs the nvidia-drivers and reboots. That is when the shit hits the fan. I followed the symlinks from /tftpboot down to the orbiter...none of them are broken. I assume there are supposed to be only two links in /tftpboot/86/ one for vmlinuz and one for initrd.img. The kernel-version on the core and the md are different- I don't know if that is of significance.
Other than that, I have no idea, why 86/initrd.img not found is being reported. I also verified the permissions and that seems to be okay too.
I'm stumped
As you seem to have issues with your IRC connection, here are a couple of hints:
* ls -l the relevant directories (tftpboot, diskless/xx, diskless/xx/boot, and paste output in here.
* cut the relevant log information, and paste in here.
Maverick0815 i have seen that problem before make sure your kernel image has 0644 permission.
I don't know...1&1 seemed to have some issues with me yesterday
here ist the content of /usr/pluto/diskless/86/boot
Quotetotal 44188
-rw-r--r-- 1 root root 1214709 Jun 28 2016 abi-3.16.0-77-generic
-rw-r--r-- 1 root root 176220 Jun 28 2016 config-3.16.0-77-generic
lrwxrwxrwx 1 root root 56 Apr 2 19:51 initrd.img -> /usr/pluto/diskless/86/boot/initrd.img-3.16.0-77-generic
-rw-r--r-- 1 root root 34468576 Apr 2 19:14 initrd.img-3.16.0-77-generic
-rw-r--r-- 1 root root 176500 Mär 12 2014 memtest86+.bin
-rw-r--r-- 1 root root 178176 Mär 12 2014 memtest86+.elf
-rw-r--r-- 1 root root 178680 Mär 12 2014 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 843 Apr 3 21:30 pastebinit
-rw-r--r-- 1 root root 2795312 Jun 28 2016 System.map-3.16.0-77-generic
lrwxrwxrwx 1 root root 53 Apr 2 19:52 vmlinuz -> /usr/pluto/diskless/86/boot/vmlinuz-3.16.0-77-generic
-rw-r--r-- 1 root root 6034368 Jun 28 2016 vmlinuz-3.16.0-77-generic
this is diskless/86
Quotetotal 80
drwxr-xr-x 2 root root 4096 Apr 2 13:51 bin
drwxr-xr-x 2 root root 4096 Apr 3 21:30 boot
drwxr-xr-x 3 root root 4096 Apr 2 13:50 dev
drwxr-xr-x 144 root root 12288 Apr 2 19:15 etc
drwxr-xr-x 4 root root 4096 Apr 2 13:48 home
lrwxrwxrwx 1 root root 33 Apr 2 13:37 initrd.img -> boot/initrd.img-3.16.0-77-generic
drwxr-xr-x 22 root root 4096 Apr 2 19:09 lib
drwxr-xr-x 2 root root 4096 Apr 2 13:48 media
drwxr-xr-x 3 root root 4096 Apr 2 13:40 mnt
drwxr-xr-x 2 root root 4096 Apr 2 13:33 opt
drwxr-xr-x 2 root root 4096 Apr 11 2014 proc
drwx------ 6 root root 4096 Apr 2 13:43 root
drwxr-xr-x 14 root root 4096 Apr 2 13:48 run
drwxr-xr-x 2 root root 4096 Apr 2 19:10 sbin
drwxr-xr-x 2 root root 4096 Apr 2 13:33 srv
drwxr-xr-x 2 root root 4096 Mär 13 2014 sys
drwxrwxrwt 5 root root 4096 Apr 2 19:14 tmp
drwxr-xr-x 11 root root 4096 Apr 2 13:34 usr
drwxr-xr-x 14 root root 4096 Apr 2 13:48 var
lrwxrwxrwx 1 root root 30 Apr 2 13:37 vmlinuz -> boot/vmlinuz-3.16.0-77-generic
this is tftpboot/86
Quotetotal 0
lrwxrwxrwx 1 root root 33 Apr 2 19:06 initrd.img -> /usr/pluto/diskless/86/initrd.img
lrwxrwxrwx 1 root root 30 Apr 2 19:06 vmlinuz -> /usr/pluto/diskless/86/vmlinuz
so far so good...what logs do I need to check?
Your list is strange.
Your initrd image is 34468576 bytes big. It is named initrd.img-3.16.0-77-generic, but initrd.img-3.16.0-77-generic on my system is only 28213576 bytes. However, a new kernel (initrd.img-4.4.0-62-generic) is around 34 million bytes.
This looks like something got screwed.
See what happens when you a reinstall of linux-image-3.16.0-77-generic, ie.
chroot /usr/pluto/diskless/86
apt-get install --reinstall linux-image-3.16.0-77-generic
exit
and try booting again.
The maximum size our current tftp server supports is <32MB
What happened is this and the result is the same
Quote
dcerouter_1047595:/home/linuxmce# chroot /usr/pluto/diskless/86
root@dcerouter:/# apt-get install --reinstall linux-image-3.16.0-77-generic
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "de_DE.UTF-8",
LC_MONETARY = "de_DE.UTF-8",
LC_ADDRESS = "de_DE.UTF-8",
LC_TELEPHONE = "de_DE.UTF-8",
LC_NAME = "de_DE.UTF-8",
LC_MEASUREMENT = "de_DE.UTF-8",
LC_IDENTIFICATION = "de_DE.UTF-8",
LC_NUMERIC = "de_DE.UTF-8",
LC_PAPER = "de_DE.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
grep: /proc/cpuinfo: No such file or directory
This kernel does not support a non-PAE CPU.
dpkg: error processing archive /var/cache/apt/archives/linux-image-3.16.0-77-generic_3.16.0-77.99~14.04.1_i386.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.16.0-77-generic /boot/vmlinuz-3.16.0-77-generic
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-3.16.0-77-generic_3.16.0-77.99~14.04.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@dcerouter:/#
Google for chroot mounting dev and proc - do that outside the chroot, and try again.
Sorry for the delay. I did my googling and this is the outcome so far:
Quotelogin as: linuxmce
linuxmce@dcerouter's password:
Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-115-generic i686)
*
linuxmce@dcerouter:~$ sudo su
[sudo] password for linuxmce:
dcerouter_1047595:/home/linuxmce# mount --bind /proc /usr/pluto/diskless/86/proc
dcerouter_1047595:/home/linuxmce# mount --bind /dev /usr/pluto/diskless/86/dev
dcerouter_1047595:/home/linuxmce# mount --bind /sys /usr/pluto/diskless/86/sys
dcerouter_1047595:/home/linuxmce# chroot /usr/pluto/diskless/86
root@dcerouter:/# apt-get install --reinstall linux-image-3.16.0-77-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libglamor0 libllvm3.4
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/15.6 MB of archives.
After this operation, 0 B of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
linux-image-3.16.0-77-generic
Authentication warning overridden.
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "de_DE.UTF-8",
LC_MONETARY = "de_DE.UTF-8",
LC_ADDRESS = "de_DE.UTF-8",
LC_TELEPHONE = "de_DE.UTF-8",
LC_NAME = "de_DE.UTF-8",
LC_MEASUREMENT = "de_DE.UTF-8",
LC_IDENTIFICATION = "de_DE.UTF-8",
LC_NUMERIC = "de_DE.UTF-8",
LC_PAPER = "de_DE.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
E: Can not write log (Is /dev/pts mounted?) - openpty (2: No such file or directory)
(Reading database ... 116678 files and directories currently installed.)
Preparing to unpack .../linux-image-3.16.0-77-generic_3.16.0-77.99~14.04.1_i386.deb ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Done.
Unpacking linux-image-3.16.0-77-generic (3.16.0-77.99~14.04.1) over (3.16.0-77.99~14.04.1) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.16.0-77-generic /boot/vmlinuz-3.16.0-77-generic
Setting up linux-image-3.16.0-77-generic (3.16.0-77.99~14.04.1) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Not updating initrd symbolic links since we are being updated/reinstalled
(3.16.0-77.99~14.04.1 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(3.16.0-77.99~14.04.1 was configured last, according to dpkg)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-77-generic /boot/vmlinuz-3.16.0-77-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-77-generic /boot/vmlinuz-3.16.0-77-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.16.0-77-generic /boot/vmlinuz-3.16.0-77-generic
update-initramfs: Generating /boot/initrd.img-3.16.0-77-generic
cryptsetup: WARNING: failed to detect canonical device of 192.168.80.1:/usr/pluto/diskless/86
cryptsetup: WARNING: could not determine root device from /etc/fstab
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.16.0-77-generic /boot/vmlinuz-3.16.0-77-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.16.0-77-generic /boot/vmlinuz-3.16.0-77-generic
run-parts: executing /etc/kernel/postinst.d/update-symlinks 3.16.0-77-generic /boot/vmlinuz-3.16.0-77-generic
chmod: cannot operate on dangling symlink '/boot/initrd.img'
chmod: cannot operate on dangling symlink '/boot/vmlinuz'
chmod: cannot operate on dangling symlink '/boot/initrd.img'
chmod: cannot operate on dangling symlink '/boot/vmlinuz'
/ /
/
root@dcerouter:/#
And does it work now? If not, what errors do you see? And paste the ls information you pasted above again.
Unfortunately it does not work. I think it may have something to do with the "dangling symlink"?
Here are the contents of the respective folder
/usr/pluto/diskless/86/boot
Quotetotal 44192
-rw-r--r-- 1 root root 1214709 Jun 28 2016 abi-3.16.0-77-generic
-rw-r--r-- 1 root root 176220 Jun 28 2016 config-3.16.0-77-generic
lrwxrwxrwx 1 root root 56 Apr 2 19:51 initrd.img -> /usr/pluto/diskless/86/boot/initrd.img-3.16.0-77-generic
-rw-r--r-- 1 root root 34468040 Apr 8 13:59 initrd.img-3.16.0-77-generic
-rw-r--r-- 1 root root 176500 Mär 12 2014 memtest86+.bin
-rw-r--r-- 1 root root 178176 Mär 12 2014 memtest86+.elf
-rw-r--r-- 1 root root 178680 Mär 12 2014 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 843 Apr 3 21:30 pastebinit
-rw-r--r-- 1 root root 2795312 Jun 28 2016 System.map-3.16.0-77-generic
lrwxrwxrwx 1 root root 53 Apr 2 19:52 vmlinuz -> /usr/pluto/diskless/86/boot/vmlinuz-3.16.0-77-generic
-rw-r--r-- 1 root root 6034368 Jun 28 2016 vmlinuz-3.16.0-77-generic
/usr/pluto/diskless/86
Quotetotal 80
drwxr-xr-x 2 root root 4096 Apr 2 13:51 bin
drwxr-xr-x 2 root root 4096 Apr 8 13:59 boot
drwxr-xr-x 3 root root 4096 Apr 2 13:50 dev
drwxr-xr-x 144 root root 12288 Apr 2 19:15 etc
drwxr-xr-x 4 root root 4096 Apr 2 13:48 home
lrwxrwxrwx 1 root root 33 Apr 8 13:59 initrd.img -> boot/initrd.img-3.16.0-77-generic
drwxr-xr-x 22 root root 4096 Apr 2 19:09 lib
drwxr-xr-x 2 root root 4096 Apr 2 13:48 media
drwxr-xr-x 3 root root 4096 Apr 2 13:40 mnt
drwxr-xr-x 2 root root 4096 Apr 2 13:33 opt
drwxr-xr-x 2 root root 4096 Apr 11 2014 proc
drwx------ 6 root root 4096 Apr 4 18:58 root
drwxr-xr-x 14 root root 4096 Apr 8 13:59 run
drwxr-xr-x 2 root root 4096 Apr 2 19:10 sbin
drwxr-xr-x 2 root root 4096 Apr 2 13:33 srv
drwxr-xr-x 2 root root 4096 Mär 13 2014 sys
drwxrwxrwt 5 root root 4096 Apr 8 13:59 tmp
drwxr-xr-x 11 root root 4096 Apr 2 13:34 usr
drwxr-xr-x 14 root root 4096 Apr 2 13:48 var
lrwxrwxrwx 1 root root 30 Apr 8 13:59 vmlinuz -> boot/vmlinuz-3.16.0-77-generic
/tftboot/86
Quotetotal 0
lrwxrwxrwx 1 root root 33 Apr 2 19:06 initrd.img -> /usr/pluto/diskless/86/initrd.img
lrwxrwxrwx 1 root root 30 Apr 2 19:06 vmlinuz -> /usr/pluto/diskless/86/vmlinuz
The files are still to large. I wonder if this has to do with some modules that are being compiled for your nvidia card.
That Sounds plausible, since the Setup was working up to the point when the graphics driver was being compiled
Seems the need to update the tftpd server grows...
Background: atftpd only supports downloads up to 32MB - I'll see what I can do create some new packages that will probably pull some other tftpd server in.
Would I be able to install one manually?
I am running it manually atm, but it involves using dpkg -r --force-xxx to get rid of atftpd and apt-get download another tftpd and manually installing it. This will cause the pluto-newmd-interactor package to be broken (in terms of package management, not functionality).
I am currently working on getting the MySQL glitches of 1604 sorted out. Between that and getting VDR onto a rpi MD, I'll see if I can find some time to get another tftpd into the mix.
No sweat...I still remember Rule #1
Maverick,
just a heads up. Installation of another tftpd server was successful. I will now need to implement the config for it, modify some package definitions in sqlCVS and hopefully, that will get us moving forward.
thank you very much for taking the time for the heads up! That sounds great.
I was that update for tftpd was up and installed it. So far that was working. However there was trouble with nvidia-375, which did not install correctly, so that I could not complete a wizard.
I decided to delete the me and start again. How the md won't even Setup and quits with Kernel-panic 0x00000200
You need to be a bit more verbose.
I'm trying:
I want to setup a new md (asrock ion300). Pxe booting works. It loads the initial image, but does not complete the setup. Instead it quits with a kernel-panic message.
Normally its supposed to setup the image, download driverd etc, until it says we announce ourselves to the router.....it never gets this far. Kernel-panic happens quite early.
Quote from: maverick0815 on June 07, 2017, 09:03:21 PM
I'm trying:
I want to setup a new md (asrock ion300). Pxe booting works. It loads the initial image, but does not complete the setup. Instead it quits with a kernel-panic message.
Normally its supposed to setup the image, download driverd etc, until it says we announce ourselves to the router.....it never gets this far. Kernel-panic happens quite early.
to confirm, that's before announcing to the router? Which version/arch of lmce?
Sent from my Nexus 5 using Tapatalk
I am on lmce 14.04
Quote from: maverick0815 on June 07, 2017, 10:08:43 PM
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
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.
/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.
I tried and this is what happens
Quotedcerouter_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
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.
We are coming full circle :-D - about 8-9 years ago the script already used the latest available kernel.
Heh. It did. ;) It's back the way it was now. :D
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
Lets start a new thread for that one. Have you tried using the number/letter keys to choose the output prior to selecting resolution?
As you suggested, I opened a new thread...I hope I am beeing verbose enough
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?