Skip to content
Snippets Groups Projects
New look: Off

'No space left on device' error during pmbootstrap.py install

    • Closed Imported Issue created by Administrator @root

    Created by: sagev9000

    Trying to build for i9100 fails when it gets to Fill Install Blockdevice

    [21:26:43] ERROR: Command failed: (native) % cd /mnt/rootfs_samsung-i9100 && cp -a efs boot sys srv run root media sbin bin usr lib dev tmp etc mnt var proc /mnt/install/

    cp: write error: No space left on device cp: write error: No space left on device cp: write error: No space left on device

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      Thanks for trying out postmarketOS! Could you post a big chunk of the end of the log file (as shown in pmbootstrap log)?

      BTW: The i9100 currently only supports installation to a sd card (pmbootstrap install --sdcard).

      EDIT: You've posted this in the chat, that should be useful:

      
(016988) [18:14:38] DEBUG: Size of chroot: 143893015
(016988) [18:14:38] % sudo du --summarize --apparent-size --block-size=1 /home/sage/.local/var/pmbootstrap/chroot_rootfs_samsung-i9100/boot
12437572 /home/sage/.local/var/pmbootstrap/chroot_rootfs_samsung-i9100/boot
(016988) [18:14:38] % sudo du --summarize --apparent-size --block-size=1 /home/sage/.local/var/pmbootstrap/chroot_rootfs_samsung-i9100/home
8192 /home/sage/.local/var/pmbootstrap/chroot_rootfs_samsung-i9100/home
(016988) [18:14:38] DEBUG: Full image size: 172661787.6
(016988) [18:14:38] (native) create samsung-i9100.img (165M)
(016988) [18:14:38] (native) % su pmos -c 'mkdir -p /home/pmos/rootfs'
(016988) [18:14:38] (native) % truncate -s 165M /home/pmos/rootfs/samsung-i9100.img
(016988) [18:14:38] (native) mount /dev/install (samsung-i9100.img)
(016988) [18:14:38] (native) mount /home/pmos/rootfs/samsung-i9100.img (loop)
(016988) [18:14:38] % sudo modprobe loop
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop7
(016988) [18:14:38] % sudo mount --bind /dev/loop7 /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop7
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop6
(016988) [18:14:38] % sudo mount --bind /dev/loop6 /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop6
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop5
(016988) [18:14:38] % sudo mount --bind /dev/loop5 /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop5
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop4
(016988) [18:14:38] % sudo mount --bind /dev/loop4 /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop4
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop3
(016988) [18:14:38] % sudo mount --bind /dev/loop3 /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop3
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop2
(016988) [18:14:38] % sudo mount --bind /dev/loop2 /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop2
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop1
(016988) [18:14:38] % sudo mount --bind /dev/loop1 /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop1
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop0
(016988) [18:14:38] % sudo mount --bind /dev/loop0 /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop0
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop-control
(016988) [18:14:38] % sudo mount --bind /dev/loop-control /home/sage/.local/var/pmbootstrap/chroot_native//dev/loop-control
(016988) [18:14:38] (native) % losetup -f /home/pmos/rootfs/samsung-i9100.img
(016988) [18:14:38] (native) % losetup --json --list
{
"loopdevices": [
{"name": "/dev/loop0", "sizelimit": "0", "offset": "0", "autoclear": "0", "ro": "0", "back-file": "/home/pmos/rootfs/samsung-i9100.img", "dio": "0", "log-sec": "512"}
]
}
(016988) [18:14:38] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native/dev/install
(016988) [18:14:38] % sudo mount --bind /dev/loop0 /home/sage/.local/var/pmbootstrap/chroot_native/dev/install
(016988) [18:14:38] (native) partition /dev/install (boot: 27M, root: the rest)
(016988) [18:14:38] (native) % parted -s /dev/install mktable msdos
(016988) [18:14:38] (native) % parted -s /dev/install mkpart primary ext2 2048s 27M
(016988) [18:14:39] (native) % parted -s /dev/install mkpart primary 27M 100%
(016988) [18:14:39] (native) % parted -s /dev/install set 1 boot on
(016988) [18:14:39] (native) % losetup --json --list
{
"loopdevices": [
{"name": "/dev/loop0", "sizelimit": "0", "offset": "0", "autoclear": "0", "ro": "0", "back-file": "/home/pmos/rootfs/samsung-i9100.img", "dio": "0", "log-sec": "512"}
]
}
(016988) [18:14:39] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native/dev/installp1
(016988) [18:14:39] % sudo mount --bind /dev/loop0p1 /home/sage/.local/var/pmbootstrap/chroot_native/dev/installp1
(016988) [18:14:39] % sudo touch /home/sage/.local/var/pmbootstrap/chroot_native/dev/installp2
(016988) [18:14:39] % sudo mount --bind /dev/loop0p2 /home/sage/.local/var/pmbootstrap/chroot_native/dev/installp2
(016988) [18:14:39] WARNING: Full disk encryption is enabled!
(016988) [18:14:39] Make sure that osk-sdl has been properly configured for your device
(016988) [18:14:39] or else you will be unable to unlock the rootfs on boot!
(016988) [18:14:39] If you started a device port, it is recommended you disable
(016988) [18:14:39] FDE by re-running the install command with '--no-fde' until
(016988) [18:14:39] you have properly configured osk-sdl. More information:
(016988) [18:14:39] <https://postmarketos.org/osk-port>
(016988) [18:14:39] (native) format /dev/installp2 (root, luks), mount to /dev/mapper/pm_crypt
(016988) [18:14:39] *** TYPE IN THE FULL DISK ENCRYPTION PASSWORD (TWICE!) ***
(016988) [18:14:39] (native) % cryptsetup luksFormat --use-urandom --cipher aes-cbc-plain64 -q /dev/installp2 --iter-time 200
(016988) [18:14:39] *** output passed to pmbootstrap stdout, not to this log ***
(016988) [18:14:44] (native) % cryptsetup luksOpen /dev/installp2 pm_crypt
(016988) [18:14:44] *** output passed to pmbootstrap stdout, not to this log ***
(016988) [18:14:45] (native) format /dev/mapper/pm_crypt (ext4), mount to /mnt/install
(016988) [18:14:45] (native) % mkfs.ext4 -F -q -L pmOS_root /dev/mapper/pm_crypt
(016988) [18:14:46] (native) % mkdir -p /mnt/install
(016988) [18:14:46] (native) % mount /dev/mapper/pm_crypt /mnt/install
(016988) [18:14:46] (native) format /dev/installp1 (boot, ext2), mount to /mnt/install/boot
(016988) [18:14:46] (native) % mkfs.ext2 -F -q -L pmOS_boot /dev/installp1
(016988) [18:14:46] (native) % mkdir -p /mnt/install/boot
(016988) [18:14:46] (native) % mount /dev/installp1 /mnt/install/boot
(016988) [18:14:46] *** (4/5) FILL INSTALL BLOCKDEVICE ***
(016988) [18:14:46] (native) copy rootfs_samsung-i9100 to /mnt/install/
(016988) [18:14:46] % sudo mkdir -p /home/sage/.local/var/pmbootstrap/chroot_native/mnt/rootfs_samsung-i9100
(016988) [18:14:46] % sudo mount --bind /home/sage/.local/var/pmbootstrap/chroot_rootfs_samsung-i9100 /home/sage/.local/var/pmbootstrap/chroot_native/mnt/rootfs_samsung-i9100
(016988) [18:14:46] (native) % cd /mnt/rootfs_samsung-i9100 && cp -a boot run usr sbin srv media bin sys proc var tmp etc lib efs root dev mnt /mnt/install/
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: can't create directory '/mnt/install/lib/device-mapper': No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: can't create directory '/mnt/install/lib/mdev': No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: can't create directory '/mnt/install/lib/security': No space left on device
cp: can't create directory '/mnt/install/efs': No space left on device
cp: can't create directory '/mnt/install/root': No space left on device
cp: can't create directory '/mnt/install/dev': No space left on device
cp: can't create directory '/mnt/install/mnt': No space left on device
(016988) [18:14:48] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(016988) [18:14:48] NOTE: The failed command's output is above the ^^^ line in the logfile: /home/sage/.local/var/pmbootstrap/log.txt
(016988) [18:14:48] ERROR: Command failed: (native) % cd /mnt/rootfs_samsung-i9100 && cp -a boot run usr sbin srv media bin sys proc var tmp etc lib efs root dev mnt /mnt/install/
(016988) [18:14:48] Run 'pmbootstrap log' for details.
(016988) [18:14:48] See also: <https://postmarketos.org/troubleshooting>
(016988) [18:14:48] Traceback (most recent call last):
File "/home/sage/git/pmbootstrap/pmb/helpers/run.py", line 53, in core
stderr=args.logfd)
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '/usr/bin/sh', '-c', "env -i CHARSET=UTF-8 PATH=/usr/lib/ccache/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin SHELL=/bin/ash HISTFILE=~/.ash_history /usr/bin/chroot /home/sage/.local/var/pmbootstrap/chroot_native sh -c 'cd /mnt/rootfs_samsung-i9100;cp -a boot run usr sbin srv media bin sys proc var tmp etc lib efs root dev mnt /mnt/install/'"]' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/home/sage/git/pmbootstrap/pmb/__init__.py", line 59, in main
getattr(frontend, args.action)(args)
File "/home/sage/git/pmbootstrap/pmb/helpers/frontend.py", line 148, in install
pmb.install.install(args)
File "/home/sage/git/pmbootstrap/pmb/install/install.py", line 331, in install
install_system_image(args)
File "/home/sage/git/pmbootstrap/pmb/install/install.py", line 209, in install_system_image
copy_files_from_chroot(args)
File "/home/sage/git/pmbootstrap/pmb/install/install.py", line 92, in copy_files_from_chroot
working_dir=mountpoint)
File "/home/sage/git/pmbootstrap/pmb/chroot/root.py", line 86, in root
return_stdout, check)
File "/home/sage/git/pmbootstrap/pmb/helpers/run.py", line 66, in core
raise RuntimeError("Command failed: " + log_message) from exc
RuntimeError: Command failed: (native) % cd /mnt/rootfs_samsung-i9100 && cp -a boot run usr sbin srv media bin sys proc var tmp etc lib efs root dev mnt /mnt/install/

      By * postmarketOS Bot on 2017-11-22T00:05:13

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: sagev9000

      Yep, that's me. I got the impression from the wiki that I could get away with just using the internal memory if I didn't include a UI in the install, but maybe I was mistaken. Either way, those are the errors I was gettings.

      By * postmarketOS Bot on 2017-11-22T00:08:23

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      Oh, then please edit the wiki to reflect that it is not possible right now.

      There's a plan to make flashing to system work though, but it will take some time until we have this: https://github.com/postmarketOS/pmbootstrap/issues/456#issuecomment-343686341 (you could also work on it if you are interested and gotten a bit more familiar with pmOS first).

      By * postmarketOS Bot on 2017-11-22T00:12:23

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      Thanks for editing the wiki @sagev9000! I've gotten a bit confused as I did not realize that you were trying the netcat method, which is described in the wiki. I assumed you were doing the regular installation.

      Flashing methods

      So let me clarify:

      • The regular installation with pmbootstrap install and pmbootstrap flasher flash_system is not working (the system flashing part doesn't work yet)
      • However, the netcat installation should work
      • Recovery installation method and sdcard installation method should work, too.

      I have edited the wiki page to reflect this, and also linked to this issue regarding the "no space left" issue. Meanwhile, @montvid ran in the same issue.

      Why do you get "no space left on device"?

      First some more explanation, what is going on here: During pmbootstrap install, we create the rootfs_samsung-i9100 chroot, which will hold the same data, that will end up in the image file we create. That image file can be flashed via netcat, recovery install (and usually with pmbootstrap flasher, but not for the i9100 yet as mentioned above).

      We need to set the size of that image in advance, before we copy all files into it. And it seems that at least for you two, the algorithm that calculates the image size isn't working. Therefore you get the "no space left on device" message, and with device, it means the image file we created beforehand.

      Note: By using the sdcard method, you won't run into a "no space left on device" issue, because we don't create a fixed size image, but use the whole sd card size instead.

      What can we do?

      The problem is, that calculating the right size of a folder isn't that trivial (see https://github.com/postmarketOS/pmbootstrap/pull/760#issuecomment-337043300).

      The following snippet is where we calculate the image size, currently 120% (1.20) of what we calculated the root size to be. Could you play with this value, until it works for you (try 1.5 etc.), and report back?

      https://github.com/postmarketOS/pmbootstrap/blob/bc2784ece7dbbb5b9fbc8e1855566d3e9e770e59/pmb/install/install.py#L62-L66

      (CC: @drebrez)

      By * postmarketOS Bot on 2017-12-04T20:21:30

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      I can reproduce this now (selected plasma-mobile as UI, maybe that triggers it?). Made a PR with a fix, that works for me (always increasing the root partition size by 50 MB). Please test if you have time.

      By * postmarketOS Bot on 2017-12-07T23:32:46

      Edited by Ghost User
      • Administrator
        Administrator @root · Imported
        Author Owner

        The installation section sais to comment here with a no space left issue, i can reproduce this pretty reliably with xiamoi-armani (as it is in-tree already), i can play around a bit with the values to see if i can get it to build.

        log-armani-install.txt

        By Ghost User on 2020-04-11T22:13:46

        Edited by Ghost User
      • Administrator
        Administrator @root · Imported
        Author Owner

        Thanks for reporting, @kamirama! I've just created a proposal to resolve this once and for all for everybody who is affected: #1904 (closed) please have a look and consider giving it a shot :gun: :smiley:

        By Oliver Smith on 2020-04-11T22:13:46

      • Please register or sign in to reply
    • Administrator mentioned in issue #1904 (closed) · Imported

      mentioned in issue #1904 (closed)

      By Oliver Smith on 2020-04-11T22:10:56

    • Administrator
      Administrator @root · Imported
      Author Owner

      same situation for this, thanks!

      log.txt

      P.S. I set the boot partition is 32MB by "pmbootstrap init", instead of 128MB as default

      By Edward Elric on 2020-08-11T09:13:36

      Edited by Administrator
    • Administrator
      Administrator @root · Imported
      Author Owner

      After revert to BOOT partition to 128MB my problem is solved.

      By Edward Elric on 2020-08-11T09:23:03

      • Administrator
        Administrator @root · Imported
        Author Owner

        I am suddenly facing this error. Tried adding Extra free space upto 95. Still not solved. Also getting the issue on sdcard.

        By Software Freedom Fighter on 2021-03-30T14:15:51

        Edited by Administrator
      • Administrator
        Administrator @root · Imported
        Author Owner

        I also saw it on bpo, but only for pinephone/pinetab + phosh images on edge and v21.03. (not for any of the other devices or UIs).

        For bpo, I had to set extra_space to 500 to make it pass. Try that, and if it does not work, please create a new issue - this one is ancient.

        By Oliver Smith on 2021-03-30T14:15:51

      • Please register or sign in to reply
    Please register or sign in to reply