Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

HP Notebook: The recovery partition could not be found

- - - - -

  • Please log in to reply
210 replies to this topic

#26
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,902 posts
  • Joined 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Donator

Yes Jaclaz. The MBRINST I had downloaded from HP looks like the one in that blog. Remember that (in my other topics) my SoftThinks software does not come with the MBRINST.exe. The function that it provides is coded into their software via a DLL which exists in the partition.

Bottom line, you can try running MBRINST, but only if you can find the MBR.INI in the recovery partition. Use that as your INI source in the command. But be warned, if something is missing, or the file is incorrect (there are more than one in the partition) you may make it so your partition is not bootable.

Also note that this tool (from the quote) is being run from Windows, and probably not from the recovery partition itself.
MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg


How to remove advertisement from MSFN

#27
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

THIS IS ONLY VALID FOR PEOPLE WITH A HP COMPUTER,WHERE THE click on Start, Run, input CMD and press enter, to open a Command Prompt window
type in the following command:
C:\windows\SMINST\mbrinst.exe /ini C:\windows\SMINST\mbr.ini /r /q
the PC will reboot from the "HP Recovery partition".
When the window "Welcome to HP PC Recovery" is displayed, click on Cancel to exit.
PC will reboot, and this time the "Press F11 for recovery" should appear for 5 seconds, before booting to thew chooice between Vistra and XP

The instructions on the Italian site are consistent with these:
http://www.thestuden...ad.php?t=653972
though it seems like the used MBRINST.EXE is the one in the Recovery Partition. :unsure:

I beleive that there are some differences here. The path of mbrinst.exe is completely different so the command given didn't work. Even if I know the correct path, I don't think that it will be accessable.
But if the purpose of that command is to restore mbr from mbr.ini, I can do that from mbrinst.exe right?

But be warned, if something is missing, or the file is incorrect (there are more than one in the partition) you may make it so your partition is not bootable.


I'll try some options in the mbrinst window and report the results.

#28
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09
I tried the mbrinst as i said...it made no difference. It just kept saying : !warning the recovery partition could not be located.

I tried other .exe &.cmd files......no desired results were obtained..

The only choise left was the full recovery......and because of all this time-wasting I was frustrated...I recovered the system without backing up my files...[ It doesn't matter anymore]

After a while, an error message popped up saying that the MBR is too long like 30 bits while should be 16 or something like that.

Anyway the recovery procedure continiued. What happened next still didn't happen yet. I'm still waiting for the process to complete, so I thought to invest the time and give some feedback on the situation.


EDIT: I'm Screwed.......The recovery process completed and I ofcourse lost all my files. That would have been an acceptable sacrifice if I was able to create the recovery disks, but the problem is still there. Somehow, the partition can perform a complete recovery but lost the link with the softthinks software.

Now I'm done with all my available options. Anybody has a solution to recover the link between softthinks and recovery partition?.....There is only one option left that I'll choose soon : GIVE UP.

Edited by ahmad2080, 02 April 2009 - 04:42 PM.


#29
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,568 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Now I'm done with all my available options. Anybody has a solution to recover the link between softthinks and recovery partition?.....There is only one option left that I'll choose soon : GIVE UP.


Wait a minute, before giving up. (usually IT IS NOT AN OPTION! :angry: , but I do understand your frustration :))

