Jump to content











Photo
- - - - -

AIOboot how to fix PBR

usb aioboot windows 10

Best Answer alacran , 08 April 2019 - 07:19 PM

Well if BootIce can't help you it means your PBR info is damaged, then I think re partition/format is the safer option, hope you have all info to recreate your USB AIO device.

 

EDIT: Before making this post Raex contactected me by PM and I answered this to him:

 

 

Since there are several options you can select when you first create your AIO, I don't know what to suggest to you, since I don't know previous status.

 

But I have an idea, if you have another USB stick avalilable just partition/format it with AIO as you did before, then open it with BootIce and see what is your MBR and PBR, eject it and plug your problematic device and try to recreate what you deleted.

 

And this is today Post 15 from Raex

 

 

I took Alacran's advice and used another usb through aioboot and then got the pbr through it. I tried several times to recreate it through aioboot but idk why it never created successfully enough to boot at all. After I copied the pbr from the other usb it booted successfully.

 

NOTE: This post was edited to keep track of solution, since I assume Raex having a very low Post Count can't make any edit to the thread.

 

alacran

Go to the full post


  • Please log in to reply
18 replies to this topic

#1 Raex

Raex

    Newbie

  • Members
  • 16 posts
  •  
    United States

Posted 08 April 2019 - 05:01 PM

I somehow managed to mess up my AIOboot usb. Fortunately I was experimenting to see if I could get Sergei Strelec's grub4dos menu entry to show up in aioboot menu. Unfortunately while doing so I messed up the PBR for it. Unfortunately I had made the backup for MBR of my usb but not the PBR. Thus now I am unable to boot my usb in legacy mode. It keeps giving me grub error, no such media found. 

 

Downside, my usb still works in UEFI mode, but not in legacy mode. 

 

Reason I tried to mess with MBR/PBR was because sergei strelec wouldn't show me the rest of the options in uefi mode. It only booted the winpe whereas in legacy mode it showed me a grub2 menu listing the other entries it has. 



#2 alacran

alacran

    Silver Member

  • .script developer
  • 965 posts
  •  
    Mexico

Posted 08 April 2019 - 06:36 PM

Try to make new PBR using BootIce: http://reboot.pro/fi...-bootice-v1332/

 

alacran



#3 Raex

Raex

    Newbie

  • Members
  • 16 posts
  •  
    United States

Posted 08 April 2019 - 06:44 PM

How can I go about doing so without formatting the USB. Any help???



#4 alacran

alacran

    Silver Member

  • .script developer
  • 965 posts
  •  
    Mexico

Posted 08 April 2019 - 06:46 PM

Using BootIce as I suggested on my previous post you do not need to reformat/repartition your USB.



#5 Raex

Raex

    Newbie

  • Members
  • 16 posts
  •  
    United States

Posted 08 April 2019 - 06:54 PM

Using BootIce as I suggested on my previous post you do not need to reformat/repartition your USB.

 

Sent you a PM regarding it, I have no idea how to make a new PBR at all. That's what I was asking help for.



#6 alacran

alacran

    Silver Member

  • .script developer
  • 965 posts
  •  
    Mexico

Posted 08 April 2019 - 07:05 PM

I think the pictures are clear, just select what kind of MBR or PBR you want and Install/config.

Attached Thumbnails

  • AIO MBR.png
  • AIO PBR.png


#7 Raex

Raex

    Newbie

  • Members
  • 16 posts
  •  
    United States

Posted 08 April 2019 - 07:07 PM

I'm trying to do so but it gives me error. How I messed it up is when I tried to install the Grub4Dos as PBR and it didn't boot, then I tried to change it back to the BOOTMGR one, but it still gives me the grub error. 



#8 alacran

alacran

    Silver Member

  • .script developer
  • 965 posts
  •  
    Mexico

Posted 08 April 2019 - 07:19 PM   Best Answer

Well if BootIce can't help you it means your PBR info is damaged, then I think re partition/format is the safer option, hope you have all info to recreate your USB AIO device.

 

EDIT: Before making this post Raex contactected me by PM and I answered this to him:

 

 

Since there are several options you can select when you first create your AIO, I don't know what to suggest to you, since I don't know previous status.

 

But I have an idea, if you have another USB stick avalilable just partition/format it with AIO as you did before, then open it with BootIce and see what is your MBR and PBR, eject it and plug your problematic device and try to recreate what you deleted.

 

And this is today Post 15 from Raex

 

 

