<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It looks as if it was trying a network boot first.</blockquote><div>Not necessarily. If PXE is in the boot order as a later item in the list and the earlier items in the list don't contain bootable devices, then it'll get to and try PXE. So picture could simply be showing that the previous boot devices in the list didn't boot and so it's trying PXE last (and failing because no TFTP server configured, etc.).</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I think Chad has has seen an occasional Windows update problem.</blockquote><u>Occasional</u>? *snort*<div>But you're right-ish. DF + Windows Updates == occasional boot problems. But the symptoms are different. Lynne' problem is earlier in the boot process where the firmware is trying to hand over control to a boot sector stored on some boot device (BIOS or UEFI w/BIOS-compatibility enabled) or to an OS loader/OS kernel (EFI/UEFI-style). The firmware isn't finding a device with a valid boot sector or OS loader/kernel and so finally gives up with the "ERROR: No boot disk has been detected..." message. The problem appears to either be hardware failure, the UEFI boot manager has become corrupted or otherwise changed (if these are EFI/UEFI computers), or an important part of the storage device has become corrupted. In the Windows Update scenario, the firmware has found a boot device and has handed execution over to the executables on the storage device and is failing slightly later in the boot process.</div><div><br></div><div>In retrospect, I suppose it's <u>possible</u> that it could be the same problem: When installing Windows, by default, a Windows partition is created for typical booting, but a Recovery Partition is also created. The recovery partition is booted when the normal Windows partition won't boot. With the Windows Update problems I've experienced, the normal Windows partition fails over to the recovery partition. But if there is no recovery partition on her computers, then it could show the "no boot disk" error. That's probably not the case, though.</div><div><br></div><div>An aside: <a href="https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Booting">https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Booting</a> Gives a brief overview of the (U)EFI boot process. UEFI isn't BIOS so it might be a little hard to wrap your head around if you cut your teeth on BIOS. I still have to catch myself sometimes and reorient my thinking about the firmware.<br></div><div><div><br></div><div><br clear="all"><div><div dir="ltr" class="m_7585262478067680470gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>______________________________<br><b>Chad Neeper</b><br><font size="1">Senior Systems Engineer</font><br><br><b>Level 9 Networks</b><br><font size="1">740-548-8070 (voice)<br>866-214-6607 (fax)</font><br><br><font size="1"><i>Full IT/Computer consulting services -- Specialized in public libraries</i></font><br></div></div></div></div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 9, 2019 at 11:56 AM Bob Neeper via OPLINTECH <<a href="mailto:oplintech@lists.oplin.org" target="_blank">oplintech@lists.oplin.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>FWIW Chad didn't mention these.</p>
<p>Are 3,4 & 5 in an area not under observation, where a patron
could be doing something?<br>
Is USB and other device booting inhibited?<br>
It looks as if it was trying a network boot first.<br>
</p>
<p>Is the UEFI password protected?<br>
I think if the AHCI setting got changed to IDE, or vice versa
there may be OS problems.</p>
<p>Is DeepFreeeze installed? <br>
I think Chad has has seen an occasional Windows update problem.</p>
<pre class="gmail-m_7585262478067680470gmail-m_235243819046009272moz-signature" cols="80">R. W. (Bob) Neeper
(Retired Toledo Scale Engineer & Library Computer Guy)
<a class="gmail-m_7585262478067680470gmail-m_235243819046009272moz-txt-link-abbreviated" href="mailto:neeperro@gmail.com" target="_blank">neeperro@gmail.com</a>
Doing Genealogy at:
Community Library
Sunbury, Ohio
</pre>
<div class="gmail-m_7585262478067680470gmail-m_235243819046009272moz-cite-prefix">On 9/9/2019 10:26 AM, Lynne Welch via
OPLINTECH wrote:<br>
</div>
<blockquote type="cite">
<p>Hello colleagues,</p>
<p>We have 5 HP Pro 3500 Series MT desktop units used by the
public. All bought at the same time with the same specs from the
same people. In April or May 2018 we replaced the hard drives
with Kingston SSDs so they would be faster.</p>
<p>Early in August 2019 we came in one day and OPLIN 1 and 2 were
just fine, but 3, 4, and 5 showed "Cannot boot". I've attached a
screenshot.</p>
<p>New Kingston SSDs did not solve the problem, so we replaced
them with Intel SSDs in OPLIN 3 and 4 last Thursday. We
re-installed the original hard drive in OPLIN 5 since we could
only get 2 Intel SSDs.</p>
<p>Today OPLINs 3 and 4 show the same "cannot boot" error, while 1
and 2 (on the original Kingston SSDs), and 5 (on the original
harddrive it came with) are humming along just fine. Argh!</p>
<p>We are at our wit's end, especially with school starting back
up. Any suggestions?</p>
<p>Thanks,</p>
<p>Lynne</p>
<div>
<div class="gmail-m_7585262478067680470gmail-m_235243819046009272pre" style="margin:0px;padding:0px;font-family:monospace"><span class="gmail-m_7585262478067680470gmail-m_235243819046009272sig">-- <br>
Lynne Welch – Herrick Memorial Library of Wellington, Ohio
USA<br>
tel 440-647-2120 email <a href="mailto:welchly@herrickliboh.org" target="_blank">welchly@herrickliboh.org</a><br>
</span></div>
</div>
<br>
<fieldset class="gmail-m_7585262478067680470gmail-m_235243819046009272mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_7585262478067680470gmail-m_235243819046009272moz-quote-pre">_______________________________________________
OPLINTECH mailing list
<a class="gmail-m_7585262478067680470gmail-m_235243819046009272moz-txt-link-abbreviated" href="mailto:OPLINTECH@lists.oplin.org" target="_blank">OPLINTECH@lists.oplin.org</a>
<a class="gmail-m_7585262478067680470gmail-m_235243819046009272moz-txt-link-freetext" href="http://lists.oplin.org/mailman/listinfo/oplintech" target="_blank">http://lists.oplin.org/mailman/listinfo/oplintech</a>
*** Send notification mesages from your library's ILS directly to patrons' cellphones. For FREE: <a class="gmail-m_7585262478067680470gmail-m_235243819046009272moz-txt-link-freetext" href="https://www.oplin.ohio.gov/sms***" target="_blank">https://www.oplin.ohio.gov/sms***</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
OPLINTECH mailing list<br>
<a href="mailto:OPLINTECH@lists.oplin.org" target="_blank">OPLINTECH@lists.oplin.org</a><br>
<a href="http://lists.oplin.org/mailman/listinfo/oplintech" rel="noreferrer" target="_blank">http://lists.oplin.org/mailman/listinfo/oplintech</a><br>
<br>
*** Send notification mesages from your library's ILS directly to patrons' cellphones. For FREE: <a href="https://www.oplin.ohio.gov/sms***" rel="noreferrer" target="_blank">https://www.oplin.ohio.gov/sms***</a><br>
</blockquote></div>