Thank you for your reply. Fortunately, I was able to fix the problem
with the help of another respondent to my plea.
Help from folks like you and your colleagues on the 'net has kept my
Computational Chemistry research going has since the early days of
Slackware
On 08/20/2023 10:30 AM, Michael Kjörling wrote:
On 20 Aug 2023 08:14 -0400, from s.mol...@sbcglobal.net:
error: no such device; 1d937ccf-2b57-4dcd-97d9-83522d7s04f1.
error: unknown filesystem.
grub fescue>
Quite often this type of error is caused by grub.cfg being either
corrupted or out of sync with the reality of your system's storage.
The first thing I would try is to use some kind of recovery boot
environment to boot and (important) chroot into the root file system,
make sure /boot is mounted for /boot/grub (something like mount -a
from the Debian installer rescue environment with the root file system
as root should do), make a backup copy of /boot/grub/grub.cfg
somewhere, and run both update-grub and grub-install <boot device> to
regenerate grub.cfg and rewrite the GRUB boot code on disk. Pay close
attention to any error messages or warnings in the process.
Once you're able to boot into the normal system, you'll want to
similarly re-run both update-grub and grub-install to make sure that
the results are sane and gives you a system that will boot normally.
I'm assuming that particularly "fescue" is a typo in the email; GRUB
should say "rescue". If it really does say "fescue", something is very
wrong with your GRUB installation.
And yes, if GRUB is OK then you should be able to boot the system
manually at the GRUB prompt, if your / and /boot file systems are
intact.
--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype: smolnar1
