Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



ahmad2080

HP Notebook: The recovery partition could not be found

Recommended Posts

ahmad2080    0

At last........I've launched the recovery console.. :thumbup

How did I do that?... It took all the day to restore my system to factory, and at last, another success...

I just hope that this fixes both F8 and F11.....

However, here is how I launched WinPE:

http://technet.microsoft.com/en-us/l.....;/cc721886.aspx

and here is a snippet from their site.

To create an entry to boot a WIM image from hard disk
  • Create the {ramdisktoptions} object in your BCD store by specifying the following. Drive should be the drive that contains the image.
    bcdedit /create {ramdiskoptions} /d "Ramdisk options"
    bcdedit /set {ramdiskoptions} ramdisksdidevice partition=Drive
    bcdedit /set {ramdiskoptions} ramdisksdipath bootboot.sdi
  • Create a new boot application entry by specifying:
    bcdedit /create /d "Boot from WIM" /application OSLOADER
  • This will return an identifier (GUID) for the newly created entry. This new entry will be referred to as {GUID} in the rest of this procedure. Next specify the following:
    bcdedit /set {GUID} device ramdisk=[c:]sourcesboot.wim,{ramdiskoptions}
    bcdedit /set {GUID} path windowssystem32winload.exe
    bcdedit /set {GUID} osdevice ramdisk=[c:]sourcesboot.wim,{ramdiskoptions}
    bcdedit /set {GUID} systemroot windows
  • If you are booting into Windows Preinstallation Environment (Windows PE), then you will also need to specify:
    bcdedit /set {GUID} winpe yes
    bcdedit /set {GUID} detecthal yes
  • Next specify the following to add your new entry to the display order:
    bcdedit /displayorder {GUID} /addlast

When I tried the above procedure...it didn't work.

Here is how it worked with me (just a small C to D modification):

  • Create the {ramdisktoptions} object in your BCD store by specifying the following. Drive should be the drive that contains the image.
    bcdedit /create {ramdiskoptions} /d "Ramdisk options"
    bcdedit /set {ramdiskoptions} ramdisksdidevice partition=D:
  • bcdedit /set {ramdiskoptions} ramdisksdipath bootboot.sdi
  • Create a new boot application entry by specifying:
    bcdedit /create /d "Boot from WIM" /application OSLOADER
  • This will return an identifier (GUID) for the newly created entry. This new entry will be referred to as {GUID} in the rest of this procedure. Next specify the following:
    bcdedit /set {GUID} device ramdisk=[D:]sourcesboot.wim,{ramdiskoptions}
    bcdedit /set {GUID} path windowssystem32winload.exe
    bcdedit /set {GUID} osdevice ramdisk=[D:]sourcesboot.wim,{ramdiskoptions}
    bcdedit /set {GUID} systemroot windows
  • If you are booting into Windows Preinstallation Environment (Windows PE), then you will also need to specify:
    bcdedit /set {GUID} winpe yes
    bcdedit /set {GUID} detecthal yes
  • Next specify the following to add your new entry to the display order:
    bcdedit /displayorder {GUID} /addlast

I hope that this is ends my endless laptop story :wacko: ......

EDIT: I'm sorry, I forgot to upload bcdedit.exe.......here it is: bcdedit.rar

Edited by ahmad2080

Share this post


Link to post
Share on other sites

ahmad2080    0

OK....Here are my final results:

  • F8 returns to duty :rolleyes: and works perfectly
  • F11 shows the error message :
    A disk read error occured[*]Press Ctrl+Alt+Del to restart


When I press Ctrl+Alt+Del it doesn't respond....

So the major question now is : Should I burn the recovery disks now?? or try to recover the F11 function by applying another system recovery (This time by setting the recovery partition as Active)???

What I've understood from all the previous 7 pages in this thread is that the F11 hotkey is completely related to the MBR which cannot affect a recovery operation from recovery Disks.....which means that it's safe now to burn the disks, Right?

Share this post


Link to post
Share on other sites
Snack    0

One more thing to do

Copy boot\boot.sdi from the Windows Vista installation DVD (C:\WINDOWS\Boot\DVD\PCAT) to d:\boot directory (By default this folder is hidden in Windows Explorer)

Edited by Snack

Share this post


Link to post
Share on other sites
ahmad2080    0
One more thing to do

Copy boot\boot.sdi from the Windows Vista installation DVD to d:\boot directory (By default this folder is hidden in Windows Explorer)

You mean the recovery DVD that I still didn't create??? And what's the point? You are thinkiing that this may solve the F11 problem?

Edited by ahmad2080

Share this post


Link to post
Share on other sites
Snack    0

Found one more solution :)

