Subj : Updating grub boot order
To   : ARELOR
From : Dumas Walker
Date : Mon Sep 23 2019 07:33 pm

> My suggestion:

> insert the card or storage media of the sbc into
> a running system with a matching architecture,
> mount that card and chroot to it. ie:

> # mount /dev/your_card /mnt/whatever
> # mount -o bind,dev /dev /mnt/whatever/dev
> # mount -o bind,proc /proc /mnt/whatever/proc
> # mount -o bind,sys /sys /mnt/whatever/sys
> # chroot /mnt/whatever sh

> Now you are inside the operating system of the
> card. Configure the bootloader to your leissure
> . You may also want to give other boot loaders
> a try, such as Lilo or Syslinux, which imo are
> way more sane for small simple setups.

That is a great idea, thanks!  BTW, I remember that I had a cable for it,
serial-to-USB, I think, that allowed me to plug it in as a USB device and
boot it that way.  It did boot, but the logon program is issuing a seg
fault when I try to log on!  I am guessing the networking is also hosed,
which is why I could not connect via SSH or get it to respond to a ping
request.

I am guessing that chrooting it is not going to fix that issue with the
logon program.  I think I really hosed something up.  I think I rebooted it
at the wrong time during the upgrade.  It had installed the new kernel but
I was doing a "limited space" upgrade where you do an "apt-get upgrade" and
then "dist-upgrade."  Since the kernel had updated, I thought I should
reboot but I had only done the first of the two steps.  No telling what
state I left it in.  :(

Either that, or there is a problem with the board now.  Seg faults can be
caused by a hardware issue, but I am hoping it is either my "bad state"
theory or an issue with the SD card.

---