Re: New build - Active partition query



In message <#BOrxgvSIHA.5128@xxxxxxxxxxxxxxxxxxxx>, Anna <myname@xxxxxxxxx> writes

"rbelNews" <rbel1@xxxxxxxxxxxxxx> wrote in message
news:M7ZSEyA223dHFw8L@xxxxxxxxxxxxxxxxx
New PC build, new SATA drive with Win XP Home SP2.

Just added an IDE drive from an older PC and Disk Management is showing as
disk 0 and the first partition of this as a logical drive and *active*
(there is no system or data on it).

The SATA drive with the system loaded is now shown as disk 1 (was disk 0)
and the C partition as healthy (system).

This system is booting OK, although pausing for confirmation of the IDE
disk for some reason, but I would have thought the C partition on the SATA
drive should be the active one but I cannot find a way of 'inactivating'
the current active partition.

Grateful for any advice.

--
rbel


rbel:
Since you don't indicate otherwise, I'm assuming you're not experiencing any
significant problem here other than some slight pause during bootup re the
system recognizing the PATA (IDE) HDD.

It's perfectly normal in your configuration that the system (Disk
Management) would be reflecting your boot drive, the SATA HDD as
"Healthy(System)" and your secondary HDD as "Healthy(Active)".

It's possible the Disk 0 - 1 reversals are due to the boot priority order in
your motherboard's BIOS. Possibly that setting indicates the PATA HDD
occupies a higher order of priority than the SATA (or SCSI) HDD. The system
will still (usually) default to the bootable SATA HDD under those
circumstances when it finds the PATA HDD to be an unbootable device - I'm
assuming, of course, that your PATA HDD is not bootable. Actually, I'm not
really sure whether that accounts for the Disk 0 -1 reversals in your
situation, but you might want to check out your boot priority (and any
related) BIOS settings.

Anna

No problems effecting the use. Initially I just wondered why the disk numbers had changed and then noticed the Active notation for the first PATA drive partition. The first guidance I read on active state indicated that there should only be one active partition on a *computer* and that it should be on the boot disk - I can now see that this was just poor wording.

The BIOS settings are:
Boot sequence - no PATA drive listed
HDDs - PATA drive listed as 2nd drive.

I can only assume that it is the presence of the active setting on the PATA drive that has caused the disk numbering to change.

--
rbel
.



Relevant Pages

  • SUMMARY: Moving /usr From Under Root "/" To Its Own Partition
    ... One of the reasons for doing this is to end up with a smaller root ... Install the boot block and boot off the new drive. ... " In order for the root partition to be fscked and remounted ... D> temporarily on the existing disk. ...
    (SunManagers)
  • Re: laptop - new HD - no CD or floppy drive
    ... I put the laptop HD back in the PC and I could boot from it. ... If the primary partition has an incorrect boot sector. ... If the disk geometry is incorrect. ...
    (microsoft.public.windowsxp.hardware)
  • Re: laptop - new HD - no CD or floppy drive
    ... I put the laptop HD back in the PC and I could boot from it. ... If the primary partition has an incorrect boot sector. ... If the disk geometry is incorrect. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Copying Bootable Drive in XP
    ... I have Partition Magic 8.0 and I am not having luck ... through its disk cloning or disk imaging process. ... HDDs, so that the "destination" HDD would be the recipient of the clone ...
    (microsoft.public.windowsxp.general)
  • Re: Can I boot of an XP System disk, nested in a logical volume
    ... I'll boot of Partition Magic or some other kind of magic and fix it that-a-way. ... It's been a long time since I messed with partitions like this, but in the back of my head I have this fragment about boring registry hands-on editing, 'derived Disk ID's' and the 'Master Boot Sector' -- that's S as in 'Senile'. ... One reason for the drive letter change on cloned drives is to keep the parent drive hooked up the first time the clone is booted, being that the clone has the same Mount Manager database, and being that the Mount Manager *always* respects drive letter assignments, it will see the parent drive and its valid disk signature and assign the C: drive letter to the original C: drive, so there will be no C: letter available for the clone. ...
    (microsoft.public.windowsxp.basics)