Crostini Failure After Chrome OS 74 Upgrade

Crostini has completely melted down after I upgraded my Pixelbook to Chrome OS 74.

After I upgraded to Chrome OS Version 74.0.3729.125 I started the Terminal and saw a message saying that the Linux apps was being upgraded. The upgrade completed and Terminal launched.

I then enabled the backup feature and ran a backup before starting my second container. I moved the backup file to my NAS.

Later I launched Gnome Terminal, which was in a second container. I saw a message saying that the Linux apps was being upgraded, I assumed that meant the second container was being upgraded and so I waited but the upgrade never completed, all I saw was the "cursor" spinning over the Gnome Terminal icon.

After waiting an hour for the upgrade to complete, I shutdown the Pixelbook. At this point I don't know if something in that container broke during the upgrade or I broke it when I shutdown the Pixelbook. (I recall that I had Docker containers running in this second container so I wonder if that was the cause.)

After the Pixelbook came backup I decided to try and manually start the second container, which was named fjmdocker. I got the following error.

(termina) chronos@localhost ~ $ run_container.sh --container_name fjmdocker --shell --user frankmcpherson run_container: warning: container token not supplied; garcon may not function Device container_token removed from fjmdocker Device sshd_config added to fjmdocker Device ssh_host_key removed from fjmdocker Device ssh_authorized_keys removed from fjmdocker Error: Common start logic: Failed to change ownership of: /mnt/stateful/lxd/storage-pools/default/containers/fjmdocker/rootfs/var/lib/docker/btrfs/subvolumes/f7c8b736243dcc72741dde106af324f6a11997827808bcd5a2ef56eedf52ebeb/etc/iproute2/rt_realms Try `lxc info --show-log fjmdocker` for more info run_container: error: Failed to start container 'fjmdocker'

While contemplating what to do next the Pixelbook shutdown. Upon the restart I tried launching Terminal, which never started. I then attempted to access termina via crosh and got the following.

crosh> vmc start termina Error: routine at frontends/vmc.rs:118 `vm_start(vm_name,user_id_hash,matches.opt_present("enable-gpu"))` failed: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." crosh>

At this point I determined Crostini was completely messed up and I determined I needed to remove it and start over, hoping that I could restore penguin from the backup I made after the upgrade to Chrome OS 74.

I went in to settings and disabled the Linux apps. I launched the Terminal, got a command prompt and confirmed I had a clean container. I did a sudo apt update && sudo apt upgrade.

Next, I decided to try a restore. I copied the backup file to the Chrome OS Downloads folder and started the restore, which gets about half way through and then Pixelbook shuts down. I tried running the restore twice with the same thing happening both times.

At this point I don't have an option other than to rebuild from scratch, a casualty of running beta software. Fortunately, I haven't lost any real data, although I did have a local copy of this wiki installed that I was using for some local documentation and that data was not backed up.