dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2489
share rss forum feed


chucky5150
Divers do it Deeper

join:2001-11-03
New Iberia, LA

corrupted / missing boot sector - windows 7

I don't know what started my problems but I'm guessing it had something to do with the storm that came through last night. I should have remembered to shut down the computer.

My computer was stuck in a loop of "Installing updates, please don't shut down until finished." It would reboot and come back to this screen. Must have happened about 10 times before I decided that was enought and went ahead messing it up (or trying to fix it) my own.

Lucky I have 2 installations of Windows 7 on here, might also be the cause of my issues.

First install was on a normal HDD and that is the copy that happens to be working now. I'm betting it has something to do with the master boot record.

Second copy of Windows 7 (my main install) is on a SSD that I installed at a later date.

I went into the BIOS and turned off booting to all but the SSD hard drive and guess what happened. It wouldn't boot.

I've tried the startup recovery and writing a new partition boot sector. It fixed what it found, or at least told me it did.

Upon running the bootrec /fixboot command I was greeted with "element not found"

Bummer.

I'm thinking there should be an easy(ish) was to do this as I an boot into one copy of windows just fine. I just can't seem to get back to the Win 7 that I have been using for the past months. Is it as simple as finding a way to copy the MBR from one hard drive to the other?

Up next on the to-do list is find a battery back up for the computer.

Thank you.
--
Member of the US Air Force since May 7th, 2002 To March 29th, 2005

"You sneak up behind yourself and remove your pants before you realize what's going on." KOL


aguen
Premium
join:2003-07-16
Grants Pass, OR
kudos:2

First item, when you boot your system normally from the HDD, no changes to the BIOS boot order, do you first see a "boot select menu"?

When booting from the HDD, can you see the partitions on the SSD in Disk Management? Can you open/browse the SSD?



chucky5150
Divers do it Deeper

join:2001-11-03
New Iberia, LA

said by aguen:

First item, when you boot your system normally from the HDD, no changes to the BIOS boot order, do you first see a "boot select menu"

Yes, the menu comes up. When I select a different Windows 7 I get a message saying, "the boot selection failed because a required device is inaccessible."

said by aguen:

When booting from the HDD, can you see the partitions on the SSD in Disk Management? Can you open/browse the SSD?

Yes to both. I can open folders just fine on the SSD from the HDD. Disk Management shows the drives and labels it correctly.
--
Member of the US Air Force since May 7th, 2002 To March 29th, 2005

"You sneak up behind yourself and remove your pants before you realize what's going on." KOL

aguen
Premium
join:2003-07-16
Grants Pass, OR
kudos:2
reply to chucky5150

Ok, are you familiar with the BCDEdit utility? You can find freeware version of this utility with a google search. I use one called EasyBCD Ver. 212. Install it, then run it, take a screen cap. and post it up here. It might show us or at least point us to the problem.



chucky5150
Divers do it Deeper

join:2001-11-03
New Iberia, LA

Here's the overview that the program gave me.

There are a total of 3 entries listed in the bootloader.

Default: Windows 7
Timeout: 30 seconds
Boot Drive: F:\

Entry #1
Name: Windows 7
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe

Entry #2
Name: Windows 7
BCD ID: {default}
Device: unknown
Bootloader Path: \Windows\system32\winload.exe

Entry #3
Name: Windows 7
BCD ID: {149059d5-7201-11e1-a5af-9b59f51a7a4d}
Device: unknown
Bootloader Path: \Windows\system32\winload.exe

