Booting Issue (TestDisk / PartedMagic)

[cstebila]

Booting Issue (any help very appreciated)

Here's an update:

Original problem was that I was receiving an unmountable boot volume error with a BSOD. After taking a stab at a few solutions the situation is now this. Upon being able to enter the recovery console the only Windows 7 installation showing up on the list is the system recovery reserve. I can access the command prompt, but cannot perform all commands, for example upon entering "diskpart" and than "list disk" the prompt does nothing.

I noticed the system reserve portion of the HDD was set as "boot." I used a bootable OS (PartedMagic) to set the "boot" partition to the C: the system partition. I also redirected Windows Load Manager / Boot Manager to "C:" for "default ospartition" etc.

Rebooting I found a new error "bootmgr not found" so I copied the boot files from the system reserved recovery porition of the HDD to the system porition. Now following the windows loading bar, I receive a blank screen, and cannot access the recovery console via the installation disc. Anyone have any suggestions? ANY advice is extremely appreciated!

---

original problem

Hey guys,

Having a seemingly severe problem, and was wondering if anyone had any potential tips. Here's the story: Was running Windows 7 32bit on my HP laptop, when it unexpectedly shut down due to the battery reaching very low levels. (the reason for this was battery calibration)

The problem begins here. Upon reboot I receive the error "unmountable boot volume" on the standard blue error screen. I did some research and found that running a "chkdisk" would potentially remedy the situation. Downloaded a Windows 7 32bit recovery iso, booted from it to run a "chkdisk" from the command line, but after the first menu (language select) didn't receive any further prompts (just a blank windows themed screen)

I then downloaded "PartedMagic" (not to be confused with Partition Magic), a bootable OS featuring a wide array of tools. I ran a program called TestDisk and rewrote my MFT using the MFT mirror. Hoping this would solve the problem, I rebooted to find a different error as opposed to the blue screen. I didn't record the code, however it was a generic "Windows Failed to Start" error, which seems to have resulted from the MFT being rewritten.

Upon seeing this, I injected my Windows 7 installation disc, which I realized I should have done at the start. I got to the "repair my computer" screen and chose "Startup Repair" but noticed my OS partition wasn't showing up for scanning, only another partition labeled "D" that read space: 0 Having a good feeling that scanning this "D" partition would not solve any problem, as it wasn't the OS one, I went ahead and started the scan just hoping for some fortune. I came back over an hour later to find it still scanning. I promptly canceled this, although it said the scan make take over an hour, I had a feeling this was a futile attempt.

Which leaves me at the current position. I can no longer get to the recovery council from either discs, and can't boot up Windows. (instead of a blue screen, or error report, I now get a blank screen following the standard Windows 7 loading bar)

Some options I have are: booting PartedMagic and utilizing one of many tools. One of these tools TestDisk (which I used earlier to rewrite the MFT) gives me some options as well. I'm not well versed in either of the programs, but am more than able to follow advice. Below are links to both the site for Parted Magic, and a TestDisk's Wiki.

What's semi-assuring is, I see the worst case scenario as formatting the drive, and re-installing 7, however I want to pursue this as a last effort.

* Also I wanted to note, I was able to see my data through PartMagic, from both partitions (the OS and data) so the drive isn't corrupt!

* TestDisk reads "Hidden Sectors Present" before running a search for these sectors, it displays the following

" Partition Start End Size In Sectors

P HPFS - NTFS 0 32 33 12 223 19 173921687

Error:size boot_sector 802639530 > partition 802639529 Invalid NTFS or EXFAT boot"

This info / message is displayed beside my other partitions which are without error. An option I have is to search for the sector, and rewrite the partition. However wanted to see if anyone had input before doing this.

Any advice or help on this is extremely appreciated, and can't be stated enough, as, as of this moment I'm lost.

Either way, if you have no advice, thanks for taking the time to read through this, I appreciate it very much anyways,

Camaren

links:

List of Parted Magic tools
Test Disk wiki
Running Test Disk
NTFS MFT Boot Repair page

 

[theog]

Check your HD.
http://www.sevenforums.com/tutorials/433-disk-check.html (let the scan finish)

Check with a hard drive diagnostic tools.
Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Make sure Windows 7 partition is active. http://www.sevenforums.com/tutorials/71432-partition-mark-active.html?ltr=P

http://www.sevenforums.com/tutorials/681-startup-repair.html?ltr=S
Note: You may need to do startup repair 3 to 4 times.

http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html
http://www.sevenforums.com/tutorials/668-system-recovery-options.html
http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[cstebila]

Check your HD.
http://www.sevenforums.com/tutorials/433-disk-check.html (let the scan finish)

Check with a hard drive diagnostic tools.
Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Make sure Windows 7 partition is active. http://www.sevenforums.com/tutorials/71432-partition-mark-active.html?ltr=P

http://www.sevenforums.com/tutorials/681-startup-repair.html?ltr=S
Note: You may need to do startup repair 3 to 4 times.

http://www.sevenforums.com/tutorials/2083-system-repair-disc-create.html
http://www.sevenforums.com/tutorials/668-system-recovery-options.html
http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

Cannot perform Disk Check due to inability to reach recovery council / boot windows. The same applies to your suggestions to "Repair Install" and "Create Recovery Disc."