I took Alacran's advice and used another usb through aioboot and then got the pbr through it. I tried several times to recreate it through aioboot but idk why it never created successfully enough to boot at all. After I copied the pbr from the other usb it booted successfully.

 

NOTE: This post was edited to keep track of solution, since I assume Raex having a very low Post Count can't make any edit to the thread.

 

alacran


Edited by alacran, 15 April 2019 - 01:04 AM.


#9 alacran

alacran

    Silver Member

  • .script developer
  • 965 posts
  •  
    Mexico

Posted 08 April 2019 - 07:25 PM

Reason I tried to mess with MBR/PBR was because sergei strelec wouldn't show me the rest of the options in uefi mode. It only booted the winpe whereas in legacy mode it showed me a grub2 menu listing the other entries it has. 

 

Isn't it a grub4dos menu? If this is the case grub4dos can't boot anything on UEFI (secure boot) mode, it only works fine on Legacy mode, so nothing to fix then.



#10 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14778 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 09 April 2019 - 09:39 AM

Well if BootIce can't help you it means your PBR info is damaged, then I think re partition/format is the safer option, hope you have all info to recreate your USB AIO device.

Safer?

 

It is a PBR, not brain surgery or rocket science, it can be fixed just fine if needed, it is not like BootIce (which is an excellent tool) is the only and ultimate PBR recovery tool.

 

Out of curiosity, if your car doesn't start in the morning, do you check the battery and starter motor connections first or do you directly remove the engine and fit in a new one? :dubbio:

 

:duff:

Wonko



#11 Raex

Raex

    Newbie

  • Members
  • 16 posts
  •  
    United States

Posted 09 April 2019 - 01:47 PM

Safer?

 

It is a PBR, not brain surgery or rocket science, it can be fixed just fine if needed, it is not like BootIce (which is an excellent tool) is the only and ultimate PBR recovery tool.

 

Out of curiosity, if your car doesn't start in the morning, do you check the battery and starter motor connections first or do you directly remove the engine and fit in a new one? :dubbio:

 

:duff:

Wonko

Lmao, well considering when you go out in outer space, and there's a new entity in front of you whom you know nothing about, are you gonna say hi to it first or start attacking at it. Lol in short, when you have lesser knowledge people are bound to do what they can think of at that moment, wouldn't you agree to it?

 

Isn't it a grub4dos menu? If this is the case grub4dos can't boot anything on UEFI (secure boot) mode, it only works fine on Legacy mode, so nothing to fix then.

Yes it's grub4dos menu, and damn that really sucks right there. I was hoping to convert the menu to grub2 but had little to no success. Anyways I'll just leave sergei alone perhaps. 



#12 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14778 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 09 April 2019 - 04:45 PM

Lmao, well considering when you go out in outer space, and there's a new entity in front of you whom you know nothing about, are you gonna say hi to it first or start attacking at it. 

I don't know, probably I would have already seen that entity coming ;) thus having the time to post on the NASA board :w00t: for advice.

 

The point is that I would be expecting that those actually familiar with outer space had some actual solutions to the problem at hand, not a generic "If the Apollo entity-recognition software didn't recognize that entity it is safer to nuke him/her/it and everything else in two-three light-years range around it :ph34r: ". 

 

Now, seriously, a PBR can usually be re-built just fine, particularly in your case most probably the BPB (Bios Parameter Block) is just fine as you can access the files on that volume, so it is a matter of making sure of this and then use a simpler tool to write to it "standard" code, such as bootsect.exe can do with either the /NT52 or /NT60 switches.

At this point the PBR should normally be valid and BootIce would recognize it and allow you to further change it to some other code.

 

If you want you can dump your current PBR (and being a FAT32 some more sectors), upload it to any free hosting site and post a link to it and I'll have a look, only to make sure that the data is valid.

I would need the MBR (to check data in the partition table is coherent with the BPB data) and the PBR+15 sectors.

 

You can use the HDhacker to dump the data:

http://dimio.altervi...g/eng/#HDHacker

 

You want first sector of the Physicaldrive (save to mynicembr.bin) and first 16 sectors of the Logicaldrive (save to mybadbadpbr.bin).

Then make a zip or 7z archive, upload to *somewhere* and post a link.

 

Is it safe? :dubbio:

https://www.imdb.com...uotes/qt0247572

 

:duff:

Wonko



#13 alacran

alacran

    Silver Member

  • .script developer
  • 965 posts
  •  
    Mexico

Posted 10 April 2019 - 05:55 AM

