<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.2769" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=558390914-28112005><FONT face=Arial color=#0000ff size=2>The
Inaccessible Boot device message can be generated by a bad driver or by a bad
boot.ini file. I am not suggesting this was your problem, but I have run
into two occasions where installing an updated raid driver or an OS patch that
touched the VFAT or NTFS drivers actually changed the hard drive
enumeration. Once \Device\Harddisk1 was reenumerated to \Device\Harddisk2,
hilarities ensued. The only fix was to modify the boot.ini file to fix the
problem. Also, I have seen one instance where an updated RAID driver broke
a raid1 mirror on my OS volume. For some reason, the drive that was tagged
as the boot drive was considered out of sync by the raid card. Microsoft
PSS couldn't help me with that one, nor the RAID card vendor
(LSI).</FONT></SPAN></DIV>
<DIV><SPAN class=558390914-28112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=558390914-28112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=558390914-28112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=558390914-28112005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B>On Behalf Of </B>Simon, Bill<BR><B>Sent:</B> Sunday, November 27, 2005 1:53
PM<BR><B>To:</B> 'Martin Lohnert';
'cisco-voip@puck-nether.net'<BR><B>Subject:</B> RE: [cisco-voip] OS
2000.4.1<BR><BR></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2>I don't see that any one responded to you on
this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2>We encountered 0x7B Inaccessible Boot Device blue screen
errors not when updating the OS (as might be expected) but when installing a
CallManager service release! After working with (and without) TAC for
several days the only solution we had was to rebuild this machine from scratch
(our publisher - sigh). </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2>TAC was not helpful to us in this case and continually
pointed to the hardware as the culprit. However, nothing on the hardware
had changed and after many scandisk/checkdisk operations we found no problems
with the disks, either.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2>Rebuilding the system DID take care of the problem but we
were unsatisfied in that we never did figure out what the problem was and
should it surface again with an upgrade, we will be in the same
boat.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2>Good luck,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=975514819-27112005><FONT face=Arial
color=#0000ff size=2>Bill</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/plain format -->
<P><FONT size=2>---<BR>Bill Simon - bills@tns.its.psu.edu - (814)
865-2270<BR><A
href="http://tns.its.psu.edu/">http://tns.its.psu.edu/</A><BR><BR></FONT></P>
<DIV> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Martin Lohnert
[mailto:lohnert@gmail.com] <BR><B>Sent:</B> Monday, November 21, 2005 9:52
AM<BR><B>To:</B> cisco-voip@puck-nether.net<BR><B>Subject:</B> [cisco-voip]
OS 2000.4.1<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi,</DIV>
<DIV>I just came across installing OS 2000.4.1 for the first time and wonder
how is everyone else's experience with it? A pleasant surprise was there's
only 1 DVD per vendor now (HP/IBM) and the whole imaging process requires
less interaction. The installation finsihed with a mini-setup but after a
restart, I end-up with a blue-screen (INACCESSIBLE_BOOT_DEVICE)... Very
strange, as this is reproducible and happens everytime. On a 2nd server
(both MCS-7825-H1) the OS boots, runs HP utilities installation,
restarts, and ends-up in a different blue-screen
(KMODE_EXCEPTION_NOT_HANDLED) and unable to boot. I've never experienced
anything like this with the 2000.2.x installations, but they are
not supported on this platform... </DIV>
<DIV>Martin</DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>