<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#CCCCCC">
<br>
<br>
<div class="moz-cite-prefix">On 6/29/19 8:11 PM, John Strazzarino
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:C1C5E7A1-0399-4859-8B62-1D03015E9FF2@yahoo.com">
<pre class="moz-quote-pre" wrap="">Getting back to my NUC computer
It now says file ‘/grub2/i386-pc/normal.mod’ not found
Ls command gives (hd0) (hd0,msdos11) and so forth thru (hd0,msdos5), then msdos2 and msdos1
Tried a bunch of insmod and cat commands but they don’t seem to work
Thoughts?
Sent from my iPad</pre>
</blockquote>
<br>
Have you tried plugging in your external DVD/CD drive and
booting<br>
up a copy of SuperGrub2 which is a live disk that finds all the
bootable<br>
and sometimes not bootable files on the disk?<br>
If you could get the PCLOS booted up then you could probably<br>
fix the problem by re-installing GRUB2.<br>
<br>
Also Rescatux another live boot CD which can fix lots of
problems<br>
might be able to fix this problem.<br>
<br>
As Rick mentions in his remarks Dual-boot situations can be
problematic<br>
but I have gotten them to work in the past.<br>
<br>
You might want to take a look at the MUC's firmware/BIOS
settings.<br>
<br>
Bobbie Sellers<br>
<blockquote type="cite"
cite="mid:C1C5E7A1-0399-4859-8B62-1D03015E9FF2@yahoo.com">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On Jun 26, 2019, at 9:49 PM, Rick Moen <a class="moz-txt-link-rfc2396E" href="mailto:rick@linuxmafia.com"><rick@linuxmafia.com></a> wrote:
Quoting John Strazzarino (<a class="moz-txt-link-abbreviated" href="mailto:jstrazza@yahoo.com">jstrazza@yahoo.com</a>):
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">At the last meeting, Bobbie tried to fix my dual boot (win/10,
PCLOS64), but rendered it unbootable. When booting, it brings you to
grub rescue. Uncertain how to proceed..
When booting from a USB stick with pclos64
A df command gives this.....
/dev/root.old 30M mounted on /initrd
/dev/shm 3.9G mounted on /
None 3.9Gmounted on /dev
/dev/sdb1 1.9G mounted on /initrd/cdrom
/dev/loop0 1.8G mounted on /initrd/loopfs
None 3.8G mounted on /union
None 3.9G mounted on /dev/shm
None 3.9G mounted on /union/bar/run/user/500
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Hi, John. Sorry to hear about the problem.
I notice that PC-Linux OS has defaulted to GRUB2 (as opposed to the very
different GRUB 1.x that is often called 'GRUB Legacy') in releases since
2016, so I infer that you can rely on GRUB2-oriented recovery guides
such at this one:
<a class="moz-txt-link-freetext" href="https://www.howtoforge.com/tutorial/repair-linux-boot-with-grub-rescue/">https://www.howtoforge.com/tutorial/repair-linux-boot-with-grub-rescue/</a>
Not intended as any kind of complaint, but information missing from your
account that makes it more-difficult to assist include:
1. How your PC-Linux OS filesystems are laid out. The 'df' output
correctly reports filesystems mounted by the live-booted USB stick, but
those don't appear to include any from your NUC's regular main storage.
Not that this omission is very troublesome, actually. Probably you have
a small EFI FAT (system) partition, a large NTFS partition for
MS-Windows 10, aanother large ext4 partition for the Linux root
filesystem, and maybe a swap partition, and maybe a Windows 'recovery
partition.
2. Through what chain of actions (what softare, how configured) your
NUC booted before its booting got broken. That would be really handy to
know, right now.
Anyway, the above-cited guide is one of many similar ones that may help.
Unsolicited opinion: Over many years, I can't help noticing that
there's high incidence of broken boot configurations among users who
elect to dual-boot. An argument can thus be made for avoiding
dual-boot, having a very simple boot setup that you understand, and
leaving it alone.
Where you have a serious need for multiple OSes on a host, using VM
technology (e.g., VirtualBox) is often much more satisfactory than is
dual-booting (given adequate RAM).
_______________________________________________
sf-lug mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sf-lug@linuxmafia.com">sf-lug@linuxmafia.com</a>
<a class="moz-txt-link-freetext" href="http://linuxmafia.com/mailman/listinfo/sf-lug">http://linuxmafia.com/mailman/listinfo/sf-lug</a>
SF-LUG is at <a class="moz-txt-link-freetext" href="http://www.sf-lug.org/">http://www.sf-lug.org/</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
sf-lug mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sf-lug@linuxmafia.com">sf-lug@linuxmafia.com</a>
<a class="moz-txt-link-freetext" href="http://linuxmafia.com/mailman/listinfo/sf-lug">http://linuxmafia.com/mailman/listinfo/sf-lug</a>
SF-LUG is at <a class="moz-txt-link-freetext" href="http://www.sf-lug.org/">http://www.sf-lug.org/</a> </pre>
</blockquote>
<br>
</body>
</html>