ruben04
asked on
Breaking software mirror disaster
Hello all.
I have problem with MS Server 2003 standard. Server have 3 scsi disks. 2 of them were in a software mirror. They have system on them. 3rd one have data and its not in a raid.
After breaking mirror (throu disk management) the system was unable to boot. When booting up the server, there are 2 options available:
1.Windows (default)
2.boot mirror - secondary plex (something like this)
When trying to boot with first option, server just hang and there is nothing to see exacp the black screen.
When booting with 2nd option, blue screen appears. bsod with no special information (ilke irq_less_or_not_equal....)
I tryed restoring it with recovery console. try to run fixmbr, fixboot and nothing worked. finally i tryed to rebuild boot.ini with bootcfg /rebuild. the process was unsecessfull. tool was unable to write the boot.ini
Next thing i tryed was asr. At the end of the restores, everything appears successful, but an error is automatically displayed in notepad which says -
The recovery application "c:\windows\system32\asr_p fu.exe\res tore\sifpa th=c:\wind ows\repair \asr.sif" returned an error code 0x2. Since this indicated an unrecoverable error:asr cannot continue on this machine.
After this unsecessfull attempt, there is a new bsod saying irq_less_or_not_equal
i am out of ideas. Is there a hero who can help me. Thx
I have problem with MS Server 2003 standard. Server have 3 scsi disks. 2 of them were in a software mirror. They have system on them. 3rd one have data and its not in a raid.
After breaking mirror (throu disk management) the system was unable to boot. When booting up the server, there are 2 options available:
1.Windows (default)
2.boot mirror - secondary plex (something like this)
When trying to boot with first option, server just hang and there is nothing to see exacp the black screen.
When booting with 2nd option, blue screen appears. bsod with no special information (ilke irq_less_or_not_equal....)
I tryed restoring it with recovery console. try to run fixmbr, fixboot and nothing worked. finally i tryed to rebuild boot.ini with bootcfg /rebuild. the process was unsecessfull. tool was unable to write the boot.ini
Next thing i tryed was asr. At the end of the restores, everything appears successful, but an error is automatically displayed in notepad which says -
The recovery application "c:\windows\system32\asr_p
After this unsecessfull attempt, there is a new bsod saying irq_less_or_not_equal
i am out of ideas. Is there a hero who can help me. Thx
I suppose you have yet seen http://support.microsoft.com/kb/936923/en-us
... but just in case
Rodeca
... but just in case
Rodeca
ASKER
Sry guys for late replay.
I sucessfully restored with asr. The problem was in media. Server was upgraded with service pack and i was trying to restore it from media without of service pack. That was the couse of error code 0x2.
I didn't tryed again to break sw mirror on system partition. it will have to wait.
thx for replays
I sucessfully restored with asr. The problem was in media. Server was upgraded with service pack and i was trying to restore it from media without of service pack. That was the couse of error code 0x2.
I didn't tryed again to break sw mirror on system partition. it will have to wait.
thx for replays
angelIII:
No objection to full refund.
But, the answer may be useful to somebody:
"error 0x2" is explained at "http://support.microsoft.com/kb/936923/en-us" as a result of "trying to restore it from media without of service pack" (quotes mean quoteds :-)
Regards
Rodeca
No objection to full refund.
But, the answer may be useful to somebody:
"error 0x2" is explained at "http://support.microsoft.com/kb/936923/en-us" as a result of "trying to restore it from media without of service pack" (quotes mean quoteds :-)
Regards
Rodeca
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
irq_less_or_not_equal means usualy disk problem.
So you can try to remove the first disk from system or the second disk.
A good option is to put that disk on other server and inspect the boot.ini file.
Dan