Chrome developers have historically been told to make disk images that have larger-than-normal rootfs sizes, since builds of Chrome with symbols won't fit in the default layout.

Try building with a 4 GB rootfs:

./setup_board --board=link && \
./build_packages --board=link && \
./build_image --board=link --noenable_rootfs_verification \
        --disk_layout=4gb-rootfs test

Flash image to USB, boot your Pixel 1 off it, and on-device run chromeos-install.

This fails with a screen full of SMART disk logs.

The actual error (offscreen) is something like "mount: wrong fs type, bad option..."

If you build an image with --disk_layout=2gb-rootfs everything works.

I'm not sure what the underlying issue is -- but it seems wrong that build_image will make an image you can't install.

vapier/derat - do we have a crbug component for CrOS build tool issues?