Discussion Locked

MBR on IDE0, create MBR on SATA

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This topic seems to popup all over message boards and FAQs, yet I cannot see a clear solution to my problem. So I'll ask this again, as clearly as possible, and hope that I get some knowledgable respondents. Please, if you have not done this before, refrain from answering. It's one thing to 'know how' and another to have actually done this.

I had a Windowx XP installation on IDE0 (that's primary master). I installed two new SEAGATE 80 GB SATA HDs and placed them in a RAID 0 configuration (also called Disk Striping). I installed Windows XP on the SATA configuration and now it I am using full-time and no longer need the installation on IDE 0. I plan to take the HD on IDE 0 and used it elsewhere. Except, the MBR is on IDE 0.

So, now, what should I do. Feel free to suggest any tools you'd like to help me solve this issue, whether it be Windowx XP CD and Recovery mode's Fixmbr and Fixboot commands, or a commercial boot manager. I am using a DFI board, which happens to be the NFII Ultra Infinity with Nvidia Chipset. The SATA chip on the board is the Silicin Image 3114. Thanks for all of your help in advance.

12 replies

by vijaykumar

Please try the following;
Boot the PC with a DOS floppy or windows 98 floppy. Make sure you have the fdisk utility in it. You can always change to another floppy with the utility. It is even better if you have a bootable CD with all these utilities.
Run this command fdisk /mbr. This command writes a new MBR
Normally only Linux installations have this problem? I mean if you have to remove Linux and load Windows XP or any other operating system.
For safety, you may also disconnect your SATA drives while performing this operation.

If you boot off an Xp CD; use this link
"http://www.radix-europe.com/faq/14/"

Use this link for fdisk options;
http://support.microsoft.com/default.aspx?kbid=255867&product=w98

Thanx

by fifasg

Thanks for your advice, but you see, I'd like to write the MBR to the SATA drives, I'm not concerned about the other drive (IDE0) as I plan to disconnect it anyways.

by vijaykumar

Sorry about that. I was a little misled as you said you need to use the IDE0 for something different. Tell me if it is a s/w raid from Windows o/s is or h/w raid from BIOS or an interface immediately after post where you can access the h/w at a lower level but before the operating system starts.

by fifasg

Thanks for your reply.
It is actually a h/w RAID.
Silicon Image SATARaid, Sil 3114.
RAID 0, Disk Striping

Managing RAID sets is handled by the BIOS, during bootup. I can access it by pressing CTRL-S or F4.

Anything else, just ask. Thanks again.

by rodolfo

take out phisically ide0 - disconnet pwr cable -
set bios to start from cd
insert XP cd, boot, follow - after Eula - not at the first repair page - choose repair.
MBR will be rewritten on s-ata raid 1
good luck

by todd.crites

I have a similar set up. The trick is to move your XP boot files to the new RAID volume.

1.) You will need to determine if the system BIOS allows you to boot from a RAID volume. If so, set it to do so. The BIOS will look to IDE0 for boot sector before the RAID so the change should be transparent.
2.) Boot to XP as normal and proceeded to migrate the boot files. These files are located on the ?system disk? (IDE0). XP typically uses three files to initialize the boot process. They are ntldr, NTDETECT.COM.com and boot.ini.The BIOS locates and starts ntldr, the boot loader. Ntldr processes the boot.ini file, which points to where the XP kernel is located. In your case, RAID0. Ntldr then starts NTDETECT.COM, which reports info back to ntldr. Ntldr then passes the hardware info to Ntoskrnl.exe (Windows kernel), on your RAID and away you go.
3.) Copy ntldr, NTDETECT.COM and boot.ini to your RAID root directory. Note: The files are marked Hidden and System so you need to check show in view folder properties.
4.) Unplug your PATA drive and all should be good to go.

Microsoft?s knowledge base has extensive how to?s on this. Good luck.

by Former member

have you considered that the splitting the OS between two drives doubles the probability of OS failure, personally, I went with the OS on one drive and stripped the data drives

by bschmidt

Since the problem seems pretty much resolved (actually all you have to do is set BIOS up to boot from SATA drives, boot to XP CD and install Windows as if from scratch -- did that a lot in my last job) I don't feel bad about posting this. I'd have to agree, data striping doubles your chances of a system crash if there is no mirroring. You have 2 drives to possible fail instead of 1, and if 1 goes out there goes the system. Better to make a standalone system drive and stripe separate data drives.

by fifasg

although this is an off-topic comment, i thought to reply to your post.

my OS is just software that i can re-install whenever, however, my data is ir-replacable. the choice to strip the OS across two drives is a performance issue, you should see how much faster windows is. as for my data, i'd rather mirror that on a SATA RAID.

by aaron a baker

I'm going to assume that you are using Hard drives that have not been formatted.
The question is are you gong to format/partition them and how?
I always return to the actual Maker if at all possible as they would know the best configuration. In the case of Maxtor, I would use Maxtor "MaxBlaster" download off their website. Then I would partition the drive and then allow Maxtor to do the actual transfer of all the files on your C: Drive.
It does this automatically and the results have always been good for me.
This in my opinion is the easiest way to proceed. Yes we can do FDisk and a wide variety of other methods but when you consider that the Drive is a Maxtor, the program is Maxtor, the Division/Partition is Maxtor, it's pretty hard to go wrong.
Format and partition using Maxblaster and allow it to transfer all your files thus creating the badly needed C: on you Primary S.A.T.A

Good Luck
Regards
Aaron A Baker

by fifasg

I was able to successfully boot my system from the SATA RAID set without having PATA installation and so I wanted to present my results here so that others may benefit. Thank you to all of those who helped, I used your suggestions and combined those with some of my knowledge to conclude the following procedure. Thanks again.

Issue: MBR on PATA and I would like to have MBR boot record on SATA drive.

Scenario: I had a Windows XP installation on PATA and later created another Windows XP installation on a SATA RAID. I was ready to wipe-out my PATA installation as I no longer had any use for it, except, the MBR resided on it, and if I had wiped it, my SATA installation would no longer be accesible. When I created the SATA installation, the installer created a second entry in the boot loarder file (boot.ini) located on the PATA installation. This made the SATA installtion only accessible via the PATA device.

Solution: To circumvent the PATA device and create an MBR boot record on the SATA RAID installation, the following steps were taken.
1) Copy over from the root directory of the PATA installation, boot.ini, NTDETECT.COM, and ntldr, to the root of the SATA RAID installation.
2) Unplug the power for the PATA devices.
3) Boot the Windowx XP installation CD and attempt to use the repair mechanism; in specific, the commands FIXMBR and FIXBOOT.
4) For me, step three did not work, instead, i used the Emergency Boot CD available from ebcd.pcministry.com, created by Mikhail Kupchik.
5) When I booted the EBCD, I chose the option marked as SMART BOOT MANAGER, this was option #9.
6) The next screen that appeared allowed me to set the disk I wanted to boot from, and here, I chose the entry HD0 of type HP/NTFS. I saved my changes and restarted.
7) After rebooting, I was faced with the boot loader that had existed on the PATA installation (with 2 boot options). Now, all I had to do was remove the boot entry that pointed to the PATA installation and then I was done! The MBR now resided on the SATA RAID set.

This discussion is closed to new replies.