Can you access the Recovery partition (say it's D:\) and open a command prompt and run in it:
DIR /S D:\ >C:\Recdir.txt
(change D: driveletter accordingly to your setup.

And attach the resulting Recdir.txt file?

I am curious to see what files are in it.

jaclaz

#30
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

Can you access the Recovery partition (say it's D:\) and open a command prompt and run in it:

DIR /S D:\ >C:\Recdir.txt
(change D: driveletter accordingly to your setup.

And attach the resulting Recdir.txt file?

I am curious to see what files are in it.

jaclaz

The recovery partition is D: too in my case. When i typed that command the result was dissapointing [ACESS DENIED].
I don't know why.
I guess that you are right, It's not an option. :angry:

EDIT: I've lost my mind......totally.
I forget to run cmd as administrator. Any way I attached the results.
Attached File  me.txt   7.14KB   28 downloads

Attached Files


Edited by ahmad2080, 03 April 2009 - 07:00 AM.


#31
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,568 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
It is possible that from that command prompt you cannot access the ROOT of you C:\ drive? :w00t:

Try changing to the D:\ recovery partition and issuing:
DIR /S >C:\Recdir.txt
or try placing the output file on some other place, a USB stick would be allright, but I need to see a complete list with directory structure and filesizes to (maybe :unsure:) understand how the thingy is made together:
DIR /S >X:\Recdir.txt

jaclaz

#32
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

It is possible that from that command prompt you cannot access the ROOT of you C:\ drive? :w00t:

Try changing to the D:\ recovery partition and issuing:

DIR /S >C:\Recdir.txt
or try placing the output file on some other place, a USB stick would be allright, but I need to see a complete list with directory structure and filesizes to (maybe :unsure: ) understand how the thingy is made together:
DIR /S >X:\Recdir.txt

jaclaz


jaclaz:
You must have replied while I was editing the post.Check it up again plz.

#33
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,902 posts
  • Joined 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Donator

Yeah, I hate that "Recovery Partition not found" message.

NOTE: I claim no responsibility as to the consequences if you use the following information. I have no tested these tools on a Soft Thinks partition, only on a Windows PE partition. If you attempt the following, make sure you research how to install a standard MBR in case it becomes damaged with these tools.

There may be yet another option, and that would be to use the steps I had done in my Recovery Partition project. It requires the use of MBR.EXE, which isn't the same as MBRInst.exe. It is available on Terrabyte Unlimited's website. This is what needs to be done.

The MBR.exe needs to be put in the root of the recovery partition. You also need it in the root of the C drive. You run this command first from the MBR.exe on C. You can run it from Windows.

mbe.exe 0 1 /H

This sets the recovery partition to be hidden (as it should be)

mbr.exe 0 /install selm 10 11 "Press F11 for recovery" 0xC 0x1C

the 11 and F11 in the above line can be another number. They must equal each other.

You can now restart the computer. Press F11 and it should try to boot into the recovery partition. If it fails, you will get a standard error message like operating system not found, etc. If this happens then this method will not work for you. If you cannot boot into Windows after a fail, you need to run the command below somehow, via NTFSDOS or a PE CD.

If you are able to boot into the recovery partition, you must run another command before you can boot into Windows again. And that is:

mbr.exe 0 /reset

The reason is when you press F11, the recovery partition becomes Active and the C drive (may) become hidden.
MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg

#34
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09
Tripredacus:
Let me first ask a question before trying that on the softhinks partition:
Is the problem that I have completly related to the MBR?
Is the MBR the primary reason why Softhinks can't see the partition?

I got in contact with HP online chat & with HP E-mail service but both didn't help.
they just keep saying that I have to buy the disks if I need them. I tried to make them tell me how to solve the problem technically but the only result was getting me on my nerves.

When I was chatting with their technican explaining the whole problem, I realized that I forgot to say (here in MSFN) that I once (before Partition magic and HP tool) executed the Recovery Disk creation and it showed how many DVD's I needed. At that time I didn't have the required empty DVD's so I simply exited the program.

The HP technican told me that the program was designed to be executed and burn DVD's only one time.
I don't beleive the 'one time execution' part, but let's assume that this is right. Then the problem of creating disks has nothing to do with PM & HP tool (Maybe they only affected the F11 function at start up)
If that is correct then MBR programs won't solve the problem. Right?

So if anyone tried to execute the Recovery disk creation twice and succeeded to reach the page where it tells how many DVD's are required, it'll make me sure that the problem cause is the MBR. Then I'll proceed Tripredacus's idea.


#35
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,327 posts
  • Joined 14-September 05
  • OS:none specified
  • Country: Country Flag

The HP technican told me that the program was designed to be executed and burn DVD's only one time.
I don't beleive the 'one time execution' part, but let's assume that this is right. Then the problem of creating disks has nothing to do with PM & HP tool (Maybe they only affected the F11 function at start up)
If that is correct then MBR programs won't solve the problem. Right?

So if anyone tried to execute the Recovery disk creation twice and succeeded to reach the page where it tells how many DVD's are required, it'll make me sure that the problem cause is the MBR. Then I'll proceed Tripredacus's idea.

I am thinking it's probably the MBR. What bit you initially was using PM and allowing it to fiddle with the MBR.

And I believe the HP Technician is wrong! Once you Restore from the Recovery Partition, you are back to Factory Install (just like when you bought it). I did this already on that HP/Compaq I told you about. Resets everything on the recovered OS partition! Therefore, the option to create disks reappears. The sole purpose of creating the Disks is in case your whole HDD is wiped (or something) and you need to Restore (from somewhere). I did that several times as a test scenario (after Ghosting). And I can't honestly remember if the option to recreate the Recovery Partition existed after using the Disk Set (sorry...).

Your main problem seems to be (right now) getting booted into the Recovery Partition.

edit - and FWIW, if you used PM, then maybe you have PTEDIT (Partition Table Editor), although I don't know if it would help or not...
basic info on PTEDIT (now owned by Symantec) -
http://service1.syma...004063693751462
another tidbit (and ptedit download) -
http://service1.syma...src=bar_sch_nam
WARNING! The above info in last link could (probably would) destroy the special HP code (I believe to exist there).
fyi (more or less accurate) - http://www.datarecov...ition_types.htm

Edited by submix8c, 03 April 2009 - 10:24 AM.

Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#36
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,568 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
@ahmad2080

Yes, we were cross-posting.

I'll have a look at the list.

Can you also check your "normal" partition for the presence of files MBRINST.EXE and MBRINST.INI, and if you find them detail where they are?

@submix8
The second link IS dangerous :w00t:, expecially beacuse it will make you edit the BOOT RECORD of the partition (read bootsector), that has nothing to do with the MBR.

PTEDIT is the DOS version.

PTEDIT32 is the Windows version.

There is a Freeware, beeblebrox, with most of the capabilities of PTEDIT32:
http://students.cs.byu.edu/~codyb/
(but that will leave bootsectors alone) ;)

jaclaz

#37
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

And I believe the HP Technician is wrong! Once you Restore from the Recovery Partition, you are back to Factory Install (just like when you bought it). I did this already on that HP/Compaq I told you about. Resets everything on the recovered OS partition! Therefore, the option to create disks reappears.

Maybe the file that says that the recovey disk creation has been execyted lies in the Recovery partition, so it'll be untouched even with a full recovery.

Your main problem seems to be (right now) getting booted into the Recovery Partition.

No, I can set my recovery partition as Active and when I restart I can begin the recovery process.My problem is to make the recovery disk creation software on Vista to see the recovery partition so I can make the recovery disks.

edit - and FWIW, if you used PM, then maybe you have PTEDIT (Partition Table Editor), although I don't know if it would help or not...
basic info on PTEDIT (now owned by Symantec) -
http://service1.syma...004063693751462
another tidbit (and ptedit download) -
http://service1.syma...src=bar_sch_nam
WARNING! The above info in last link could (probably would) destroy the special HP code (I believe to exist there).
fyi (more or less accurate) - http://www.datarecov...ition_types.htm

Thanks for the links but I can't trust symantec any more. It caused all of this trouble.

#38
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,568 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Thanks for the links but I can't trust symantec any more. It caused all of this trouble.


To be fair :rolleyes: , it was you that caused the trouble by using improperly a tool, no offence intended :) to you, rest assured, but the guys at Symantec are already busy enough attempting to add some more bloat in the Norton "line" of antivirii that they cannot actually produce some accurate documentation about Powerquest Norton Partition Magic, explaining to the less experienced user that it is a dangerous app if used improperly. :whistling:

jaclaz

#39
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

Can you also check your "normal" partition for the presence of files MBRINST.EXE and MBRINST.INI, and if you find them detail where they are?

No, they don't exist in the Normal partition(c:\).

When I said that I was able to log into the recovery partition I was wrong.
When I set the recovery partition as Active (or using F8) I do log into the recovery manager, but when I opened a cmd there I found that I was standing on [X:\WINDOWS\SYSTEM32]

Beside the X:\ partition (which is called the boot partition) there are C: & D: (My original partitions)

so the MBRinst.exe file that I showed you was from the boot partition not the recovery partition.
I don't know from where did the boot partition come from and what is its relation to the recovery partition, but I can list all of its contents [alot of .exe &.cmd files].

#40
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

Thanks for the links but I can't trust symantec any more. It caused all of this trouble.


To be fair :rolleyes: , it was you that caused the trouble by using improperly a tool, no offence intended :) to you, rest assured, but the guys at Symantec are already busy enough attempting to add some more bloat in the Norton "line" of antivirii that they cannot actually produce some accurate documentation about Powerquest Norton Partition Magic, explaining to the less experienced user that it is a dangerous app if used improperly. :whistling:

jaclaz

mmm, yeah that's fair. So you suggest to use the tool given by submix8c ?

EDIT: The tool that you gave me jaclaz : http://students.cs.byu.edu/~codyb/
is not comaptable with vista.

Edited by ahmad2080, 03 April 2009 - 11:23 AM.


#41
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,568 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

I don't know from where did the boot partition come from and what is its relation to the recovery partition, but I can list all of its contents [alot of .exe &.cmd files].


Yep, another DIR /S of that would be useful.

It's strange that noone reported this before, (I mean beeblebrox being incompatible with Vista), :unsure: maybe it must be run in some compatibility mode or whatever.

You can try using my MBRbatch, it should work under Vista too, though it's a bit cumbersome:
http://www.boot-land...?showtopic=3191
http://www.boot-land...?showtopic=5000

However, for the moment there is no need for a partition table editor, since we don't know WHAT to edit. ;)

jaclaz

#42
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09
Can MBRbatch really fix the whole problem?

EDIT: the DIR /s command on X:\ gave me a 1MB file (about 500 lines) which I can't Upload due to the 200 kb limitation.

Edited by ahmad2080, 03 April 2009 - 04:15 PM.


#43
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,902 posts
  • Joined 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Donator

Well let's look at the problem now. You've pulled off a full recovery. The original problem was you couldn't get to the recovery and couldn't make the discs. So now we are at the point where you need to make the discs? Or, wait you did say that you lost your function key after doing a recovery?

I want to make sure I understand exactly what is needed at this point. If you can get into the recovery partition, you do not need to use my steps at all.

I wanted to point out, the commands with mbr.exe, they refer to specific things. For example, let's take this:

mbr 0 1 /h

This is MBR (the program) and 0 (is the physical disk number) and 1 (is the partition number) and /h (means hide). Alternatively, there is an /uh which is unhide that could be used.

Now, if HP followed the Best Practices, the recovery partition would be the first partition, and the OS partition would be the second one. OK so I'm going to say if you want to do this step, you're going to need to do some diskpart action. For example:

List Disk
List Vol
List Part

these should give enough information.

As far as the CD burning deal. You execute this app from Windows. It obviously looks somewhere, like a file or a registry entry, to see if it made a CD before. ... I'm not sure if I should continue about that part of this thread...
MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg

#44
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

Well let's look at the problem now. You've pulled off a full recovery. The original problem was you couldn't get to the recovery and couldn't make the discs. So now we are at the point where you need to make the discs? Or, wait you did say that you lost your function key after doing a recovery?

I want to make sure I understand exactly what is needed at this point. If you can get into the recovery partition, you do not need to use my steps at all.

I'll restate everything to make sure everybody understands everything:
1-Everything works perfectly
2-Executed RecoveryDisk creation but didn't burn the dvds
3-Installed PM --> Recovery partition became invisible.
4-Installed HP tool --> Recovery partition became visible.
5-RecoveryDisk creation software doesn't work (The recovery partition could not be found) & the F11 function key became disabled.
6-Tried some programs to undo all of this.[Acronis,EasyBCD,MBRInst,..]With no +ve results.
7-Used F8(advanced boot loader) to apply a full system recovery, which was done perfectly except an error about MBR--> "MBR string is too long 30 bytes.It should be 16 bytes"
8-Tried the F11 function --> still doesn't work.
9-RecoveryDisk creation software still doesn't work (The recovery partition could not be found)

My condition now:
10-can perform a full sytem recovery using F8(advanced boot loader) then "Repair my computer" then "Recovery manager"
11- F11 at start up doesn't make the recovery manager begin ( as before in 1)
12-can't create recovery disks because of the error message (The recovery partition could not be found)

I think that both [11 &12] are related to the MBR. So if I could fix the MBR as it was before, the f11 will work & the SoftThinks software will see the partition as a recovery partition. [and that's all what I need]

NOTES:
-If fixing MBR fixed [11] and didn't fix [12] then the HP technican was right about the one-time execution, so I'll order the recovery disks.
-If fixing MBR fixed [12] and didn't fix [11] I'll be satisfied.
-If fixing MBR didn't fix anything -----> I GIVE UP.
-If fixing MBR made things worse.....I'll format the whole harddisk and install windows XP. :angry:

Tools that I have:
13- MBRInst.exe & DiskPart.exe & Patch.cmd &other .cmd &.exe files that exist in the boot partition.
14- can read any log file
15- can access any partition through cmd prompt in system recovery options [ from F8 & repair my computer]

I hope that this gives you all a pretty good picture on my current situation.

Edited by ahmad2080, 03 April 2009 - 03:18 PM.


#45
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

Now, if HP followed the Best Practices, the recovery partition would be the first partition, and the OS partition would be the second one. OK so I'm going to say if you want to do this step, you're going to need to do some diskpart action. For example:

List Disk
List Vol
List Part

these should give enough information.

Yes I need this step, I want to make the Recovery partition the first partition using Diskpart [Maybe this is what confused partition magic; it saw the OS partition as partition number 2 and it decided that it was an error in the partition table that it had to fix, which made the recovery partition dissapear. Is that a good thoery?]

I've attached a screenshot showing the List Disk ,List Vol & List Part commands on my notebook.

Attached File  diskpart.JPG   133.57KB   37 downloads

In the (List part) there is an offset field (what is offset?)showing 288GB for partition2 (recovery partition) Is that fine?

What's the next step?

Edited by ahmad2080, 03 April 2009 - 03:32 PM.


#46
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,568 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
The thing that I find strange is that the recovery partition was visible "from factory".

Usually, but really cannot say on HP laptops, and probably not all of them are the same, the Recovery partition is normally hidden and accessible only through the F11 or whatever hotkey while booting.

Most probably, as Tripredacus pointed out, in order for the MBRINST.EXE to work properly, the partition must be hidden before, possibly with the "stupid" 12 partition ID:
http://www.msfn.org/...o...08515&st=28
the (ab)use of 12 type partition dates back to Compaq:
http://www.win.tue.n...on_types-1.html

12 Configuration/diagnostics partition

ID 12 (decimal 18) is used by Compaq for their configuration utility partition. It is a FAT-compatible partition (about 6 MB) that boots into their utilities, and can be added to a LILO menu as if it were MS-DOS. (David C. Niemi) Stephen Collins reports a 12 MB partition with ID 12 on a Compaq 7330T. Tigran A. Aivazian reports a 40 MB partition with ID 12 on a 64 MB Compaq Proliant 1600. ID 12 is used by the Compaq Contura to denote its hibernation partition. (dan@fch.wimsey.bc.ca)

NCR has used ID 0x12 MS-DOS partitions for diagnostics and firmware support on their WorldMark systems since the mid-90s. DataLight's ROM-DOS has replaced MS-DOS on more recent systems. Partition sizes were once 72M (MS-DOS) but are now 40M (ROM-DOS).

Intel has begun offering ROM-DOS based "Service Partition" support on many OEM systems. This support initially used ID 0x98 but has recently changed to ID 0x12. Intel provides their own support for this partition in the form of a System Resource CD. Partition size has remained constant at 40M. See e.g. sds2.pdf. (Chuck Rouillard)

IBM also uses 0x12 for its Rescue and Recovery partition on Thinkpad laptops. See also thinkwiki.org.

for the record, Dell's use the even more "stupid" DE:
http://www.goodells....ility/index.htm

I guess that whether a partition type 12 is visible or hidden depends on the particular BIOS of the machine, MS and IBM (OS/2) have always considered partition types with a leading 1 to be the hidden version of the corresponding ones with a leading 0.


@ahmad2080
Upload the file to rapidshare or a similar file hosting and post the link.

Also, the contents of your (possibly more than one) MBRINST.INI might be of use.

jaclaz

#47
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

@ahmad2080
Upload the file to rapidshare or a similar file hosting and post the link.

Also, the contents of your (possibly more than one) MBRINST.INI might be of use.

jaclaz

I didn't understand most of your post. I'm not familiar with partition IDs.

Here is the result of DIR /s in (X:\) :

http://rapidshare.co.../booot.txt.html
This is the MBR.INI file in (X:\):
Attached File  MBR.INI   4.95KB   43 downloads

These are all MBR files that I could find in both partitions C & D :
MBR.INI in C:\system.sav\Util
MBR.ini in C:\ program Files\SMINST
MBRINST.VBS (Script file) in C:\system.sav\Util
MBRINST.BT_ in C:\system.sav\Util
MBEINST.LOG in C:\system.sav\Logs --> ( has only one line in it "MBRInst returned 0 " )
MBR.DLL in C:\Program Files

#48
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,327 posts
  • Joined 14-September 05
  • OS:none specified
  • Country: Country Flag
Info gathering here (in sequence)...

ahmad2080 -
When I said that I was able to log into the recovery partition I was wrong.
When I set the recovery partition as Active (or using F8) I do log into the recovery manager, but when I opened a cmd there I found that I was standing on [X:\WINDOWS\SYSTEM32]

Beside the X:\ partition (which is called the boot partition) there are C: & D: (My original partitions)
--
jaclaz -
However, for the moment there is no need for a partition table editor, since we don't know WHAT to edit.
------
ahmad2080 -
EDIT: the DIR /s command on X:\ gave me a 1MB file (about 500 lines) which I can't Upload due to the 200 kb limitation.
--
jaclaz -
Now, if HP followed the Best Practices, the recovery partition would be the first partition, and the OS partition would be the second one.
(...and - )
As far as the CD burning deal. You execute this app from Windows. It obviously looks somewhere, like a file or a registry entry, to see if it made a CD before.
--
ahmad2080 -
7-Used F8(advanced boot loader) to apply a full system recovery, which was done perfectly except an error about MBR--> "MBR string is too long 30 bytes.It should be 16 bytes"
8-Tried the F11 function --> still doesn't work.
9-RecoveryDisk creation software still doesn't work (The recovery partition could not be found)
My condition now:
10-can perform a full system recovery using F8(advanced boot loader) then "Repair my computer" then "Recovery manager"
(...and - )
I've attached a screenshot showing the List Disk ,List Vol & List Part commands on my notebook.
* note @ahmad2080 - correct, kind of (refer to jaclaz' stmt about "best paractices" - it's "reversed")
* note @jaclaz - remember the topic#=131023 about HDD offsets? sounds familiar...
+++++++++
(my comments as-of now...)
Now, it "appears" that -
1- Booting, as you say via F8 or Setting Active, looks suspiciously like Window PE, since you're seeing an "X" drive.
2- "Used F8(advanced boot loader) to apply a full system recovery" sounds more like Recovery Console (like in 2k/XP/2k3), not Recovery Partition. (?confused?)
3- HP apparently didn't follow the "best practices" (the one I worked with was an XP Home on Compaq, Recovery was FAT32, 1st one on HDD).
4- DO NOT actually edit the Partition Table. It was more a suggestion to see what the HexFlag value is. This is how you got here. A HexEditor that will take you to the FirstTrack would reveal much the same. DO NOT use one and actually edit.
5- "F11" function is gone because the MBR "HP Special Code" (not "standard") is gone. The same may/may-not be true of the PBR of the D-drive (as in my Compaq scenario - not "standard").
6- The "Create Disks" function must be looking for a particular value in the Partition Table (FirstTrack) and is not finding it (in addition to jaclaz' stmt about "registry"). The Compaq Recovery Partition was "hidden" with a special value. In addition, once disks were created, the Option was removed from the Start/Programs "list"; that is, until a Full System Restore was done (as I stated).
7- Finally - "MBR string is too long 30 bytes.It should be 16 bytes". This is extremely suspicious...

This post is strictly an info-gathering expedition and for confirmation purposes. It would sure be nice of HP if they would just reveal what that "special Partition HexValue" is.

Other members trying to help, you're up next... (sheesh!)

edit - ARG! turned an attempt to shorten the post (via codebox) baaad! changed to in-line single quotation (long but easier to read)...

Edited by submix8c, 04 April 2009 - 10:40 AM.

Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#49
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,568 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

I didn't understand most of your post. I'm not familiar with partition IDs.

In the MBR there are 4 (four) partition entries, each 16 (sixteen) bytes long.
In each of these entries, fifth byte is Partition ID.
See this:
http://mirror.href.c.../PartTables.htm
and the already linked to:
http://www.win.tue.n...on_types-1.html

Here is the result of DIR /s in (X:\) :
....
This is the MBR.INI file in (X:\):
....

Good. :)
Though I am still missing some info, maybe I overlooked it :unsure:

In your DISKPART report, you have two partitions:
the "main" one which gets letter C:\
and
the "recovery" one which gets letter D:\

Where does the X:\ come from?

Is it the letter that is given to the PE .WIM image that you boot when you choose the recovery partition?


These are all MBR files that I could find in both partitions C & D :
MBR.INI in C:\system.sav\Util
MBR.ini in C:\ program Files\SMINST
MBRINST.VBS (Script file) in C:\system.sav\Util
MBRINST.BT_ in C:\system.sav\Util
MBEINST.LOG in C:\system.sav\Logs --> ( has only one line in it "MBRInst returned 0 " )
MBR.DLL in C:\Program Files


Most probably you have set your system not to show executable files.
I would bet ;) that you probably have in
C:\system.sav\Util a MBRINST.EXE file
and as well and definitely one in
C:\ program Files\SMINST

Now, should this latter info be confirmed, you have a
C:\Program File\SMINST\MBRINST.EXE
and a
C:\Program File\SMINST\MBR.INI
this sounds very like the \SMINST\ path reported before:
http://www.msfn.org/...o...31620&st=24

Now, you posted the MBR.INI that you found in your X:\ drive, whatever it is, can you post also the one in C:\system.sav\Util\ and the one in C:\Program Files\SMINST\?

Unless they are all identical, of course.

I will also need a DIR /S of C:\system.sav\Util\ and a DIR /S of C:\Program Files\SMINST\

jaclaz

#50
ahmad2080

ahmad2080

    Member

  • Member
  • PipPip
  • 102 posts
  • Joined 27-March 09

Info gathering here (in sequence)...
(my comments as-of now...)
Now, it "appears" that -
1- Booting, as you say via F8 or Setting Active, looks suspiciously like Window PE, since you're seeing an "X" drive.
2- "Used F8(advanced boot loader) to apply a full system recovery" sounds more like Recovery Console (like in 2k/XP/2k3), not Recovery Partition. (?confused?)
7- Finally - "MBR string is too long 30 bytes.It should be 16 bytes". This is extremely suspicious
This post is strictly an info-gathering expedition and for confirmation purposes. It would sure be nice of HP if they would just reveal what that "special Partition HexValue" is.


The exact error message about MBR is : "Master Boot Record Strings too long! Your strings are 30 Bytes but the Master Boot Record has only 18 Bytes for strings"
It appeared again while I ran the PATCH.CMD file in X:\windows\system32

About the recovery from F8: F8 opens the advanced boot menu, then I choose "Repair My computer" which opens "system recovery options" which has some recovery tools (Startup Repair , System restore, command prompt,......and RECOVERY MANAGER). From the RECOVERY MANAGER I can perform a full recovery.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users