missing operating system error

L

LPW

I recently upgraded from a 60GB Western Digital hard drive to a 120GB WD
hard drive. On my 60GB drive, I had two partitions--each one running a
version of Windows XP. Using PartitionMagic 8.0, I was able to switch from
one partition to the other by making one active and bootable and the other
hidden.

After upgrading to the 120GB hard drive, I can no longer boot into the
second partition. When I try, I get the error message: "Missing Operating
System." I can still boot into the first partition.

My PC is running WinXP with all the latest updates. The PC is a Dell
desktop, about three years old, with the latest BIOS.

I know there are certain limitations for a boot partition. But I'm confused
why my dual boot system worked with the 60GB drive but not with the 120GB
drive. Can someone explain why I can no longer boot into the OS on the
second partition, and if there's a workaround or solution to this problem?

Thanks for your help.
 
R

Rod Speed

LPW said:
I recently upgraded from a 60GB Western Digital hard drive to a 120GB WD hard
drive. On my 60GB drive, I had two partitions--
each one running a version of Windows XP. Using PartitionMagic 8.0, I was able
to switch from one partition to the other by making one active and bootable
and the other hidden.
After upgrading to the 120GB hard drive, I can no longer boot into the second
partition. When I try, I get the error message: "Missing Operating System." I
can still boot into the first partition.

You stuffed up the cloning of the 60G drive to the 120G drive.

What did you use to do that ?

Does the 120G drive show up as 120G on the black bios screen at boot time ?
My PC is running WinXP with all the latest updates. The PC is a Dell desktop,
about three years old, with the latest BIOS.
I know there are certain limitations for a boot partition. But I'm confused
why my dual boot system worked with the 60GB drive but not with the 120GB
drive. Can someone explain why I can no longer boot into the OS on the second
partition,

You stuffed up the cloning of the 60G drive to the 120G drive.
and if there's a workaround or solution to this problem?

Yes, clone the 60G drive to the 120G drive properly.
 
D

dscotts

LPW said:
I know there are certain limitations for a boot partition. But I'm confused
why my dual boot system worked with the 60GB drive but not with the 120GB
drive. Can someone explain why I can no longer boot into the OS on the
second partition, and if there's a workaround or solution to this problem?
more details, like Rod asked you, what program did you use to transfer
the OS. that can be a tricky proposition on its own, let alone duel
OS's. just went through upgrade hell the other weekend and if it wasn't
for Ghost I would have had to punt. even the guy at Maxtor told me the
following Monday his utilities have limitations and probably the best
and most reliable way to transfer a OS over is an image cloning program.
some of the HD utilities, this one did, will add a DDO (disk overlay
program) by default for allowing the BIOS to identify the bigger HD's,
which he admitted could happen whether your system needs it or not. some
programs and OEM systems don't like DDO's, Partition manager could very
well be one of these. plus, have you looked in WinXP's disk management
to see what type of partitions the software created. the MaxiBlast for
instance, was creating 1 primary and then an extended partition with
logical drives when for my needs I needed a second primary drive for the
recovery program. I would assume you should have a primary partition for
each operating system.
 
L

LPW

Here's the process I used: I kept the 60GB drive as the master and installed
the new 120GB as the slave. I then used PartitionMagic to copy the primary
and secondary partitions from the 60GB to the 120GB. I've done the same
thing before with smaller drives and never had a problem.

When I couldn't boot up into the second partition, I also tried creating a
Ghost image of the second partition from the 60GB and restoring that to the
120GB drive as the second partition. But that didn't work either.

According to PartitionMagic and WinXP, both partitions are primary, just
like on the original drive.

Other than using PM and Ghost, are there other products or different methods
I could try?

Thanks for your help.
 
E

Eric Gisin

The "missing operating system" message means the MBR read the partition boot sector,
but it does not have the "55 AA" boot signature.

You could try using boot.ini on the working part to boot both partitions:
you need two multi entries with partition(1) and (2).
 
R

Rod Speed

LPW said:
Here's the process I used: I kept the 60GB drive as the master and
installed the new 120GB as the slave. I then used PartitionMagic to
copy the primary and secondary partitions from the 60GB to the 120GB.
I've done the same thing before with smaller drives and never had a problem.

