🐞 POSSIBLE ROOTFS CORRUPTION - ChromeOS BADLY DAMAGED after installing chromebrew and updating chromeOS at the same time

[Vicky-Boi]

Describe the bug
This is probably just stupidity on my part, but my chromebook started acting extremely weirdly after I installed chromebrew and updated my chromebook at the same time. Literally every single command i run in the shell (except cd) segfaults, with no other exceptions.

This normally wouldn't be too much of a problem for me, since I can just recover with a recovery drive... yeah i spoke too soon

I think my chromeos rootfs is so badly damaged it REFUSES to boot both a recovery drive AND an RMA shim. Every time I try, my chromebook says "No valid recovery image found."

I have since been able to fix this problem by returning to safe mode and then returning back to dev mode, however I think this problem can be avoided entirely by using a few internal checks or warning the users. It has been a pain to find a fix to the problem, and it requies a complete wipe of user data.

To Reproduce
Steps to reproduce the behavior:

1. I installed chromebrew as instructed.
2. While chromebrew was installing, initiate chromeOS update in settings.
3. Once both are done, restart.

Expected behavior
Nothing to screw up..?

Environment: Paste the output of crew sysinfo -v between the two *** below

---

Segmentation fault (core dumped)

---

What I think needs to be done:

  - [ ] check if chromeos is on the latest version..?

[Vicky-Boi]

If anyone else needs this - return to safe mode then go back to dev mode. Doing this fixed the problem for me.

According to superchicken at #9612, running:

unset LD_LIBRARY_PATH
cat /usr/local/etc/crew/meta/glibc_lib235.filelist | grep .so | grep -v gconv | xargs rm -rf
export LD_LIBRARY_PATH=/usr/local/lib64

also fixes this problem.

[VenomousSteam81]

I just updated but I had already installed chromebrew.

[VenomousSteam81]

It might be because GLIBC hasn't been updated yet. You can go into VT-2 and try to use sudo but it ends up giving an error about GLIBC not being updated.

[VenomousSteam81]

Look at #9614

[VenomousSteam81]

You could have done /usr/sbin/sudo /bin/bash in VT-2 to get into a root shell lol.
I'm going to backup my .bashrc and remove the current one until this is fixed and there's a way to update it.
Edit: That did NOT work. It removed some of the sommelier errors but the shell is still bugged out.

[VenomousSteam81]

Someone else found a quick fix here, thankfully. It does work too.

[Vicky-Boi]

Someone else found a quick fix here, thankfully. It does work too.

Does the unset command work while chromeOS is in that state? This would've been useful when I still had the issue, but I managed to back up all my data so I just used my method to repair my chromebook. The fixes mentioned by superchicken seem promising, however I've already removed chromeOS entirely by this point so I'm not willing to try this fix.