Boot Block Problem

[mike3411 0]

The other day when I rebooted my computer after up[censored] some drivers, it

refused to boot. It goes through the BIOS and POST fine, seems to detect my

SCSI HD properly, then I get:

Searching for boot record from SCSI .... OK

And nothing else happens. I booted from the Win2k CD, tried to use the

automatic recovery process, it couldn't find the installation, I had the

emergency disk for the second of my two Win2k installs, using that it ran

the repair utilities, said it had completed, reboots the computer, and stops

at exactly the same spot. What can I do, short of reinstalling? How can I

fix this?

Thanks!

-Mike C.

[tweaked 0]

i have the exact same problem, what mobo are you using, i just got the cusl2 a week ago...

[mike3411 0]

SuperMicro PIISCD - i820 w/ MTH

-Mike

[marlyman 0]

what drivers did u update???

what scsi card do u use???

[Damien 0]

Have you checked the cables on the scsi drives? Sometimes they can work themselves loose just enough to allow detection but not booting. ALso are you're drives properally terminated i.e. the last drive on the chain with the terminator jumper activated?

 

If win 2K cannot find the installation - it probably means that the system cannot find the drive. Have you undated either the SCSI bios or the MB's bios recently? Sometimes an updated bios can have detrimental effects of scsi cards - I had an experience recently with my Abit KA7 with the new bios my Adaptec 29160 wouldn't boot.

 

------------------

[AgeKnight 0]

I have a similar problem, I couldn't reboot after installing SP1. It helps if I let the CD on the drive. But it's anoying!. I wonder if reformating again would help it.

 

BTW, I use a CUSL2 too. Wouldn't this be a Mobo issue?.

[mike3411 0]

I just reinstalled Win2k to a second directory, backed up my important stuff, and then reformatted+reinstalled. It was in no way a hardware issue, but rather crappy boot management by Win2k and the recovery process's failure to correct that.

-Mike

[Damien 0]

Cheers Mike, we may need this info in the future - I can't believe that for such an advanced operating system Windows 2000 was unable to correct you're problem.