You've ended up with a bad copy of the
second partition, no viable boot record in it.
When I couldn't boot up into the second partition, I also tried
creating a Ghost image of the second partition from the 60GB and restoring
that to the 120GB drive as the second partition. But that didn't work either.
According to PartitionMagic and WinXP, both partitions are primary,
just like on the original drive.
Other than using PM and Ghost, are there other products or different methods I
could try?

It is possible to do it with ghost. The main trick is to clone the
entire drive, AND DO IT FROM THE GHOST CD OR FLOPPY
SO YOU CAN PHYSICALLY DISCONNECT THE ORIGINAL DRIVE
FOR THE FIRST BOOT AFTER THE CLONE HAS BEEN MADE.
XP will claim to have found new hardware, ask to be allowed to
do a reboot, allow that and it should be fine. You can connect
the original drive again after that if you want.

You can also use True Image to clone the physical drive.
 
D

dscotts

LPW said:
Here's the process I used: I kept the 60GB drive as the master and installed
the new 120GB as the slave. I then used PartitionMagic to copy the primary
and secondary partitions from the 60GB to the 120GB. I've done the same
thing before with smaller drives and never had a problem.

When I couldn't boot up into the second partition, I also tried creating a
Ghost image of the second partition from the 60GB and restoring that to the
120GB drive as the second partition. But that didn't work either.

According to PartitionMagic and WinXP, both partitions are primary, just
like on the original drive.

Other than using PM and Ghost, are there other products or different methods
I could try?
I fooled around all weekend and as I said, in the end it was Ghost's
disk to disk copy feature that made it happen. after many bad attempts I
came to assume that the best way to get an OS copied was to let Ghost do
all the figuring as it seems the thing it can do the most reliable is
just make an exact clone of a drive, no changes. so that's what I ended
up doing after fumbling with using Maxibast to do the whole thing,
creating partitions in disk management, using Maxiblast copy utility,
formating them, not formating them, using Ghost copying disk to disk
with a created partition, restoring from a backup image to a created
partition, all were unstable in some fashion and would only lead to
headaches if I accepted the results. so, like I said, after staring at
those options and reading and finally after hours into the night I guess
some of the definitions started sinking in, I decided I'd just let Ghost
9 do it all.

by that I mean, give it a blank HD as the slave (use XP disk management
to erase the partitions you have created already if necessary), do a
disk to disk copy of drive C: with the following switches enabled.

Check source for file system errors
Check destination for file system errors
Set drive active
Destination partition type - Click Primary partition
Set new Drive letter
Copy MBR (master boot record)

with that, it makes a clone in every way, a copied 30 GB primary
partitions drive C:, and I guess most importantly, volume size. I am
assuming that forcing the copy into a different sized partition may
cause volume (disk geometry) problems so that is why it is best to let
it do everything itself, backup image copy as well, I assume that was
the problem I had with image restore.

for some, this would be a little of a bummer, if, as you are hoping to
do and double both your operating partitions, but in your case, you have
partition magic so after you get it running right you can just use PM to
change their sizes so you should be covered. there is a switch to have
it use up all the unallocated space remaining which probably is fine for
copying an OS to a new bigger drive as this program then can make that
change within its setup and probably not an issue but then you would end
up with 1 partition 30 GB and the other 90. this switch might also be
the key to setting up a partition and then copy to that partition and
use this switch which then may make the new volume calculations to make
it right, or it just might use the rest of the unallocated space on the
whole drive and maybe default back to the original problem of a created
partition, experiments for a later date???

then, before I'd shut it down, I would do the same thing with the your
second partition, copy it over. I'm also assuming that the best thing to
do is have the new drive start out with all the assigned partitions
present like the last one so everything is as it looked when last the OS
shut down. except, with the duel boot thing this is where it might get
tricky again. I don't know if you need to add a 'MBR' to this second
drive or designate it an 'active' drive as well, 2 switches, changes,
necessary for copying an OS so you may have to experiment here but I
would think that the duel boot is running off of the primary OS and it
makes all the changes internal to have the second partition act as an OS
rather than using Windows settings. but again, I don't know, someone
else may know better.

then, after you have copied the 2 partitions, unplug, move the new drive
to master, take out the old, start it up in order for Windows to change
the mapping of the new drives and that should hopefully work. then, if
your lucky, use PM to increase the partitions as you want. one last
thing, without assuming the obvious, I would defrag and error-check both
those drives (partitions) first, if they are a housekeeping mess this
makes it much harder on the process and can sometimes be part of, or the
problem.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top