Rich
asked on
Booting from software mirror non-responsive
I have a windows 2000 SBS with a pair of non-raid scsi hard drives set up as dynamic disks and windows mirroring. running. When I boot the server, I get the option to boot from the main or the mirrored drive (as defined in boot.ini). However, when I select the boot from the mirrored drive, I do not get the windows startup, just a blinking cursor. The drives are identical and the mirror appears to be working properly. I have tried going into the scsi setup utility and set the boot to ID 1 (from ID 0), but it would not boot this way, either.
I recently had a failed primary drive in this configuration with the same problem, and although the data was OK on the mirrored drive, I could not boot from it, either. After reinstalling the OS and copying the data to the new drive and setting the mirror again, I will be back in the same situation as before. What am I missing?
I recently had a failed primary drive in this configuration with the same problem, and although the data was OK on the mirrored drive, I could not boot from it, either. After reinstalling the OS and copying the data to the new drive and setting the mirror again, I will be back in the same situation as before. What am I missing?
Could you please list your boot.ini here?
Check this Microsoft article. It shows you the trick to boot your mirror disk:
http://support.microsoft.com/kb/925581
K
http://support.microsoft.com/kb/925581
K
ASKER
Here is the boot.ini file:
[boot loader]
timeout=30
default=multi(0)disk(0)rdi sk(0)parti tion(2)\WI NNT
[operating systems]
multi(0)disk(0)rdisk(0)par tition(2)\ WINNT="Win dows 2000 Server - disk0" /fastdetect
multi(0)disk(1)rdisk(0)par tition(2)\ WINNT="Win dows 2000 Server - disk1 - Mirror" /fastdetect
In looking at it myself, I am not sure why it says partition(2). The Graphical layout in the Disk Managment snapin shows it listed first, with a small (55MB EISA Configuration) volume (no label) listed second on Disk0 and a same size (55 MB Unallocated) partition listed second on Disk1. That is the only difference between the two disks that I can tell.
[boot loader]
timeout=30
default=multi(0)disk(0)rdi
[operating systems]
multi(0)disk(0)rdisk(0)par
multi(0)disk(1)rdisk(0)par
In looking at it myself, I am not sure why it says partition(2). The Graphical layout in the Disk Managment snapin shows it listed first, with a small (55MB EISA Configuration) volume (no label) listed second on Disk0 and a same size (55 MB Unallocated) partition listed second on Disk1. That is the only difference between the two disks that I can tell.
Are they both connect to the same controller on one cable?
If not, try to change the value of rdisk on the second line to 1 instead of 0.
In looking at it myself, I am not sure why it says partition(2)....
Your first partition could be the EISA and of course C: is number 2
K
If not, try to change the value of rdisk on the second line to 1 instead of 0.
In looking at it myself, I am not sure why it says partition(2)....
Your first partition could be the EISA and of course C: is number 2
K
Check this link if you want to know more about boot.ini structure
http://www.computerhope.com/issues/ch000492.htm
K
http://www.computerhope.com/issues/ch000492.htm
K
ASKER
The disks are SCSI disks on the same cable, so rdisk(x) should always be 0 (according to the info at the link you sent). They are at SCSI ID 0 and 1, which is correctly set in disk(x) parameter.
recently had a failed primary drive in this configuration with the same problem...
You need to read the below Technet to be sure your mirror is in place. If you did not set it to mirror correctly, break the mirror and reset it.
http://technet2.microsoft.com/windowsserver/en/library/72c7fdee-97d5-4476-bc5e-a859d8b49a931033.mspx?mfr=true
K
You need to read the below Technet to be sure your mirror is in place. If you did not set it to mirror correctly, break the mirror and reset it.
http://technet2.microsoft.com/windowsserver/en/library/72c7fdee-97d5-4476-bc5e-a859d8b49a931033.mspx?mfr=true
K
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Makes sense. That is what happened the first time. So is there no way to manually copy/create a MBR on the second mirrored drive? I guess I would have to wonder what the point of the mirroring is.
Any suggestions for an inexpensive hardware solution? I already have a SCSI 160 controller, which does not appear to have RAID capability.
Any suggestions for an inexpensive hardware solution? I already have a SCSI 160 controller, which does not appear to have RAID capability.
go for a adaptec card if its just raid 0,1 and 5 1 channel can pick em up for just over £100
you can build a MBR to the second disk but it is a mission and all has to be done at low level
my advice is get a adaptec or similar card and hardware raid it mate much better.
you can build a MBR to the second disk but it is a mission and all has to be done at low level
my advice is get a adaptec or similar card and hardware raid it mate much better.
ASKER
Thanks for all comments. It is amazing to me that the Windows Mirror does not create an MBR, since auto/manual failover to reboot onto mirrored drive seems to me to be critical. I will be looing into Adaptec card.
yep is not good i have been there mate its ok if the primary is not completly dead and you can boot to the mirror but other then that not good
I never did like the software mirroring .....
I hope this helps !