by pbgapski » Fri Jun 26, 2020 3:08 pm
$this->bbcode_second_pass_quote('JohnM', 'O')ne thing I'd really like to know for when this happens again with a future update is how to recover without wiping the eMMC. I have Arch installed on /dev/mmcblk0p1 (kernel) and /dev/mmcblk0p2 (root) and my bootloader is still owned by Google, just like the OP. However, I'm unable to boot from a USB stick. CTL-U at the scary power-on screen just makes two loud beeps but is otherwise ignored so when I updated to the bad kernel my only option was to use a Chrome OS recovery medium (actually, an SD card), then from Chrome get a root terminal and enable booting from external storage. Once done I was able to boot from that same USB stick, then re-install to the eMMC. Obviously, I'd prefer to repair the problem rather than start from scratch. Once I've booted Arch using CTL-D I seem to lose the ability to use CTL-U.
I have the same CTRL-U boot problem, and had the same fate with the kernel upgrade.
To double check, earlier this week I made a dd copy of emmc to a usb drive, and then recovered chromeos, enabled dev mode and usb boot, and disabled signed boot.
Then I booted with CTRL-U with the usb drive, and restored the emmc from the usb drive. At next reboot, CTRL-D took me to arch linux on the emmc.
However, on the boot screen, now the same usb drive gives me the double beep and does not boot.
Anyone understands this behavior or has some tips to share?