General discussion

Locked

Active Partitions on Both Master/Slave D

By gmichaels ·
I have a situation where I have 2 hard drives both showing active partitions (Master/Slave). When I boot the system it tries to use the slave's active partition to boot and finds no mbr and fails to boot. In FDisk I can see both drives but only the slave (drive 2) gets a drive letter C: when it should be C: (drive 1) the master was partitioned as NTFS while the slave is FAT32. This setup worked just fine until I swaped motherboards to upgrage to a 2.2mhz system. After the upgrade I had this problem come up. FDISK will not let me set drive 2 to non-active. So I cannot seem to get out of this mess.

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Active Partitions on Both Master/Slave D

by gmichaels In reply to Active Partitions on Both ...

Just to add: the bios sees the drives just fine as master/slave. So all jumpers/cables etc are set up fine. If a use a win98 boot disk the slave shows up as C: and I cannot navigate at all to the master as it never got assigned a drive letter.

Collapse -

Active Partitions on Both Master/Slave D

by gmichaels In reply to Active Partitions on Both ...

Used Norton Ghost to deactivate slave partition. Still the master drive would not boot. Also tried gdisk with /mbr to reinitialize the mbr. Still no luck. Also tried just booting with the 1 master drive connected. Still no luck. I hit the gui windows 2000 startup screen then get a blue sceen of death saying my drive is not bootable and to check for viruses. Looks like I may have to wipe it and start over. Can't figure how this got this far since it was working just fine until I put in a new motherboard.

Collapse -

Active Partitions on Both Master/Slave D

by Gigelul In reply to Active Partitions on Both ...

About using Win98 boot diskette. Is mormal to see only the D drive as C drive. Win98 diskette FAT32 can't access/see NTFS partition. You tried to make Win98/Fat32-master drive and the other one HDD-slave? What is your second OS?

Collapse -

Active Partitions on Both Master/Slave D

by Gigelul In reply to Active Partitions on Both ...

Later I see that your second OS is Win2000. I think that the master HDD must be Win2000. Win2000 can access the both NTFS and FAT32.

Collapse -

Active Partitions on Both Master/Slave D

by Gigelul In reply to Active Partitions on Both ...

Try to remember how was installed your system. Which OS was first installed and on which HDD and post comments.
I will try to give you the correct solution.

Collapse -

Active Partitions on Both Master/Slave D

by gmichaels In reply to Active Partitions on Both ...

I think I have everybody confused. This was not a dual boot system. Win2000 OS was on C: and the drive was just a plain old slave. Not sure why the drive was set to active when it had no OS on it. So when the master was not recognized as bootable this left me with 2 unbootable drives.

Collapse -

Active Partitions on Both Master/Slave D

by Shanghai Sam In reply to Active Partitions on Both ...

This is the way I would do it, (and have done a few).
Firstly, have all disks ready, drivers available, etc. Win2K can seldom be reclaimed after a motherboard change, due to reliance on the Hardware Abstraction Layer, (HAL), during installation! Win9x is easier to do.
Change the drive order, put the slave as master and the master as slave, by moving the jumper on each drive, and setting the BIOS to Auto detect all drives. After the BIOS startup screen shows the drives properly, let Win 9x start. Copy the contents of the Win9x directory from the CD to somewhere on the HD, (normally Windows\Options\Cabs). Rename or move the folder Windows\INF\Other\ so that the wrong drivers are not found again. "Other" contains the INF files for devices not built-in to Win9x.
Restart in Safe Mode, open Device Manager, and one at a time, delete every device. Yes, each and every device, remove. Shut down to Power OFF, then restart the machine and Win9x will "find new hardware", lots of it, but IDEis third level, so CD drives are unavailable for awhile, and that's why we copy the CAB files to into Windows\Options\Cabs. Normally, I make a folder named Drivers\ under Windows\Options and copy the install files for each device into it's own folder, (ie: NIC\, MDM\, etc.).
Once Win9x is stable again and all the devices are working, start the Win2K setup from CD while running in Win9x. This will insure that the CD is working, and that Win2K will make it "Dual Boot". Use Win2K setup to removeand recreate the partition on the second drive, then do a fresh install of Win2K.
After this fix is made, Win9x sees C and the CD becomes D, Win2K will see Win9x on C, itself on D, and the CD becomes E, this is normal and expected.

Collapse -

Active Partitions on Both Master/Slave D

by gmichaels In reply to Active Partitions on Both ...

I think I have everybody confused. This was not a dual boot system. Win2000 OS was on C: and the drive was just a plain old slave. Not sure why the drive was set to active when it had no OS on it. So when the master was not recognized as bootable this left me with 2 unbootable drives.

Collapse -

Active Partitions on Both Master/Slave D

by gmichaels In reply to Active Partitions on Both ...

I think I have everybody confused. This was not a dual boot system. Win2000 OS was on C: and the drive was just a plain old slave. Not sure why the drive was set to active when it had no OS on it. So when the master was not recognized as bootable this left me with 2 unbootable drives.

Collapse -

Active Partitions on Both Master/Slave D

by TheChas In reply to Active Partitions on Both ...

I suspect the W2K crashed because the second drive was missing, and caused errors.

Without using special switches, fdisk only accesses the master drive in a multi-drive setup.

Mount just the slave, and use fdisk to disable the active partition.

Another MAJOR problem could be that you do not have a driver capable of accessing your drives from W2K.
You did remove all hardware from device manager before removing the old motherboard???

If you just swapped motherboards, then I think your best bet is to wipe the drive and re-install W2K.
You might want to boot from the W2K CD, and give recovery console a try before re-installing the OS.

Chas

Back to Hardware Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums