enter-chroot or edit-chroot immediately reboots the machine

[eritain]

Chronicling the ongoing collapse of crouton under Google's tender ministrations ...

Running on a reef board (which is an Intel chip). Was forced to accept ChromeOS extended updates in order for Google Drive integration to keep working. Got "upgraded" to 132.0.6834.225 (Official Build) (64-bit).

Since that time, any time I pop over to VT-2 and try to sudo enter-chroot or sudo edit-chroot -all it reboots my machine. edit-chroot manages to get 2 lines into its output before the screen blanks. enter-chroot doesn't even manage to drop any of its now routine error messages before it's gone.

My chroot does automatically start up an SSH server when I enter it, but no graphical programs such as chromium or steam, which were causing reboots for other people already. Terminal only.

Reinstalling crouton doesn't help.

Kind of wish I hadn't "upgraded" my OS, 'cause if I still had a working chroot, I'd have a viable alternative to ChromeOS's Google Drive integration: use Rclone to mirror a local directory up to Google Drive.

Thanks, Google!

[dnschneid]

yeesh, that's quite bad. -l for edit-chroot does call enter-chroot -x under the hood, so I would expect that to fail if enter-chroot does as well. enter-chroot -x ignores most of the contents of the chroot, so your config (including sshd) won't affect it.

You can try running sudo mount-chroot -p nameofyourchroot and see what happens. If it fails, then something it's poking at is making Chrome unhappy. If it succeeds (doesn't reboot), then the suspect becomes some of the system modifications that enter-chroot makes. You'd have to instrument it with set -x at the start and maybe some carefully placed sleep 1 lines so you have a hope of seeing output before it triggers a reboot...