Haines Brown <hai...@histomat.net> wrote: > I tried the chroot method, but with little luck. ... > # chroot /sysroot > > # grub-install /dev/sdb > bash grub-install: command not found > > # ls -la /usr/sbin | grep grub-install > -rwxr-xr-x 1 root root 102046 Oct 28 2018 grub-install > > # /usr/sbin/grub-install /dev/sdb > # bash: /usr/sbin/grub-install: No such file or directory > > At my wits end I remove and reinstall grub2-common. Did not help.
Sorry, it's outside my knowledge envelope. I know the steps do work as I've done them several times in the past. I don't know what the requirements are in terms of compatibility between the linux kernel that's booted and the "broken" system that you chroot to - are they the same architecture you are using ? Also, I take it you mounted all the directories (/proc, /dev, etc) ? In the back of my mind is whether the error message is a result of a lower level issue - eg a mismatch between kernel and system. _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng