reynhout / chrx

Chromebook Unix
419 stars 56 forks source link

Need help getting back into Linux partition. #47

Closed ghost closed 7 years ago

ghost commented 7 years ago

Basically I went and updated GalliumOS and didn't update grub properly which is now preventing me from booting into it. I think I just need to reinstall grub so I thought to try to use the installer to install the grub partition again or something. After booting it up I got this

chronos@localhost / $ cd ; curl -Os https://chrx.org/go && sh go chrx installer, version 2.4.1

Hardware ID: CELES_D25-B4A-F8A-A9K
Model:       Samsung Chromebook 3
Released:    2016
CPU Family:  Intel Braswell
Prognosis:   success likely, ONLY IF FIRMWARE HAS BEEN UPDATED!

Checking hardware support for legacy boot... OK Setting up target disk /dev/mmcblk0...

Installing to /dev/mmcblk0p7... Found a dos partition table in /dev/mmcblk0p7 Proceed anyway? (y,n)

What should I put in, and what should I do to reinstall grub?

reynhout commented 7 years ago

Don't do any of that.

Do this: https://www.reddit.com/r/GalliumOS/comments/5mhjd3/acer_14_wont_boot_after_grub_update/dc3o3iv/?st=iyx72g0o&sh=e942f15b

ghost commented 7 years ago

For some reason I ended up with an error at the chroot commands

chronos@localhost ~ $ sudo bash localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # mkdir /tmp/a localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # GALLIUMOS_ROOT=/dev/mmcblk0p7 localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # mount $GALLIUMOS_ROOT /tmp/a localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # mount -o bind /proc /tmp/a/proc localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # mount -o bind /dev /tmp/a/dev localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # mount -o bind /dev/pts /tmp/a/dev/pts localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # mount -o bind /sys /tmp/a/sys localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # mount -o bind /run /tmp/a/run localhost u-1b95088fd3adbaa73192abb16574c545c8be38bd # chroot /tmp/a /bin/bash groups: cannot find name for group ID 11 groups: cannot find name for group ID 207 groups: cannot find name for group ID 208 groups: cannot find name for group ID 219 groups: cannot find name for group ID 1001 To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details.

root@localhost:/# sudo chroot /tmp/a /bin/bash chroot: cannot change root directory to '/tmp/a': No such file or directory

edit: I did the stuff the proper way (I'm seriously tired, as for proper I mean I made the folders myself) and this time I get: root@localhost:/# chroot /tmp/a /bin/bash chroot: failed to run command ‘/bin/bash’: No such file or directory

reynhout commented 7 years ago

You only need to chroot /tmp/a /bin/bash once. The first time you did it (when your prompt changed) it worked correctly. Those messages about group names are not errors.

ghost commented 7 years ago

Okay I've done it! Thanks for helping me out kind dude, I'll make sure never to make this mistake again now.