(not completed yet)

I think at this point left only users with completely destroyed HP recovery system :wacko:

So you can (must) clear all traces that was made by various (illegal from HP devlopers point of view) software to PC.

Function key F11 from boot menu.

to restore it working

First step: download and burn Vista repair CD

Boot from this media and do Startup Repair --> and you get clear BCD file along with restored to standart MBR 0 sector.

Check if bootsector D: have a RECOVERY marker (Post #115)

Further steps:

To be able to boot into recovery WinRE with F11 try this workaround:

Unzip this command set to C\HP\RECOVERY\BIN Cmd.rarCopy to this folder file cmd.exe from c:\windows\system32 (to simplify execution)

note:

Scripts need some redactions to be pointed to SMINST directory (replace location) and MBRins file (may be renamed) see post #149

* run WAUfix_new.bat from the set --> it will repair F11 & F8 function in MBR and fix system BCD

* run cmd.exe

* copy and paste to cmd window this script (to be sure the file boot.sdi is present on D:\boot)

xcopy /r C:\WINDOWS\Boot\DVD\PCAT\boot.sdi d:\boot\boot.sdi

Reboot and press F11 --> you should see Softhink restore menu.

If not

Caution: this BCD from my Pavilion Recovery partition!!! Restore it from bak if this tip doesn't working!!!

Unzip to the same folder: Working_D.rar

* copy and paste to cmd window this script

xcopy /r d:\boot\bcd d:\boot\bcd.bak

xcopy /r working_d.bcd d:\boot\bcd

Following this at last I felt into SoftThinks Recovery menu.

Solution:

Now I succesfully restored my HP from discs created in posts #115 #125

Edited by Snack

Share this post


Link to post
Share on other sites
Snack    0

Tripredacus

That's a weird option there, the DMI to drive 1...

Take a look on sector 8 in MBR from HP at offset 0x1000 is there a SOFTHINK label with all PC configuration?

Share this post


Link to post
Share on other sites
ahmad2080    0

Snack, I don't have WAUfix.bat in C:\HP\recovery\bin

What's your noteboook model?

F11 in my case, makes the recovery partition active..but doesn't load the recovery manager...

Also, when I executed MBRInst.exe, this was the result:

post-237972-1239981525_thumb.jpg

So F11 CAN locate the recovery partition and shows the error message "disk read error".......

AND MBRInst.exe CAN see my recovery partition but can't update its boot record.......

:wacko:

I just want to know who is the suspect here??? MBR? BOOT SECTORS?

or it's all about NTDLR and BCD??

If the only purpose of F11 hotkey is to set D: as active, then it's working fine.

But what then? If a partition is active it should be able to load \windows\system32\winload.exe which exists only in the boot.WIM file....is that why the "disk read error" message appears?

Can somebody please clarify the root of my problem here? :(

I'm LOST.

Edited by ahmad2080

Share this post


Link to post
Share on other sites
Snack    0

1. Do you have this file in D:\boot directory?

If not > copy and paste this script to elevated command prompt

xcopy /r C:\WINDOWS\Boot\DVD\PCAT\boot.sdi d:\boot\boot.sdi

2. Check disk D: for errors

right click on disc D: > properties > tools > check now > automatically fix file system errors

3. Do you have C:\windows\SMINST directory with mbr.dll there? (Where Softhink keep files)

4. Is there HPRM-BCDFix.cmd C:\HP\recovery\bin?

If not > upload it from post #140 along with WAUfix.bat

Share this post


Link to post
Share on other sites
ahmad2080    0
1. Do you have this file in D:\boot directory?

If not > copy and paste this script to elevated command prompt

xcopy /r C:\WINDOWS\Boot\DVD\PCAT\boot.sdi d:\boot\boot.sdi

2. Check disk D: for errors

right click on disc D: > properties > tools > check now > automatically fix file system errors

3. Do you have C:\windows\SMINST directory with mbr.dll there? (Where Softhink keep files)

4. Is there HPRM-BCDFix.cmd C:\HP\recovery\bin?

If not > upload it from post #140 along with WAUfix.bat

  1. yes, boot.sdi already exists in d:\boot
  2. There are no errors
  3. The SMINST folder in my case is in C:\program files not windows
  4. no, HPRM-BCDFix.cmd exists only in SMINST folder

What's giong around in your mind ? :blink:

Share this post


Link to post
Share on other sites
ahmad2080    0
Did you try my method with mbr.exe ahmad?

Actually, I hoped that I won't be in need to use mbr.exe.......

The last time I messed with MBR made me Suffer to undo the changes I made....

However, I'll try this one.

Here is my partinfo.txt :

PARTINFW 1.11
Copyright (c) 1996-2008 TeraByte, Inc. All rights reserved.

Run date: 04/17/2009 21:00

====================================================================
MBR Partition Information (HD0 - 0x5BAE7BDD)
(CHS: 1022/254/63) (WCHS: 38913/255/63)
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 32 33 | 7 | 1023 254 63 | 2048 | 602947576 |
| 1: | 0 | 1023 254 63 | 7 | 1023 254 63 | 602949632 | 22187713 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 2048 Total Sectors: 602947576 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 2048
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x023F03FF7
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x023F03FF
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xC05669A156699944
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 602949632 Total Sectors: 22187713 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 602974208
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x015227FF
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x015287F
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x8E02A92E2A91BE9
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------

As you can see, both partitions have the same file system ID.

So I used mbr.exe as you said to hide D:, and now this is the new partinfo.txt:

PARTINFW 1.11
Copyright (c) 1996-2008 TeraByte, Inc. All rights reserved.

Run date: 04/17/2009 21:12

====================================================================
MBR Partition Information (HD0 - 0x5BAE7BDD)
(CHS: 1022/254/63) (WCHS: 38913/255/63)
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 32 33 | 7 | 1023 254 63 | 2048 | 602947576 |
| 1: | 0 | 1023 254 63 | 17 | 1023 254 63 | 602949632 | 22187713 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 2048 Total Sectors: 602947576 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 2048
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x023F03FF7
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x023F03FF
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xC05669A156699944
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x17 LBA: 602949632 Total Sectors: 22187713 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 602974208
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x015227FF
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x015287F
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x8E02A92E2A91BE9
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

After restarting windows the D partition file system returned again to 0x7!!!!!! :blink:

Should I proceed the other steps?

Share this post


Link to post
Share on other sites
ahmad2080    0

.........

I executed both commands in one windows session:

MBR 0 1 /H

mbr 0 /install selm 10 11 "Press F11 for Recovery" 0x7 0x17

and then restarted the computer and pressed F11......

The same error message appeared :

A disk read error occured 
Press Ctrl+Alt+Del to restart

BTW, the recovery partition automatically returns to its original file system ID 0x7, so all what I had to do to boot into windows again was setting C: as Active using mbrwizd.exe in my bootable USBStick.....

Using the command MBR 0 /reset did not erase the edited mbr portions but erased my original MBR and my system became unbootable again......wait a second...

This is strange, now I have to press F11 to boot Vista, otherwise it says that I don't have a bootable device.!!! :blink:

It doesn't matter, I restored my original mbr again using HDhacker...

I just want to know who is the suspect here??? MBR? BOOT SECTORS?

or it's all about NTDLR and BCD??

If the only purpose of F11 hotkey is to set D: as active, then it's working fine.

But what then? If a partition is active it should be able to load \windows\system32\winload.exe which exists only in the boot.WIM file....is that why the "disk read error" message appears?

I really want to know the answer of these questiions.....

Any more ideas??

EDIT:" I don't beleive in HP special MBR code to load WINRE using the F11 function.........IMHO, all what we need now is a way to load D:\boot\boot.wim using the F11 function.

This explins what I mean : post-237972-1240000788_thumb.jpg

Edited by ahmad2080

Share this post


Link to post
Share on other sites
Snack    0

All routine in MBR has only purpose - set keys to pointing on partition bootloader - which wake up bootmgr with options read from local BCD (three different ones - for C:, for D: and for DVD)

I got wiped BCD along with MBR for many times on C: and in every cause, using Vista Restore CD and WUAfix (modified), make restored normal boot process with all those keys and menues working well.

As I see you are stoped on BCD from D:.

If objects in BCD is incorrect you will not be able to boot :huh: looking errors (MS only knows) even Blue Screen.

1. Look for sure if present signature RECOVERY in bootsector D:

2. Edit WUAfix script (find and replace "windows" with "program files")

3. I there in SMINST folder somewhat like mbr.dll or mbrinst.exe?

4. If mbrinst.exe present instead of mbr.dll (my PC) then edit WUAfix the same way as in p.2

Edited by Snack

Share this post


Link to post
Share on other sites
ahmad2080    0

Ok,

Thanks all of you for your time and effort....

The F11 problem has not been solved [nothing worked], and I will give up at this part....

So here is what I'm gonna do:

Burn the recovery disks and then recover my system using them.....

If the disks booted and loaded the recovery manager, that'll be enough...

If not, there is a trick to burn them again....so I'll return again to the unanswered questions " Primary function of F11 " and " Files needed to boot from an active partition with windows vista on it" and search for their answers..... :ph34r:

Thanks,

Ahmad :hello:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×