Issues when Installing to Chroot to SD Card

[gsilvers]

Hello,

Hopefully I am not doing something stupid here. I've installed chroots to my SSD but 16gb of space is no good! I have a 64 GB SD card I've tried formatting to the default exfat as well as ext4 and regardless of what format I use when I install arch via chroagh I get the following error:

error: Partition / too full: 185533 blocks needed, 154662 blocks free error: not enough free disk space error: failed to commit transaction (not enough free disk space) Errors occurred, no packages were upgraded. Failed to complete chroot setup. Unmounting /media/removable/Chroagh/chroots/arch...

This occurs when the script is installing the largest part of the chroot, x11 and the desktop enviornment (in this case gnome).

The SD card is fully empty and has more than enough space. Could anyone help?

[drinkcat]

What command are you using to install chroagh? Can you post the output of df -h as well?

[gsilvers]

I execute two commands to perform the installation

$ sudo ln -s /media/removable/Chroagh/chroots/ /usr/local/chroots followed by $ sudo sh -e installer/main.sh -r arch -t gnome

I am going to clear the SD card back off and get you the partition info. I was trying some more combo's this morning.

[gsilvers]

Hmm well this certainly is the start of the issue.

chronos@localhost / $ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 1.2G 1015M 175M 86% / devtmpfs 1.9G 0 1.9G 0% /dev tmp 1.9G 17M 1.9G 1% /tmp run 1.9G 572K 1.9G 1% /run shmfs 1.9G 50M 1.9G 3% /dev/shm /dev/mmcblk0p1 11G 1.1G 8.7G 11% /home /dev/mmcblk0p8 12M 24K 12M 1% /usr/share/oem /dev/mapper/encstateful 3.1G 52M 3.0G 2% /var media 1.9G 0 1.9G 0% /media none 1.9G 0 1.9G 0% /sys/fs/cgroup /home/.shadow/5c7585645bae57186e0a0cc51f802f21996fcbb0/vault 11G 1.1G 8.7G 11% /home/chronos/user

I just reformatted the SD card. It is showing as nearly 59gb of ext4 on my other machine.

[drinkcat]

and the output of cat /etc/lsb-release? I suspect your version of Chromium OS does not have support for ext4, you your SD card does not get mounted (so you're installing in a tmpfs...).

See https://github.com/dnschneid/crouton/issues/954 (ext4 support is coming back in the next batch of releases, though).

[gsilvers]

I am on stable

CHROMEOS_AUSERVER=https://tools.google.com/service/update2 CHROMEOS_BOARD_APPID={493FA09F-94EA-B829-46E0-48B12FD7264D} CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1} CHROMEOS_DEVSERVER= CHROMEOS_RELEASE_APPID={493FA09F-94EA-B829-46E0-48B12FD7264D} CHROMEOS_RELEASE_BOARD=swanky-signed-mpkeys CHROMEOS_RELEASE_DESCRIPTION=6158.64.0 (Official Build) stable-channel swanky CHROMEOS_RELEASE_NAME=Chrome OS CHROMEOS_RELEASE_TRACK=stable-channel CHROMEOS_RELEASE_VERSION=6158.64.0 GOOGLE_RELEASE=6158.64.0

I was under the impression they reverted the removed support for ext2/3/4 in stable no?

[drinkcat]

They did, but 6158.64.0 does not include the revert.

The easiest solution, while waiting for the next release, is to mount the device manually, e.g.

sudo mount /dev/sda1 /media/removable/xyz

[gsilvers]

Would swapping to beta get me to a recent enough build?

[drinkcat]

No. dev channel (6366.0.0) is the only one to have it at this stage.

[gsilvers]

Strange they must have some more work to do swapped to beta channel updated and rebooted and show v6366 and the partition is not recognized. No worries I will just have to mount /dev/mmcblkp1 manually as you suggested. I'm going to mark this closed but give a shout if you need any assistance testing with SD cards. I will be a user of your project for some time I as I'm now the owner of the chromebook I was messing wtih.

[drinkcat]

You're right, ext4 works on 6373.0.0 (canary), but not on 6366.0.0.