sinovip bananapi_bpi-r3 bash: 8: Bad file descriptor #11760
Comments
nejtr0n
changed the title
|
I experience the same issue when trying to build the sdcard image. I already looked at target/linux/mediatek/image/filogic.mk where the artifact gets defined, but couldn't quite figure it out. https://github.com/openwrt/openwrt/blob/a96382c1bb204698cd43e82193877c10e4b63027/target/linux/mediatek/image/filogic.mk (initial support) Seems there were some changes and it now checks for some config settings. My config has both settings enabled: Not sure, where it goes wrong. |
|
The image might be too big. "bash: 8: Bad file descriptor" seems to be a failed call to an error message in the check-size routine: So, if I get it right, the trick might be to build with CONFIG_TARGET_ROOTFS_INITRAMFS=n. According to 1a6f6a1 the image size can be bigger then. EDIT I just successfully built the image by deselecting "Target Images" / "ramdisk" (CONFIG_TARGET_ROOTFS_INITRAMFS: embed the root filesystem into the kernel initramfs). |
|
It seems to my image compiled too with CONFIG_TARGET_ROOTFS_INITRAMFS=n. I've tried to increase partitions, but no succeed |
|
May be there are some other places, where we need to change initramfs size .... |
|
Partition table is defined at lines 19-39. Guess that needs to be adjusted too. Do you need the initramfs partition for testing in your setup? It don't think I need the features it provides: https://openwrt.org/docs/techref/image.format#initramfs So just disabling it might be the easiest way to go forward. |
|
I looked at the image that is provided by Sinovoip. If I understand correctly, their kernel partition has a size of 64M: So it should be possible to adjust the partition size. |
|
I need Initramfs to boot from lvm in the future. From my point of view exclude it is not right way. |
|
I successfully installed the resulting image without the initramfs using the SD card -> NAND -> eMMC way, that is described here: If you have access to the serial console, you can also do a TFTP boot from the bootloader. But yeah, expanding the partition would just make that issue go away completely. |
|
I've tried to do it too, but when I'm booting from nand, there is no @polskafan do you know how to erase nand from sdcard boot? I'll try to one more time |
|
I first tried this, until I realized the official openwrt doesn't build an image for NAND: The command to erase flash is So I had to stop after the NAND erase and follow the other set of instructions. |
|
@polskafan , yeah, after erasing NAND everything seems to be working. Flased fresh image to emmc with uart from boot menu. Thank you very much bro!! I think we could close issue? |
|
But all settings are wiped after reboot =) root@OpenWrt:~# df -h |
|
I have read that this can happen, when using the eMMC. But settings are saved for me. I build my image with the script from the OpenMPTCPRouter repository, maybe something is different there. So I don't know whats going on there. I guess this issue could be closed for me, even though the "Bad file descriptor" message is clearly a bug. |
|
it affects the bpi-r3 updates through auc or attendedsysupgrade too (for some days) : |
|
I've noticed, that it is dockerd related issue. When I include dockerd in firmware, root mounting on ram So I compiled dockerd with module option, and install it after flashing openwrt to sdcard. |
Describe the bug
Hello.
Could not build image with some custom packages. It seems to be misconfiguration of kernel or image size.
Error:
OpenWrt version
r21740-0cc1c302b1
OpenWrt target/subtarget
mediatek/filogic
Device
Bananapi BPI-R3
Image kind
Self-built image
Steps to reproduce
Get latest config
apply diff config
make defconfig and build
Actual behaviour
Error while packing image
Expected behaviour
Image successfully build
Additional info
It seems to be kernel or image partition size.
I've tried to change
CONFIG_TARGET_ROOTFS_PARTSIZE to 204, but no success.
And there is no CONFIG_TARGET_KERNEL_PARTSIZE for that device.
(When I add it to .config and make defconfig, it disappears)
Diffconfig
Terms
The text was updated successfully, but these errors were encountered: