[cisco-voip] OS 2000.4.1

[Fretz, EA Eric at IS]

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).
 
 
 
 

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Simon, Bill
Sent: Sunday, November 27, 2005 1:53 PM
To: 'Martin Lohnert'; 'cisco-voip at puck-nether.net'
Subject: RE: [cisco-voip] OS 2000.4.1


I don't see that any one responded to you on this.
 
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).  
 
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.
 
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.
 
Good luck,
Bill
 

---
Bill Simon - bills at tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/ <http://tns.its.psu.edu/> 



 


  _____  

From: Martin Lohnert [mailto:lohnert at gmail.com] 
Sent: Monday, November 21, 2005 9:52 AM
To: cisco-voip at puck-nether.net
Subject: [cisco-voip] OS 2000.4.1


Hi,
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... 
Martin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20051128/94e118ef/attachment-0001.html