I have 3 drives, C-OS internal, D-data internal, E-data external. "Bootmgr" appears on C and E, but not D. I thought this was some kind of error, deleted it off E, machine wouldn't boot. A quick fix with the Win 7 DVD, all was well again.
Is there any reason the bootmgr file is on the external drive?
C = RAIDO - 4 SSDs
D = 64 GB Patriot SSD
E = WD 640 GB spinner - connected by eSATA cable to eSATA port on back panel.
Check with DISKPART or free Partition Wizard that only your OS drive is Active.
If not, mark ONLY the Win7 partition active then boot the DVD/Repair CD to run Startup Repair up to 3 separate times with reboots to repair or write the MBR to Win7.
Last edited by gregrocker; 25 Jul 2010 at 15:20.
Thanks GR, as soon as I get the machine to boot up I'll check it out. Right now it is in rough shape, not related to the bootmgr issue.
If it won't start Windows, then boot the Win7 DVD repair console, press Shift F10 or click through to Recovery Tools list to open a Command line, then use DISKPART to mark Win7 partition active: Partition - Mark as Active - Windows 7 Forums.URL
Close command line, from Recovery Tools list select Startup Repair to run up to 3 separate times with reboots to repair or write the MBR to Win7: Startup Repair - Windows 7 Forums.URL
If it continues to fail to start, tell us exactly when it fails and any error message.
I got machine booted - when I was working in the case to add 2 drives, I moved a SATA cable to one of the SSDs in the RAID 0 array. Once I secured the cable, all was well and I just deleted the bootmgr file off the drive, which I now have as part of a 2 drive RAID 1 array for data.
Thank you for your reply.
As far as the operating system is concerned, an eSATA drive is not necessarily external.
Quote