#62 mkdir and mount point failure
Opened 2 months ago by vbatts. Modified 2 months ago

from HEAD (fee9b3d)

vbatts@melisma:~/src/arm-image-installer$ sudo ./arm-image-installer --image=./Fedora-LXDE-armhfp-32-1.6-sda.raw.xz --media=/dev/mmcblk0 --target=rpi3 --addkey=/home/vbatts/.ssh/authorized_keys 

=====================================================
= Selected Image:
= ./Fedora-LXDE-armhfp-32-1.6-sda.raw.xz
= Selected Media : /dev/mmcblk0
= U-Boot Target : rpi3
= SSH Public Key /home/vbatts/.ssh/authorized_keys will be added.
=====================================================

*****************************************************
*****************************************************
******** WARNING! ALL DATA WILL BE DESTROYED ********
*****************************************************
*****************************************************

 Type 'YES' to proceed, anything else to exit now

= Proceed? YES
umount: /dev/mmcblk0: not mounted.
= Writing:
= ./Fedora-LXDE-armhfp-32-1.6-sda.raw.xz
= To: /dev/mmcblk0 ....
4444954624 bytes (4.4 GB, 4.1 GiB) copied, 66 s, 67.3 MB/s
0+573134 records in
0+573134 records out
4815060992 bytes (4.8 GB, 4.5 GiB) copied, 340.513 s, 14.1 MB/s
= Writing image complete!
mkdir: cannot create directory ‘/tmp/{boot,root,fw}’: File exists
mount: /tmp/boot: mount point does not exist.
mount: /tmp/fw: mount point does not exist.
Error: mount /dev/mmcblk0p1 /tmp/fw failed
vbatts@melisma:~/src/arm-image-installer$ ls /tmp/ | grep boot
{boot,root,fw}/

looks like the shell expansion is not happening correctly :smile:


What are the details of your host system?

vbatts@melisma:~/src/arm-image-installer$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os

I'm guessing #!/bin/sh is assuming #!/bin/bash functionality.

Login to comment on this ticket.

Metadata