And the debug version:

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=F:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {149059d9-7201-11e1-a5af-9b59f51a7a4d}
resumeobject {149059dc-7201-11e1-a5af-9b59f51a7a4d}
displayorder {149059dd-7201-11e1-a5af-9b59f51a7a4d}
{149059d9-7201-11e1-a5af-9b59f51a7a4d}
{149059d5-7201-11e1-a5af-9b59f51a7a4d}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-------------------
identifier {149059dd-7201-11e1-a5af-9b59f51a7a4d}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {149059de-7201-11e1-a5af-9b59f51a7a4d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {149059dc-7201-11e1-a5af-9b59f51a7a4d}
nx OptIn

Windows Boot Loader
-------------------
identifier {149059d9-7201-11e1-a5af-9b59f51a7a4d}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {149059da-7201-11e1-a5af-9b59f51a7a4d}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {149059d8-7201-11e1-a5af-9b59f51a7a4d}
nx OptIn

Windows Boot Loader
-------------------
identifier {149059d5-7201-11e1-a5af-9b59f51a7a4d}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {149059d6-7201-11e1-a5af-9b59f51a7a4d}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {149059d4-7201-11e1-a5af-9b59f51a7a4d}
nx OptIn

I don't remember why there are three Window 7s but there is. I guess I must have reformatted and just installed onto a different partition in order to not have to format all my stuff.
--
Member of the US Air Force since May 7th, 2002 To March 29th, 2005

"You sneak up behind yourself and remove your pants before you realize what's going on." KOL

aguen
Premium
join:2003-07-16
Grants Pass, OR
kudos:2
reply to chucky5150

Well.... BCD can't find either of the last 2 instances of Win 7 installs, see the osdevice unknown entries in the last 2 win 7 entries.

Not sure whats up with the Windows Boot Manager being on the F: partition either really. Anyway, the boot manager doesn't know where to look (Drive ID) for the second instance of win7 on your SSD drive.

You have made changes do to the things you've already tried to do which probably hasn't helped. Did you happen to make a recovery disc for the install to the SSD? If not, then I'd suggest performing a "repair install" with your win 7 install disk and be sure to point it at the SSD.



chucky5150
Divers do it Deeper

join:2001-11-03
New Iberia, LA
reply to chucky5150

Well, I think I've made some forward progress. I'm able to get the right win 7 (the on on SSD) to boot, however, it is stuck in a loop of trying to install an update.

I also made some changes in EasyBCD (added a location for one of the installs and did a name change). That seemed to have helped. Ran the Startup Recovery again and that made some changes that seem to have helped some.

No, I never did make a recovery disk. It was always on the something I should be doing list.

Here's the updated info from EasyBCD

There are a total of 2 entries listed in the bootloader.

Default: Windows 7 on SSD
Timeout: 30 seconds
Boot Drive: F:\

Entry #1
Name: Windows 7 on SSD
BCD ID: {default}
Drive: G:\
Bootloader Path: \Windows\system32\winload.exe

Entry #2
Name: Windows 7 Home Premium (recovered)
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe

Now with debugging
Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=F:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {149059dd-7201-11e1-a5af-9b59f51a7a4d}
resumeobject {149059dc-7201-11e1-a5af-9b59f51a7a4d}
displayorder {149059dd-7201-11e1-a5af-9b59f51a7a4d}
{149059e0-7201-11e1-a5af-9b59f51a7a4d}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {149059dd-7201-11e1-a5af-9b59f51a7a4d}
device partition=G:
path \Windows\system32\winload.exe
description Windows 7 on SSD
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {149059de-7201-11e1-a5af-9b59f51a7a4d}
recoveryenabled Yes
osdevice partition=G:
systemroot \Windows
resumeobject {149059dc-7201-11e1-a5af-9b59f51a7a4d}
nx OptIn
pae Default
sos No
debug No

Windows Boot Loader
-------------------
identifier {149059e0-7201-11e1-a5af-9b59f51a7a4d}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium (recovered)
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {fc1b54e5-5b90-11e2-9662-806e6f6e6963}

--
Member of the US Air Force since May 7th, 2002 To March 29th, 2005

"You sneak up behind yourself and remove your pants before you realize what's going on." KOL


captokita
Premium
join:2005-02-22
Calabash, NC
reply to chucky5150

When you do the F8 menu boot, do you have the option "Repair my computer" at the top? If so, have you tried to run a system restore from that environment?

I know it's an SSD, and this is bad for it, but have you run chkdsk on the drive from your working installation of 7? That might fix whatever is causing the loop boot (failed repeat updates)

Though I would personally try running system restore on it first to a date last week.

Good luck!