As mentioned, I already ran a "Startup Repair." I'll check out the WD diagnostic utilities, though I believe the TestDisk / Parted Magic will have the way forward.

 

[theog]

You can do a disk check from Startup repair.

View attachment 83028

 

[cstebila]

You can do a disk check from Startup repair.

View attachment 83028

Unfortunately once I click Windows Startup Repair, all I get is a blank screen following the loading.

Appreciate the suggestions a ton though. Unable to access windows, recovery council, and startup repair. The only thing I got left is looking to be messin with the HDD itself.

 

[theog]

When booting from CD/DVD?

 

[cstebila]

When booting from CD/DVD?

Yeah same, booting from installation disc gets me to where I can click "Repair Your Computer" but doesn't prompt me again after. While booting from a recovery disc asks me to choose a language, and doesn't prompt again after. Just blank windows themed screens.

I have a feeling this is due to my canceling of the 1 Startup Repair I ran originally. Before canceling that in the midst of it, I was able to get to the council. I'm thinking to look through my BIOS for some potential settings to clear things up.

 

[theog]

Click on repair my Computer OR Press Shift+F10 (for command prompt).

View attachment 83031 View attachment 83032

 

[cstebila]

In the midst of trying this right now, thank you for this advice so far. I really really really appreciate it!

edit: Just ran a "chkdsk c:/f"

Message

Windows has checked the file system and found no problems.

However it is still not booting. Someone suggested potentially running a bootsector.exe and fixing the MBR.

 

[theog]

In the midst of trying this right now, thank you for this advice so far. I really really really appreciate it!

edit: Just ran a "chkdsk c:/f"

Message

Windows has checked the file system and found no problems.

However it is still not booting. Someone suggested potentially running a bootsector.exe and fixing the MBR.

http://www.sevenforums.com/tutorials/681-startup-repair.html?ltr=S
Note: You may need to do startup repair 3 to 4 times.

 

[cstebila]

Just wondering, would you recommend doing the Startup Repair, or bootsector.exe fix MBR first. I only ask because I had potentially overwrote the MFT.

edit: btw, at the risk of being pure annoying, just wanted to say thanks again.

 

[theog]

http://www.sevenforums.com/tutorials/681-startup-repair.html?ltr=S
Note: You may need to do startup repair 3 to 4 times.[/QUOTE]


OR

Make sure Windows 7 partition is active.http://www.sevenforums.com/tutorials/71432-partition-mark-active.html?ltr=P

Type in command line
Try this:
bootrec /fixboot
bootrec /fixmbr
bootrec /rebuildbcd

 

[cstebila]

Still not allowing me to access Startup Repair (via console which fails to appear or at Windows Startup). When trying to set the partition as the active one, after DISKPART the command prompt displays the initial info, than won't allow any typing, freezes. Same happens if I just type in "DISKPART>list disk" no listing just a frozen command prompt.

Been running rebuildbcd, any it also appears frozen.

edit: I ran "bcd edit" and got the following and found that:

Windows Boot Manager device was set a C:

while

Windows Boot Loader device was set a D:

would changing this to C, potentially help, or is this just my data partition loading at the same time?

 

[cstebila]

Here's an update:

Original problem was that I was receiving an unmountable boot volume error with a BSOD. After taking a stab at a few solutions the situation is now this. Upon being able to enter the recovery console the only Windows 7 installation showing up on the list is the system recovery reserve. I can access the command prompt, but cannot perform all commands, for example upon entering "diskpart" and than "list disk" the prompt does nothing.

I noticed the system reserve portion of the HDD was set as "boot." I used a bootable OS (PartedMagic) to set the "boot" partition to the C: the system partition. I also redirected Windows Load Manager / Boot Manager to "C:" for "default ospartition" etc.

Rebooting I found a new error "bootmgr not found" so I copied the boot files from the system reserved recovery porition of the HDD to the system porition. Now following the windows loading bar, I receive a blank screen, and cannot access the recovery console via the installation disc. Anyone have any suggestions? ANY advice is extremely appreciated!

 

[cstebila]

Sorry for the shameless bump (even though there is some shame) just hoping someone may stumble across it and think of a suggestion.

Thanks theog for the help so far, you helped me make some progress.

 

[StillC]

I am just reporting a similar incident from which i was able to recover.

It started as i was stepping through the recovery disk i had made with the Windows 7 facilities toward re-imaging from an image i had stored in an external drive (Scorpio Blue) using (again) the Windows 7 facilities. I was not quite ready to execute, so i cancelled out of the dialogue process toward a re-image. After that, when i rebooted, i got error message:

"bootmgr not found"

So i used my recently-made restore/repair disk to repair and after one or two tries, was successful in getting Windows to boot normally.
----
That's one issue. The other thing that happened was after i re-imaged my C: drive, the external HD gained an additional partition called 'System Reserve', which was about 62 MB free of 99 MB. It appeared empty when opened, but would store and show a text file if i wanted. Besides that, i could not see/find the 299 GB partition anymore on the external HD. My battery ran out of power, so i resumed troubleshooting in the morning with power, and this time was able to find the temporarily lost partition on the external HD. It was gone, and now it was back.
----
I've survived, and am pretty impressed with the backup facilities in Windows 7 (Home Premium), but thought i would just report this to give someone/anyone a heads up in case there is something here that needs to be addressed among Microsoft troubleshooters.

~Still