boot problem

boot problem

Post by Kali » Fri, 14 Nov 2003 17:28:13


i am working on win 2000 server and upon booting this
morning i got the blue screen with the message " stop
for numbers in hex and incaccessible_Boot_Device, and it
wouldn't even boot at safe mode.
please help me. thank you in advance
 
 
 

boot problem

Post by kali » Fri, 14 Nov 2003 18:08:57

Maybe iwasn't that clear on my first message:
i get this message whenver the machine boot and it stalls
can anyone help me i would very grateful:
stop
0x0000007B(0x8188c970,0x0000102,0x00000000,0x00000000)
inaccessible_Boot_Device
please what can i do ? it won't even start at safe mode.
thank you in advance
.

 
 
 

boot problem

Post by Aurelien [ » Sat, 15 Nov 2003 00:21:13

"kali" < XXXX@XXXXX.COM > a rit dans le message de

________

Hi Kali,

Typically, this error appears when a boot driver fails to initialize the
boot device (hard disk in general).
Installing a new SCSI adapter or disk controller might induce this error.
- If you have installed a new device or a new adapter, try to remove it.
- In the recovery console, you can also launch a chkdsk /r to check and
repair the disk integrity.

A lot of known issue with stop 0x7b are listed in the microsoft knowledg
base. Please have a look in it and check if it meets your problem.
http://www.yqcomputer.com/ ;EN-US;KBHOWTO&sd=GN&ln=EN-US

Use the key word "0x0000007B"

Aurelien Goillot
Microsoft France
 
 
 

boot problem

Post by anonymou » Sat, 15 Nov 2003 03:06:40

Kali,
I have an old DOS 6.2 (I think) boot floppy, which somehow
destroys the hard drive master boot record resulting in
same behavior as you describe. The only sure fire solution
is to start from scratch and reformat the offending boot
hard drive. You have to do fdisk with option to restore
the Master Boot Record . I think, not sure, it is
FDISK /MBR or FDISK space MBR.
Do FDISK ? to get help and to display the options.

Aurelien
would you please refrain from giving your solution to
anybody! It is the standard MS solution (run chkdsk),
which WILL not work on DEAD system! You need working
system to run DOS chkdsk. I wish someone in Redmond would
take this nonsense out of the Windows and publicly admit
that when things go south this bleeding edge technology
has to fall back on DOS to recover in too many cases!

Cheers Vaclav

The susgest
le message de

stalls
initialize the
induce this error.
try to remove it.
chkdsk /r to check and
microsoft knowledg
problem.
US;KBHOWTO&sd=GN&ln=EN-US
 
 
 

boot problem

Post by Aurelien [ » Sat, 15 Nov 2003 18:53:35

< XXXX@XXXXX.COM > a rit dans le message de

Kali,
I have an old DOS 6.2 (I think) boot floppy, which somehow
destroys the hard drive master boot record resulting in
same behavior as you describe. The only sure fire solution
is to start from scratch and reformat the offending boot
hard drive. You have to do fdisk with option to restore
the Master Boot Record . I think, not sure, it is
FDISK /MBR or FDISK space MBR.
Do FDISK ? to get help and to display the options.

Aurelien
would you please refrain from giving your solution to
anybody! It is the standard MS solution (run chkdsk),
which WILL not work on DEAD system! You need working
system to run DOS chkdsk. I wish someone in Redmond would
take this nonsense out of the Windows and publicly admit
that when things go south this bleeding edge technology
has to fall back on DOS to recover in too many cases!

Cheers Vaclav

The susgest
__________

Hi,

As I said before the stop 0x7b appears because of a a boot device
initialisation faillure.
That could be due to:
- corrupted scsi adapter or disk controler
- disk corruption
- system corruption

I am sure that to format the system and fix the master boot record will work
but this is not always the smartest solution, expecially on servers.

So before formating the system I propose to you the following tests:
- If you have installed a new device or a new adapter, try to remove it.
=> test if the computer boots correctly
- In the recovery console, you can also launch a chkdsk /r to check and
repair the disk integrity.
=> test if the computer boots correctly
- In recovery console launch a system reparation

=> test if the computer boots correctly

The better solution will be to analyse the memory.dmp generated to directly
point on the problem, but that could not be done on newsgroup.

Hope that it will help
Aurelien
 
 
 

boot problem

Post by clair » Mon, 20 Sep 2004 21:02:45

hi,

on start, I get a :
1962: aucun SE detect. appuyez sur F1 pour refaire
l'amorge
(no OS detected, F1 to reboot)
after several attempt ctrl+alt+supp, I manage to load
windows but after a while the C hard drive disappear on my
system?!
thx for your help
 
 
 

boot problem

Post by MV » Mon, 20 Sep 2004 22:06:20


hi,

on start, I get a :
1962: aucun SE detect. appuyez sur F1 pour refaire
l'amorge
(no OS detected, F1 to reboot)
after several attempt ctrl+alt+supp, I manage to load
windows but after a while the C hard drive disappear on my
system?!
thx for your help
==========
Your first step should be to download & run the
diagnostic program that the manufacturer of your
hard disk makes freely available on his home site.

Your should also find out if your problem is temperature
related: Is it easier to start the machine when it's warm?
 
 
 

boot problem

Post by Ben-Zion J » Tue, 21 Sep 2004 16:56:19

Look at IBM Support page at this URL [Unwrap long line!]:

http://www.yqcomputer.com/
lndocid=MIGR-45383&selectarea=SUPPORT&tempselected=5

A hard disk drive boot error (error codes 1962 and
I999030X) can have the following causes.

Error FRU/Action

The startup drive is not in the boot sequence in
configuration. Check the configuration and ensure the
startup drive in the boot sequence.

No operating system installed on the boot drive. Install
an operating system on the boot drive

The boot sector on the startup drive corrupted. The drive
must be formatted.
Attempt to access and recover (back-up) the failing hard
disk drive
Format the hard disk drive using the operating systems
programs

The drive is defective. Replace the hard disk drive.







message