Win 2000 Stop 0x07B when booting from mirror disk on proliant ML370

[Jurgen Goedbloed]

Hi all,

I have a compaq proliant ML370 G2 with 2 18 GB SCSI HDD's, running windows 2000. Windows system partition is mirrored on both disks (software mirror). Disk 0 died last week.

I broke the mirror, but now when I try to start the computer from disk 1 with a boot disk, windows boots, but ends with a blue screen (stop 0x07B inacessible boot device).

Does anyone have a clue what could be the cause and how to solve it?

Details of boot.ini:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Server" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINNT="Microsoft Windows 2000 Server mirror disk" /fastdetect

[SAKET_5]

Hi there,

Could you confirm on the following:
1.Do you have no hardware mirrors, i.e. two SCSI HDD not configured for RAID 1 mirror on the smart array controller?
2.Do you have any other similar server?If yes, you can try copying the boot.ini from one of these healthy servers and then use Recovery Console (Boot off Windows 2000 CD and then use Recovery Console as the repair option)to replace your existing boot.ini file.

Hope this progresses your case and don't forget to assign points:)

Regards,

[kris rombauts]

Hello Jurgen,

do you know how many partitions the first (failed) disk had originally ?

Maybe this disk contained one parition more (the utilities or eisa config partition) and if so then the partition number to boot from is 2 as opposed to 1 under 'normal' disks that do not have that special partition.

To fix this, change the reference to the partition number on the second disk that you are trying to boot from ,from (2) into (1) in the boot.ini (second entry) so this becomes :

multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microsoft Windows 2000 Server mirror disk" /fastdetect


If this does not fix the issue, can you confirm the first (bad) disk has been physically removed because a disk might be bad but if still left in the server and if it reacts to the SCSI inquiry it will still be seen as disk 0 even when it's media is bad and the second disk is then still disk 1 and not disk 0 and the boot.ini still points to the first disk really.

Either one or both of the above actions hopefully fix your issue.

HTH

Kris

[kcpant]

It seems you have implimented S/W RAID 1 on the disks. it happens sometimes if both the disks are not exactly same in specs. installing the disk 1 ( second HDD) in place of disk 0 ( replacing faulty disk with working one) might solve your problem.try it.furthe, there is no need to use a boot disk if your mirrored disk is working properly.

regards,

K C Pant

[Jurgen Goedbloed]

Hi all,

Thanks for your replies. I have a similar server, so I tried to boot that server from the same boot disk. That worked fine.

I am sure that this is a software mirror, there are no smart array controllers inside the system. Both disks have an EISA partition.

When I tried the emergency recovery console, I couldn't access the system partition from disk 1. Also, with the repair option from the Windows 2000 server install CD the same: couldn't access the partition.

I think something went wrong when I broke the mirror. I think the only thing to do now is to reinstall Windows, as there are no system partitions left on both disks...