# Converting a mender debian image for tinkerboad issue **URL:** \ **Category:** General Discussions\ **Tags:** debian\ **Created:** [November 20, 2020, 6:31pm UTC](https://hub.mender.io/t/converting-a-mender-debian-image-for-tinkerboad-issue/2872 "2020-11-20T18:31:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![asnchzv](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@asnchzv](https://hub.mender.io/u/asnchzv)\ **Post date:** [November 20, 2020, 6:31pm UTC](https://hub.mender.io/t/converting-a-mender-debian-image-for-tinkerboad-issue/2872/1 "2020-11-20T18:31:46Z")
Hello, this is my first time using mender. I’ve followed the convert a mender debian image tutorial trying to get one image for Asus Tinkerboard. I’m stuck in the last step, this is the output: > citysense@citysense-desktop:~/mender-convert$ sudo MENDER\_ARTIFACT\_NAME=release-1 ./docker-mender-convert > –disk-image input/golden-image-1.img > –config configs/mender\_convert\_config > –overlay rootfs\_overlay\_demo/ > Running mender-convert --disk-image input/golden-image-1.img --config configs/mender\_convert\_config --overlay rootfs\_overlay\_demo/ > Running mender-convert-extract: --disk-image input/golden-image-1.img --config configs/mender\_convert\_config --overlay rootfs\_overlay\_demo/ > 2020-11-20 18:04:43 [INFO] [mender-convert-extract] Using configuration file: configs/mender\_convert\_config > 2020-11-20 18:04:43 [INFO] [mender-convert-extract] Using configuration file: configs/mender\_convert\_config > 2020-11-20 18:04:43 [INFO] [mender-convert-extract] Validating disk image > 2020-11-20 18:04:43 [INFO] [mender-convert-extract] Disk parsed successfully > 2020-11-20 18:04:43 [INFO] [mender-convert-extract] NUMBER OF PARTS: 2 TYPE: dos > 2020-11-20 18:04:43 [INFO] [mender-convert-extract] PART 1: SIZE: 64M TYPE: 0xc > 2020-11-20 18:04:43 [INFO] [mender-convert-extract] PART 1: extracting to work/part-1.fs > 2020-11-20 18:04:44 [INFO] [mender-convert-extract] PART 2: SIZE: 3.9G TYPE: 0x83 > 2020-11-20 18:04:44 [INFO] [mender-convert-extract] PART 2: extracting to work/part-2.fs > 2020-11-20 18:09:34 [INFO] [mender-convert-extract] Extracting boot gap to work/boot-gap.bin > Running mender-convert-modify: --disk-image input/golden-image-1.img --config configs/mender\_convert\_config --overlay rootfs\_overlay\_demo/ > 2020-11-20 18:09:38 [INFO] [mender-convert-modify] Using configuration file: configs/mender\_convert\_config > 2020-11-20 18:09:38 [INFO] [mender-convert-modify] Using configuration file: configs/mender\_convert\_config > 2020-11-20 18:09:56 [INFO] [mender-convert-modify] Installing Mender client and related files > grep: work/boot/hdmi/hdmi\_modes.txt: Input/output error > 2020-11-20 18:10:10 [INFO] [mender-convert-modify] Found Linux kernel image in boot part, moving to rootfs/boot > 2020-11-20 18:10:10 [INFO] [mender-convert-modify] Found Linux kernel image: > > work/boot/zImage > > 2020-11-20 18:10:10 [WARN] [mender-convert-modify] Detected a kernel which does not have an EFI stub. This kernel is not supported when booting with UEFI. Please consider using a U-Boot port if the board has one (look for a board specific file in `configs`), or find a kernel which has the CONFIG\_EFI\_STUB turned on. To ignore this message and proceed anyway, set the MENDER\_IGNORE\_MISSING\_EFI\_STUB=1 config option. > 2020-11-20 18:10:10 [INFO] [mender-convert-modify] Unfortunately we where not able to find the initrd image. > 2020-11-20 18:10:10 [INFO] [mender-convert-modify] Please specify the image name using MENDER\_GRUB\_INITRD\_IMAGETYPE (only required if your board is using this) > install: cannot create directory ‘…/boot/EFI’: Read-only file system > make: \*\*\* [Makefile:56: install-boot-files] Error 1 > mender-convert-modify has finished. Cleaning up… > umount: work/boot: no mount point specified. > rm: cannot remove ‘work/rootfs’: Device or resource busy > rm: cannot remove ‘work/boot/zImage’: Read-only file system > rm: cannot remove ‘work/boot/rk3288-miniarm.dtb’: Read-only file system > rm: cannot remove ‘work/boot/overlays/ads7846-tinker.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/audioinjector-addons.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/camera-ov5647.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/ds1307.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/es90x8q2m-dac.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/googlevoicehat-soundcard.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/hifiberry-amp.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/hifiberry-dac.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/hifiberry-dacplus.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/hifiberry-digi-pro.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/hifiberry-digi.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/iqaudio-dac.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/iqaudio-dacplus.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/iqaudio-digi-wm8804-audio.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/justboom-dac.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/justboom-digi.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/lirc-rpi.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/lirc-toshiba.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/mcp2515-can0.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/pitft35-resistive-tinker.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/pps-gpio.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/rpi-dac.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/seeed-2mic-voicecard.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/w1-gpio.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/waveshare32b-tinker.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/overlays/waveshare35a-tinker.dtbo’: Read-only file system > rm: cannot remove ‘work/boot/hw\_intf.conf’: Read-only file system > rm: cannot remove ‘work/boot/extlinux/extlinux.conf’: Read-only file system > rm: cannot remove ‘work/boot/extlinux/.\_extlinux.conf’: Read-only file system > rm: cannot remove ‘work/boot/wlan\_preload.EXAMPLE’: Read-only file system > rm: cannot remove ‘work/boot/config.txt’: Read-only file system > rm: cannot remove ‘work/boot/.\_hw\_intf.conf’: Read-only file system > rm: cannot remove ‘work/boot/hdmi/hdmi\_modes.txt’: Read-only file system > rm: cannot remove ‘work/boot/System Volume Information/WPSettings.dat’: Read-only file system > rm: cannot remove ‘work/boot/System Volume Information/IndexerVolumeGuid’: Read-only file system Any info will be very helpful. Thanks a lot! ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [November 23, 2020, 9:41am UTC](https://hub.mender.io/t/converting-a-mender-debian-image-for-tinkerboad-issue/2872/2 "2020-11-23T09:41:02Z")
> [@asnchzv](#): > > install: cannot create directory ‘…/boot/EFI’: Read-only file system > make: \*\*\* [Makefile:56: install-boot-files] Error 1 Odd. Are you running on a Mac? ---
**Author:** ![asnchzv](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@asnchzv](https://hub.mender.io/u/asnchzv)\ **Post date:** [November 23, 2020, 3:17pm UTC](https://hub.mender.io/t/converting-a-mender-debian-image-for-tinkerboad-issue/2872/3 "2020-11-23T15:17:55Z")
Hi, no. I’m running on Ubuntu (Nvidia Jetson). ---
**Author:** ![asnchzv](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@asnchzv](https://hub.mender.io/u/asnchzv)\ **Post date:** [November 25, 2020, 3:30pm UTC](https://hub.mender.io/t/converting-a-mender-debian-image-for-tinkerboad-issue/2872/4 "2020-11-25T15:30:01Z")
There’s rpi and beaglebone config files, but none works. How can I make a config file for Tinkerboard Debian? ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [November 30, 2020, 5:19pm UTC](https://hub.mender.io/t/converting-a-mender-debian-image-for-tinkerboad-issue/2872/5 "2020-11-30T17:19:40Z")
I would imagine it’s similar to the other Debian configs that are available however each Board/OS combination may require customization. We do offer [consulting services](https://mender.io/support-and-services/board-integration) for this or if you do it yourself we would gladly accept a PR and a [board integration post](https://hub.mender.io/c/board-integrations/6) here. Drew