Here we are talking of an AIO USB stick with some tools installed by means of AIO Boot (wich by the way I translated to Spanish), the program makes all partitioning and formating required, also installs MBR/PBR as required (several options are available) according with your options selected.   Then BCDs, grub2 files and config files, and grub4dos files and menu.lst files are involved as boot options and you can go from one menu to the other or back to previous menu, of course the program give you easy options available to edit those menus, config files and BCDs.

 

So this is not the main internal HD having problems that of course deserves all possible efforts to recover the valuable info into it (if you don't have backups).

 

I have a 16 GB AIO Boot USB for my use and also had problems trying to make it do some more extra things than the available options particularly with VHDs in my case, and I was able to fix the problems once or twice.

 

But also have found that many times you waist more time and effort to fix something than if you just format and start from a clean install.

 

And yes after 10 or maybe 15 minutes trying to fix something on the OS, if I can't find the software source of the problem I do the same with my OSs partitions redeploying my backup.wim(s), as all documents, games, additional programs, Portables, etc. are on another partition and also have backups of them just in case.

 

So it is a matter of being practical and do not expend unnecessary time and resources on something that can be easily solved just by remaking it from the beginning (or from backup if any).

 

alacran


  • Raex likes this

#14 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14778 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 10 April 2019 - 08:46 AM

I know :), but what you are saying now (correctly BTW :thumbsup: ) it is that nuking the whole stuff and start again from scratch can be (in this specific case of a device with contents created by an automated program and not later modified) faster/more practical/easier/more productive/requiring less effort, which has nothing to do with the approach being "safer".

 

The alternative in the case of a PBR it is pretty much binary, you either (manually with a hex editor or with the help of dedicated tools) fix it (and if it is fixed it is fixed) or you don't.

 

Besides, and with all due respect both to you and to the OP, the idea of running again the AIOboot and recreate the thingy ex novo is pretty much obvious, I assumed that the OP (for whatever reasons) didn't want to re-run the AIOboot because he wanted to keep some of the modifications he already made, and then asked for support.

 

:duff:

Wonko



#15 Raex

Raex

    Newbie

  • Members
  • 16 posts
  •  
    United States

Posted 14 April 2019 - 11:21 PM

Woah, sorry I did not actually got the notifications from this thread again somehow, idk why. Anyways I took Alacran's advice and used another usb through aioboot and then got the pbr through it. I tried several times to recreate it through aioboot but idk why it never created successfully enough to boot at all. After I copied the pbr from the other usb it booted successfully. 



#16 alacran

alacran

    Silver Member

  • .script developer
  • 965 posts
  •  
    Mexico

Posted 15 April 2019 - 12:53 AM

Then you finally followed the advice from the Private Messenger and made another AIO Boot stick and used it to recreate your damaged PBR.

 

I'm going to edit my post here where you said was the right answer to make it clear for future readers how it was finally solved, since I assume you having so small Post Count can't make any editions yet, thanks for informing us how it was solved.

 

alacran



#17 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14778 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 April 2019 - 08:51 AM

So after all the PBR was "fixed" (and the stick was not "nuked"), good :).

:duff:
Wonko

#18 Raex

Raex

    Newbie

  • Members
  • 16 posts
  •  
    United States

Posted 15 April 2019 - 09:31 AM

Thanks Alacran, and I actually have some posts left still so I can make the edits. 

 

I just had to extract the PBR from other usb and then import it back to the one which was damaged. As soon as I did that it accepted it and I got the boot menu. I had to add the entries manually though since it had none, because I never loaded the OSes on the other usb and thus had to manually create the entries for individual stuff I had. It was a little tricky but I managed to do that, for the guid I just copied them from the MBR. 

 

Also, thanks Wonko, lol yeah it wasn't nuked and I got it fixed eventually haha. 

 

-Raex



#19 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14778 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 April 2019 - 10:59 AM

As a side-side note (and as a word of warning for the casual passer-by) this worked in this case ONLY because of EITHER:
1) the second stick being identical to the first one
2) the partition/volume at hand was the ESP (or whatever) that AIOBOOT always creates with the same size and at the same offset on *any* stick
AND:
3) the volume serial number (or the hash/checksum of the bootsector) or the UUID isn't used (actually perused) by any program/distro/whatever on the stick
or - if you prefer - it is not generally possible to "transplant" a bootsector from one device to another without "adapting" the BPB and the volume serial[1].

:duff:
Wonko

[1] the volume serial is actually rarely used, and I don't want to seem more royalist than the king, but you never know, and it costs nothing (or nearly nothing) to do things as eailproof as possible.
  • Raex likes this





Also tagged with one or more of these keywords: usb, aioboot, windows 10

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users