New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cubietruck build fails on Ubuntu #151
Comments
The build scripts for Armbian images are brand new, not sure how much of it actually has been tested. |
cubietruck is tested - both vanilla and legacy and works ok on my end - from attached screenshot it looks like sd-card is either not found or corrupt - pls try again to rewrite image on sd-card or try another sd-card - pls see also debug notes on armbian saying 97% of all boot issues is either unreliable sd-card or power supply. |
@chrismade I think what you've done with this modification is just great. It will allow basically any board to run volumio... |
will do |
@chrismade Thanks for helping me troubleshoot this issue. The sd-card contains 3 partitions: BOOT, volumio and volumio_data here is a pastebin of the fdisk output and the contents of the partitions here is the build log |
@gdimopoulos thanks for this excellent debug info - we are coming closer to the root cause but I cannot offer a fix yet - it fails to create the volumio init-ramdisk on your end for some unknown reason: your log shows:
On my end it looks like this:
I have Debian 8u2 for my build environment: What is your build env (seems to be ubuntu)? Can you pls post output from PS: unfortunately switch to legacy won't fix it as this code is the same for both |
could you please insert a line after line number 1 ... !/bin/sh |
@volumio is there a chance to offer more xz-compressed pre-built images for download? |
My build machine is running Ubuntu 16.04 LTS Here is the build log after adding the the problem is still there and there seems to be a confirmed bug for Ubuntu server 16.04 |
@gdimopoulos: I believe this is not related as the build process uses a customized script to build an initramfs under chroot. |
@gkkpch Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. ... failed! dnsmasq: cannot create netlink socket: Address family not supported by protocol Starting Music Player Daemon: mpdFeb 27 09:18 : errno: Failed to open /var/lib/mpd/tag_cache: No such file or directory Starting Music Player Daemon: mpdFeb 27 09:20 : errno: Failed to open /var/lib/mpd/tag_cache: No such file or directory |
Hmm, those messages are OK, so nothing suspicious there.
…On 27 Feb 2017 11:48, "gdimopoulos" ***@***.***> wrote:
@gkkpch <https://github.com/gkkpch>
I found these 4 errors in the log that might be related to the failure of
the mkinitramfs script.
1.
Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. ... failed!
failed!
1.
dnsmasq: cannot create netlink socket: Address family not supported by
protocol
failed!
invoke-rc.d: initscript dnsmasq, action "start" failed.
1.
Starting Music Player Daemon: mpdFeb 27 09:18 : errno: Failed to open
/var/lib/mpd/tag_cache: No such file or directory
ERROR: Could not determine network interfaces, you must use a interfaces
config line
failed!
invoke-rc.d: initscript mpd, action "start" failed.
dpkg: error processing package mpd (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up init (1.22) ...
Setting up python-gtk2 (2.24.0-4) ...
Setting up libglade2-0:armhf (1:2.6.4-2) ...
Setting up python-glade2 (2.24.0-4) ...
Setting up avahi-discover (0.6.31-5) ...
Processing triggers for libc-bin (2.19-18+deb8u7) ...
Processing triggers for ca-certificates (20141019+deb8u2) ...
Updating certificates in /etc/ssl/certs... 174 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Processing triggers for python-support (1.0.15) ...
Processing triggers for initramfs-tools (0.120+deb8u2) ...
Errors were encountered while processing:
mpd
1.
Starting Music Player Daemon: mpdFeb 27 09:20 : errno: Failed to open
/var/lib/mpd/tag_cache: No such file or directory
ERROR: Could not determine network interfaces, you must use a interfaces
config line
failed!
invoke-rc.d: initscript mpd, action "start" failed.
dpkg: error processing package mpd (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (215-17+deb8u6) ...
Errors were encountered while processing:
mpd
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#151 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AMfAG_HIvFwz79DcMhMESdmZHKrA1vguks5rgqnhgaJpZM4MMHDj>
.
|
most errors can be ignored, we only need to focus why this happened (happens):
|
from what I read here ( thanks @gdimopoulos ) Status changed to 'Confirmed' because the bug affects multiple users. there is no fix from the volumio team - as this ubuntu bug is confirmed since May 2016 - and is no bug in debian (which is pretty close to ubuntus codebase) |
True, but we are not using mkinitramfs. |
@gdimopoulos - first my apologies - I need a "set -x" in However, I checked extended shell output on my machine and this script is doing a lot of /sys reading in order to determine the root device - |
I think it fails here: Error please report bug on initramfs-tools basically it cannot find the required modules to embed in the initramfs, so its not adding any of them. Therefore the initram does not get created, and the system will never boot... |
@gdimopoulos can you please give us another log |
@chrismade I'll give it another try with set -x and debug="y" to see if I can get any more details and report back here. I can also report that I tried the build on a Debian machine and everything worked without a hiccup. I should probably rename the issue to "cubietruck build fails on Ubuntu" because this seems to be an Ubuntu related issue. |
@gdimopoulos excellent ! yes, I assume that issue is related to ubuntu |
@chrismade I agree, people should be advised to go with Debian until this issue is fixed. It is possible that there is a problem with the particular version of initramfs-tools on Ubuntu that might be fixed in the future. |
@ALL,
I believe the problem is caused by initramfs-tools not being installed properly, which in the end could a qemu issue on ubuntu. We have seen more of those, IIRC on debian too (git clones that did not work). Carefull with 'MODULES=most', we had that in the beginning and C1/2 wouldn't boot because of initrd size. In case it doesn't, you might be lucky with ext4load/ fatload to adapted memory locations.
On 27 Feb 2017, at 22:52, chrismade <notifications@github.com> wrote:
@gdimopoulos excellent ! yes, I assume that issue is related to ubuntu
we should recommend debian instead for the time being
thx again for spending so much time in digging into this issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@gdimopoulos - pls share output from another try with set -x and debug="y" - I'm still curious ;-) |
@chrismade Yes, I'm still interested to solve this. I ran the build again with this morning with the two options enabled but didn't have time to post it here. From a quick first look, I didn't see any additional info being printed in that part of the log. I'll share the log tonight so you and anyone else interested can have a look. |
@gdimopoulos no hurry - I just would like to see what happened before this line is printed: mkinitramfs: failed to determine device for / |
@chrismade here is the promised log |
Thank you @gdimopoulos -here is the part of concern: .. [ ! -d /sys/devices/ ] .. echo Error please report bug on initramfs-tools |
The debian ( = working ) version looks like this: .. [ ! -d /sys/devices/ ] I propose as @gdimopoulos found a workaround solution by using debian instead of ubuntu and it appears that the Volumio team can't fix this ... ...to CLOSE this issue as WONTFIX - and wait for the ubuntu team to fix this |
Curious why this issue is cubietruck image dependent. |
@chrismade I can see that the debian process is a bit different than the ubuntu one. Still I cannot identify the reason why it fails since the log doesn't provide any useful info. I'm fine with closing the issue as wontfix given that this is probably an ubuntu specific issue. @macmpi I can also successfully build RPi on my system but the script fails for all the armbian-based images with the same error. |
LOG (debian stretch): ...
Creating initramfs 'volumio.initrd'
+ echo -------- mkinitramfs-custom.sh ---------
-------- mkinitramfs-custom.sh ---------
+ umask 0022
+ export PATH=/usr/bin:/sbin:/bin
+ keep=n
+ CONFDIR=/etc/initramfs-tools
+ verbose=y
+ test -e /bin/busybox
+ BUSYBOXDIR=/bin
+ test -e /usr/lib/initramfs-tools/bin/busybox
+ export BUSYBOXDIR
+ getopt -o c:d:ko:r:v -n /usr/local/sbin/mkinitramfs-custom.sh -- -o /tmp/initramfs-tmp
+ OPTIONS= -o '/tmp/initramfs-tmp' --
+ [ 0 != 0 ]
+ eval set -- -o '/tmp/initramfs-tmp' --
+ set -- -o /tmp/initramfs-tmp --
+ true
+ outfile=/tmp/initramfs-tmp
+ shift 2
+ true
+ shift
+ break
+ . /usr/share/initramfs-tools/scripts/functions
+ . /usr/share/initramfs-tools/hook-functions
+ . /etc/initramfs-tools/initramfs.conf
+ MODULES=dep
+ BUSYBOX=y
+ KEYMAP=n
+ COMPRESS=gzip
+ DEVICE=
+ NFSROOT=auto
+ EXTRA_CONF=
+ [ -e /usr/share/initramfs-tools/conf.d/* ]
+ [ -e /etc/initramfs-tools/conf.d/* ]
+ [ -d /usr/share/initramfs-tools/conf-hooks.d/* ]
+ [ -e /usr/share/initramfs-tools/conf-hooks.d/* ]
+ [ -n ]
+ [ -z /tmp/initramfs-tmp ]
+ touch /tmp/initramfs-tmp
+ readlink -f /tmp/initramfs-tmp
+ outfile=/tmp/initramfs-tmp
+ ls -t /lib/modules
+ cat
+ head -n2
+ versions=4.4.16
+ echo 4.4.16
+ awk {print $1}
+ v_version=4.4.16
+ echo 4.4.16
+ awk {print $2}
+ o_version=
+ [ -n ]
+ mktemp -d /var/tmp/mkinitramfs_XXXXXX
+ DESTDIR_REAL=/var/tmp/mkinitramfs_cO3XEC
+ chmod 755 /var/tmp/mkinitramfs_cO3XEC
+ mktemp -d /var/tmp/mkinitramfs_XXXXXX
+ DESTDIR_OTHER=/var/tmp/mkinitramfs_aZWNOi
+ chmod 755 /var/tmp/mkinitramfs_aZWNOi
+ dpkg --print-architecture
+ DPKG_ARCH=armhf
+ [ armhf = armhf ]
+ LIB_GNUE=/lib/arm-linux-gnueabihf
+ DESTDIR=/var/tmp/mkinitramfs_cO3XEC
+ version=4.4.16
+ echo Version: 4.4.16
Version: 4.4.16
+ build_initramfs
+ [ -z ]
+ compress=gzip
+ command -v gzip
+ dpkg --compare-versions 4.4.16 lt 2.6.38
+ [ gzip = lzop ]
+ [ gzip = xz ]
+ [ -d /tmp/initramfs-tmp ]
+ MODULESDIR=/lib/modules/4.4.16
+ [ ! -e /lib/modules/4.4.16 ]
+ [ ! -e /lib/modules/4.4.16/modules.dep ]
+ export MODULESDIR
+ export version
+ export CONFDIR
+ export DESTDIR
+ export DPKG_ARCH
+ export verbose
+ export KEYMAP
+ export MODULES
+ export BUSYBOX
+ export __TMPCPIOGZ
+ export __TMPEARLYCPIO
+ mkdir -p /var/tmp/mkinitramfs_cO3XEC/bin
+ mkdir -p /var/tmp/mkinitramfs_cO3XEC/conf/conf.d
+ mkdir -p /var/tmp/mkinitramfs_cO3XEC/etc
+ mkdir -p /var/tmp/mkinitramfs_cO3XEC/lib/modules
+ mkdir -p /var/tmp/mkinitramfs_cO3XEC/run
+ mkdir -p /var/tmp/mkinitramfs_cO3XEC/sbin
+ mkdir -p /var/tmp/mkinitramfs_cO3XEC/scripts
+ mkdir -p /var/tmp/mkinitramfs_cO3XEC//lib/modules/4.4.16
+ [ -f /lib/modules/4.4.16/modules.builtin ]
+ cp -p /lib/modules/4.4.16/modules.builtin /var/tmp/mkinitramfs_cO3XEC/lib/modules/4.4.16/modules.builtin
+ [ -f /lib/modules/4.4.16/modules.order ]
+ cp -p /lib/modules/4.4.16/modules.order /var/tmp/mkinitramfs_cO3XEC/lib/modules/4.4.16/modules.order
+ [ -f /etc/initramfs-tools/modules ]
+ add_modules_from_file /etc/initramfs-tools/modules
+ [ ! -e /etc/initramfs-tools/modules ]
+ grep ^[^#] /etc/initramfs-tools/modules
+ read module args
+ [ -n overlay ]
+ force_load overlay
+ manual_add_modules overlay
+ local prefix kmod options firmware
+ [ 1 -eq 0 ]
+ read prefix kmod options
+ modprobe --all --set-version=4.4.16 --ignore-install --quiet --show-depends overlay
+ [ insmod != insmod ]
+ [ -e /var/tmp/mkinitramfs_cO3XEC//lib/modules/4.4.16/kernel/fs/overlayfs/overlay.ko ]
+ install -Dpm 644 /lib/modules/4.4.16/kernel/fs/overlayfs/overlay.ko /var/tmp/mkinitramfs_cO3XEC//lib/modules/4.4.16/kernel/fs/overlayfs/overlay.ko
+ [ y = y ]
+ echo Adding module /lib/modules/4.4.16/kernel/fs/overlayfs/overlay.ko
Adding module /lib/modules/4.4.16/kernel/fs/overlayfs/overlay.ko
+ modinfo -k 4.4.16 -F firmware /lib/modules/4.4.16/kernel/fs/overlayfs/overlay.ko
+ read prefix kmod options
+ echo overlay
+ read module args
+ [ -n squashfs ]
+ force_load squashfs
+ manual_add_modules squashfs
+ local prefix kmod options firmware
+ [ 1 -eq 0 ]
+ + modprobe --allread --set-version=4.4.16 prefix --ignore-install kmod options --quiet
--show-depends squashfs
+ [ builtin != insmod ]
+ continue
+ read prefix kmod options
+ echo squashfs
+ read module args
+ [ -n nls_cp437 ]
+ force_load nls_cp437
+ manual_add_modules nls_cp437
+ local prefix kmod options firmware
+ [ 1 -eq 0 ]
+ modprobe --all --set-version=4.4.16+ --ignore-install --quiet --show-depends nls_cp437
read prefix kmod options
+ [ builtin != insmod ]
+ continue
+ read prefix kmod options
+ echo nls_cp437
+ read module args
+ [ -f /usr/share/initramfs-tools/modules.d/* ]
+ dep_add_modules
+ dep_add_modules_mount /
+ local dir block minor dev_node FSTYPE dev_sys_path
+ local modules=
+ dir=/
+ [ ! -d /sys/devices/ ]
+ + mount
read -r dev foo mp foo fs opts rest
+ [ /boot = / ]
+ read -r dev foo mp foo fs opts rest
+ [ /dev = / ]
+ read -r dev foo mp foo fs opts rest
+ [ /proc = / ]
+ read -r dev foo mp foo fs opts rest
+ [ /sys = / ]
+ read -r dev foo mp foo fs opts rest
+ eval
+ [ -z ]
+ [ -r /proc/mounts ]
+ read dev mp fs opts rest
+ [ /boot = / ]
+ read dev mp fs opts rest
+ [ /dev = / ]
+ read dev mp fs opts rest
+ [ /proc = / ]
+ read dev mp fs opts rest
+ [ /sys = / ]
+ read dev mp fs opts rest
+ eval
+ [ / != / ]
+ [ = ubifs ]
+ [ / = / ]
+ [ = /dev/root ]
+ [ -z ]
+ echo mkinitramfs: failed to determine device for /
mkinitramfs: failed to determine device for /
+ echo mkinitramfs: workaround is MODULES=most, check:
mkinitramfs: workaround is MODULES=most, check:
+ echo grep -r MODULES /etc/initramfs-tools/
grep -r MODULES /etc/initramfs-tools/
+ echo
+ echo Error please report bug on initramfs-tools
Error please report bug on initramfs-tools
+ echo Include the output of 'mount' and 'cat /proc/mounts'
Include the output of 'mount' and 'cat /proc/mounts'
+ exit 1
Creating uInitrd from 'volumio.initrd'
/usr/bin/mkimage: Can't open /boot/volumio.initrd: No such file or directory
Cleaning up
/bin/rm: cannot remove '/boot/volumio.initrd': No such file or directory
Unmounting Temp devices
==> Tinkerboard device installed
... |
Build |
finally succeeded on a debian jessie host, thx |
this little difference between ubuntu and debian is still a "known issue" - I did some investigations around it but couldn#t find a solution - so move onto a debian host is still the recommended workaround |
This is how it should be handled and it will work on debian and ubuntu host versions.
"modules=dep", even when it "works", does not do anything anyway. Tested with Odroid builds on Debian jessie, Debian buster and Ubuntu 18.04 and should work with any other build script which is using "modules=dep". |
First of all thank you for the effort to provide support for A20 devices.
I tried building the vanilla image for cubietruck with the commands provided in the instructions:
./build.sh -b arm -d armbian_cubietruck_vanilla -v 2.0
I then flashed the image with Etcher and tried to boot my cubietruck with it.
The boot process fails with the message "Ramdisk image is corrupt or invalid"
Here are some screenshots of the boot log
https://goo.gl/photos/Cm24u48CBF978ft9A
The text was updated successfully, but these errors were encountered: