Crouton: chroot install - sed: can't read tests/cras_test_client

[niveknosredneh]

chronos@localhost ~/Downloads $ sudo edit-chroot -all
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
WARNING: Unable to register core dump handler.
crouton: version 1-20190710132432~master:7e345389
release: xenial
architecture: amd64
targets: xfce
host: version 12345.0.0 (Official Build) dev-channel cave 
kernel: Linux localhost 3.18.0-19718-g3647ead2beb2 #1 SMP PREEMPT Sun Jul 14 21:59:29 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

Trying to install a fresh chroot.

sudo ~/Downloads/crouton -t xfce

...
The following packages were automatically installed and are no longer required:
  libasound2-dev:i386 libc6-dev:i386 libglib2.0-0 libspeex-dev:i386 libspeex1:i386 libspeexdsp-dev:i386 linux-libc-dev:i386 pkg-config
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
sed: can't read tests/cras_test_client.c: No such file or directory
Failed to complete chroot setup.
sh: 0: /tmp/crouton.GLr/host-bin/unmount-chroot: warning: script from noexec mount; see https://chromium.googlesource.com/chromiumos/docs/+/master/security/noexec_shell_scripts.md
/tmp/crouton.GLr/host-bin/unmount-chroot: 42: .: /tmp/crouton.GLr/host-bin/../installer/functions: warning: script from noexec mount; see https://chromium.googlesource.com/chromiumos/docs/+/master/security/noexec_shell_scripts.md
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

also fails after sudo install -Dt /usr/local/bin -m 755 ~/Downloads/crouton
and running crouton instead of ~/Downloads/crouton

[TopRamenModernShaman]

Bump, I have been battling this exact same issue.

I also notice you have the noexec mount issue. That could be fixed by typing 'mount -o remount,exec /tmp
' that essentially sets that directory to allow executables. New chrome update tried to secure those directories and made them by default nonexecutable

[alphawave7]

/sorry, posted this in another issue when it belonged here
Fresh powerwash on Acer 15 Chromebook.
Also experiencing hung install with unmount..example:

upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
sed: can't read tests/cras_test_client.c: No such file or directory
Failed to complete chroot setup.
The chroot setup script may be broken. Your chroot is not fully configured.
Removing the chroot setup script. You may want to update your chroot again.
UID 1000 not found in xenial
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
chronos@localhost / $

[rjwboys1]

also getting

sed: can't read tests/cras_test_client.c: No such file or directory
Failed to complete chroot setup.
Unmounting /media/removable/Linux/chroots/xenial...

sudo edit-chroot -all
name: xenial
encrypted: no
Entering /media/removable/Linux/chroots/xenial...
WARNING: Unable to register core dump handler.
crouton: version 1-20190710132432~master:7e345389
release: xenial
architecture: amd64
targets: unity
host: version 12345.0.0 (Official Build) dev-channel lulu
kernel: Linux localhost 3.14.0 #1 SMP PREEMPT Sun Jul 14 22:03:14 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /media/removable/Linux/chroots/xenial...

[tjbergst]

I had the same issue as the OP. I applied the noexec mount issue fix from @TopRamenModernShaman and it was able to successfully create the chroot. On the beta channel.

[rjwboys1]

I the same issue as the OP. I applied the noexec mount issue fix from @TopRamenModernShaman and it was able to successfully create the chroot.

i have done that and only got rid of the noexec messages but still can't create chroot

[Dupplicate]

Also have these issues. Was able to remount /tmp in exec mode, but missing cras_test_client stops installation anyway.

[rjwboys1]

i have even tried deleteing chroot and rebooting

[mrredstone11]

ive been getting the cras test error too

[slimsh0tty]

Same issue:

chronos@localhost ~ $ sudo edit-chroot -all
Password:
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20190710132432~master:7e345389
release: xenial
architecture: amd64
targets: xfce
host: version 12345.0.0 (Official Build) dev-channel nocturne
kernel: Linux localhost 4.4.185-16695-gfba3f42d7c64 #1 SMP PREEMPT Sun Jul 14 21:40:04 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
chronos@localhost ~ $

Can anyone confirm that this is also broken for the stable channel? This maybe a DEV channel issue.

[TopRamenModernShaman]

Yeah the noexec just gets rid of a few errors. I keep getting "Warning: unable to register core dump handler" aswell as the test/cras errors. I have not tried this out of dev channel, I havent been home to do so. Can anyone try this on the standard boot?

[Dupplicate]

I tried wiping the chromebook (out and back into devmode). Problem persists.
Can it be that using an alternative chroot root is a problem? Mine is on an (ext4) SD card.

[TopRamenModernShaman]

GOOD NEWS!!!! I GOT IT!!

So based on @slimsh0tty the channel is part of the issue. So here's my break down for everyone.

-Power washed my chromebook;
-Put chromebook into Dev-mode;
-Logged in and went to settings -> About Chrome OS -> Detailed Build Info -> Change channel to Stable;

Now that we're back into a Dev-mode and stable channel chromebook we can almost start the crouton installation, but we need to do a few things.

-First we need to 'sudo mkdir /usr/local/bin' if that directory isnt already there;
-Secondly I had to do this to create a directory within chroot that I didnt have ''/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/var'' (replace xenial with what ever target you choose for the crouton flavor);
-Thirdly you have to run the "sudo mount -o remount,exec /tmp" ;(Note on that one, chromeOS had a new update that essentially for security wont let you run executables from just any directory, so you had to flip the NOEXEC flag on /tmp to executable);

From there you should be good to go! Hope this helps @niveknosredneh

[rjwboys1]

will try later

[slimsh0tty]

Thanks to @TopRamenModernShaman, I now have a working chroot on my Pixel Slate. Going back to stable and powerwashing after was the key.

[Dupplicate]

Can confirm for Acer Chromebook R11.
After switching to stable channel + devmode error no longer occurs.

[boywondr16]

@TopRamenModernShaman - Step 2 - the creation of the "var" directory--and I'm limited in my knowledge, so bear with me--where do I input that? I can get enter-chroot to allow me into anything without unmounting because of that stupid UID 1000 error.

[Civon]

GOOD NEWS!!!! I GOT IT!!

So based on @slimsh0tty the channel is part of the issue. So here's my break down for everyone.

-Power washed my chromebook;
-Put chromebook into Dev-mode;
-Logged in and went to settings -> About Chrome OS -> Detailed Build Info -> Change channel to Stable;

Now that we're back into a Dev-mode and stable channel chromebook we can almost start the crouton installation, but we need to do a few things.

-First we need to 'sudo mkdir /usr/local/bin' if that directory isnt already there;
-Secondly I had to do this to create a directory within chroot that I didnt have ''/var/run/crouton/mnt/stateful_partition/crouton/chroots/xenial/var'' (replace xenial with what ever target you choose for the crouton flavor);
-Thirdly you have to run the "sudo mount -o remount,exec /tmp" ;(Note on that one, chromeOS had a new update that essentially for security wont let you run executables from just any directory, so you had to flip the NOEXEC flag on /tmp to executable);

From there you should be good to go! Hope this helps @niveknosredneh

that works! help a lot.
my symptom is always stop at compiling CRAS(i386).
here is my gist note