On Thu, 15 Feb 2007 10:38:05 -0800, retired fire
I will try to give you a brief history of the Issue:
Thanks!
Brand new Vista Premium built computer. Asus M2NPV-VM (on board SATA
controller, 1 gig memory, 256 meg graphics, etc.....)
OK...
http://www.asus.com/products4.aspx?l1=3&l2=101&l3=0&model=1138&modelmenu=1
....odd to see the words "flagship" and "micro-ATX" in the same
sentence, heh heh! GeForce 6150 + nForce 430 chipset, S-ATA with
RAID. Are you Vista-32 or Vista-64?
This looks nasty...
http://support.asus.com/download/download.aspx?SLanguage=en-us&model=M2NPV-VM
....the device tree loses several nodes when I choose OS = Vista-32,
including the S-ATA. Either that means no extra drivers are required
because Vista includes them, or Asus/nVidia have some work to do.
Installed new Seagate 160 gig SATAII for Vista system drive.
Installed new Seagate 120 gig PATA for second hard drive. (backup purposes).
OK. At this point I'd want to know which S-ATA and IDE channels and
(IDE) master/slave relationships apply. Depending on BIOS, you could
end up with an identity collision between S-ATA and IDE devices.
Installed clean full version of Vista Business...(only OS ever installed on
new computer).
Vista installed without any issue (no SATA driver needed). (both drives
recognized in the BIOS and in Vista....
Rebooted Vista with install disk still in DVD drive, and booted just fine...
Removed DVD install disk and rebooted, would not boot at all..
Ah, OK. This is a common failure pattern
With the DVD in place, you bypass:
- selection of HD as boot device by BIOS
- MBR code in whatever HD the BIOS would have booted
- possibly, the PBR in the partition being booted
- possibly, the boot configuration file (no longer Boot.ini)
So that's where to dig. Most likely the MBR isn't on the HD you
thought it would be, and that has to cross-boot to the Vista HD.
Normally I avoid these sort of hassles by having only the one HD and
the installation optical drive hooked up at the time the OS is
installed. Even USB sticks left in place can mess things up.
Placed DVD install disk back in DVD drive and rebooted, booted just fine..
Removed second hard drive (PATA), and completely reinstalled Vista to the
only drive in the computer (SATA), and all went without issue again, but this
time I could boot without having the install disk in the DVD drive....
OK, that's good...
Reinstalled second hard drive (PATA).... it was immediately recognized by
the BIOS and Vista.... was able to copy files to and from this drive.....
I think at this point, I'd have wanted that PATA (IDE) HD
freshly-wiped, in case there was confusing stuff left on it.
Then I went to make a Complete PC Backup of Vista to the PATA
drive.....Complete PC Backup went without a hitch..... It backed up to the
PATA drive.....
Now how did that backup get made? If you did a full byte dump from
the one HD to the other so that the IDE HD would be bootable, then I
can see a mad boon risin', as CCR woudl say.
Then I went to Restore the Complete PC Backup of Vista back to the SATA
system drive, and quess what..... It did not find the SATA system driive......
Ew!
Contacted Microsoft and have an open case # on this issue....
OK... let us know how it goes...
Microsoft had me remove the PATA drive and try to do a Complete PC Backup to
an external PATA drive (via USB)... Backup again went without a hitch....
and it ALSO restored back to the SATA system hard drive......
OK; does the S-ATA now work, after that restore?
I further wanted to test this, so I again put the internal PATA drive in the
computer, and tried to restore from the external PATA drive via USB to the
SATA system hard drive, and guess what, it could not find the SATA hard drive
again.....
My guess is an identity overlay. Try avoiding that by avoiding these
matches: S-ATA 0 + Primary Master, S-ATA 1 + Primary Slave, S-ATA 2 +
Secondary Master and S-ATA 3 + Secondary Slave.
Note also that some IDE devices have different jumpers for Master with
Slave and Single HD, that you should use an 80-pin IDE cable, and that
it matters which connectors you use on the cable (the end is the
Master, the middle is the Slave) even if you aren't using Cable Select
jumpering. Don't mix Cable Select with explicit Master / Slave
jumpering on the same IDE channel.
Sorry if this is well familiar to you, but we gotta get it out the way
NOTE: Latest version of BIOS and lates version of Nvidia drivers are
installed on the system..... Boot order in BIOS is SATA first, PATA second.
All drives formated NTFS, and have not created any additional partitions....
OK. No two NTFS volumes share the same serial number, i.e. one not
cloned from the other?
Boot order looks fine, but the order in which HDs are discovered and
presented by BIOS to OS may differ, and the difference may matter.
What are the Master/Slave and S-ATA identities?
Thanks for a very succinct problem summary, BTW
--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!