PDA

View Full Version : [all variants] [Boot-Repair] Graphical tool to repair the PC boot in one click



Pages : [1] 2 3 4 5 6 7 8 9 10

YannBuntu
May 28th, 2011, 08:18 AM
If you want help reviewing your summary report from Boot-Repair, post new thread with link to pastebin.
http://ubuntuforums.org/newthread.php?do=newthread&f=333

"Boot-Repair" is a small graphical tool to repair frequent boot problems.

- repair the boot when an OS does not boot any more after installing Ubuntu
- repair the boot when access to GRUB and any OS is lost (maybe due to a Windows software that wrote into the MBR gap (https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/441941), or a OEM MBR lock),
- reinstall GRUB bootloader easily
- create a Boot Info Summary in 1 click !
- restore a generic bootsector (MBR), or the original MBR if it has been saved by Clean-Ubiquity (https://launchpad.net/clean-ubiquity)

http://pix.toile-libre.org/upload/img/1315191717.png (http://pix.toile-libre.org/?img=1315191717.png)

Get a CD including Boot-Repair:
- Boot-Repair-Disk (https://sourceforge.net/projects/boot-repair-cd/files/) is a CD that automatically runs Boot-Repair at start-up.
- or: Boot-Repair is also included in all Linux Secure disks (https://sourceforge.net/p/linux-secure).

Install and run Boot-Repair in Ubuntu (in case you can't burn a CD):
just type in a Terminal:


sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && (boot-repair &)

Boot-Repair can be installed & used from any Ubuntu session (normal session, or live-CD, or live-USB).
PPA packages are available for Ubuntu versions precise(12.04LTS), trusty(14.04LTS), utopic(14.10), vivid(15.04).

Use Boot-repair:
Launch it from System->Administration->Boot-Repair menu if you use Gnome, or search "boot" in the dash if you use Unity. Then follow the menus...

You can contribute by :
- translating (https://translations.launchpad.net/boot-repair/trunk) (now ~60 languages)
- voting on Launchpad for these bugs: 1st (https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/806291), 2nd (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/747279), 3rd (https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/653474), 4th (https://bugs.launchpad.net/os-uninstaller/+bug/823152)
- suggesting improvements

If you want help reviewing your summary report from Boot-Repair, post new thread with link to pastebin.
http://ubuntuforums.org/newthread.php?do=newthread&f=333

drs305
May 28th, 2011, 11:45 AM
Thank you. I haven't tried all Boot Repair's capabilities yet but it is a welcome addition to the slowly growing list of helpful Grub 2 graphical apps.

TheGrave
May 28th, 2011, 10:59 PM
Great stuff, thanks a lot! I assume that the latest version is included in the Ubuntu Secure 11.04:

http://ubuntuforums.org/showpost.php?p=10084551&postcount=1

Is this ISO for x64 or i386? I messed up my x64 server at home and now I have to send somebody that hasn't seen Linux in his life to repair it. The GUI will definitely decrease the process length in terms of hours. I upgraded from 10.10 to 11.04 and got the grub_env_export error. Now, as I think of it again, maybe I did the stupidity to install grub in the partition itself instead in the MBR (used to be in the MBR with 10.10). This situation should be corrected with your tool, right?

I reinstalled grub using method 1 in the past without an issue:

https://help.ubuntu.com/community/Grub2#Reinstalling%20from%20LiveCD

I'm still not sure if the chroot method is necessary in my case. Any idea?

YannBuntu
May 29th, 2011, 03:27 AM
Thank you for your encouragements :)

If the GRUB you want to repair is located in a 64bits distribution, you need to install & use Boot-Repair from a 64 bit distribution.

As the "Ubuntu Secured" ISO are all 32bits ISO, just use any normal 64bits *Ubuntu CD, install Boot-Repair on it, and use it to repair your 64 bit distro GRUB.

manickaselvam
May 30th, 2011, 06:30 AM
Hi YannBuntu (http://ubuntuforums.org/member.php?u=485559), Trying to download "Boot-repair" but with very little success. Can you please enlighten me? I'm stuck with "grub rescue>" after upgrading from Karmic to Natty!! (Along with Win7).

YannBuntu
May 30th, 2011, 10:15 AM
Hi manickaselvam,

I understand from your message that your PC does not give access to any OS (nor Windows, nor Ubuntu) any more, I am right ?

If that is the case, you will need to :

FIRST STEP
either:
- if your broken Ubuntu was 32bits, get a Ubuntu 32bits CD, or better : Ubuntu Secured CD (http://ubuntuforums.org/showpost.php?p=10084551&postcount=1) (32 bits)
- if the broken Ubuntu was 64 bits, get a Ubuntu 64bits CD, or better : Ubuntu Secured 64 bits CD (http://ubuntuforums.org/showpost.php?p=10084551&postcount=1)
and burn it on a CD from another computer.

SECOND STEP
Then, when you have this CD, put it into your computer's CD driver, boot your PC on it, choose "Try Ubuntu" at first screen, there a "live-session" (Ubuntu desktop running on RAM) will appear.

THIRD STEP
From this "live-session" :
- If you are using a Ubuntu Secured CD, Boot-repair is already installed into it.
- If you are using a standard version of Ubuntu, Download/Install Boot-Repair in it by either : add ‘ppa:yannubuntu/boot-repair’ to your Software Sources via the Software Centre or by typing the 2 following commands in a Terminal session:
* sudo add-apt-repository ppa:yannubuntu/boot-repair
* sudo apt-get update && sudo apt-get install boot-repair-ubuntu

FOURTH STEP
From the "live-session" :
Search Boot-Repair in the Applications menu, and run it with default options (this will reinstall GRUB in sda), except if your BIOS is configured to boot on another disk.
Then shutdown your PC, remove the CD, and reboot the PC to check if it worked. :)

If it did not work, please open a new thread HERE (http://ubuntuforums.org/newthread.php?do=newthread&f=333) (describe exactly what you did and what happened when upgrading from Karmic to Natty, your hardware description, and the output result of the bootinfoscript (http://ubuntuforums.org/showpost.php?p=8104352&postcount=1)), and then give us the link here so that we can follow the discussion.

TheGrave
May 30th, 2011, 06:30 PM
My mother became a Linux admin with 5 hours of tutoring over the phone and a million commands sent via SMSes. She managed to reinstall GRUB using the CHROOT method \\:D/ Next thing I know she is preparing for RHCE :D I didn't have to use your tool but I'm very willing to see it in the next installer. Making a backup of the MBR is a great feature that HAS to be in Ubuntu. First time I installed it on the same drive with Windows I got totally f*cked up because I didn't reboot in Windows after resizing its partition and it took me a few days to find the right tool to restore it. From now on - Windows only on VMWare Player!

Anyway, I just wanted to say thanks for writing this great tool and I hope it gets approved for the next release installer. Is it able to perform the CHROOT method as well by the way? Should be just a few extra lines of code.

YannBuntu
May 31st, 2011, 01:14 AM
Hello TheGrave, thank for your encouragements ! :)
I agree with you that Ubuntu should backup the MBR, like many other Linux distro already do since a long time.
Yes Boot-Repair uses the chroot method by default, except when it cannot (when you reinstall the GRUB that is on the system currently in use).

@all : if you also want the MBR to be automatically saved when installing Ubuntu, please vote (login, "Does this bug affect you? -> Yes) for this inclusion request : https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/747279

drs305
May 31st, 2011, 02:06 AM
@all : if you also want the MBR to be automatically saved when installing Ubuntu, please vote (login, "Does this bug affect you? -> Yes) for this inclusion request : https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/747279

I know the Grub devs have discussed this and some want to automatically create a backup, so they are aware of the issue. I don't know the status of that option, so keep those 'bug' requests coming.

YannBuntu
May 31st, 2011, 03:31 AM
Indeed, I proposed it a long time ago (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/633064) (you can vote for this one too ;) )

Important : just saving the MBR would be a first improvement, but Clean-Ubiquity (https://launchpad.net/~yannubuntu/+archive/clean-ubiquity/) does better : when Clean-Ubiquity saves the MBR, it also links (via UUID) the backup to the Linux installation that erased the MBR, so that the OS-Uninstaller (https://launchpad.net/~yannubuntu/+archive/os-uninstaller) tool can work.

heepie
June 1st, 2011, 09:48 PM
How do you get the menu from the first screenshot on top of the thread? When I launch the boot-repair I only get the second screenshot without any visible option to change...

I'm trying to restore my windows loader. I made a fresh install of Ubuntu, the Windows menu option is the grub menu at startup but when selected I get a blank screen with the cursor waiting on the top left and nothing else happens.

I've tried running boot-repair but it doesn't seem to fix the problem, that's why I'm asking for the option to go to the first screenshot menu option of boot-repair.

Thank you

YannBuntu
June 2nd, 2011, 12:52 AM
Hi Heepie,

The full window below appears only if Boot-Repair detects Clean-Ubiquity MBR backups (https://launchpad.net/~yannubuntu/+archive/clean-ubiquity) (e.g. the 1st time you installed Ubuntu was via the Ubuntu Secured Remix (http://ubuntuforums.org/showthread.php?t=1615667), not a standard Ubuntu CD) on your computer.

http://pix.toile-libre.org/upload/img/1299426403.png (http://pix.toile-libre.org/?img=1299426403.png)

If Boot-Repair does not detect any Clean-Ubiquity MBR backup (e.g. the 1st time you installed Ubuntu was via a standard Ubuntu CD, so that your disk MBR has been erased by GRUB ), Boot-repair will only propose you to reinstall GRUB :

http://pix.toile-libre.org/upload/img/1306401412.png (http://pix.toile-libre.org/?img=1306401412.png)

So you are in the 2nd case (no Clean-Ubiquity backup detected). You can first try to reinstall GRUB. If this does not fix your problem, try to purge GRUB (via Advanced Options). If you still get the problem, here are Recovery disks to restore Windows boot: for 7 (http://neosmart.net/blog/2009/windows-7-system-repair-discs/), Vista (http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/) and XP (http://www.vista-xp.fr/forum/topic240.html). These tools repair more than the MBR, so after using them try again to reinstall GRUB. If you get access to both Windows and Ubuntu, that's perfect. If not, use the Recovery disk again, but unfortunately you will have access only to Windows, so please open a new thread in this forum (http://ubuntuforums.org/forumdisplay.php?f=333) explaining in detail what you did and observe, and give me the link here so that I can try help.

YannBuntu
June 2nd, 2011, 12:58 AM
@manickaselvam and all 64bits users : I just finished creating Ubuntu Secured 11.04 64 bits (http://ubuntuforums.org/showpost.php?p=10084551&postcount=1).
So if you need to repair a 64 bits system, just burn this CD, you will find Boot-Repair directly in it !

(I modify the post #1 and #6 of this thread).

heepie
June 2nd, 2011, 07:16 AM
Thank you for you quick reply. You send me toward the right direction.

I fixed the problem by doing:

1.- Restoring Window 7 bootloader by following this (http://ubuntuforums.org/showthread.php?t=1014708)

2.- And then Reinstalling Grub 2 from LiveCD by following the "SIMPLEST - Copy LiveCD Files" option from here (https://help.ubuntu.com/community/Grub2#SIMPLEST - Copy LiveCD Files)

Problem solved.

I also found this very useful:


Grub 2 Basics (http://ubuntuforums.org/showthread.php?t=1195275)
How to fix Vista/Window 7 when the boot files are missing (http://ubuntuforums.org/showpost.php?p=5726832&postcount=4)
boot_info_script.sh (http://sourceforge.net/projects/bootinfoscript/)

YannBuntu
June 2nd, 2011, 09:36 AM
Happy this helped :)

FYI, using Windows Recovery CD, then reinstalling GRUB via Boot-Repair, would have given the same result but would have been faster and easier ! (just keep in mind for next time Windows breaks ;) )

YannBuntu
June 2nd, 2011, 01:26 PM
Just created a documentation in the Ubuntu wiki : https://help.ubuntu.com/community/Boot-Repair

Thanks Martin ;)

YannBuntu
June 7th, 2011, 12:30 PM
Thanks Chriske for your message. I am glad to see that Boot-repair is useful to people :)

efincoop
June 12th, 2011, 10:08 PM
I am trying to set up a desktop to dual boot Unbuntu & Windows 7 premium. I have tried 3 times now without success. Windows 7 was on the desktop first, then I have tried installing Ubuntu 10.10 & 11.04. In either case once I install Ubuntu the desktop boots straight to Ubuntu and never shows the grub menu. I can download & install the startup manager tool, change the boot preference to Windows, but then I can only boot Windows, I have even trued EasyBCD with no luck.

Do you think you tool can help resolve my issue?

YannBuntu
June 13th, 2011, 03:16 AM
Hi Efincoop,

If Startup-manager proposes Windows in the entries, that means that GRUB is correctly installed and detects Windows. So reinstalling GRUB via Boot-Repair won't be useful.
It may be just a problem of "hidden" GRUB, or else GRUB display duration is set on GRUB_TIMEOUT=0. You can try to display GRUB at your computer start by keeping "Shift" key pressed. Also, please copy-paste here the content of your /etc/default/grub file .
e.g. mine is :

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=2
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

ProNux
June 14th, 2011, 01:15 PM
The instruction worked for me. Here's my history.

1. I have a dual boot PC - Win7 and Ubuntu Natty.

2. I boot at Windows and "enabled" or use my last partition of hard disk to save some of my data.

3. I restart and Grub won't show up.

Why not include this Boot-Repair utility by default in the future Ubuntu releases? Just a suggestion.

YannBuntu
June 14th, 2011, 02:33 PM
Magandang gabi Pronux :D


I boot at Windows and "enabled" or use my last partition of hard disk to save some of my data.

Just for my information, please can you send me (yannubuntu ATT gmail DOTT com) screenshots of how you "enable" your partition ?


Why not include this Boot-Repair utility by default in the future Ubuntu releases?

First it should be translated in main languages. Could you help with tagalog please? (online (https://translations.launchpad.net/boot-repair) or via a po file that you send me by email (https://sourceforge.net/projects/os-uninstaller/files/po.tar.gz/download) )


@all: of course anyone can help by translating !
:)

martini1179
June 17th, 2011, 01:40 AM
I take it that Boot-Repair doesn't work with legacy GRUB? I need to install Windows 7, but I have been updating Ubuntu on this drive since Jaunty and still have legacy GRUB.

YannBuntu
June 17th, 2011, 04:17 PM
Hi martini1179,
Boot-Repair should work also with GRUB Legacy. :D
Remark : the "purge" option uninstalls GRUB (grub grub-pc and grub-common) packages, and reinstalls grub-pc.

NuB4Life
June 24th, 2011, 03:42 PM
THANK YOU!!!

This was even easier than it looked like it was going to be!:D

Manbeardo
June 26th, 2011, 11:52 PM
Thanks for the tool; it works great! One bit of feedback: the forum post contains instructions for installing boot-repair from the terminal, but the wiki page does not. It would be helpful to add that information to the wiki page. Thanks!

YannBuntu
June 27th, 2011, 12:29 PM
Thanks for your comments ! I am happy Boot-Repair helps people :D

@Manbeardo : installation instructions are in the wiki https://help.ubuntu.com/community/Boot-Repair

Bucky Ball
July 5th, 2011, 07:44 PM
Boot-repair rocks. I installed 11.04 and it installed its grub over the 10.10 grub I was using. I wanted 10.10 to be in control. Boot-repair fixed this in a jiffy. It should be in the repos.

Cheers YannBuntu, great stuff. ;)

YannBuntu
July 6th, 2011, 04:00 AM
Thanks. You are right. I created an inclusion request.

@all: if you like Boot-Repair, you can vote on Launchpad to ask its inclusion in Ubuntu's repositories : https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/806291
So that it will be much easier to install it.. :guitar:

Bucky Ball
July 6th, 2011, 05:09 AM
I have left a comment there and will be burning a CD version of Boot-repair today to keep in my digital tool-kit. Thanks again. ;)

YannBuntu
July 6th, 2011, 05:16 AM
Thanks. To vote for inclusion, login to Launchpad, then on https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/806291 click on "Does this bug affect you?" and choose Yes. :)

Luke M
July 6th, 2011, 06:20 AM
Good work. This stuff should be added to the standard release.I used boot-repair to make a partition bootable (using "force" option). Worked fine.If it could convert a logical partition to a primary partition (I did this manually :-)), that would be magic.

YannBuntu
July 6th, 2011, 12:13 PM
Hi Luke,
Sorry I don't have such "super-powers" :D but next Boot-repair release (which is in alpha stage now) will get new options.. keep in touch ...

(just for my information) you mean you installed GRUB in the partition of your Ubuntu, in order to chainload it from another bootloader ?

Boot-Repair is already included in several derivatives of Ubuntu : Linux Hybryde, Voyager OS ... if you need a Ubuntu CD with Boot-Repair, I recommand you use Ubuntu Secured (http://ubuntuforums.org/showthread.php?t=1615667) (which is simply Ubuntu + 3 little tools including Boot-Repair) :)

Luke M
July 6th, 2011, 12:47 PM
Hi Luke,
Sorry I don't have such "super-powers" :D but next Boot-repair release (which is in alpha stage now) will get new options.. keep in touch ...

(just for my information) you mean you installed GRUB in the partition of your Ubuntu, in order to chainload it from another bootloader ?

Boot-Repair is already included in several derivatives of Ubuntu : Linux Hybryde, Voyager OS ... if you need a Ubuntu CD with Boot-Repair, I recommand you use Ubuntu Secured (http://ubuntuforums.org/showthread.php?t=1615667) (which is simply Ubuntu + 3 little tools including Boot-Repair) :)

Yes. The ubuntu install did not give me grub, even though I used the proper option. It was a logical partition, could that be why it didn't install? Logical partitions are not normally bootable (with standard MBR code), but they could be bootable using some other tools.

YannBuntu
July 6th, 2011, 01:28 PM
Normally GRUB should have detected your OS even on a logical partition. If not, this is a bug that you should report to GRUB developpers.
For my information, which other bootloader did you use to chainload GRUB ?

Luke M
July 6th, 2011, 02:15 PM
Normally GRUB should have detected your OS even on a logical partition. If not, this is a bug that you should report to GRUB developpers.
For my information, which other bootloader did you use to chainload GRUB ?

Plop boot manager. Alternatively, with the partition as primary I can boot direct with standard MBR. I prefer to have everything inside the partition.

YannBuntu
July 6th, 2011, 02:28 PM
ok, thanks.

YannBuntu
July 20th, 2011, 02:44 AM
Quick preview of next Boot-Repair's release :

The welcome menu:
http://pix.toile-libre.org/upload/img/1311126070.png (http://pix.toile-libre.org/?img=1311126070.png)

The Advanced options:
http://pix.toile-libre.org/upload/img/1311126144.png (http://pix.toile-libre.org/?img=1311126144.png)

Please contact me if you want to participate to tests, or help translating in your language.

JASONFUSARO
July 22nd, 2011, 03:05 PM
Just installed it and ran it to check it out but I got this

There is no boot backup on this computer.
This will reinstall GRUB bootloader.
Do you want to continue?


and I chose not to continue, because I am not sure what the next screen would be or what would take place, if it would create an environment that no longer worked, that has been working.


What would have happened had I chose to continue???



Thank you

YannBuntu
July 22nd, 2011, 03:25 PM
If you choose to continue, the window to reinstall GRUB will appear:

http://pix.toile-libre.org/upload/original/1306401412.png

Luke M
July 22nd, 2011, 05:38 PM
Does boot-repair create a directory named clean? Assuming the answer is yes, I don't like the fact that it wrote to a non-installation partition, and also used a filename which is illegal in Windows (contains a colon) - so it can't be viewed or deleted. Is this intentional or a bug?

Bucky Ball
July 22nd, 2011, 09:07 PM
... I don't like the fact that it wrote to a non-installation partition, and also used a filename which is illegal in Windows (contains a colon) - so it can't be viewed or deleted. Is this intentional or a bug?

Haha. Computers are foolproof but there's no proof against fools. Best read the instructions ... :)

JASONFUSARO
July 22nd, 2011, 10:31 PM
If you choose to continue, the window to reinstall GRUB will appear:

http://pix.toile-libre.org/upload/original/1306401412.png


I selected it and got

Screenshot1 and when I selected install I ended up with the second screenshot which said everything was succesful but if you look at the third screenshot there is nothing in grub.cfg absolutely empty!!!


What happened??

And what will happen when I reboot???

JASONFUSARO
July 22nd, 2011, 10:40 PM
Should I have made a backup first??

YannBuntu
July 23rd, 2011, 03:34 AM
Hello

@Luke : good remark. Yes Boot-Repair creates a /clean folder in all OSs partitions. It contains logs and MBR backups, so I strongly suggest you don't remove it. The /clean folder is duplicated in all OSs partitions for security purpose. If really you want to remove it, you can do it from a live-CD or from your Ubuntu.

@JASONFUSARO : on your first attached screenshot, we can see that no OS was selected at the right side of "OS to boot by default" line. This probably means that os-prober did not detect any Linux on your computer. Please can you send me by email (yannubuntu att gmail dott com) a ZIP of your /var/log/clean folder ? (so that I can understand your situation and help you better)

JASONFUSARO
July 23rd, 2011, 07:11 PM
Hello

@Luke : good remark. Yes Boot-Repair creates a /clean folder in all OSs partitions. It contains logs and MBR backups, so I strongly suggest you don't remove it. The /clean folder is duplicated in all OSs partitions for security purpose. If really you want to remove it, you can do it from a live-CD or from your Ubuntu.

@JASONFUSARO : on your first attached screenshot, we can see that no OS was selected at the right side of "OS to boot by default" line. This probably means that os-prober did not detect any Linux on your computer. Please can you send me by email (yannubuntu att gmail dott com) a ZIP of your /var/log/clean folder ? (so that I can understand your situation and help you better)



If you look closely I selected sda6 in the lower area and that folder does not exist, although I am looking in sda6 (UbuntuStudio64)

Now if you look at the second screenshot there is a clean folder but that is in my Toorox which is on sda10 (TooroxGnome64) but when I ran the Boot Repair I was running UbuntuStudio


The last Screenshot is my current partiton scheme






EDIT**
can you please explain:
After solving a problem in the forum, don't forget to improve the Wiki !

YannBuntu
July 23rd, 2011, 07:50 PM
Thank you Jason. According to the log, "os-prober" did not detect any OS. You can check if it is still the case by typing the following command, which should list your systems:

sudo os-prober

If you have time I would be happy if you could test next Boot-Repair's release which is nearly finished. (now v3 beta). I see you have a splendid multi-boot, so your feedback is very interesting :)

To install Boot-repair v3 beta:

sudo add-apt-repository ppa:yannubuntu/boot-repair-dev && sudo add-apt-repository ppa:yannubuntu/os-uninstaller-dev && sudo apt-get update && sudo apt-get remove -y boot-repair-ubuntu boot-repair clean-ubiquity-common boot-repair-common os-uninstaller os-uninstaller-ubuntu && sudo apt-get install -y boot-repair os-uninstaller

(this also installs OS-Uninstaller v3 beta)

To come back to Boot-Repair v2 stable:

sudo add-apt-repository --remove ppa:yannubuntu/boot-repair-dev && sudo add-apt-repository --remove ppa:yannubuntu/os-uninstaller-dev && sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo add-apt-repository ppa:yannubuntu/os-uninstaller && sudo apt-get update && sudo apt-get remove -y boot-repair-ubuntu boot-repair clean-ubiquity-common boot-repair-common os-uninstaller os-uninstaller-ubuntu && sudo apt-get update && sudo apt-get install -y boot-repair-ubuntu os-uninstaller-ubuntu

Remark : before any test, be sure you have :
- a backup of your data (as usual ;) )
- a live-CD or live-USB of Ubuntu Secured (http://ubuntuforums.org/showthread.php?t=1615667), so you can easily reinstall GRUB.

JASONFUSARO
July 23rd, 2011, 08:26 PM
Thank you Jason. According to the log, "os-prober" did not detect any OS. You can check if it is still the case by typing the following command, which should list your systems:

sudo os-proberIf you have time I would be happy if you could test next Boot-Repair's release which is nearly finished. (now v3 beta). I see you have a splendid multi-boot, so your feedback is very interesting :)

To install Boot-repair v3 beta:

sudo add-apt-repository ppa:yannubuntu/boot-repair-dev && sudo add-apt-repository ppa:yannubuntu/os-uninstaller-dev && sudo apt-get update && sudo apt-get install -y boot-repair-ubuntu boot-repair clean-ubiquity-common boot-repair-common os-uninstaller os-uninstaller-ubuntu(this also installs OS-Uninstaller v3 beta)

To come back to Boot-Repair v2 stable:

sudo add-apt-repository --remove ppa:yannubuntu/boot-repair-dev && sudo add-apt-repository --remove ppa:yannubuntu/os-uninstaller-dev && sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo add-apt-repository ppa:yannubuntu/os-uninstaller && sudo apt-get update && sudo apt-get remove -y boot-repair-ubuntu boot-repair clean-ubiquity-common boot-repair-common os-uninstaller os-uninstaller-ubuntu && sudo apt-get update && sudo apt-get install -y boot-repair-ubuntu boot-repair clean-ubiquity-common os-uninstaller os-uninstaller-ubuntuRemark : before any test, be sure you have :
- a backup of your data (as usual ;) )
- a live-CD or live-USB of Ubuntu Secured (http://ubuntuforums.org/showthread.php?t=1615667), so you can easily reinstall GRUB.




jason@UbuntuStudio64bit:~$ sudo os-prober
[sudo] password for jason:
/dev/sda1:Windows Vista (loader):Windows:chain
/dev/sda10:Gentoo Base System release 2.0.2:Gentoo:linux
/dev/sda11:unknown Linux distribution:Linux:linux
/dev/sda12:Zorin OS 5 (11.04):Ubuntu:linux
/dev/sda15:Slackware Linux (Slackware 13.37.0):Slackware:linux
/dev/sda5:Chakra Linux (2011.04_20110521-1):Chakra:linux
/dev/sda7::Arch:linux
/dev/sda8::Arch1:linux
/dev/sda9:Ubuntu 10.10 (10.10):Ubuntu1:linux
It missed UbuntuStudio64bit which I am running right now on sda6

sda9 is Ubuntu Ultimate

sda7 is CtkArch and sda8 is ArchBang

sda10 is TooroxGnome64 bit

sda11 is Puppy


**NOTE**

If you look at my Partition setup I am using GRUBBOOT partition as a dedicated boot partition.

This is where I modify grub.cfg


I would be happy to test it



Might be useful to you??



jason@UbuntuStudio64bit:~$ sudo add-apt-repository ppa:yannubuntu/boot-repair-dev && sudo add-apt-repository ppa:yannubuntu/os-uninstaller-dev && sudo apt-get update && sudo apt-get install -y boot-repair-ubuntu boot-repair clean-ubiquity-common boot-repair-common os-uninstaller os-uninstaller-ubuntu
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp://keyserver.ubuntu.com:80/ --recv 3C48D16124B50277AF10D27F32B18A1260D8DA0B
gpg: requesting key 60D8DA0B from hkp server keyserver.ubuntu.com
gpg: key 60D8DA0B: "Launchpad PPA for YannUbuntu" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver hkp://keyserver.ubuntu.com:80/ --recv 3C48D16124B50277AF10D27F32B18A1260D8DA0B
gpg: requesting key 60D8DA0B from hkp server keyserver.ubuntu.com
gpg: key 60D8DA0B: "Launchpad PPA for YannUbuntu" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
Ign http://archive.canonical.com natty InRelease
Ign http://security.ubuntu.com natty-security InRelease
Ign http://us.archive.ubuntu.com natty InRelease
Ign http://us.archive.ubuntu.com natty-updates InRelease
Ign http://ppa.launchpad.net natty InRelease
Ign http://ppa.launchpad.net natty InRelease
Hit http://archive.canonical.com natty Release.gpg
Hit http://us.archive.ubuntu.com natty Release.gpg
Hit http://security.ubuntu.com natty-security Release.gpg
Ign http://ppa.launchpad.net natty InRelease
Get:1 http://ppa.launchpad.net natty Release.gpg [316 B]
Hit http://archive.canonical.com natty Release
Hit http://us.archive.ubuntu.com natty-updates Release.gpg
Hit http://security.ubuntu.com natty-security Release
Hit http://ppa.launchpad.net natty Release.gpg
Get:2 http://ppa.launchpad.net natty Release.gpg [316 B]
Hit http://us.archive.ubuntu.com natty Release
Hit http://us.archive.ubuntu.com natty-updates Release
Hit http://archive.canonical.com natty/partner amd64 Packages
Get:3 http://ppa.launchpad.net natty Release [9,766 B]
Hit http://security.ubuntu.com natty-security/main Sources
Hit http://ppa.launchpad.net natty Release
Ign http://archive.canonical.com natty/partner TranslationIndex
Hit http://us.archive.ubuntu.com natty/main Sources
Hit http://us.archive.ubuntu.com natty/restricted Sources
Hit http://us.archive.ubuntu.com natty/universe Sources
Hit http://us.archive.ubuntu.com natty/multiverse Sources
Hit http://us.archive.ubuntu.com natty/main amd64 Packages
Hit http://security.ubuntu.com natty-security/restricted Sources
Hit http://security.ubuntu.com natty-security/universe Sources
Hit http://security.ubuntu.com natty-security/multiverse Sources
Hit http://security.ubuntu.com natty-security/main amd64 Packages
Hit http://security.ubuntu.com natty-security/restricted amd64 Packages
Hit http://us.archive.ubuntu.com natty/restricted amd64 Packages
Hit http://us.archive.ubuntu.com natty/universe amd64 Packages
Hit http://us.archive.ubuntu.com natty/multiverse amd64 Packages
Ign http://us.archive.ubuntu.com natty/main TranslationIndex
Ign http://us.archive.ubuntu.com natty/multiverse TranslationIndex
Ign http://us.archive.ubuntu.com natty/restricted TranslationIndex
Ign http://us.archive.ubuntu.com natty/universe TranslationIndex
Get:4 http://ppa.launchpad.net natty Release [9,772 B]
Hit http://security.ubuntu.com natty-security/universe amd64 Packages
Hit http://security.ubuntu.com natty-security/multiverse amd64 Packages
Ign http://security.ubuntu.com natty-security/main TranslationIndex
Ign http://security.ubuntu.com natty-security/multiverse TranslationIndex
Ign http://security.ubuntu.com natty-security/restricted TranslationIndex
Ign http://security.ubuntu.com natty-security/universe TranslationIndex
Hit http://us.archive.ubuntu.com natty-updates/main Sources
Hit http://us.archive.ubuntu.com natty-updates/restricted Sources
Hit http://us.archive.ubuntu.com natty-updates/universe Sources
Hit http://us.archive.ubuntu.com natty-updates/multiverse Sources
Hit http://us.archive.ubuntu.com natty-updates/main amd64 Packages
Hit http://us.archive.ubuntu.com natty-updates/restricted amd64 Packages
Hit http://us.archive.ubuntu.com natty-updates/universe amd64 Packages
Hit http://us.archive.ubuntu.com natty-updates/multiverse amd64 Packages
Ign http://us.archive.ubuntu.com natty-updates/main TranslationIndex
Ign http://us.archive.ubuntu.com natty-updates/multiverse TranslationIndex
Ign http://us.archive.ubuntu.com natty-updates/restricted TranslationIndex
Ign http://us.archive.ubuntu.com natty-updates/universe TranslationIndex
Get:5 http://ppa.launchpad.net natty/main Sources [1,919 B]
Get:6 http://ppa.launchpad.net natty/main amd64 Packages [1,529 B]
Ign http://ppa.launchpad.net natty/main TranslationIndex
Hit http://ppa.launchpad.net natty/main Sources
Hit http://ppa.launchpad.net natty/main amd64 Packages
Ign http://ppa.launchpad.net natty/main TranslationIndex
Get:7 http://ppa.launchpad.net natty/main Sources [1,932 B]
Get:8 http://ppa.launchpad.net natty/main amd64 Packages [1,535 B]
Ign http://ppa.launchpad.net natty/main TranslationIndex
Ign http://archive.canonical.com natty/partner Translation-en_US
Ign http://archive.canonical.com natty/partner Translation-en
Ign http://security.ubuntu.com natty-security/main Translation-en_US
Ign http://security.ubuntu.com natty-security/main Translation-en
Ign http://security.ubuntu.com natty-security/multiverse Translation-en_US
Ign http://security.ubuntu.com natty-security/multiverse Translation-en
Ign http://security.ubuntu.com natty-security/restricted Translation-en_US
Ign http://security.ubuntu.com natty-security/restricted Translation-en
Ign http://security.ubuntu.com natty-security/universe Translation-en_US
Ign http://security.ubuntu.com natty-security/universe Translation-en
Ign http://ppa.launchpad.net natty/main Translation-en_US
Ign http://ppa.launchpad.net natty/main Translation-en
Ign http://ppa.launchpad.net natty/main Translation-en_US
Ign http://us.archive.ubuntu.com natty/main Translation-en_US
Ign http://us.archive.ubuntu.com natty/main Translation-en
Ign http://ppa.launchpad.net natty/main Translation-en
Ign http://ppa.launchpad.net natty/main Translation-en_US
Ign http://us.archive.ubuntu.com natty/multiverse Translation-en_US
Ign http://us.archive.ubuntu.com natty/multiverse Translation-en
Ign http://us.archive.ubuntu.com natty/restricted Translation-en_US
Ign http://us.archive.ubuntu.com natty/restricted Translation-en
Ign http://ppa.launchpad.net natty/main Translation-en
Ign http://us.archive.ubuntu.com natty/universe Translation-en_US
Ign http://us.archive.ubuntu.com natty/universe Translation-en
Ign http://us.archive.ubuntu.com natty-updates/main Translation-en_US
Ign http://us.archive.ubuntu.com natty-updates/main Translation-en
Ign http://us.archive.ubuntu.com natty-updates/multiverse Translation-en_US
Ign http://us.archive.ubuntu.com natty-updates/multiverse Translation-en
Ign http://us.archive.ubuntu.com natty-updates/restricted Translation-en_US
Ign http://us.archive.ubuntu.com natty-updates/restricted Translation-en
Ign http://us.archive.ubuntu.com natty-updates/universe Translation-en_US
Ign http://us.archive.ubuntu.com natty-updates/universe Translation-en
Fetched 27.1 kB in 2s (9,930 B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
clean-ubiquity
The following NEW packages will be installed:
boot-repair-common os-uninstaller os-uninstaller-ubuntu
The following packages will be upgraded:
boot-repair boot-repair-ubuntu clean-ubiquity-common
3 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 194 kB of archives.
After this operation, 492 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/yannubuntu/boot-repair-dev/ubuntu/ natty/main clean-ubiquity-common all 2.05-0ppa31~natty [21.3 kB]
Get:2 http://ppa.launchpad.net/yannubuntu/boot-repair-dev/ubuntu/ natty/main boot-repair-common all 2.05-0ppa38~natty [60.5 kB]
Get:3 http://ppa.launchpad.net/yannubuntu/boot-repair-dev/ubuntu/ natty/main boot-repair all 2.06-0ppa51~natty [62.3 kB]
Get:4 http://ppa.launchpad.net/yannubuntu/boot-repair-dev/ubuntu/ natty/main boot-repair-ubuntu all 2-0ppa4~natty [19.1 kB]
Get:5 http://ppa.launchpad.net/yannubuntu/os-uninstaller-dev/ubuntu/ natty/main os-uninstaller all 2.0-0ppa21~natty [24.4 kB]
Get:6 http://ppa.launchpad.net/yannubuntu/os-uninstaller-dev/ubuntu/ natty/main os-uninstaller-ubuntu all 2-0ppa3~natty [6,118 B]
Fetched 194 kB in 1s (186 kB/s)
(Reading database ... 171626 files and directories currently installed.)
Preparing to replace clean-ubiquity-common 2.0-0ppa1~natty (using .../clean-ubiquity-common_2.05-0ppa31~natty_all.deb) ...
Unpacking replacement clean-ubiquity-common ...
Selecting previously deselected package boot-repair-common.
Unpacking boot-repair-common (from .../boot-repair-common_2.05-0ppa38~natty_all.deb) ...
Preparing to replace boot-repair 2.001-0ppa4~natty (using .../boot-repair_2.06-0ppa51~natty_all.deb) ...
Unpacking replacement boot-repair ...
Preparing to replace boot-repair-ubuntu 2-0ppa1~natty (using .../boot-repair-ubuntu_2-0ppa4~natty_all.deb) ...
Unpacking replacement boot-repair-ubuntu ...
Selecting previously deselected package os-uninstaller.
Unpacking os-uninstaller (from .../os-uninstaller_2.0-0ppa21~natty_all.deb) ...
Selecting previously deselected package os-uninstaller-ubuntu.
Unpacking os-uninstaller-ubuntu (from .../os-uninstaller-ubuntu_2-0ppa3~natty_all.deb) ...
Processing triggers for python-support ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for desktop-file-utils ...
Processing triggers for python-gmenu ...
Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...
Processing triggers for python-support ...
Setting up clean-ubiquity-common (2.05-0ppa31~natty) ...
Setting up boot-repair-common (2.05-0ppa38~natty) ...
Setting up boot-repair (2.06-0ppa51~natty) ...
Setting up boot-repair-ubuntu (2-0ppa4~natty) ...
Setting up os-uninstaller (2.0-0ppa21~natty) ...
Setting up os-uninstaller-ubuntu (2-0ppa3~natty) ...
Processing triggers for python-support ...

YannBuntu
July 23rd, 2011, 08:35 PM
this time os-prober worked without problem.

> It missed UbuntuStudio64bit which I am running right now

This is normal, os-prober does not show the OS in use.

Separate /boot partition is not taken in charge in Boot-Repair v2, but you are lucky : I added this feature in the v3 beta :)

You can try the v3, but don't validate if no OS is proposed as "OS to boot by default".

Concerning your last log, i see no problem. You can check that you have the last versions of packages by looking at https://launchpad.net/~yannubuntu/+archive/boot-repair-dev/+packages

JASONFUSARO
July 23rd, 2011, 08:45 PM
Here is the run

2ndSS

It picked up running OS

I selected force grub into sda6 ss#4


which gave me this error ss#5


Not ebough room to upload another screen but it is of Boot Repair Please wait few second which is still running????


I shut it down and got the boot successfully repaired


I will check var/log and place another post

JASONFUSARO
July 23rd, 2011, 08:55 PM
This is what I have



The screenshots are from sda6


and this is the grub.cfg file



#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 2.6.39.3' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
linux /boot/vmlinuz-2.6.39.3 root=/dev/sda6 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
}
menuentry 'Ubuntu, with Linux 2.6.39.3 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
echo 'Loading Linux 2.6.39.3 ...'
linux /boot/vmlinuz-2.6.39.3 root=/dev/sda6 ro single
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 2.6.38-10-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
linux /boot/vmlinuz-2.6.38-10-generic root=UUID=ae95fcff-e194-4dec-9342-3b029ff999c2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-10-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-10-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
echo 'Loading Linux 2.6.38-10-generic ...'
linux /boot/vmlinuz-2.6.38-10-generic root=UUID=ae95fcff-e194-4dec-9342-3b029ff999c2 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-10-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=ae95fcff-e194-4dec-9342-3b029ff999c2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
echo 'Loading Linux 2.6.38-8-generic ...'
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=ae95fcff-e194-4dec-9342-3b029ff999c2 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-generic
}
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###



the 3rd screen shot is my BOOTGRUB but it did not place a grub folder there but it did create oldbooot

as I stated before this is the dedicated boot partition and no distro nor is it a linux partition it is 200 MB fat


I hope this stuff helps you and I am always willing to help or test something for you, I enjoy fixing things

I have to fix my grub and copy it back and I will look at the others to see if I find anything interesting


again please explain the following:

After solving a problem in the forum, don't forget to improve the Wiki !

JASONFUSARO
July 23rd, 2011, 09:11 PM
There are some that you placed ie.. grub.cfg that are blank yet they exist and are in the appropriate boot folders and some that you placed that are not blank, would this information be helpful to you and would the resulting grub.cfg's original and yours as comparisons be useful to you?

I know my setup is rather complex, but that always helps in catching things that you would not otherwise encounter in basic scenario's.

Please let me know.


I am going to reboot now, just to check things out.

JASONFUSARO
July 23rd, 2011, 09:15 PM
I am back

Reboot went fine, everything is AOK!

JASONFUSARO
July 23rd, 2011, 09:17 PM
Hello

@Luke : good remark. Yes Boot-Repair creates a /clean folder in all OSs partitions.It contains logs and MBR backups, so I strongly suggest you don't remove it. The /clean folder is duplicated in all OSs partitions for security purpose. If really you want to remove it, you can do it from a live-CD or from your Ubuntu.



Please explain, what will happen if I remove these?

Every MBR backups folder is empty, should this be the case??


Now this may or may not make a difference to why the output is as it is

I just compiled the Linux 3.0 kernel yesterday

jason@UbuntuStudio64bit:~$ uname -a
Linux UbuntuStudio64bit 3.0.0 #2 SMP Fri Jul 22 20:02:30 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

see screenshot also


But I never ran update-grub, which I don't need to because of the GRUBBOOT partition, does this have an effect on system variables that your software has access to and by my not having ran update-grub as was required have an impact on the software??

YannBuntu
July 24th, 2011, 03:06 AM
Thanks for the feedback. Please send me again a TAR.GZ of your /var/log/clean folder, so that I can see the logs.

Does Boot-Repair v3 work when you reinstall GRUB in an OS without separate /boot ?
Does Boot-Repair v3 work when you reinstall GRUB in the MBR (e.g. not sda6, but sda) ?

JASONFUSARO
July 24th, 2011, 03:30 AM
Thanks for the feedback. Please send me again a TAR.GZ of your /var/log/clean folder, so that I can see the logs.

Does Boot-Repair v3 work when you reinstall GRUB in an OS without separate /boot ?
Does Boot-Repair v3 work when you reinstall GRUB in the MBR (e.g. not sda6, but sda) ?






Screenshot #5 of post #49 shows that error and Which var/log/clean folder do you want, the one that I ran it on or all of them, it placed it in all the installed os's some were blank as I stated in a previous post.

I will try sda after I am done with the Gparted resize I doing right now.

YannBuntu
July 24th, 2011, 09:41 AM
again please explain the following:

After solving a problem in the forum, don't forget to improve the Wiki !

It is just my signature, it appears automatically under all my messages in the forum. The Wiki I talk about is also called the "Community Documentation" (https://help.ubuntu.com/community/Boot-Repair).


grub.cfg that are blank

Boot-Repair should create no blank file. If it happens that is a bug that we need to solve, please indicate me the localization of the files that are blanked.


I know my setup is rather complex, but that always helps in catching things that you would not otherwise encounter in basic scenario's.

You are right, your config is perfect to debug :)


Reboot went fine, everything is AOK!

Perfect !


Please explain, what will happen if I remove these?

In your particular case, nothing. The (/var/log)/clean contains logs and all necessary backups (MBR, grub files..) in case we need to debug, or in case Boot-Repair bugs for example.
And for users who installed a distro containing Clean-Ubiquity, there can be also, in the /clean/mbr_backups folder, a special MBR backup (linked to the UUID of the installed distro) that can be restored via Boot-Repair and/or OS-Uninstaller.


Every MBR backups folder is empty, should this be the case??

Yes it is normal, because you did not use Clean-Ubiquity, so your Vista MBR is definitely lost (erased the first time you installed GRUB).


I just compiled the Linux 3.0 kernel yesterday

This won't have any impact on Boot-Repair.



But I never ran update-grub, which I don't need to because of the GRUBBOOT partition, does this have an effect on system variables that your software has access to and by my not having ran update-grub as was required have an impact on the software??

Boot-Repair automatically runs update-grub after reinstalling GRUB.

Can you detail what is your "GRUBBOOT partition", and how you use it ? which distro use it ?
I understood it was just a separate /boot partition for your UbuntuStudio (only, not for any other OS), but I am not sure...

JASONFUSARO
July 24th, 2011, 04:07 PM
Did you receive the clean.tar.gz files I emailed





Can you detail what is your "GRUBBOOT partition", and how you use it ? which distro use it ?
I understood it was just a separate /boot partition for your UbuntuStudio (only, not for any other OS), but I am not sure...
I set it up as per instructions in this link

http://members.iinet.net/~herman546/p20/GRUB2%20Bash%20Commands.html (http://members.iinet.net/%7Eherman546/p20/GRUB2%20Bash%20Commands.html)


it is not tied to any Distro in particular so it can be modified and changed at will, and no update-grub executed in any other distro has an effect on it, I simply transfer the menu entry into it.

here is my copy which is on parition #2 and is formated as fat the partition Label is GRUBBOOT




#insmod part_gpt
#insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

set menu_color_normal=black/white
set menu_color_highlight=white/red

insmod part_msdos
insmod ext2
set gfxmode=640x480
set root='(hd0,msdos10)'
search --no-floppy --fs-uuid --set=root AC82-C4B4
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
#set root='(hd0,msdos10)'
#search --no-floppy --fs-uuid --set=root /dev/sda2
search --no-floppy --fs-uuid --set=root AC82-C4B4
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root AC82-C4B4
load_video
##############insmod jpeg
terminal gfxterm
insmod png
background_image -m /boot/grub/1110.png
set timeout=95
### END /etc/grub.d/00_header ###



### BEGIN /etc/grub.d/42_NEW_Chakra_Distros ###
menuentry "Windows Vista (loader) (on /dev/sda1)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root C65A6C105A6C0013
chainloader +1
}
menuentry "-" {
set
}

menuentry "Chakra Linux, with Linux vmlinuz26 Fallback (on /dev/sda5)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
#search --no-floppy --fs-uuid --set=root ca7b9adc-9887-496c-a1ad-a3a5ec4f3cf6
linux /boot/vmlinuz26 root=/dev/sda5 ro quiet
#/dev/disk/by-uuid/ca7b9adc-9887-496c-a1ad-a3a5ec4f3cf6 ro quiet
initrd /boot/kernel26.img
}
menuentry "-" {
set
}

menuentry 'UbuntuStudio 64 bit on sda6, with Linux 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {

insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
#search --no-floppy --fs-uuid --set=root c7e7c5c2-09fe-4db4-8633-554f90059f45
linux /boot/vmlinuz-2.6.38-8-generic root=/dev/sda6 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry 'UbuntuStudio TEST KERNEL Linux 2.6.39.3 TEST KERNEL' --class ubuntu --class gnu-linux --class gnu --class os {

insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
#search --no-floppy --fs-uuid --set=root c7e7c5c2-09fe-4db4-8633-554f90059f45
linux /boot/vmlinuz-2.6.39.3 root=/dev/sda6 ro quiet splash vt.handoff=7
initrd /boot/initramf-2.6.39.3
}
menuentry 'UbuntuStudio TEST KERNEL Linux 3.0.0 TEST KERNEL' --class ubuntu --class gnu-linux --class gnu --class os {

insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
#search --no-floppy --fs-uuid --set=root c7e7c5c2-09fe-4db4-8633-554f90059f45
linux /boot/bzImage-3.0.0 root=/dev/sda6 ro quiet splash vt.handoff=7
initrd /boot/initramfs-3.0.0
}
menuentry "CtkArch Linux (on /dev/sda7)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos7)'
#search --no-floppy --fs-uuid --set=root 0920168c-5419-4412-8134-713ed2c3814c
#linux /boot/vmlinuz26 root=/dev/disk/by-uuid/0920168c-5419-4412-8134-713ed2c3814c ro quiet resume=/dev/disk/by-uuid/759ac79d-c3af-49f4-ae9a-19a2e3464a02
linux /boot/vmlinuz26 root=/dev/sda7 ro quiet
#resume=/dev/disk/by-uuid/759ac79d-c3af-49f4-ae9a-19a2e3464a02
initrd /boot/kernel26.img
}

menuentry "ArchBang Linux, with Linux vmlinuz26" --class archlinux --class gnu-linux --class gnu --class os {
#load_video
#set gfxpayload=keep
#insmod gzio
#insmod part_msdos
#insmod ext2
set root='(hd0,msdos8)'
#search --no-floppy --fs-uuid --set=root /dev/sda8 #ee7be487-f281-4072-9af3-72612c9a684c
#echo 'Loading ArchBang Linux kernel vmlinuz26 ...'
linux /boot/vmlinuz26-patched root=/dev/sda8 ro quiet
#echo 'Loading initial ramdisk ...'
initrd /boot/kernel26-patched.img
}
menuentry "Ultimate, with Linux 2.6.35-25-generic (on /dev/sda9)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos9)'
#search --no-floppy --fs-uuid --set=root /dev/sda9 #52777f50-fd1d-42d8-9a17-5ad1ddf0b794
#linux /boot/vmlinuz-2.6.35-25-generic root=UUID=52777f50-fd1d-42d8-9a17-5ad1ddf0b794 ro quiet splash
linux /boot/vmlinuz-2.6.35-30-generic root=/dev/sda9 ro quiet splash
initrd /boot/initrd.img-2.6.35-30-generic
}

menuentry "Toorox Gnome 64 bit (on /dev/sda10)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos10)'
#search --no-floppy --fs-uuid --set=root /dev/sda10 #91033a5b-7407-4a80-b1aa-07ff96202ee3
linux /boot/vmlinuz root=/dev/sda10 nomce noapic lang=us
}
menuentry "Puppy, with Linux (on /dev/sda11)" --class gnu-linux --class gnu --class os {
'insmod part_msdos
'insmod ext2
set root='(hd0,msdos11)'
#search --no-floppy --fs-uuid --set=root /dev/sda11 #856f3983-f4e9-45da-b500-e199fefbbad1
linux /boot/vmlinuz root=/dev/sda11 pmedia=atahd

}
menuentry "Zorin, (Software design Pkgs) with Linux (on /dev/sda12)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos12)'
#search --no-floppy --fs-uuid --set=root /dev/sda12 #06ca0e47-d483-4dbe-bfe8-4656dc6cd0eb
linux /boot/vmlinuz-2.6.38-8-generic root=/dev/sda12 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry "Slackware, (Software design Pkgs) with Linux (on /dev/sda15)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext3
set root='(hd0,msdos15)'
#search --no-floppy --fs-uuid --set=root 6a3011c0-3c9e-4832-aede-6472452da31a
#linux /boot/vmlinuz-generic-2.6.37.6 root=UUID=6a3011c0-3c9e-4832-aede-6472452da31a
linux /boot/vmlinuz-huge-2.6.37.6 root=/dev/sda15 rdinit= ro
initrd /boot/initrd.gz
}
### END /etc/grub.d/42_NEW_Chakra_Distros ###



Now as to



Does Boot-Repair v3 work when you reinstall GRUB in the MBR (e.g. not sda6, but sda) ?
I ran it again and selected the windows MBR view attached screenshot


and the result of that was the following, I am posting all my steps in the hopes of maybe helping others, hopefully it does not make it more confusing?





Thanks for the feedback. Please send me again a TAR.GZ of your /var/log/clean folder, so that I can see the logs.

Does Boot-Repair v3 work when you reinstall GRUB in an OS without separate /boot ?
Does Boot-Repair v3 work when you reinstall GRUB in the MBR (e.g. not sda6, but sda) ?


Well if you look at the screenshot I selected MBR but that only booted me straight into windows no boot menu at all.

Now I had some work to do!

Luckily I had made a Grub2 USB some time back but the menu did not coincide with my current setup all the partitions were wrong, because I have been changing things around alot to get a feel fro the system.

Luckily it was set with UUID's so Ubuntu booted and I decided to fix the USB to coincide with my current setup, but that ran me into another problem becuase I missed a step and since I was running UbuntuStudio wich I upgraded to Grub2 did not get added to the grub.cfg.

so when I rebooted I had a kernel panic!

Now I could not get into anything that had Grub2 upgrade and could not fix it, CtkArch has a problem with pacman etc...etc..

Finally ran a Live CD and got back a menu, but it was not current, and your software renamed boot to oldboot so I had to rename it after deleting the one your software created.

Now once I was able to boot back into my menu I decided to update the GrubBoot USB to make it current:




After I could not get back into grub menu

I put a Grub2 USB I had made


jason@UbuntuStudio64bit:~$ sudo blkid

To find the label of the USB

jason@UbuntuStudio64bit:~$ blkid
/dev/sda1: LABEL="WindowsVista" UUID="C65A6C105A6C0013" TYPE="ntfs"
/dev/sda2: LABEL="BOOTGRUB" UUID="AC82-C4B4" TYPE="vfat"
/dev/sda3: UUID="35b20b9d-52cd-4ed4-803f-3a22ed821f66" TYPE="swap"
/dev/sda5: LABEL="Chakra" UUID="ca7b9adc-9887-496c-a1ad-a3a5ec4f3cf6" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda6: LABEL="UbuntuStudio64bi" UUID="ae95fcff-e194-4dec-9342-3b029ff999c2" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: LABEL="CtkArch64" UUID="0920168c-5419-4412-8134-713ed2c3814c" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda8: LABEL="ArchBang" UUID="ee7be487-f281-4072-9af3-72612c9a684c" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda9: LABEL="UltimateEdition" UUID="52777f50-fd1d-42d8-9a17-5ad1ddf0b794" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda10: LABEL="TooroxGnome64" UUID="00a7cb0b-392f-47be-bb3f-e76b5296ba78" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda11: LABEL="Puppy" UUID="856f3983-f4e9-45da-b500-e199fefbbad1" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda12: LABEL="Zorin" UUID="847decb3-ad18-42c7-90dd-1b5a8715e290" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda13: LABEL="DistroHood" UUID="edee5a0c-2b54-46af-aaa5-1c1147587deb" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda14: LABEL="Slackware" UUID="6a3011c0-3c9e-4832-aede-6472452da31a" TYPE="ext4"
/dev/sda15: LABEL="Zenwalk" UUID="391ded26-9183-409f-b780-5632075d5ed1" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda16: LABEL="FusionLinux" UUID="8efba70a-15c5-4eb5-bb40-e9e28c3d0002" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb1: LABEL="GrubBoot" UUID="91210090-7641-4a87-96d3-d2d9c6056940" TYPE="ext2"
/dev/sdb2: UUID="80079494-a1c1-4f19-99b4-6f2e82f90297" TYPE="ext2"
/dev/sdc1: LABEL="HP_320GB-ActiveSoft" UUID="F0B8E610B8E5D55E" TYPE="ntfs"
/dev/sdd1: LABEL="ReadyBoost-SysUtilities" UUID="8A9C26F89C26DE87" TYPE="ntfs"



I then put grub on the USB's MBR

sudo grub-install --root-directory=/media/GrubBoot /dev/sdb
Installation finished. No error reported.


wrote grub.cfg to the USB

root@UbuntuStudio64bit:/home/jason# grub-mkconfig -o /media/GrubBoot/boot/grub/grub.cfg

Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.39.3
Found linux image: /boot/vmlinuz-2.6.38-10-generic
Found initrd image: /boot/initrd.img-2.6.38-10-generic
Found linux image: /boot/vmlinuz-2.6.38-8-generic
Found initrd image: /boot/initrd.img-2.6.38-8-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Windows Vista (loader) on /dev/sda1
Found Gentoo Base System release 2.0.2 on /dev/sda10
Found unknown Linux distribution on /dev/sda11
Found Zorin OS 5 (11.04) on /dev/sda12
Found Slackware Linux (Slackware 13.37.0) on /dev/sda14
Found Chakra Linux (2011.04_20110521-1) on /dev/sda5
Found Arch on /dev/sda7
Found Arch1 on /dev/sda8
Found Ubuntu 10.10 (10.10) on /dev/sda9
done


so I can modify it without being root if I have to

root@UbuntuStudio64bit:/home/jason# chmod 777 -R /media/GrubBoot


so it should be ready for the next time I need it


But since I have a dedicated boot partition I had to modify GrubBoot/boot/grub/grub.cfg which needed root=UUID= entries as opposed to root=/dev/sda6 since I will be booting from the USB device and added back my UbuntuStudio64 menu entries


#


#insmod part_gpt
#insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

set menu_color_normal=black/white
set menu_color_highlight=white/red

insmod part_msdos
insmod ext2
set gfxmode=640x480
set root='(hd0,msdos10)'
search --no-floppy --fs-uuid --set=root ee7be487-f281-4072-9af3-72612c9a684c
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
#set root='(hd0,msdos10)'
search --no-floppy --fs-uuid --set=root /dev/sda2
#search --no-floppy --fs-uuid --set=root /dev/sda10
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root AC82-C4B4
load_video
##############insmod jpeg
terminal gfxterm
insmod png
background_image -m /boot/grub/1110.png
set timeout=95
### END /etc/grub.d/00_header ###



### BEGIN /etc/grub.d/42_NEW_Chakra_Distros ###
menuentry "Windows Vista (loader) (on /dev/sda1)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root C65A6C105A6C0013
chainloader +1
}
menuentry "-" {
set
}

menuentry "Chakra Linux, with Linux vmlinuz26 Fallback (on /dev/sda5)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root ca7b9adc-9887-496c-a1ad-a3a5ec4f3cf6
linux /boot/vmlinuz26 root=UUID=ca7b9adc-9887-496c-a1ad-a3a5ec4f3cf6 ro quiet
initrd /boot/kernel26.img
}
menuentry "-" {
set
}

menuentry 'UbuntuStudio 64 bit on sda6, with Linux 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {

insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=ae95fcff-e194-4dec-9342-3b029ff999c2 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry 'UbuntuStudio TEST KERNEL Linux 2.6.39.3 TEST KERNEL' --class ubuntu --class gnu-linux --class gnu --class os {

insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
linux /boot/vmlinuz-2.6.39.3 root=UUID=ae95fcff-e194-4dec-9342-3b029ff999c2 ro quiet splash vt.handoff=7
initrd /boot/initramf-2.6.39.3
}
menuentry 'UbuntuStudio TEST KERNEL Linux 3.0.0 TEST KERNEL' --class ubuntu --class gnu-linux --class gnu --class os {

insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set=root ae95fcff-e194-4dec-9342-3b029ff999c2
linux /boot/bzImage-3.0.0 root=UUID=ae95fcff-e194-4dec-9342-3b029ff999c2 ro quiet splash vt.handoff=7
initrd /boot/initramfs-3.0.0
}
menuentry "CtkArch Linux (on /dev/sda7)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos7)'
search --no-floppy --fs-uuid --set=root 0920168c-5419-4412-8134-713ed2c3814c
linux /boot/vmlinuz26 root=UUID=0920168c-5419-4412-8134-713ed2c3814c ro quiet resume=/dev/disk/by-uuid/759ac79d-c3af-49f4-ae9a-19a2e3464a02
initrd /boot/kernel26.img
}

menuentry "ArchBang Linux, with Linux vmlinuz26" --class archlinux --class gnu-linux --class gnu --class os {
#load_video
#set gfxpayload=keep
#insmod gzio
#insmod part_msdos
#insmod ext2
set root='(hd0,msdos8)'
search --no-floppy --fs-uuid --set=root ee7be487-f281-4072-9af3-72612c9a684c
#echo 'Loading ArchBang Linux kernel vmlinuz26 ...'
linux /boot/vmlinuz26-patched root=UUID=ee7be487-f281-4072-9af3-72612c9a684c ro quiet
#echo 'Loading initial ramdisk ...'
initrd /boot/kernel26-patched.img
}
menuentry "Ultimate, with Linux 2.6.35-25-generic (on /dev/sda9)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos9)'
search --no-floppy --fs-uuid --set=root 52777f50-fd1d-42d8-9a17-5ad1ddf0b794
linux /boot/vmlinuz-2.6.35-25-generic root=UUID=52777f50-fd1d-42d8-9a17-5ad1ddf0b794 ro quiet splash
initrd /boot/initrd.img-2.6.35-30-generic
}

menuentry "Toorox Gnome 64 bit (on /dev/sda10)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos10)'
search --no-floppy --fs-uuid --set=root 00a7cb0b-392f-47be-bb3f-e76b5296ba78
linux /boot/vmlinuz root=UUID=00a7cb0b-392f-47be-bb3f-e76b5296ba78 nomce noapic lang=us
}
menuentry "Puppy, with Linux (on /dev/sda11)" --class gnu-linux --class gnu --class os {
'insmod part_msdos
'insmod ext2
set root='(hd0,msdos11)'
search --no-floppy --fs-uuid --set=root 856f3983-f4e9-45da-b500-e199fefbbad1
linux /boot/vmlinuz root=UUID=856f3983-f4e9-45da-b500-e199fefbbad1 pmedia=atahd

}
menuentry "Zorin, (Software design Pkgs) with Linux (on /dev/sda12)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos12)'
search --no-floppy --fs-uuid --set=root 847decb3-ad18-42c7-90dd-1b5a8715e290
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=847decb3-ad18-42c7-90dd-1b5a8715e290 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry "Slackware, (Software design Pkgs) with Linux (on /dev/sda15)" --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext3
set root='(hd0,msdos14)'
search --no-floppy --fs-uuid --set=root 6a3011c0-3c9e-4832-aede-6472452da31a
#linux /boot/vmlinuz-generic-2.6.37.6 root=UUID=6a3011c0-3c9e-4832-aede-6472452da31a
linux /boot/vmlinuz-huge-2.6.37.6 root=UUID=6a3011c0-3c9e-4832-aede-6472452da31a rdinit= ro
initrd /boot/initrd.gz
}
### END /etc/grub.d/42_NEW_Chakra_Distros ###





Now I am back where I started, I tested the USB boot and that is ok now.




Boot-Repair should create no blank file. If it happens that is a bug that we need to solve, please indicate me the localization of the files that are blanked.
You should have them in the tars that I sent. But again I am doing things in a non standard way I believe and this may be the culprit??

I hope this is not to confusing?

YannBuntu
July 24th, 2011, 04:36 PM
Thanks a lot for your feedback! :D
In the last screenshot, you chose to restore a generic MBR that boots Vista directly. Looks like it worked :)

I just uploaded a new version (v3 Beta3) on ppa:yannubuntu/boot-repair-dev

- corrects separate /boot detection
- takes into account FAT restrictions (no case sensitive)
- takes into account mounting points with spaces
- corrects /cdrom detection which led to bug when reinstalling into current os

Please can you check that this new version :
- does not rename your /boot folder into /oldbooot
- reinstalls GRUB correctly whatever the place you choose and the "OS to boot by default " you choose

--> and like usual, please send me a TAR of your /clean folder ;)

JASONFUSARO
July 24th, 2011, 05:23 PM
Thanks a lot for your feedback! :D
In the last screenshot, you chose to restore a generic MBR that boots Vista directly. Looks like it worked :)

I just uploaded a new version (v3 Beta3) on ppa:yannubuntu/boot-repair-dev

- corrects separate /boot detection
- takes into account FAT restrictions (no case sensitive)
- takes into account mounting points with spaces
- corrects /cdrom detection which led to bug when reinstalling into current os

Please can you check that this new version :
- does not rename your /boot folder into /oldbooot
- reinstalls GRUB correctly whatever the place you choose and the "OS to boot by default " you choose

--> and like usual, please send me a TAR of your /clean folder ;)


did you receive the last tar I sent which included all of them?


partition dev location mbr_backups
WindowsVista sda1 clean/mbr_backups EMPTY
Chakra sda5 clean/mbr_backups EMPTY
UbuntuStudio sda6 clean/mbr_backups EMPTY
CtkArch sda7 "" EMPTY
ArchBang sda8 "" ""
UltimateEdition sda9 "" ""
TooroxGnome64 sda10 "" ""
Puppy sda11 "" ""
Zorin sda12 "" ""
Slackware sda14 "" ""

Chakra sda5 var/log/clean/log
2011-07-23__15:31boot-repair13
2011-07-23__15:31.boot-repair.log.tee
sda folder current_mbr.img
sda1 folder EMPTY
sda2 folder EMPTY
sda3 folder NONE
sda4 folder NONE
sda5 folder etc_default_grub grub.cfg
sda6 folder etc_default_grub grub.cfg
sda7 folder EMPTY
sda8 folder etc_default_grub NONE
sda9 folder etc_default_grub grub.cfg
sda10 folder NONE grub.cfg
sda11 folder EMPTY
sda12 folder etc_default_grub grub.cfg
sda13 folder EMPTY
sda14 folder EMPTY
sda15 folder EMPTY
sda16 folder EMPTY
sdb folder current_mbr.img
sdb1 folder EMPTY
sdc folder current_mbr.img
sdc1 folder EMPTY
2011-07-24__00:03boot-repair34
2011-07-24__00:03.boot-repair.log.tee
sda folder current_mbr.img mbr_before_restoring_mbr.img
sda1 folder EMPTY
sda2 folder EMPTY
sda3 folder NONE
sda4 folder NONE
sda5 folder EMPTY
sda6 folder EMPTY
sda7 folder EMPTY
sda8 folder EMPTY
sda9 folder EMPTY
sda10 folder EMPTY
sda11 folder EMPTY
sda12 folder EMPTY
sda13 folder EMPTY
sda14 folder EMPTY
sda15 folder EMPTY
sda16 folder EMPTY
sdb folder current_mbr.img
sdb1 folder EMPTY
sdb2 folder EMPTY
sdc folder current_mbr.img
sdc1 folder EMPTY
sdd folder current_mbr.img
sdd1 folder EMPTY
2011-07-23__23:25boot-repair25
2011-07-23__23:25.boot-repair.log.tee
2011-07-23__23:25.boot-repair.log.paste
boot_info_script.sh
RESULTS.txt
sources.list
sda folder current_mbr.img
sda1 folder EMPTY
sda2 folder EMPTY
sda3 folder NONE
sda4 folder NONE
sda5 folder etc_default_grub grub.cfg
sda6 folder etc_default_grub grub.cfg
sda7 folder EMPTY
sda8 folder etc_default_grub
sda9 folder etc_default_grub grub.cfg
sda10 folder grub.cfg
sda11 folder EMPTY
sda12 folder etc_default_grub grub.cfg
sda13 folder EMPTY
sda14 folder EMPTY
sda15 folder EMPTY
sda16 folder EMPTY
sdb folder current_mbr.img
sdb1 folder EMPTY
sdc folder current_mbr.img
sdc1 folder EMPTY


If you notice a difference of partitions in the interim I have gotten rid of woof and shared and added Zenwalk and FusionLinux I have not installed anything to them yet but plan to for the software design capabilities, but I have not changed nor deleted any of the var/log/clean/log or var/log/clean/mbr_backups folders your software has created. And all var/log/clean/log folders contain 3 folders for the three seperate runs I performed.





you don't need this if you received the last tar I emailed you, which I don't know?

JASONFUSARO
July 24th, 2011, 05:31 PM
Thanks a lot for your feedback! :D
In the last screenshot, you chose to restore a generic MBR that boots Vista directly. Looks like it worked :)

I just uploaded a new version (v3 Beta3) on ppa:yannubuntu/boot-repair-dev

- corrects separate /boot detection
- takes into account FAT restrictions (no case sensitive)
- takes into account mounting points with spaces
- corrects /cdrom detection which led to bug when reinstalling into current os

Please can you check that this new version :
- does not rename your /boot folder into /oldbooot
- reinstalls GRUB correctly whatever the place you choose and the "OS to boot by default " you choose

--> and like usual, please send me a TAR of your /clean folder ;)


I just dowloaded it but nowhere does it specify version info which would be helpful.

YannBuntu
July 24th, 2011, 05:34 PM
Yes, I received your email with the TAR. (I replied to it). It concerns your test with V3 beta2.

Now please test v3 beta3, which is indeed the new packages I just uploaded in the PPA :) (you can check that you have the last versions by checking the versions that are currently in the PPA here: https://launchpad.net/~yannubuntu/+archive/boot-repair-dev/+packages )

To get v3 Beta3, just update your packages (if you use it form an installed session), or reinstall the PPA-dev+the packages (if you test from a live-CD).

JASONFUSARO
July 24th, 2011, 05:52 PM
SS#1 This is showing that I have the boot flag set on this partition I assume

SS#4 Please explain, and grub configuration from current partition I assume

SS#2 Only shows two other Distros, shouldn't it be listing all of them??

And if I select sda6 to boot from where I am at now, the next time around I will not have an option to boot into sda2 of which there is no distro, now if I place a kernel in that partition even though there is not an OS located there should/would it be added to this list??


I am going to try that right now and then run your software, I assume that is what it searches for, am I correct?

No. still the same just three sda6,9,12

JASONFUSARO
July 24th, 2011, 10:49 PM
I selected apply and after it ran I checked to see if it renamed my boot directory and it didn't SS#1

I rebooted

I got the following boot menu:

Ubuntu with Linux 2.6.39.3 ------------------> Kernel Panic
Previous Linux versions ------------------> SUB MENU
Memory test I did not select
Windows Vista (loader) ------------------ > AOK
Gentoo Base System release 2.0.2 on sda10 ----------> this is TooroxGnome64bit Explanation #1
Unknown Linux distribution on sda11 -------------> Puppy AOK
Ubuntu with Linux 2.6.38-10-generic sda12 ---------> Zorin AOK
SAME AS ABOVE
Unetbootin on sda12 ----^ rebooted don't know why this was found
Slackware on sda14 --------------------------> kernel panic
Zorin on sda14 -----------> did not select this is an error slackware is on 14
Chakra Linux sda5 --------------------------> same as Toorox Explanation #1
Arch Linux on sda7 --------------------------------> CtkArch AOK
Arch1 on sda8 --------------------------------> ArchBang same as Toorox & Chakra Explanation #1
Ubuntu 2.6.35-30 sda9 -----------------------> Ultimate Edition AOK

SUB MENU
Ubuntu 2.6.38-10 --------------------> UbuntuStudio64 AOK WHERE I AM RIGHT NOW
Ubuntu 2.6.38-8 --------------------> did not select


Question:
Why did it not find UbuntuStudio64 kernel 3.0.0 (it is named bzImage-3.0)



Explanation #1

ArchBang, Chakra and Toorox home folders are located on partition #13 DistroHood, but were not placed there during an install, they have to be mounted.


I then emailed you the clean results and a boot info script


You asked if lib32 or lib64

Distro lib32 lib34
Puppy N N
Toorox Y Y
UbuntuStudio Y Y
Zorin Y Y
Slackware N Y
Chakra N Y
CtkArch N Y
ArchBang N Y
Ultimate Edition N Y


In your email you asked if os-prober was working, the executable is set


The next thread will detail getting back to booting off sda2

JASONFUSARO
July 24th, 2011, 10:54 PM
Fifth run

I selected restore MBR SS#!

I was unsure of those codes in parens SS#2 please explain

My selection SS#3-4 MBR sda2



Screen after run SS#5



I then rebooted (see next thread for results)

JASONFUSARO
July 24th, 2011, 11:05 PM
Then FEAR set in!!! My Heart rate shot up I started to sweat all sorts of horrible thoughts raced through my head when I seen screenshot #1 especially when I got it twice!!


I then reached for that USB boot hat I made earlier SS#2

and in a couple of seconds I felt a little better when I seen SS#3



and SS#4 brought on a relaxing calmness



now to figure out what went wrong?

YannBuntu
July 25th, 2011, 01:32 AM
Hi

I just dowloaded it but nowhere does it specify version info which would be helpful.

You can check your packages versions via Synaptic for example.


SS#1 This is showing that I have the boot flag set on this partition I assume

No, you don't have to care for your current boot flag position. Boot-Repair will re-set the boot flag if necessary.



SS#4 Please explain, and grub configuration from current partition I assume

The "GRUB options" tab's purpose is to let the user edit the /etc/defaults/grub file of the OS selected in the "GRUB location" tab.
So mainly to add kernel options.

If you click on the button "Edit GRUB configuration file", you will see that it edits the /etc/defaults/grub file of the OS selected in your "GRUB location" tab.



SS#2 Only shows two other Distros, shouldn't it be listing all of them?

For the moment, Boot-repair can only reinstall GRUB into the Linux using apt. Support for other distros is a feature that I wish to implement, but this is long-term view and I will need help.



And if I select sda6 to boot from where I am at now, the next time around I will not have an option to boot into sda2 of which there is no distro, now if I place a kernel in that partition even though there is not an OS located there should/would it be added to this list?

Please refer to the email I sent you this morning: the "Place GRUB into" and "Force GRUB into" is for "GRUB stage1".
What you are thinking about is the location of grub.cfg.

YannBuntu
July 25th, 2011, 02:00 AM
I selected apply and after it ran I checked to see if it renamed my boot directory and it didn't

Perfect. This bug is fixed.


I got the following boot menu:

Ubuntu with Linux 2.6.39.3 ------------------> Kernel Panic
Previous Linux versions ------------------> SUB MENU
Memory test I did not select
Windows Vista (loader) ------------------ > AOK
Gentoo Base System release 2.0.2 on sda10 ----------> this is TooroxGnome64bit Explanation #1
Unknown Linux distribution on sda11 -------------> Puppy AOK
Ubuntu with Linux 2.6.38-10-generic sda12 ---------> Zorin AOK
SAME AS ABOVE
Unetbootin on sda12 ----^ rebooted don't know why this was found
Slackware on sda14 --------------------------> kernel panic
Zorin on sda14 -----------> did not select this is an error slackware is on 14
Chakra Linux sda5 --------------------------> same as Toorox Explanation #1
Arch Linux on sda7 --------------------------------> CtkArch AOK
Arch1 on sda8 --------------------------------> ArchBang same as Toorox & Chakra Explanation #1
Ubuntu 2.6.35-30 sda9 -----------------------> Ultimate Edition AOK

SUB MENU
Ubuntu 2.6.38-10 --------------------> UbuntuStudio64 AOK WHERE I AM RIGHT NOW
Ubuntu 2.6.38-8 --------------------> did not select


Question:
Why did it not find UbuntuStudio64 kernel 3.0.0 (it is named bzImage-3.0)



Explanation #1

ArchBang, Chakra and Toorox home folders are located on partition #13 DistroHood, but were not placed there during an install, they have to be mounted.


I then emailed you the clean results and a boot info script

ok, I will have a look. Thanks.






You asked if lib32 or lib64

Distro lib32 lib34
Puppy N N
Toorox Y Y
UbuntuStudio Y Y
Zorin Y Y
Slackware N Y
Chakra N Y
CtkArch N Y
ArchBang N Y
Ultimate Edition N Y

Thanks also for this check.

JASONFUSARO
July 25th, 2011, 02:19 AM
As I stand now I get a boot menu with Vista option higlighted and the time ticking, if I select an arrow down the timer stops and then it is stuck can't move to select any option, can press e to edit or ctrl-c to get to Grub > and back again but only to same stuck option.

I entered some commands but have not rebooted yet to see results, have been viewing threads and such.

YannBuntu
July 25th, 2011, 02:47 AM
Then FEAR set in!!! My Heart rate shot up I started to sweat all sorts of horrible thoughts raced through my head when I seen screenshot #1 especially when I got it twice!!

This is normal: you restored a generic MBR and chose to make it boot sda2:
http://ubuntuforums.org/attachment.php?attachmentid=198327&d=1311544220

Maybe this could have worked if you had installed the stage1 of your GRUB into sda2. Remark : you cannot do this action via Boot-Repair.


[QUOTE=JASONFUSARO;11082666]As I stand now I get a boot menu with Vista option higlighted and the time ticking, if I select an arrow down the timer stops and then it is stuck can't move to select any option, can press e to edit or ctrl-c to get to Grub > and back again but only to same stuck option.

Try to boot your live-CD , install Boot-Repair , and repair (default option should work fine, if not choose "Purge GRUB" in the Advanced options). And as explained before, DON'T select "Force GRUB".

JASONFUSARO
July 25th, 2011, 02:55 AM
[QUOTE=JASONFUSARO;11082219]Then FEAR set in!!! My Heart rate shot up I started to sweat all sorts of horrible thoughts raced through my head when I seen screenshot #1 especially when I got it twice!!

This is normal: you restored a generic MBR and chose to make it boot sda2:
http://ubuntuforums.org/attachment.php?attachmentid=198327&d=1311544220

Maybe this could have worked if you had installed the stage1 of your GRUB into sda2. Remark : you cannot do this action via Boot-Repair.




Try to boot your live-CD , install Boot-Repair , and repair (default option should work fine, if not choose "Purge GRUB" in the Advanced options).



Thats what I have done, just have not rebooted yet, thought I did it before but might have missed something.
Still scanning posts.

I am also getting ready to install to more Distros Zenwalk and Fusion Linux for the software design capabilities.

YannBuntu
July 25th, 2011, 03:23 AM
Also, from now : each time you use Boot-Repair, please tick the "Create BootInfo summary" in the Advanced Options, this will make such window appear:

http://ubuntuforums.org/attachment.php?attachmentid=198329&d=1311544220

Then, instead of sending me the /clean folders by email, you just need to give me the URL. Convenient isn't it ? :D

JASONFUSARO
July 25th, 2011, 07:03 AM
also, from now : Each time you use boot-repair, please tick the "create bootinfo summary" in the advanced options, this will make such window appear:

http://ubuntuforums.org/attachment.php?attachmentid=198329&d=1311544220

then, instead of sending me the /clean folders by email, you just need to give me the url. Convenient isn't it ? :d




will do

YannBuntu
July 25th, 2011, 04:27 PM
Hi
packages names have changed on the DEV PPA, so I updated the installation instructions:
http://ubuntuforums.org/showpost.php?p=11078448&postcount=46

sXeChris
July 25th, 2011, 07:11 PM
Excellent program -- just used it to get me out of a sticky situation.

YannBuntu
July 26th, 2011, 12:11 PM
Thanks sXeChris ! If you like Boot-Repair, you can ask its inclusion in official repositories here : https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/806291 :)

@all: I need help to test Boot-Repair v3 beta. Is there someone having Windows7 who is ok to do a little test ? :guitar:

dino99
July 26th, 2011, 02:32 PM
you get my "me too" for your great idea, go ahead and many thanks of course :)

wkulecz
July 27th, 2011, 02:48 PM
Worked perfectly to restore a cloned system that somewhere had a wrong UUID somewhere in the grub setup that I couldn't find.

Not only should this be in the repos, it should be on all future Ubuntu distribution disks!

YannBuntu
August 4th, 2011, 10:27 AM
@dino99 and wkulecz : thanks for your kind words. :)

@all : I am on the way to release Boot-Repair v3. To make it even better, I search volunteers to test it in 2 particular cases:
1) separate /boot partition
2) RAID disks

Please contact me if you use one of these two configurations and are ok for little tests. :D

YannBuntu
August 10th, 2011, 04:13 PM
New version now available !

For download instructions, see post#1.


Screenshots :
http://pix.toile-libre.org/upload/img/1312988896.png (http://pix.toile-libre.org/?img=1312988896.png)

http://pix.toile-libre.org/upload/img/1312988935.png (http://pix.toile-libre.org/?img=1312988935.png)

http://pix.toile-libre.org/upload/img/1312988963.png (http://pix.toile-libre.org/?img=1312988963.png)

http://pix.toile-libre.org/upload/img/1312988983.png (http://pix.toile-libre.org/?img=1312988983.png)

http://pix.toile-libre.org/upload/img/1312989003.png (http://pix.toile-libre.org/?img=1312989003.png)

|{urse
August 10th, 2011, 04:20 PM
I fix a crapload of ubuntu boxen in my shop, this totally saves me a billion keystrokes. THX

drs305
August 10th, 2011, 05:51 PM
Very nice improvement. Thanks YannBuntu

emarkay
August 10th, 2011, 08:25 PM
Hi manickaselvam,
.......
FOURTH STEP
.........
If it did not work, please open a new thread HERE (http://ubuntuforums.org/newthread.php?do=newthread&f=333) - - -

Note from page one #6 - the "HERE" only opens a generic new post - it's not adding to an existing post apparently. Is this correct?

Going to have to try this out in a few minutes - I added a new HD and had just completed a fully configured new WinXP. Apparently an old Lucid on the old volume has totally confused things. I reformatted that volume away, and reinstalled Lucid (twice) but I still I only get Grub Rescue prompt, and FIXBOOT and FIXMBR don't work.

This is my last hope before reinstalling EVERYTHING (Win and Lin) again..

Edit: Note that the Lucid LTS is now 10.04.3, this version here is 10.04.2, FYI. The Boot Repair I just downloaded also appears to be the old version, with the orange illustrations, not the bluish ones.

emarkay
August 10th, 2011, 09:05 PM
!@#$%^!!! This didn't work.
It scanned the system, then said it would repair the missing GRUB boot, and then gave me a "final confirmation" and then scanned the system again. I rebooted and I am sitll at:

"GRUB loading.
error: file not found.
grub rescue>"

I'll play around with it and if it screws things up, so what, I have another 5 or 6 hours ahead of me reinstalling Win and Lin... :(

Strange: booted to the 10.04.3 CD and looked at the new volume I installed earlier - it's volume name is a large list of characters: 990680ae-1356-4587-98ed-ee5d7535beb9, (the UUID?)and it says ext3/ext4 for filesystem type - I know I formatted that as ext4!

drs305
August 10th, 2011, 09:20 PM
!@#$%^!!! This didn't work.
It scanned the system, then said it would repair the missing GRUB boot, and then gave me a "final confirmation" and then scanned the system again. I rebooted and I am sitll at:

"GRUB loading.
error: file not found.
grub rescue>"


If you want to start a new thread and post the contents of RESULTS.txt we can take a quick look and perhaps save you the time of reinstalling everything. If you want to do this just post a link here to your new thread.

YannBuntu
August 11th, 2011, 03:23 AM
@|{urse : happy it helped :)

@emarkay : please boot again on your CD, connect internet, update the packages :

sudo apt-get update && sudo apt-get upgrade

in order to use the last version of Boot-Repair.

Try "First repair", if no success then "Second repair", and indicate us the URL that will appear. (this URL will contain the BootInfoSummary and the log in order to help us helping you :) )

DeadlyOats
August 11th, 2011, 06:45 AM
How do you get the menu from the first screenshot on top of the thread? When I launch the boot-repair I only get the second screenshot without any visible option to change...

I had the same problem...


Hi Heepie,

The full window below appears only if Boot-Repair detects Clean-Ubiquity MBR backups (https://launchpad.net/~yannubuntu/+archive/clean-ubiquity) (e.g. the 1st time you installed Ubuntu was via the Ubuntu Secured Remix (http://ubuntuforums.org/showthread.php?t=1615667), not a standard Ubuntu CD) on your computer.

That explained the reason for my problem...


... So you are in the 2nd case (no Clean-Ubiquity backup detected). You can first try to reinstall GRUB. If this does not fix your problem, try to purge GRUB (via Advanced Options).

That led me back to trying the secured ubuntu install cd and boot-repair again.

Here is the results of "boot info scrip" before I tried the purge grub method:


Boot Info Script 0.60 from 17 May 2011


============================= Boot Info Summary: ===============================

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos1)/boot/grub on this drive.
=> Windows is installed in the MBR of /dev/sdb.
=> Windows is installed in the MBR of /dev/sdc.

sda1: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 11.04
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda2: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:

sdb1: __________________________________________________ ________________________

File system: swap
Boot sector type: -
Boot sector info:

sdb2: __________________________________________________ ________________________

File system:
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: unknown filesystem type ''

sdb3: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:

sdc1: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files: /boot.ini /ntldr /NTDETECT.COM

============================ Drive/Partition Info: =============================

Drive: sda __________________________________________________ ___________________

Disk /dev/sda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 2,048 19,533,823 19,531,776 83 Linux
/dev/sda2 19,533,824 80,291,839 60,758,016 83 Linux


Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 78,292,992 80,291,839 1,998,848 82 Linux swap / Solaris
/dev/sdb2 70,275,072 78,292,991 8,017,920 83 Linux
/dev/sdb3 63 70,268,309 70,268,247 83 Linux


Drive: sdc __________________________________________________ ___________________

Disk /dev/sdc: 148.6 GB, 148597768192 bytes
255 heads, 63 sectors/track, 18065 cylinders, total 290230016 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 * 63 290,198,159 290,198,097 7 NTFS / exFAT / HPFS


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/sda1 398dec5b-1c90-4b8f-ba1e-435e6952a6de ext4
/dev/sda2 8e40df46-0fa8-41ab-b665-61e115c0f4b7 ext4
/dev/sdb1 ba6e2dec-1dbd-4a32-8a00-e9d423366062 swap
/dev/sdb3 96540cb3-2e74-4837-8bb0-c40b8a384c21 ext4 Tool Shed
/dev/sdc1 DC00E6C700E6A7AA ntfs

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sda1 / ext4 (rw,errors=remount-ro,commit=0)
/dev/sda2 /home ext4 (rw,commit=0)


=========================== sda1/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 2.6.38-10-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
linux /boot/vmlinuz-2.6.38-10-generic root=UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-10-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-10-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
echo 'Loading Linux 2.6.38-10-generic ...'
linux /boot/vmlinuz-2.6.38-10-generic root=UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-10-generic
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
echo 'Loading Linux 2.6.38-8-generic ...'
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-generic
}
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/sdc1)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(/dev/sdc,msdos1)'
search --no-floppy --fs-uuid --set=root DC00E6C700E6A7AA
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=============================== sda1/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de / ext4 errors=remount-ro 0 1
# /home was on /dev/sda2 during installation
UUID=8e40df46-0fa8-41ab-b665-61e115c0f4b7 /home ext4 defaults 0 2
# swap was on /dev/sdb1 during installation
UUID=ba6e2dec-1dbd-4a32-8a00-e9d423366062 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
--------------------------------------------------------------------------------

=================== sda1: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)

0.184913635 = 0.198549504 boot/grub/core.img 1
0.446308136 = 0.479219712 boot/grub/grub.cfg 1
1.934818268 = 2.077495296 boot/initrd.img-2.6.38-10-generic 1
1.255626678 = 1.348218880 boot/initrd.img-2.6.38-8-generic 2
1.317691803 = 1.414860800 boot/vmlinuz-2.6.38-10-generic 2
0.961071014 = 1.031942144 boot/vmlinuz-2.6.38-8-generic 1
1.934818268 = 2.077495296 initrd.img 1
1.255626678 = 1.348218880 initrd.img.old 2
1.317691803 = 1.414860800 vmlinuz 2
0.961071014 = 1.031942144 vmlinuz.old 1

================================ sdc1/boot.ini: ================================

--------------------------------------------------------------------------------
[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

--------------------------------------------------------------------------------

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown BootLoader on sdb2

00000000 5a cb cf e5 32 f1 17 cd 87 02 f8 44 f5 fb 84 ee |Z...2......D....|
00000010 4f 15 e0 bf b0 9a e9 2a 5e f1 77 61 9a 42 8d ce |O......*^.wa.B..|
00000020 5d 30 35 59 5e ba e3 fc c8 b5 be a0 7b 39 9a 33 |]05Y^.......{9.3|
00000030 6f 0a 5d a2 ff 77 dd 5f 1f b9 5b 71 3a 4c 9a 7e |o.]..w._..[q:L.~|
00000040 9e 30 46 ab b5 7f 3f 5a 18 71 58 80 f1 9b 81 65 |.0F...?Z.qX....e|
00000050 fc 32 6d 30 d1 8d d6 49 1c 9a 5d ca d3 cf 3e 90 |.2m0...I..]...>.|
00000060 3e 0b 6d 2b d4 16 38 7d b8 8a d2 b5 f1 ef 16 21 |>.m+..8}.......!|
00000070 d0 bf 06 08 e9 49 97 9e 1f 67 d4 53 83 42 17 f4 |.....I...g.S.B..|
00000080 f3 8c 9d 65 73 19 3a 69 9c 65 f9 49 05 2e 0b d7 |...es.:i.e.I....|
00000090 3d 0d dc e7 26 b3 bd d3 4d a2 03 84 17 91 c4 79 |=...&...M......y|
000000a0 96 af bb 09 dd 78 f1 d7 4c 1f 74 99 12 af 36 84 |.....x..L.t...6.|
000000b0 f0 e1 b5 5d e8 20 d0 17 f5 57 be fb bb bb ab b6 |...]. ...W......|
000000c0 d2 4f 68 d9 a6 9b 26 63 7b a4 f6 fb a5 49 bd ef |.Oh...&c{....I..|
000000d0 6b 72 4e 65 6e d2 03 52 ce 2c 4a 87 c9 0c b8 8f |krNen..R.,J.....|
000000e0 bf 7b e8 67 3a 40 bd dc c7 57 82 0f 5a d4 ee bb |.{.g:@...W..Z...|
000000f0 63 d9 6c c1 3b 59 3a 6f 31 7a 7c 66 34 a4 4a 66 |c.l.;Y:o1z|f4.Jf|
00000100 1c c1 b3 cb 6f 7c a9 d2 fe 39 dd 87 3a 42 cc ab |....o|...9..:B..|
00000110 22 6c 81 85 d2 32 f4 ad 7d a6 8d 90 10 ba b4 e7 |"l...2..}.......|
00000120 1b 6c f3 db 9d d2 7b 1f 6e 61 dc ea fb b6 f4 b1 |.l....{.na......|
00000130 27 3d ba 6f bb be c2 b9 87 7b aa bb de c6 f2 8d |'=.o.....{......|
00000140 2f 7a 7f 18 1a 71 11 2e 19 d3 a9 ef b6 d2 7b 5e |/z...q........{^|
00000150 61 d4 10 6f 5d 33 1e 7a 34 71 ef b0 ae 49 bc ca |a..o]3.z4q...I..|
00000160 48 c4 3a 43 fc cd 83 64 d0 89 46 f8 65 ee 57 df |H.:C...d..F.e.W.|
00000170 55 6b bc f6 53 97 af 73 a9 54 f7 a4 6f 6f 23 7d |Uk..S..s.T..oo#}|
00000180 8d ef 6b 53 d8 de a0 86 40 e7 55 73 84 ab e7 24 |..kS....@.Us...$|
00000190 73 db ab a7 73 bb 4d 3b d3 c6 ab 92 c2 28 e7 69 |s...s.M;.....(.i|
000001a0 dd f6 33 ee ae e2 dd ea f8 6d c3 8f 61 f3 a5 5f |..3......m..a.._|
000001b0 91 60 cd 84 8c 8f 69 e8 a8 e9 21 f4 99 1e 89 8e |.`....i...!.....|
000001c0 a2 e9 14 18 52 17 dd 5d 5e db e4 19 ba 4f be c6 |....R..]^....O..|
000001d0 f2 3f 5e 9b b2 5a 64 d9 13 3a dd 30 c9 d0 4f 5f |.?^..Zd..:.0..O_|
000001e0 72 13 46 e9 91 09 de 40 f7 ae a7 06 6f 8e 31 69 |r.F....@....o.1i|
000001f0 e7 df 74 9d 56 5e 38 50 53 4f 59 61 e5 3e c2 54 |..t.V^8PSOYa.>.T|
00000200


=============================== StdErr Messages: ===============================

unlzma: Decoder error


Here is the results of "boot info script" after the second time I ran boot repair in the live cd and changed the HDD boot order in the motherboard BIOS:


Boot Info Script 0.60 from 17 May 2011


============================= Boot Info Summary: ===============================

=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos1)/boot/grub on this drive.
=> Windows is installed in the MBR of /dev/sdb.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and uses an
embedded config file:

---------------------------------------------------------------------------
search.fs_uuid 398dec5b-1c90-4b8f-ba1e-435e6952a6de root
set
prefix=($root)/boot/grub---------------------------------------------------
-----------------------------.

sda1: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 11.04
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda2: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:

sdb1: __________________________________________________ ________________________

File system: swap
Boot sector type: -
Boot sector info:

sdb2: __________________________________________________ ________________________

File system:
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: unknown filesystem type ''

sdb3: __________________________________________________ ________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:

sdc1: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files: /boot.ini /ntldr /NTDETECT.COM

============================ Drive/Partition Info: =============================

Drive: sda __________________________________________________ ___________________

Disk /dev/sda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 2,048 19,533,823 19,531,776 83 Linux
/dev/sda2 19,533,824 80,291,839 60,758,016 83 Linux


Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 78,292,992 80,291,839 1,998,848 82 Linux swap / Solaris
/dev/sdb2 70,275,072 78,292,991 8,017,920 83 Linux
/dev/sdb3 63 70,268,309 70,268,247 83 Linux


Drive: sdc __________________________________________________ ___________________

Disk /dev/sdc: 148.6 GB, 148597768192 bytes
255 heads, 63 sectors/track, 18065 cylinders, total 290230016 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 * 63 290,198,159 290,198,097 7 NTFS / exFAT / HPFS


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/sda1 398dec5b-1c90-4b8f-ba1e-435e6952a6de ext4
/dev/sda2 8e40df46-0fa8-41ab-b665-61e115c0f4b7 ext4
/dev/sdb1 ba6e2dec-1dbd-4a32-8a00-e9d423366062 swap
/dev/sdb3 96540cb3-2e74-4837-8bb0-c40b8a384c21 ext4 Tool Shed
/dev/sdc1 DC00E6C700E6A7AA ntfs

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sda1 / ext4 (rw,errors=remount-ro,commit=0)
/dev/sda2 /home ext4 (rw,commit=0)


=========================== sda1/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 2.6.38-10-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
linux /boot/vmlinuz-2.6.38-10-generic root=UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-10-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-10-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
echo 'Loading Linux 2.6.38-10-generic ...'
linux /boot/vmlinuz-2.6.38-10-generic root=UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-10-generic
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
echo 'Loading Linux 2.6.38-8-generic ...'
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.38-8-generic
}
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos1)'
search --no-floppy --fs-uuid --set=root 398dec5b-1c90-4b8f-ba1e-435e6952a6de
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/sdc1)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(/dev/sdc,msdos1)'
search --no-floppy --fs-uuid --set=root DC00E6C700E6A7AA
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=============================== sda1/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=398dec5b-1c90-4b8f-ba1e-435e6952a6de / ext4 errors=remount-ro 0 1
# /home was on /dev/sda2 during installation
UUID=8e40df46-0fa8-41ab-b665-61e115c0f4b7 /home ext4 defaults 0 2
# swap was on /dev/sdb1 during installation
UUID=ba6e2dec-1dbd-4a32-8a00-e9d423366062 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
--------------------------------------------------------------------------------

=================== sda1: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)

2.141223907 = 2.299121664 boot/grub/core.img 1
6.239212036 = 6.699302912 boot/grub/grub.cfg 1
1.934818268 = 2.077495296 boot/initrd.img-2.6.38-10-generic 1
1.255626678 = 1.348218880 boot/initrd.img-2.6.38-8-generic 2
1.317691803 = 1.414860800 boot/vmlinuz-2.6.38-10-generic 2
0.961071014 = 1.031942144 boot/vmlinuz-2.6.38-8-generic 1
1.934818268 = 2.077495296 initrd.img 1
1.255626678 = 1.348218880 initrd.img.old 2
1.317691803 = 1.414860800 vmlinuz 2
0.961071014 = 1.031942144 vmlinuz.old 1

================================ sdc1/boot.ini: ================================

--------------------------------------------------------------------------------
[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

--------------------------------------------------------------------------------

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown BootLoader on sdb2

00000000 5a cb cf e5 32 f1 17 cd 87 02 f8 44 f5 fb 84 ee |Z...2......D....|
00000010 4f 15 e0 bf b0 9a e9 2a 5e f1 77 61 9a 42 8d ce |O......*^.wa.B..|
00000020 5d 30 35 59 5e ba e3 fc c8 b5 be a0 7b 39 9a 33 |]05Y^.......{9.3|
00000030 6f 0a 5d a2 ff 77 dd 5f 1f b9 5b 71 3a 4c 9a 7e |o.]..w._..[q:L.~|
00000040 9e 30 46 ab b5 7f 3f 5a 18 71 58 80 f1 9b 81 65 |.0F...?Z.qX....e|
00000050 fc 32 6d 30 d1 8d d6 49 1c 9a 5d ca d3 cf 3e 90 |.2m0...I..]...>.|
00000060 3e 0b 6d 2b d4 16 38 7d b8 8a d2 b5 f1 ef 16 21 |>.m+..8}.......!|
00000070 d0 bf 06 08 e9 49 97 9e 1f 67 d4 53 83 42 17 f4 |.....I...g.S.B..|
00000080 f3 8c 9d 65 73 19 3a 69 9c 65 f9 49 05 2e 0b d7 |...es.:i.e.I....|
00000090 3d 0d dc e7 26 b3 bd d3 4d a2 03 84 17 91 c4 79 |=...&...M......y|
000000a0 96 af bb 09 dd 78 f1 d7 4c 1f 74 99 12 af 36 84 |.....x..L.t...6.|
000000b0 f0 e1 b5 5d e8 20 d0 17 f5 57 be fb bb bb ab b6 |...]. ...W......|
000000c0 d2 4f 68 d9 a6 9b 26 63 7b a4 f6 fb a5 49 bd ef |.Oh...&c{....I..|
000000d0 6b 72 4e 65 6e d2 03 52 ce 2c 4a 87 c9 0c b8 8f |krNen..R.,J.....|
000000e0 bf 7b e8 67 3a 40 bd dc c7 57 82 0f 5a d4 ee bb |.{.g:@...W..Z...|
000000f0 63 d9 6c c1 3b 59 3a 6f 31 7a 7c 66 34 a4 4a 66 |c.l.;Y:o1z|f4.Jf|
00000100 1c c1 b3 cb 6f 7c a9 d2 fe 39 dd 87 3a 42 cc ab |....o|...9..:B..|
00000110 22 6c 81 85 d2 32 f4 ad 7d a6 8d 90 10 ba b4 e7 |"l...2..}.......|
00000120 1b 6c f3 db 9d d2 7b 1f 6e 61 dc ea fb b6 f4 b1 |.l....{.na......|
00000130 27 3d ba 6f bb be c2 b9 87 7b aa bb de c6 f2 8d |'=.o.....{......|
00000140 2f 7a 7f 18 1a 71 11 2e 19 d3 a9 ef b6 d2 7b 5e |/z...q........{^|
00000150 61 d4 10 6f 5d 33 1e 7a 34 71 ef b0 ae 49 bc ca |a..o]3.z4q...I..|
00000160 48 c4 3a 43 fc cd 83 64 d0 89 46 f8 65 ee 57 df |H.:C...d..F.e.W.|
00000170 55 6b bc f6 53 97 af 73 a9 54 f7 a4 6f 6f 23 7d |Uk..S..s.T..oo#}|
00000180 8d ef 6b 53 d8 de a0 86 40 e7 55 73 84 ab e7 24 |..kS....@.Us...$|
00000190 73 db ab a7 73 bb 4d 3b d3 c6 ab 92 c2 28 e7 69 |s...s.M;.....(.i|
000001a0 dd f6 33 ee ae e2 dd ea f8 6d c3 8f 61 f3 a5 5f |..3......m..a.._|
000001b0 91 60 cd 84 8c 8f 69 e8 a8 e9 21 f4 99 1e 89 8e |.`....i...!.....|
000001c0 a2 e9 14 18 52 17 dd 5d 5e db e4 19 ba 4f be c6 |....R..]^....O..|
000001d0 f2 3f 5e 9b b2 5a 64 d9 13 3a dd 30 c9 d0 4f 5f |.?^..Zd..:.0..O_|
000001e0 72 13 46 e9 91 09 de 40 f7 ae a7 06 6f 8e 31 69 |r.F....@....o.1i|
000001f0 e7 df 74 9d 56 5e 38 50 53 4f 59 61 e5 3e c2 54 |..t.V^8PSOYa.>.T|
00000200


=============================== StdErr Messages: ===============================

unlzma: Decoder error
unlzma: Decoder error


The difference is that instead of re-installing grub2 in sda, I had it installed in sdc. Notice there are two grub entries in the second results? At first I thought it didn't work, but I was still booting from sda. I had to go into the BIOS and change the boot HDD. In my motherboard BIOS, I changed the boot HDD from Maxtor [modelnumber] to AAR [forgot the rest of the name of the RAID array].

Once I did that, my PC was booting from sdc instead of sda, and the second grub2 entry. Now I can boot Ubuntu 11.04 (in sda) and WinXP (in sdc) from the grub2 in sdc.

It may be that some folks may need to change the boot order in their motherboard BIOS - if they have Windows and Ubuntu in different HDDs. I don't know for sure, but it's a thought.

Of coarse, I could be completely wrong about why my boot issue was fixed. I'd like to know what you see in my two results report to see if there is a better solution that I might have tried? I mean, would there have been a way to get WinXP to start with grub in sda and me not having to change the HDD boot order in the mobo BIOS? Also, will there be future problems because I have two grub 2's (one in sda and one in sdc)?

emarkay
August 11th, 2011, 10:58 PM
Thanks. My problem there turned out to be a bumblefinger in the BIOS settings. I "thought" HDD-1 was the first Hard Drive in the sequence (after I messed with it earlier in the day to check it) and after I finally looked again there, I found that there was a HDD-0, separate and at the top of the list, away from the other HDDs.

So it was still finding whatever remnants survived a format of the old GRUB2 on HDD-1, instead of finding one of the many reinstalled Win MBRs on HDD-0.

I have since spent my day in the corner with the Dunce hat on...

YannBuntu
August 12th, 2011, 09:34 AM
Hello


I had to go into the BIOS and change the boot HDD.

The last version of Boot-Repair would have solved your problem (by installing GRUB in all your disks).

By the way, I recommend you download the new Ubuntu Secured CD (I updated it yesterday, see https://help.ubuntu.com/community/UbuntuSecuredRemix )


will there be future problems because I have two grub 2's (one in sda and one in sdc)?

No problem I think.

@emarkay: so everything is fine now?

@boot experts: do you know any cases where installing grub-pc on a disk can cause problems ? (EFI?)

arclance
August 12th, 2011, 10:03 PM
The new 32-bit version of Boot-Repair on the live-cd and installed from the package fails with this error message.


http://ubuntuforums.org/%3Cimg%20src=%22http://i.imgur.com/lZaXX.png%22%20alt=%22%22%20title=%22Hosted%20by%2 0imgur.com%22%20/%3E
http://i.imgur.com/lZaXX.png Please use this software in a 64bits session.



I could not find any older versions so I am unable to use this program at all.

YannBuntu
August 15th, 2011, 04:35 AM
Hello , and welcome among us :)


Please use this software in a 64bits session.

If you don't have any Ubuntu 64bits CD, you can download Ubuntu Secured 64bits here (http://sourceforge.net/projects/ubuntu-secured/files/ubuntu-secured-remix-11.04-64bits.iso/download). It contains Boot-Repair out-of-the-box.
(see https://help.ubuntu.com/community/Boot-Repair for more information)

arclance
August 15th, 2011, 05:51 AM
Hello , and welcome among us :)





Please use this software in a 64bits session.




If you don't have any Ubuntu 64bits CD, you can download Ubuntu Secured 64bits here (http://sourceforge.net/projects/ubuntu-secured/files/ubuntu-secured-remix-11.04-64bits.iso/download). It contains Boot-Repair out-of-the-box.
(see https://help.ubuntu.com/community/Boot-Repair for more information)

I take this to mean Boot Repair is a 64 bit only program.
I tried the Ubuntu 64 bit CD before it would not run on my system.

If Boot Repair only works in a 64 bit environment why do your instructions in the first post say to use the 32 bit Ubuntu Secured disk to repair a 32 bit install?



Get a CD including Boot-Repair:
- If the system you want to repair is 32 bits, get Ubuntu Secured (32bits) (http://ubuntuforums.org/showpost.php?p=10084551&postcount=1)
- If the system you want to repair is 64 bits, get Ubuntu Secured 64bits (http://ubuntuforums.org/showpost.php?p=10084551&postcount=1)


If Boot Repair only works in a 64 bit environment why is it included in the 32 bit Ubuntu Secured disk?
Why do you offer a 32 bit package of Boot Repair if it only works in a 64 bit environment?

I was able to repair my boot loader from the terminal using the Ubuntu 32 bit live disk following the instructions on the purge and reinstall method found here.
https://help.ubuntu.com/community/Grub2#Rescue%20Mode%20%28%27%27grub%20rescue%3E%27 %27%29%20Booting

YannBuntu
August 15th, 2011, 07:11 AM
Hello,
happy you found a solution :)
To answer your questions, Boot-Repair is not 64bits-only. It can be used both in 32bits and 64bits session, but when run from a 32bits session it cannot repair the GRUB of a 64bits Linux (that's a limitation of the chroot system).
Generally people who use only 64bits systems/CD, or 32bits systems&CD so there is no problem.
But thanks to your feedback, I improved Boot-Repair so that the BootInfo Summary now can be created in all situations. Thanks :KS

aparigraha
August 17th, 2011, 12:28 AM
Just wanted to show my complete appreciation for this little graphical tool. It will save me many hours of time, and it will also let people with very little knowledge of Linux do everything themselves.

Thank you YannBuntu

YannBuntu
August 17th, 2011, 05:57 AM
@aparigraha : thanks for your kind words :)

@all : anyone using GPT / EFI / UEFI disk willing to help (need the result of BootInfo summary, takes 5 minutes) ?

ProNux
August 17th, 2011, 01:28 PM
Magandang gabi Pronux :D



Just for my information, please can you send me (yannubuntu ATT gmail DOTT com) screenshots of how you "enable" your partition ?



First it should be translated in main languages. Could you help with tagalog please? (online (https://translations.launchpad.net/boot-repair) or via a po file that you send me by email (https://sourceforge.net/projects/os-uninstaller/files/po.tar.gz/download) )


@all: of course anyone can help by translating !
:)

Bro, I just read your message. What I mean by "enable" is format & mount a free space at Windows 7 Disk Manager. My dual boot was working well beforehand while I have a non-partitioned free space on my HD. I opened Windows Disk Manager and I formatted/mounted the free space. After reboot, the GRUB won't show up.

arclance
August 18th, 2011, 03:07 AM
@all : anyone using GPT / EFI / UEFI disk willing to help (need the result of BootInfo summary, takes 5 minutes) ?

Sure I can do that, I have both boot and non-boot GPT disks.
Just explain how you want me to do it.

YannBuntu
August 18th, 2011, 04:36 AM
@ProNux : ok, thank you. And happy to know that Boot-Repair solves this situation too.
If you have 5 minutes to help, here is the direct link to translate Boot-Repair in Tagalog (https://translations.launchpad.net/boot-repair/trunk/+pots/cleancommon-translations/tl/+translate). Thanks! :KS

@arclance : please can you: 1) Open Boot-Repair 2) Click on "Avanced Options" 3) Unselect all options 4) Select "Create BootInfo" 5) Click "Apply" 6) Send me the URL . Thanks for your help. :guitar:

ProNux
August 18th, 2011, 05:14 AM
@ProNux : ok, thank you. And happy to know that Boot-Repair solves this situation too.
If you have 5 minutes to help, here is the direct link to translate Boot-Repair in Tagalog (https://translations.launchpad.net/boot-repair/trunk/+pots/cleancommon-translations/tl/+translate). Thanks! :KS

@arclance : please can you: 1) Open Boot-Repair 2) Click on "Avanced Options" 3) Unselect all options 4) Select "Create BootInfo" 5) Click "Apply" 6) Send me the URL . Thanks for your help. :guitar:

I'm glad & interested to help with the translation. Thanks for the link. I will provide soon.

YannBuntu
August 18th, 2011, 08:17 AM
thanks !

YannBuntu
August 19th, 2011, 02:23 AM
Boot-Repair now manages separate /boot partitions ! :guitar:

http://pix.toile-libre.org/upload/img/1313715508.png (http://pix.toile-libre.org/?img=1313715508.png)

drs305
August 20th, 2011, 03:00 PM
Yanni,

Thanks for continually improving your app. If I could make a suggestion - in your signature line you could make a link of the word "Wiki".

I'm not saying we are lazy, but providing a link to click might increase the chances that your viewers would go to your Wiki page. ;-)

Darkstar85
August 21st, 2011, 03:39 PM
Great little tool for my pc repair kit Yanni, the best part is that any reasonably smart user can fix their own issues with this little tool. My pc fix count is now up to 3 with this tool, and I've found no bugs so far, the MBR option is very handy for sorting out rootkit issues when used with live cd and clamtk.
My only caveat is that for those new to the linux world you should include a note that windows will want to run chkdisk upon it's startup. If this is already in the wiki I have overlooked it.
Love the work and hope to see more from your marvelous mind in the future.

arclance
August 22nd, 2011, 04:59 AM
Boot-Repair does not work on my laptop either same "please run in a 64bits environment" error. I have no 64 bit OS on my laptop or desktop. Does it think my 32bit OS's are 64bit for some reason? The only thing that works is make boot-info summary.

jrussell88
August 22nd, 2011, 01:09 PM
Hi Yann, this looks like a great tool.

Unfortunately I'm having some problems with it.

I installed the latest stable version 2.7-0ppa57~natty under an Ubuntu 11.04 LiveCD.

When First Repair reported it couldn't fix the problem I tried Second Repair

As an aside, this produces a series of error messages on fairly full, but still around 1Gb or so free, partitions which are not involved in either booting or the installation whiose Grub2 menu I am trying to repair. For example:

The sdb10 (Microsoft Windows XP) partition is nearly full. This can prevent to start it. Please use the file browser that just opened to delete unused files (or transfer them to another disk). Close this window when you have finished.

Then:

The sdb10 (Microsoft Windows XP) partition is still full. This can prevent to start it (e.g. you may get a Power Manager error).
After clicking OK until I got rid of these messages Software Sources opens and a 'software-properties-gtk' dialog box pops up asking to 'Install software additionally or only from these sources?' 'Replace' - 'Cancel' - 'Add', along with a list of software sources - third-party and Canonical - all of which I already have.

I press either 'Add' or 'Replace' and then 'Close' and 'Reload' the Software Sources.

Boot-Repair then returns the error message:

'Please enable a repository for the [grub-pc] package in your Software Sources. Then try again.' OK
and closes. Grub-pc is installed and up-to-date. I have all the Canonical and many other software sources enabled but I haven't found any way past this error - which doesn't make a lot of sense to me.

Can anyone suggest a way forward?

Thanks!

jrussell88
August 22nd, 2011, 01:12 PM
By the way my installation is Ubuntu 10.10 x64 and I'm using an Ubuntu 11.04 x64 LiveCD.

YannBuntu
August 23rd, 2011, 03:01 PM
@all: if you have 5 minutes, please help translating Boot-Repair in your language : https://translations.launchpad.net/boot-repair/trunk

@Darkstar85: thanks for your kind words. Yes Windows generally performs a chkdsk after Boot-Repair's use. I don't know if it is systematic, and I don't find it dangerous/surprising so I did not add any warning.

@arclance : please indicate your BootInfo URL so that we can check. For the moment, I recommend you burn and use Boot-Repair-Disk, so that you can choose the "64bits session" on start-up.

@jrussell88: The "XP partition is still full" message means you have <3% empty space, but it is not a problem if XP works correctly. The Software Sources which opened is indeed the sources of the Ubuntu you wish to repair. Please run the "First Repair", but this time select "Create BootInfo" in the Advanced Options and indicate the URL please.

jrussell88
August 24th, 2011, 12:08 AM
Thanks Yann, I ran First Repair and emailed the URL to you.

jrussell88
August 24th, 2011, 12:15 AM
And the First Repair was successful this time! So problem solved somehow - thanks.

YannBuntu
August 24th, 2011, 01:21 AM
Splendid :D

djallalnamri
August 26th, 2011, 02:32 AM
hello
i have 3 hdd
os installed on 1st one:
-ubuntu 8.04
-winxp
os installed on 2nd one:
-ubuntu 10.04
-win 7
os installed on 3rd one:
-ubuntu 11.04

i have installed win 7 after winxp
now whether i boot with 1st or 2nd hdd ... it always starts with win 7
and when i boot with 3rd hdd ... there's a grub splash-screen (grub 1.98) which allows me to start with any of the 3 ubuntu versions mentioned above
there's an old win 7 entry which doesn't work

how can boot-repair be of any assistance in this case ???

YannBuntu
August 26th, 2011, 01:40 PM
Hello djallalnamri,

Boot-Repair should be able to give you access to all your operating systems.

The default settings ("First repair") will reinstall GRUB in the MBR of all your disks, so that the disk on which your BIOS boots does not matter. You can also go in the "Advanced options" in order to choose to install GRUB only in the MBR of one disk.

If you are not sure, tick the "Create BootInfo" in the Advanced Options and indicate us the resulting URL.

djallalnamri
August 27th, 2011, 02:30 AM
hello
first thanks for reply
this is the URL :
http://pastebin.com/QZFR6TRD

YannBuntu
August 27th, 2011, 06:23 AM
Hi djallalnamri
i saw you use French system, let's continue in French by email. ;)

ottosykora
August 27th, 2011, 07:59 AM
@YannBuntu

Q1: can I replace grub2 installed in the root partition with legacy grub? respective can I install grub legacy with it in root partition?

note: the installation of grub2 into root partition is not best thing apparently, if parts of the grub get moved let say on major upgrades etc, system gets unbootable, grub legacy seems to be little bit more stable here.

Q2: can I install grub to a dedicated grub partition (not to confuse with boot partition)

YannBuntu
August 27th, 2011, 11:16 AM
Hi ottosykora,

R1: no for both questions. Contrary is possible (replace GRUB1 by GRUB2). GRUB Legacy is not supported any more, so Boot-Repair focuses on GRUB2. Therefore, Boot-Repair can do (the "OS by default" option) a reinstall+update of GRUB Legacy on condition that its package is already installed.

I confirm that installing GRUB on root partition is not recommended by GRUB developers.

R2: what do you call a dedicated grub partition ?

ottosykora
August 27th, 2011, 11:52 AM
Hi ottosykora,

R1: no for both questions. Contrary is possible (replace GRUB1 by GRUB2). GRUB Legacy is not supported any more, so Boot-Repair focuses on GRUB2. Therefore, Boot-Repair can do (the "OS by default" option) a reinstall+update of GRUB Legacy on condition that its package is already installed.

I confirm that installing GRUB on root partition is not recommended by GRUB developers.

R2: what do you call a dedicated grub partition ?

ok, pitty, as this procedure to replace the grub2 with grub legacy is always a time consuming after each install.
Could I put this function (replace grub2 with grub legacy) on a wish list?
Particularly needed to purge grub2 and install grub legacy.
It is very important, when many os are on one computer and linux systems have to be chainloaded. The use of the current grub2 is risky in such case, as it gets easy damaged. And there are AFAIK no real alternatives except Lilo, which needs again reconfig manually after each kernel change etc. Or do you know any alternatives to work reliably?

Dedicated grub partition, well I call it grub, but it is not an actual boot partition to any particular system, it just holds parts of grub and menu for chainloading the rest. It has no kernels in it etc.

YannBuntu
August 27th, 2011, 12:13 PM
How do you create this kind of "grub partition" ?

For my information, why do you chainload ? what is your main bootloader?
personally I just put GRUB2 in the MBR and in the rare cases I have to update it, I do it in 1 click with Boot-Repair ! (just run Boot-Repair and click Apply)

ottosykora
August 27th, 2011, 12:36 PM
How do you create this kind of "grub partition" ?

For my information, why do you chainload ? what is your main bootloader?
personally I just put GRUB2 in the MBR and in the rare cases I have to update it, I do it in 1 click with Boot-Repair ! (just run Boot-Repair and click Apply)

ok the grub partition is created by any partitioning tool as gparted or so.
Systems wehere I use it, i installed the grub legacy there with first part in mbr and chainload from there with most simple menu.lst diferent things, like w98, dos6.22, w7, ubuntu , fedora, debian etc.
To install the grub there, I used partially copy/paste from other system to make it simple and activated all kind of with the supper grub disk (legacy).
I do not load from there any particular kernels or other details, just use the hide/unhide for primary windows boot and also most simple menu.lst entries for linux which do not need to change except I delete one system completely, e.g.:
title Debian Leny
root (hd0,13)
chainloader +1

This way I do not need to remember which linux partition actually contains the grub files and I can delete any of the distros and the rest is still operational without any tricks.

Otherwise I use also on some older computers the bootmagic from powerquest and on some more recent others acronis .
I know also acronis has some problems, but it is comes out of the box install/unistall with a mouse click, does the job, no hassle with strange syntax in config files and such. (We have 2011 today and so Iexpect all work from intuitive gui straight away).

I also have on one older computer with bootmanager from XP loading knoppix and I used to have one with w7 loading knoppix too.
In both cases this is in fact a chainloding where loader is needed in the actual partition or os own boot partition.


And fine, you put the grub2 in mbr, but where is the rest of the grub then ? In which partition if I have 6 os installed?
I think as ususal, in the last one installed?

arclance
August 27th, 2011, 04:53 PM
@arclance : please indicate your BootInfo URL so that we can check. For the moment, I recommend you burn and use Boot-Repair-Disk, so that you can choose the &quot;64bits session&quot; on start-up.

I figured out the problem I had. Grub will not boot into LVM2 partitions until the are manually mounted in ubuntu first.
After doing that and running update-grub I can boot into the Fedora 14 partion on my laptop.

Here is the Bootinfo from before mounting the LVM2 partion
http://paste.ubuntu.com/672128/
and after
http://paste.ubuntu.com/673376/

I don't think a boot disk is a good idea for me because the disk drive in my laptop is starting to fail and it has been outputting corrupt data recently.
Is it possible to make a usb thumbdrive boot a 64-bit OS by using a 32-bit OS? The last time I tried with your 64-bit boot repair disk it did not work, it did not boot at all.

YannBuntu
August 28th, 2011, 02:27 AM
@ottosykora: ok, thank you. I knew someone-else who did the same as you, but he ended using GRUB2 in the MBR, because Legacy did not recognize some of his OS.
When you put GRUB2 in the MBR, just put the rest in one of your Ubuntu or Debian-derivative OS (preferably the one you use the most). E.g. if you have 5 OS and among them your main OS in Ubuntu11.04, just install Boot-Repair in Ubuntu11.04, and each time you want to update your menu run it and click "Apply", that's it. No need for separate partition, or manual file editing.

@Arclance: for 64bits PC, Boot-Repair must be used in a 64bits session (Ubuntu Secured 64bits (https://help.ubuntu.com/community/UbuntuSecuredRemix) for example). Also, please update Boot-Repair before running it, as there is beta GPT and LVM support in last versions.

arclance
August 28th, 2011, 02:59 AM
@Arclance: for 64bits PC, Boot-Repair must be used in a 64bits session (Ubuntu Secured 64bits (https://help.ubuntu.com/community/UbuntuSecuredRemix) for example). Also, please update Boot-Repair before running it, as there is beta GPT and LVM support in last versions.

Boot-Repair does not work on my laptop either same "please run in a 64bits environment" error. I have no 64 bit OS on my laptop or desktop. Does it think my 32bit OS's are 64bit for some reason? The only thing that works is make boot-info summary.

My laptop and desktop are both 32bit. according to your instructions in the first post I should be using the 32bit Ubuntu Secured Disc/Version.

As I said in my previous post the DVD drive in my laptop is failing and does not properly read disks anymore so burning a 64bit disk is not an option for my laptop.
I previously tried to make a bootable thumb drive with 64bit Ubuntu Secured on it but both my laptop and desktop would not boot from it.

ottosykora
August 28th, 2011, 05:32 AM
When you put GRUB2 in the MBR, just put the rest in one of your Ubuntu or Debian-derivative OS (preferably the one you use the most). E.g. if you have 5 OS and among them your main OS in Ubuntu11.04, just install Boot-Repair in Ubuntu11.04, and each time you want to update your menu run it and click "Apply", that's it. No need for separate partition, or manual file editing.



this is exactly what we are supposed to do, is suitable for one linux , but the rest should be loaded from one linux to the other.
*It is exactly what I wish to avoid if possible somehow.*

I can not understand why someone could develop such complex system in first. My whole computer is then becoming dependent on one of possibly many operating systems installed. If this gets broken (it will definitely) the whole computer is stopped.
When loading the individual kernels directly, well this will give crazy menu when having at least two last kernels in each linux. The alternative would be chainloading all others, this again is very unstable and we are back to the initial set up.
Grub2 is too fragile, difficult to manage (at least for me) and this is why you had to design this surely helpful tool after all.
If grub2 was anything working properly, nobody would need your tool.


So still I would be happy if you could include in your tool the installation of grub legacy and purging grub2 as this is essential task for half stable central stored bootmanager of what ever make.

YannBuntu
August 28th, 2011, 04:00 PM
@arclance : Boot-Repair thought you had a 64bits Ubuntu because you have 64bits librairies (which is AFAIK rare in a 32bits OS). Now I corrected this point, so you should be able to use last version of Boot-Repair in a 32bits session.

@ottosykora: purging GRUB2 is already possible (it's the first part of the Purge option), but currently you will have to install Legacy manually. I may add a "reinstall Legacy" option when I have time, please create a "wishlist" bug here (https://bugs.launchpad.net/boot-repair).

YannBuntu
September 3rd, 2011, 07:12 AM
Dear all,
Launchpad takes several hours before accepting updates, so before using Boot-Repair please make sure all icons on the following page are green : https://launchpad.net/~yannubuntu/+archive/boot-repair/+packages

Regards

pante
September 3rd, 2011, 02:55 PM
I just downloaded the CD and noted that the default wallpaper has a speaker labeled "Microsoft". Is this a bug?:lolflag:

YannBuntu
September 3rd, 2011, 04:25 PM
OMG ! :lolflag:

Even if it is mainly aimed at recovering access to Debian, Ubuntu and derivatives, Boot-Repair-Disk can also help recovering access to Windows... ;)

By-the-way, any wallpaper proposal is welcome :popcorn:

mosaic2s
September 4th, 2011, 06:43 AM
Install and run Boot-Repair in Ubuntu (in case you can't burn a CD):
just type in a Terminal:

Code:
sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update && sudo apt-get install -y boot-repair && boot-repair
Boot-Repair can be installed & used from any Ubuntu session (normal session, or live-CD, or live-USB). PPA packages are available for Ubuntu 10.04, 10.10, 11.04 and 11.10.

This method works best.

The download ISO file did not work on two comps.

YannBuntu
September 4th, 2011, 12:37 PM
Hi mosaic2s,
Boot-Repair automatically updates itself at start-up (from its PPA).
Yesterday the PPA was broken during ~15 hours (because Launchpad took time to accept an update), the consequence was that Boot-Repair main window (the one with the big logo) did not appear. If you experienced this problem, please retry with your CD the problem should have disappeared.
If you experienced a different problem, and still experience it today, please describe it more accurately.

regards

mosaic2s
September 4th, 2011, 04:28 PM
I downloaded the boot-repair-disk as ISO on 2 different days. One was 95mb, another 336mb from sourceforge.
Anyhow, assuming that 95mb was error in someway, I prepared the USB stick using the ISO file. First through tuxboot, then through USB DISK CREATOR utility within ubuntu 10.04.

The USB stick booted - and got stuck at
boot:

no response from the comp. tried second comp - same result. tried another pen drive, same response.

then I booted through CD and installed the boot-repair app. small app - downloaded quickly, and worked effectively on the hdd. I finished the work on 2 comps within 10 min.

Thanks a lot for keeping a close watch on our comments.

YannBuntu
September 5th, 2011, 02:30 AM
Hi mosaic2s,

First I recommend you always check the md5 of the ISO you download, not only Boot-Repair-Disk but also other Ubuntu ISOs.
The md5 of Boot-Repair-Disk ISO can be found by clicking on the (i) button of this page: https://sourceforge.net/projects/boot-repair-cd/files/

(on this page you will also see that the ISO is about 350Mo ;)

To calculate the md5 of your ISO, you can use the Check-File-Integrity tool: http://bipede.info/bipede/index.php?check-iso-devient-check-file-integrity

Second point: USB DISK CREATOR utility within Ubuntu cannot create USB-disk of Debian. As Boot-Repair-Disk is based on Debian, you will have to use another tool, such as :
- Lili USB Creator (http://www.linuxliveusb.com/), to be used from Windows only
- or UnetBootin : can be used from Ubuntu (install the unetbootin package) or from Windows (http://unetbootin.sourceforge.net/)

YannBuntu
September 5th, 2011, 04:06 AM
Hello, I slightly simplified the interface, so that repair is now even faster: just 1 click !!!

http://pix.toile-libre.org/upload/img/1315191717.png (http://pix.toile-libre.org/?img=1315191717.png)

Blasphemist
September 5th, 2011, 09:38 PM
I have been using this tool Yann and do very much like it. Thanks for your work!

I ran into something today that made me wonder. I haven't yet figured it out but I'll bring it to your attention anyway. I have a number of Ubuntu based and other distros installed on this laptop. One of them is Oneiric and today I did an update of that while it was the controlling grub. I last installed grub using this tool and did use the feature of adding a kernel option.

When today's software update ran it again updated the kernel and did its update-grub process. I got a grub-pc error about a modified grub config file. One of my options was to have it show me the old and new files but choice of mine seems to have been ignored as it didn't display the files. That is one reason that I don't have this figured out yet fully.

I'll keep using this and will watch for any further occurrence of this. I'm in the process of making some changes to optimize and clean up my grub for a bunch of distros so I will be able to test this further.

critin
September 6th, 2011, 03:09 AM
My ubuntu lesson for the day.

Thank you for this tool! I finally wised up and put it into my live usb this morning when I lost my grub. I didn't realize I could simply add it to a live distro. Now as long as I don't forget which usb stick it's on and copy over it, I'm all set. I wish it was pre-installed to iso's, but this works just as well now that I know it. (I already had it on my permanent install to use after installing new iso's)

Thanks YannBuntu! It's a very useful tool.

YannBuntu
September 6th, 2011, 03:39 AM
Hello!


I wish it was pre-installed to iso's

Indeed Boot-Repair is already pre-installed in several distros :
- Ubuntu Secured (https://help.ubuntu.com/community/UbuntuSecuredRemix) : an Ubuntu CD with Boot-Repair and 2 other useful tools
- Boot-Repair-Disk (http://ubuntuforums.org/showthread.php?t=1831869) : a rescue CD
- Hybryde (http://www.hybryde.org) : a distro that allows to change DE in 1 click without unlog !


I have been using this tool Yann and do very much like it.

Happy it helps!


it didn't display the files.

This is not related with Boot-Repair: the window asking if you want to keep the old conf file is normal (i think it appears each time grub-pc package is updated, on condition that you modified your /etc/default/grub, which is the case for you because you added a kernel option). But it should have displayed the 2 files, so I recommend you open a bug towards grub-pc (i don't remember the name of the configuration window that proposes "keep old or new conf file?", maybe "debconf" or something..).

mosaic2s
September 6th, 2011, 11:47 AM
Hi mosaic2s,

First I recommend you always check the md5 of the ISO you download, not only Boot-Repair-Disk but also other Ubuntu ISOs.
The md5 of Boot-Repair-Disk ISO can be found by clicking on the (i) button of this page: https://sourceforge.net/projects/boot-repair-cd/files/

(on this page you will also see that the ISO is about 350Mo ;)

To calculate the md5 of your ISO, you can use the Check-File-Integrity tool: http://bipede.info/bipede/index.php?check-iso-devient-check-file-integrity

Second point: USB DISK CREATOR utility within Ubuntu cannot create USB-disk of Debian. As Boot-Repair-Disk is based on Debian, you will have to use another tool, such as :
- Lili USB Creator (http://www.linuxliveusb.com/), to be used from Windows only
- or UnetBootin : can be used from Ubuntu (install the unetbootin package) or from Windows (http://unetbootin.sourceforge.net/)

The file size has changed indeed. that must be the problem at my end. however to download 350mb and then start over - it is easier to boot from existing CD and then install the boot-repair utility - takes hardly 5 min.

I used 2 methods to create live-usb - one from ubuntu - other tuxboot. both yielded same results. unetbootin has been modified to create tuxboot. it works for clonezilla. and should work for this also.

YannBuntu
September 6th, 2011, 12:54 PM
I did not know Tuxboot. Thanks for the feedback, i'll try it when i have time.

lswartz
September 10th, 2011, 10:30 PM
Thank you very much. It worked perfectly after I installed Win 7 on my computer with 10.04.


:D:D:D

uaebuntu
September 16th, 2011, 02:45 PM
Domo Origato YannBuntu!

I had a screwed up Grub2 after a software upgrade on my MINT 11 64bit system, tried a manual repair and a purge and reinstall of GRUB with no luck.

Installed your Boot Repair utility into my Mint Live CD and it worked like a charm.

candtalan
September 18th, 2011, 08:14 AM
Really good tool Thanks!
I used the live CD

boot-repair-disk
http://sourceforge.net/p/boot-repair-cd/home/Home/

CosmicVoyager
September 19th, 2011, 10:12 AM
Greetings,

Is there a version of Boot Repair CD that uses the 3.0 kernel from Ubuntu 11.10 beta? A beta version?

Thanks

ottosykora
September 19th, 2011, 11:42 PM
@YannBuntu

OK, one + for you today

I just have used your disk with success on small HP where I needed to restore generic mbr for w7 boot.

But still wish you include the 'replace grub2 with grub legacy' function as this is needed in many cases.
Actually I did it many times 'by hand', but just today on that small HP netbook I made a typo and screwed partially.

But now all is fine again.

Blasphemist
September 19th, 2011, 11:55 PM
@YannBuntu

OK, one + for you today

I just have used your disk with success on small HP where I needed to restore generic mbr for w7 boot.

But still wish you include the 'replace grub2 with grub legacy' function as this is needed in many cases.
Actually I did it many times 'by hand', but just today on that small HP netbook I made a typo and screwed partially.

But now all is fine again.

I'm curious about why you sometimes need to downgrade grub. Could you explain that to me. See like that wouldn't be a good idea for any buntu flavor at least because of the kernel update process.

Blasphemist
September 20th, 2011, 03:21 AM
Greetings,

Is there a version of Boot Repair CD that uses the 3.0 kernel from Ubuntu 11.10 beta? A beta version?

Thanks

Related to this, I could swear I downloaded an 11.10 secured cd last week and can't seem to find it now. Is there one or is my memory all the way gone?


Thanks

ottosykora
September 20th, 2011, 07:30 AM
many situations ask for installation of complete bootloader into the actual root partition.
This is when someone has more operating systems and uses boot manager partition and chainloads from there, or any other chainloading by use of third party boot manager, or windows boot manger or similar situation where the first part of grub should not be in mbr and bootsector of the drive.

Apparently the grub2 files are much bigger then legacy grub and there fore the can be damaged when moved. I did experience this after distro upgrades.
During installation of grub2 into partition by hand, even warning given by the developers of it is displayed

Problems never appear with grub legacy.

At the last install , I use boot manager of windows, so grub has to go to partition and has no other function there then boot the own system there.
Here it is clearly more stable then grub2.

ottosykora
September 20th, 2011, 12:03 PM
@YannBuntu

why it is needed to have internet connection during the work with the repair disk?

Could it not be done so that all essential components are on the disk itself?

Arbiel
September 22nd, 2011, 10:14 AM
Hi Yann

I fully appreciate your piece of software. The tutorial you wrote about how to use it is however lacking some informations :
when restoring the MBR, the options are sort of
mrc
mbr_c
mbr_f
altmbr
and so on.

Can you, please, include in you tutorial, the meaning of this various options

Arbiel

YannBuntu
September 22nd, 2011, 12:10 PM
Hi all, thanks for your kind messages. Just quick answers because i'm on holidays with very few pc access.

@ottosykora: boot-repair can work off-line as it contains all important packages, but it is better to connect to internet in order to get the very last updates.

@Arbiel: the default option (mbr) is the one to try first, and it works in all cases i tested. If it does not work, please tell me and try the following choices.

@Blasphemist: i did not create a Ubuntu Secured 10.10 yet, but i will do so when 10.10 is released.

Arbiel
September 22nd, 2011, 02:00 PM
Hi Yann

J'espère que tes vacances sont agréables, et ensoleillées, ce qui n'a pas vraiment été le cas en Normandie cet été.

The idea was just that, when confronted with the choice that he does not understand, the user may get a little confused. I eventually chose the mbr entry, and it did just run fine.

If this could please you, if you explain me what the various option mean, I'll make a pleasure to help you with the documentation, in both languages.

Arbiel

HutchMeister
September 30th, 2011, 12:02 PM
After starting Boot-Repair I'm seeing the message "Enabling RAID. This may require several minutes...".

It's been enabling for more than 30 mins, I suspect something may be wrong, any ideas?

YannBuntu
September 30th, 2011, 02:08 PM
@HutchMeister: this is not normal. Please open a terminal and run the following commands:

sudo fdisk -l

sudo parted -l

sudo os-prober
please indicate their output and also the output of this script (http://bootinfoscript.sourceforge.net).

PayPaul
October 8th, 2011, 06:30 PM
This may be a real dummy question but I'll fire away. Can the boot repair cd be used on a Wubi Installation? Can it also restore a wubi installation before some changes were made?

YannBuntu
October 9th, 2011, 01:48 AM
Hello


This may be a real dummy question but I'll fire away. Can the boot repair cd be used on a Wubi Installation? Can it also restore a wubi installation before some changes were made?

There is no silly question ;)
Currently, most of Wubi problems won't be solved by Boot-Repair.
I need help from Wubi experts to add such features.

YannBuntu
October 9th, 2011, 02:29 AM
This morning, I had the surprise to see that someone had added the following comments in https://help.ubuntu.com/community/Boot-Repair, so I would like to say a word about them :


Security Warning

The instructions below should be disregarded due to unacceptable security vulnerabilities. In particular, the currently posted code for Boot-Repair will do the following, all of which are unacceptable:

1. It downloads and executes scripts (as root), from two different insecure locations via http.

2. The scripts adds, without your knowledge, an un-trusted third-party package repository allowing any user with control of that system to install and run arbitrary code on your system.

Further, despite impressions to the contrary, Boot-Repair is NOT an official offering of Ubuntu.

- First, Boot-Repair is executed as root, because it is the only way to repair the boot (installing GRUB, using os-prober, or modifying the MBR, all require adminitrator privileges). All other tools dealing with boot will also use root privileges.
- Second, Boot-Repair auto-updates itself from its PPA when starting. Anyway, to install Boot-Repair, the only current way is to add this PPA.
- Boot-Repair second button ("Create a Boot-Info Summary") downloads and executes Boot-Info-Script (http://bootinfoscript.sourceforge.net/ ), which is widely used on this forum to diagnose boot problems.
- If someone is afraid of downloading something from http, he can use Boot-Repair offline.
- Boot-Repair is not in Ubuntu repositories (that is why it is needed to install a PPA).
- Boot-Repair is open-source (GNU-GPL), and Boot-Info-Script too, so anybody can check its code.

Is there such a paranoiac "Security warning" in all wiki pages talking about a PPA software ?
Proprietary (closed-source) softwares are far more dangerous than PPA software, and they are installed with root privileges too. Is there such paranoia for Google Talk plugin for example ?

drs305
October 9th, 2011, 04:22 AM
I created the Grub 2 community doc page, as well as others, which are open to others for editing (but not as open as a normal wiki). From time to time I'm surprised what shows up on the page. Even though our input in Community documentation is reviewed, things get input that sometimes aren't correct, or are misspelled, etc.

Previous pages are saved for review, so if you need to edit the latest be sure to make a detailed comment on why the change is being made. Others should review these changes/reasons before editing and your modifications and explanations for editing are submitted for review.

YannBuntu
October 9th, 2011, 01:07 PM
Thanks drs305, but my concern was not about how to use the wiki (I am ubuntu-fr wiki admin since 2007), but about the way this user added such a "I have doubts, so don't use this app" comment in the wiki without even discussing about it on this forum (nor directly with me) before.
I made this app open-source (GPLv3), and I spend a lot of time to improve it and help people, so I am a bit sad to see this person spent time to look at the code but only took time to write such a bad comment instead of suggesting improvements.
I hope my last comment will answer his worries, and anybody is welcome to ask more details if necessary.

By the way, there is no page about PPAs in the wiki... if i have time i will translate the ubuntu-fr one (http://doc.ubuntu-fr.org/ppa).

worb
October 9th, 2011, 07:25 PM
The security issues in Boot-Repair are both real and severe. The degree to which YannBuntu dismisses or excuses the issues further raises concern.

There are at least two serious issues in the current implementation:

1. While executing as root, Boot-Repair pulls a script from the web via "http" and executes it. In this way, neither the authenticity of the host nor the code are checked. Anyone with a basic understanding of software security would be shocked at this. There are many ways to attack this scenario, some of which would yield control of every system on which Boot-Repair is run!

2. Boot-Repair adds, during execution, YannBuntu's personal ppa to the system. This occurs even if the user chose to download the source so as to avoid doing this to install it! Attacks on this could yield control of every system on which Boot-Repair is installed!

In response to YannBuntu's message above:

- First, Boot-Repair is executed as root, because it is the only way to repair the boot (installing GRUB, using os-prober, or modifying the MBR, all require adminitrator privileges). All other tools dealing with boot will also use root privileges.
-- Of course it need to run as root. That is not the problem here. However, once software is running as root, the security bar is raised. Boot-Repair is doing things considered unacceptable in software even when NOT running as root.

- Second, Boot-Repair auto-updates itself from its PPA when starting. Anyway, to install Boot-Repair, the only current way is to add this PPA.
-- No software should ever update automatically w/o consent of the user. Further, the software should not register itself with the system's update engine w/o explicit consent of the user.

- Boot-Repair second button ("Create a Boot-Info Summary") downloads and executes Boot-Info-Script (http://bootinfoscript.sourceforge.net/  (http://bootinfoscript.sourceforge.net/%E3%80%80)), which is widely used on this forum to diagnose boot problems.
-- There is a reason people download code via https, and/or check signatures of code after download. If you are going to pull and execute scripts while running as root, you need to pull these from trusted, secure, sources and check signatures. This is not debatable.

- If someone is afraid of downloading something from http, he can use Boot-Repair off-line.
-- Assuming they know they SHOULD be afraid, which they won't since you've deleted the heads-up on the Wiki.

- Boot-Repair is not in Ubuntu repositories (that is why it is needed to install a PPA).
-- The degree to which you've integrated the documentation of it with items that ARE a part of the official distribution creates the impression otherwise.

- Boot-Repair is open-source (GNU-GPL), and Boot-Info-Script too, so anybody can check its code.
-- With the attack vectors you've opened up with Boot-Repair, there is no way for a user to know for sure what exactly they've run on their system.

YannBuntu
October 10th, 2011, 03:41 AM
Thanks for taking time to detail your thoughts.
- What do you recommend to improve the security during of Boot-Info-Script download and execution ?
- What do you recommend to improve the security of Boot-Repair update ?

worb
October 10th, 2011, 05:55 PM
YannBuntu -

You absolutely need to pull it from distribution for now. You have no right to introduce the kind of security risks that this software contains to anybody else's system.

You should also understand that major software vendors and open-source developers alike would ship critical security patches ASAP for the kinds of issues in your code.

I'm not here to train you in secure software development, nor to contribute to the improvement of "boot-repair".

Per your prior replies, and per your code, I honestly do not think you are qualified to write software that runs as root and is distributed to thousands, if not more, computers.

YannBuntu
October 11th, 2011, 03:40 AM
Coming from such a rude person, who has zero contribution on Launchpad, only 2 posts on this forum, and shows such bad will, I don't know if it's a bad joke or else (conflict of interest ?). :roll:

I would really be happy to understand exactly what the "risk" is, and by which mechanism a problem could arise. Are Launchpad and Sourceforge servers risky ?

Admitting it is risky to update from Launchpad, that would mean that all PPA softwares are risky !!!
Admitting it is risky to download from SourceForge, that would mean that thousands of Free Software have the same risk !!! And this risk also exists when using Boot-Info-Script "without Boot-Repair (http://bootinfoscript.sourceforge.net/)".

Anyway, if these servers are risky, what we could do for now is disabling the auto-update, and including Boot-Info-Script inside Boot-Repair.

Any "productive" comments are welcome.

worb
October 11th, 2011, 08:30 PM
OK: User knowingly registers a ppa for third-party software.
NOT OK: Script running as root registers a ppa and automatically performs an update w/o user consent or knowledge.

OK: Script running as root downloads script via https, validates cryptographic signature of script, and then executes script as root.
NOT OK: Script running as root downloads script via http and executes script as root.

Regarding ppa security, any ppa is only as secure as the owner of that ppa. In the case of Boot-Repair, YannBuntu effectively now has easy root access to every system on which it has ever been installed or run. So too would anyone who compromises YannBuntu's personal credentials or systems. For software that does not need to run as root, the risk is considerably less and perhaps tolerable. For software that runs as root, it is unacceptable.

Regarding downloading, from within a script running as root, additional scripts via http, without signature check, and executing them as root: does the problem with this really need to be explained to anybody?

YannBuntu
October 13th, 2011, 07:50 AM
I made the following changes:
- update is now optional
- included the Boot-Info-Script into Boot-Repair package (no download any more)

In the future, please report bugs in the bug tracker (https://bugs.launchpad.net/boot-repair), and tick the "This bug is a security vulnerability" checkbutton if necessary.

c-shadow
October 13th, 2011, 12:49 PM
Does it still install dmraid and mdraid packages if not present on the system?

YannBuntu
October 14th, 2011, 06:45 AM
Yes it proposes to install them when RAID is detected (currently when the string "raid" or "/dev/mapper" is detected in the output of the "blkid" command).

Thanks for having filed a bug report. I put the link here for others: https://bugs.launchpad.net/boot-repair/+bug/873473

@all: does anybody know how to reliabily detect the RAID type ?

Blasphemist
October 14th, 2011, 05:11 PM
This project is a very useful tool and I for one have seen that questions are promptly answered and requested changes handled quickly as possible. To me this is another example of the proper function and strength of the FOSS community.

I've watched the recent posts in this thread and have to comment. We've seen really very good security related enhancement ideas passed on in a way showing a lack of just plain common human respect. It just seems like much too often these days people just don't care about being nice. I know I'm going to see a lot of that in the media but I'd really rather not see that directed against someone providing a FOSS project that really helps a lot of people. Enough said.

I'd like to pass on some feedback toward making this project better and participate as best I can in making that happen. What is the best venue for passing enhancement requests? I don't yet have the skills to code in this project but I am working slowly toward that. I have requests concerning what is gathered for and presented to the user.

Like many others, it really helps for me to learn from using this to solve my issues and those of others I help in these forums. Given the recent discussion related to the boot info summary, this seems like a good time to really take a look at how that is used and how it could be improved. Should I discuss that here or on sourceforge or in some other way? Just let me know what your preference is for what I hope is a helpful conversation. I'm also available to help with testing and maybe more over time.

Thanks much

YannBuntu
October 14th, 2011, 05:42 PM
Thanks Jim for your kind words, and for helping people on this forum.

For suggestions, please fill a bug report on Launchpad (https://bugs.launchpad.net/boot-repair), and affect it as "wishlist", I find it easier to follow up.

Blasphemist
October 14th, 2011, 06:34 PM
Thanks Jim for your kind words, and for helping people on this forum.

For suggestions, please fill a bug report on Launchpad (https://bugs.launchpad.net/boot-repair), and affect it as "wishlist", I find it easier to follow up.

Will do, thanks!

dennymeta
October 18th, 2011, 07:17 PM
Just used this tool and it destroyed the partition tables on all three of my connected hard drives, not just the one I wanted to repair (hdb). The /dev/hda partition table is particularly interesting now, with partitions of unknown type, of random lengths, in non-sequential order (thought that last bit was particularly interesting). /dev/hda was the drive my main system was on, with all my personal data, so I'm a bit annoyed about that.

Unfortunately I don't have the pastebin reference so there's probably not much that can be done in the way of debugging, but I wanted to sound a note of caution - if this thing goes wrong, it goes really dramatically wrong, with potentially widespread effects. At a bare minimum, I'd recommend detaching any working drives from the system before you let Boot-Repair loose on the non-working ones.

YannBuntu
October 20th, 2011, 02:12 PM
Hello Denny, thanks for your feedback, and sorry for the trouble.
To repair the partition tables i suggest recovery tools such as TestDisk.
After this, to help debug, please send me by email (yannubuntu ATT gmail) a ZIP of the /var/log/clean folder which should be located in your Ubuntu partition.

EC120
October 23rd, 2011, 04:09 AM
Seems like a nice tool that can solve a lot of problems automatically, but I don't know how to use it in my scenario. :-k

I have a disk with 4 partitions and need to install grub in sda2, not sda (mbr)
But there is only one option available under Place GRUB into: drop-down menu - sda

http://pix.toile-libre.org/upload/img/1313715508.png

more info about my issue is in this thread:
http://ubuntuforums.org/showthread.php?t=1863379

drs305
October 23rd, 2011, 04:20 AM
Seems like a nice tool that can solve a lot of problems automatically, but I don't know how to use it in my scenario. :-k

If you want to install Grub to a partition rather than the MBR so you can chainload it you would use the bottom option in the graphic you posted.

EC120
October 23rd, 2011, 05:24 PM
Can't do that because in my case there was sda5, I think, for chainloading, not sda2.
Why is that option fixed instead of drop-down menu so user can choose the location to force GRUB into?

mörgæs
November 2nd, 2011, 12:35 AM
Just a quick 'thank you'. Finally I had some booting trouble, so I could test the ISO. It worked like a charm.

When using the boot CD, one should be patient. The program might take several minutes to run - just wait, it is not frozen.

YannBuntu
November 6th, 2011, 02:20 AM
Hello

@EC120: the chainload option only proposes to install GRUB2's "first stage" into the partition containing the "second stage" (= the partition that you select at the right of "OS to boot by default")

@mörgæs: glad to see you tried it ;) currently the "recommended repair" performs by default a fsck (filesystem repair) on all partitions, which takes time, before reinstalling GRUB (or restoring MBR). I think I will deactivate this fsck by default (it will remain possible to activate it in the Advanced options), because I am not sure of fsck package's reliability (if some fsck's expert read this, I would be happy to get some advice). This would considerably accelerate the repair.

rosiet
November 8th, 2011, 01:02 PM
Thank you thank you thank you for this wonderful app YannBuntu!! Worked like a dream (though I had to go through the rigmarole of installing synaptic in order to install pastebinit and gawk - no idea why synaptic isn't there by default in 11.10).

You've just turned a miserable morning into a very happy one. :D

martini1179
November 14th, 2011, 08:58 PM
Hi martini1179,
Boot-Repair should work also with GRUB Legacy. :D
Remark : the "purge" option uninstalls GRUB (grub grub-pc and grub-common) packages, and reinstalls grub-pc.

So just to be clear, if I want to get GRUB legacy to work when I install Windows 7 after I install Ubuntu, instead of clicking the "recommended repair" button, I should go into Advanced Options>>GRUB Location and then click the "Purge and reinstall the GRUB of:" option?

If so, I will be essentially updating GRUB legacy to GRUB "2.0", right?

Will this sort of update cause me any boot problems?

YannBuntu
November 15th, 2011, 11:40 AM
Hi Martini,

Basically:
- the "Recommended repair" will do what is ticked by default in the "Advanced options".
- the "OS to boot by default:" option (in the Advanced options) will just reinstall the GRUB (Legacy or GRUB2) which is already in the OS you choose at the right-side of "OS to boot by default:". If your system had Legacy, it will remain Legacy.
- the "Purge and reinstall the GRUB of:" option (in the Advanced options) will completely purge the GRUB (Legacy or GRUB2) of the OS you choose at the right-side of "Purge and reinstall the GRUB of:", then it will guide you to reinstall GRUB2 in it.

Each version of Ubuntu ships with a newer version of Grub. And each version of Grub corrects some bugs, and bring new ones, so we cannot be sure that the last Grub will work better on your system that the one you are using now.

First of all, I recommend you check on your current Ubuntu system the version of Grub you are using (search "grub" in Synaptic).

LeDechaine
November 23rd, 2011, 08:57 AM
Hello,
To answer your questions, Boot-Repair is not 64bits-only. It can be used both in 32bits and 64bits session, but when run from a 32bits session it cannot repair the GRUB of a 64bits Linux (that's a limitation of the chroot system).
Generally people who use only 64bits systems/CD, or 32bits systems&CD so there is no problem.

You're wrong. I'm using an ubuntu 11.10 32-bit liveCD to add grub to an ubuntu 9.04 32-bit system and Boot-Repair tells me "Please use this software in a 64bits session." looks like your software verifies if the computer supports 64-bit, but doesn't care about the installed system itself.

YannBuntu
November 23rd, 2011, 09:18 AM
Hi LeDechaine.
I will check this point again, thanks.
FYI, Ubuntu 9.04 is not supported any more. Only 10.04 and later are supported by Boot-Repair.

LeDechaine
November 23rd, 2011, 10:12 AM
Hi LeDechaine.
I will check this point again, thanks.
FYI, Ubuntu 9.04 is not supported any more. Only 10.04 and later are supported by Boot-Repair.

Which basically means boot-repair won't work for me anyway?

mörgæs
November 23rd, 2011, 10:20 AM
No matter if Boot-repair works or not you should let go of 9.04 and install a supported release. It is dangerous to use a release which has not received security bug fixes for more than a year.

LeDechaine
November 23rd, 2011, 12:14 PM
No matter if Boot-repair works or not you should let go of 9.04 and install a supported release. It is dangerous to use a release which has not received security bug fixes for more than a year.

Dangerous? Hell, you must be afraid to go outside.
Thanks for the useless comment about my computer with no internet access.

YannBuntu
November 23rd, 2011, 02:24 PM
Hello
"Boot-repair supports 10.04 and later" means that I ensure the best I can that it works for these versions only. For 9.10 and previous versions, it may work, and if not, I won't spend time to make it work.

If you want to keep 9.04, and if Boot-Repair does not work for this outdated version, you will have to repair your boot manually. For this it may be useful to know that Ubuntu 9.04 uses GRUB Legacy (which also is not supported any more).

If not, you can simply use your Ubuntu 11.10 CD to reinstall 11.10 above (or in dual-boot with) your current 9.04 system. This will install GRUB2.

YannBuntu
November 23rd, 2011, 05:08 PM
@all: I need help to improve GRUB2 reinstall on RAID5 and RAID1+0. Any clue/tutorial is welcome. :)

ktmom
November 24th, 2011, 02:20 AM
Thanks for the tool YannBuntu. That just saved me when I did something stupid to my myth install. Fixed in recorded time!

(do you have a ppa to upgrade the stupid "ideas" I keep getting? :P )

YannBuntu
November 24th, 2011, 09:48 AM
Glad to help :)
The PPA is here: https://launchpad.net/~yannubuntu/+archive/boot-repair/
if you have any suggestions, don't hesitate to write them on this forum :)

LeDechaine
November 24th, 2011, 11:22 AM
I can confirm you that this software does NOT work for Ubuntu 9.04. And I'm sick and tired of being sick and tired of fixing things that would never have been supposed to break, so I quit, bye.

YannBuntu
November 24th, 2011, 04:29 PM
@all: there are now packages for Precise (Ubuntu 12.04) on the PPA. Any feedback is welcome :)

Steve James
November 27th, 2011, 11:46 PM
Great tool - the first time I used it. Thanks a lot. Installed Win7 on a dual boot machine and lost the GRUB script. Used the boot repair disk to recover. Fantastic. Had a recurrence a few days later but now the GRUB options greyed out and I cant recover the GRUB. Running Ubuntu 11.0 Might have applied some updates in between the two instance. Any suggestions? Help!?
Thanks again.

YannBuntu
November 27th, 2011, 11:56 PM
Hello Steve,
please boot a Ubuntu CD, choose "Try Ubuntu", connect internet, run Boot-Repair, click "Recommended repair", and indicate me the URL that will appear.

Steve James
November 28th, 2011, 01:45 AM
Used a Ubuntu 10.04 CD and downloaded from PPA...and did as instructed in Ubuntu Community i.e.

sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update && sudo apt-get install -y boot-repair && boot-repair

It ran Boot repair straightaway. Previously I am sure I had to then invoke it by typing boot-repair at the CLI.
Grub tabs still greyed out. Says it repaired successfully.

Presume this is what you need:
http://paste.ubuntu.com/752068/

Await with bated breath.....

drs305
November 28th, 2011, 01:59 AM
Steve,

The RESULTS.txt does not find an Ubuntu partition on the only drive it found. The only linux partition it found was a swap partition:


Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
/dev/sda2 206,848 193,454,079 193,247,232 7 NTFS / exFAT / HPFS
/dev/sda3 193,456,126 488,280,063 294,823,938 5 Extended
/dev/sda5 476,264,448 488,280,063 12,015,616 82 Linux swap / Solaris


It also doesn't find Grub installed in the MBR:

=> Syslinux MBR (3.61-4.03) is installed in the MBR of /dev/sda.

In Boot Repair's own output section, it confirms this finding:

1 disks with OS, 1 OS : 0 Linux, 0 MacOS, 1 Windows, 0 unknown type OS.

Steve James
November 28th, 2011, 02:18 AM
Oh dear.....:(:(:(
I have just checked using the disk utility tool and you are right the partition that used to have my Ubuntu now just says FREE
Somehow with my tinkering I have managed to lose it. Luckily I have most of my stuff backed up - I think!
Is there any way to recover something from this partition. Appreciate this is a separate matter.

rthamilt
November 28th, 2011, 02:22 AM
When using boot-repair in an Ubuntu 11.10 live session, boot repair wants to install grub/ in a weird partition.

I've got a small automatically created Win7 partition, a main Win7 partition, then partitions for /, /home, and swap. boot-repair only gives me options to install grub into sda2 (Win7 main partition) or sda6 (/home partition), both incorrect. sda5 (/) isn't a choice anywhere. Any advice?

http://paste.ubuntu.com/752087/

drs305
November 28th, 2011, 02:29 AM
@ Steve,

If nothing has been written to the unallocated space, you can probably use TestDisk to restore the missing partition.

Here is a link on how to use TestDisk,
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step#Current_partition_table_stat us

As you implied, it would be best to open a new thread if you need more assistance with this.

Steve James
November 28th, 2011, 02:43 AM
Many thanks. Will try that out. Ulp...

YannBuntu
November 28th, 2011, 12:00 PM
you can probably use TestDisk to restore the missing partition.

+1. If the partition cannot be recovered completely, maybe there is a chance to recover some files.

YannBuntu
November 28th, 2011, 12:05 PM
When using boot-repair in an Ubuntu 11.10 live session, boot repair wants to install grub/ in a weird partition.

I've got a small automatically created Win7 partition, a main Win7 partition, then partitions for /, /home, and swap. boot-repair only gives me options to install grub into sda2 (Win7 main partition) or sda6 (/home partition), both incorrect. sda5 (/) isn't a choice anywhere. Any advice?

http://paste.ubuntu.com/752087/

By default (the "Recommended repair"), Boot-Repair will reinstall the GRUB of Ubuntu (sda5) into the MBR of sda. Did you try it ?

(the sda2 and sda6 you see are at the right-side of "Use a separate /boot", aren't they?)

noadvertise
November 30th, 2011, 01:40 AM
this software didn't ask for WHICH drive to repair the boot record on, it destroyed my boot disk (usb)

going back to command line for me!

YannBuntu
November 30th, 2011, 09:35 AM
Sorry for this problem. (This should have not happened, as since 3.X versions, Boot-Repair does not install GRUB in USB disks, except if chosen by the user, or if it contains an OS.)
Please could you indicate your BootInfo URL (http://ubuntuforums.org/showthread.php?t=1821980) so that we can debug ?

Please remember that the "Recommended repair" will perform the actions that are selected by default when you click on "Advanced options". These options allow to select where to install GRUB.

Furthermore, Boot-Repair creates a backup of the MBR of all disks before applying changes, so that you can restore it in case of problem.
If you need help to restore your original USB disk's MBR, please send me by email (yannubuntu ATT gmail.com) the /clean (or /var/log/clean) folder that is in your OS partition.

c.cobb
December 6th, 2011, 05:32 PM
Hi YannBuntu,
I installed your app to a 32bit Ubuntu 10.04 session running on a Live USB this morning, and also received the error "Please use this softare in a 64bits session." The system that I'm recovering is also 32bit Ubuntu 10.04, and I've never installed a 64bit OS.

A couple of other comments. The defaults would have broken my system badly (wants to install Grub to *all* MBRs by default), and I *almost* just clicked the "Apply" button without looking at the Advanced options. This also could have potentially damaged my system: while the "OS to boot by default" (recognized on sdb5, and the "Place GRUB into:" (with "sdb" selected) were correct, the "Separate /boot partition:" was recognized as sdc1, which is on a different device. So it's good for me that it didn't work anyway. (I still don't know what will happen to the boot partition -- do you reinstall /boot/grub/* files? -- if so, what happens to the existing grub.cfg file?)

My system has 3 disks: WinXP with XP loader, and 2 that are (mostly) mirror images of Ubuntu. The disk I wanted to repair was my backup Ubuntu disk that never had Grub2 installed, and still had an old WinXP Pro boot loader on it.

While I haven't read all of the postings in this thread, I've read most since page 11 (since last August), and I have to say that while this is a very nice idea, the potential for problems -- given the various possible scenarios -- is rather high. Thank you for fixing the security issues BTW -- that concerned me a lot as well.

Since the alternative is to use one or two simple command lines, I would ask that you consider updating the documentation for boot-repair, in at least three locations: the Recovering (https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows) page, your community docco page (https://help.ubuntu.com/community/Boot-Repair), and on your website, to indicate this is beta software and to use it at risk.

Of course the hard part of using the two "simple" command lines is figuring out which options and arguments to use, and your GUI tool is a nice idea. If I can provide you with any information that will help improve your app, please let me know. I have a log that includes before and after (http://ccobb.net/ubuntu/boot-repair/Gateway_MBR_Info.txt), and a screen shot (http://ccobb.net/ubuntu/boot-repair/boot-repair-options.png) that you are welcome to.
Solo mis dos centavos,

p.d. just thought of this: if the system you analyze is not drop-dead simple to figure out, maybe best to automatically open the Advanced options page so your users can see what to expect.

p.p.d. if this had updated the MBR on my USB stick, I would have been seriously bummed!

YannBuntu
December 7th, 2011, 12:44 AM
Hello c.cobb,

Thanks for your interesting feedback.

The 32-bit thing looks like a bug (that I thought I had fixed few days ago), please click the "Create BootInfo report" button and indicate in a new bug report (https://bugs.launchpad.net/boot-repair/+filebug) the URL that will appear.

Concerning your USB stick: as said previously, Boot-Repair does not install GRUB into USB disks which don't contain any OS detected by os-prober. I should change the "all disks" label by something like "all disks except USB without OS".

Concerning the default separate /boot partition, please fill in a new bug report too. (best with your BootInfo URL too).

Concerning your question about what happens to the /boot/grub files: the default ("OS to boot by default") will basically just reinstall GRUB (grub-install --recheck ,then update-grub), while the "Purge and reinstall the GRUB of" option will purge (apt-get purge grub grub-pc grub-common), delete /boot/grub, then reinstall the package (apt-get install grub-pc) and reinstall GRUB (grub-install --recheck ,then update-grub).

About the "beta" status: I agree that the tool is not perfect, and will never be able to solve 100% of the boot problems that exist. Nevertheless, it is used by ~500 people/day since more than 1 year, and considering the very little number of unsolved cases i saw, i guess that it succeeds for what is aimed at ("repairing most frequent boot problems"). It depends on what "beta" means for you, but for me B-R is less "beta" than.. GRUB2 for example ;)

Your suggestion to automatically open the Advanced options for "advanced users" (e.g. when a separate /boot is detected) is a good idea. Please fill in a blueprint here: https://blueprints.launchpad.net/boot-repair

c.cobb
December 8th, 2011, 03:43 AM
YannBuntu,
Well, with numbers like those, you're doing something right!

I'll file the bugs and blueprint w/in the next couple of days.

And great to know my USB stick wouldn't have been altered. ;-)

Just to confirm, since I did not want any of Grub's config files changed on any disk, I should have unchecked all the Advanced Main Options except for "Restore MBR," which would only run the install and skip the update, is that right?
Thanks,

bcbc
December 8th, 2011, 04:06 AM
~500 people a day requiring a boot repair? Ouch. That's not a very good stat for Ubuntu.

mörgæs
December 8th, 2011, 09:33 AM
How do you measure that?

YannBuntu
December 8th, 2011, 01:23 PM
hello


I'll file the bugs and blueprint w/in the next couple of days.

Yes please. For information, this 32/64bit bug (https://bugs.launchpad.net/boot-repair/+bug/899844) has been solved yesterday, please update your Boot-Repair and check if your problem is solved now. If not, please open a new bug report.



Just to confirm, since I did not want any of Grub's config files changed on any disk, I should have unchecked all the Advanced Main Options except for "Restore MBR," which would only run the install and skip the update, is that right?

"Restore MBR" option does not install nor update GRUB. It just makes the select MBR "generic" (syslinux type). If GRUB was installed in this MBR this will remove GRUB from it. But this will not affect the GRUB config files which are in the /boot folder.

If you want to reinstall/update GRUB without changing your grub conf files, you just need to select "Reinstall GRUB", and unselect "Unhide boot menu".


@bcbc: I agree. I would add that's not good stats for GRUB2 :(

@mörgæs: via an anonymous ping system. Stats can be found here (http://sourceforge.net/projects/boot-repair/files/statistics/). It's not very sophisticated, but it helps see which functions are most used, so which functions should be improved in priority. I hope one day it will also be a good feedback for GRUB devs.

c.cobb
December 8th, 2011, 06:18 PM
YannBuntu, thank you for the clarification.

bcbc, at first reading, I also thought 500/day sounded extreme. However, consider that 18 months ago one report (http://ostatic.com/blog/canonical-announces-12-million-ubuntu-users-google-makes-a-comeback) gives 12 million Ubuntu users, and that 500/day is around 185K uses per year. Even if every use was a unique person, that would mean 1.5% of Ubuntu users are using boot-repair. A more recent article (http://www.techspot.com/news/43709-mark-shuttleworth-200-million-ubuntu-users-by-2015.html) estimates 20 million users.

And thanks, YannBuntu, for clarifying your stats process. Any undocumented "phone home" features are unpleasant, and this was another cause for concern.

BTW, I don't see the need for boot-repair as a problem either with Ubuntu or with Grub2, but yet another example of the arrogance of a certain Redmond-based software developer who refuses to play nice with anyone else in the known universe. :-( I expect that a lot of users will want/need to dual-boot Ubuntu and Windows for the foreseeable future.

mörgæs
December 8th, 2011, 07:11 PM
@mörgæs: via an anonymous ping system. Stats can be found here (http://sourceforge.net/projects/boot-repair/files/statistics/).

Though it's anonymous I think you should warn people about what is going on. I didn't see any information about this when I used Boot-Repair.

YannBuntu
December 8th, 2011, 11:29 PM
I understand. I added a disclaimer on Boot-Repair's website (https://sourceforge.net/p/boot-repair/home/Home/).

mörgæs
December 10th, 2011, 12:17 PM
Thanks, but I was more thinking of letting Boot-Repair itself show this information. I don't think many people read Sourceforge before installing.

mbdev
December 11th, 2011, 06:07 PM
Hey, I'm just stopping by to say THANK YOU very much :)

I have Ubuntu 11.10 x64, and Windows 7 x64 dual boot. Yesterday I've decided to change sizes of my Win partitions, and well, my booting messed up. I started to receive this strange message "serious errors while mounting /", when booting Ubuntu.

Every time I chose "Press I to ignore", and all was fine, except my swap partition didn't mount automatically at start-up. I had to mount it manually every time. Neither editing /etc/fstab nor grub conf nor refreshing every setting, updating settings (and so on) helped.

But, when I used boot-repair with default repairs profile, all problems went away, now my Ubuntu works like charm again :) So, once more, thanks a lot!

YannBuntu
December 18th, 2011, 11:49 PM
Hello
several new options:
- one that solves the FlexNet error
- one to easily backup the partition table, MBR, logs on a USB disk
- one to deactivate the participation to statistics of use

http://pix.toile-libre.org/upload/original/1324245480.png
http://pix.toile-libre.org/upload/img/1324247674.png (http://pix.toile-libre.org/?img=1324247674.png)

drs305
December 20th, 2011, 06:29 AM
Thanks! :guitar:

I don't use Windows but I've always thought that FlexNet 'bug' was nasty!

We all appreciate the work you are doing to help solve Grub problems.

Happy holidays!

freacert
December 20th, 2011, 10:41 PM
sounds great, but the update-manager cannot find the package. :(


erik@erik:~$ sudo add-apt-repository ppa:yannubuntu/boot-repair
[sudo] password for erik:
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv xxxxxxxxxxxxxxxxxxxxxx
gpg: solicitando clave xxxxxxx de hkp servidor keyserver.ubuntu.com
gpg: clave xxxxxxxxx: clave pública "Launchpad PPA for YannUbuntu" importada
gpg: Cantidad total procesada: 1
gpg: importadas: 1 (RSA: 1)
erik@erik:~$ sudo apt-get update && sudo apt-get install boot-repair-ubuntu
Des:1 http://dl.google.com stable Release.gpg [198B]
Obj http://ppa.launchpad.net lucid Release.gpg
Ign http://ppa.launchpad.net/gwibber-team/ppa/ubuntu/ lucid/main Translation-es
Ign http://dl.google.com/linux/talkplugin/deb/ stable/main Translation-es
Des:2 http://ppa.launchpad.net lucid Release.gpg [316B]
Ign http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu/ lucid/main Translation-es
Obj http://ppa.launchpad.net lucid Release
Des:3 http://archive.canonical.com lucid Release.gpg [198B]
Ign http://archive.canonical.com/ubuntu/ lucid/partner Translation-es
Des:4 http://dl.google.com stable Release [1347B]
Obj http://archive.ubuntu.com lucid Release.gpg
Obj http://archive.ubuntu.com/ubuntu/ lucid/main Translation-es
Obj http://archive.ubuntu.com/ubuntu/ lucid/restricted Translation-es
Obj http://packages.medibuntu.org lucid Release.gpg
Des:5 http://ppa.launchpad.net lucid Release [14,0kB]
Des:6 http://archive.canonical.com lucid Release [8215B]
Obj http://archive.ubuntu.com/ubuntu/ lucid/universe Translation-es
Obj http://archive.ubuntu.com/ubuntu/ lucid/multiverse Translation-es
Des:7 http://archive.ubuntu.com lucid-updates Release.gpg [198B]
Ign http://archive.ubuntu.com/ubuntu/ lucid-updates/main Translation-es
Ign http://archive.ubuntu.com/ubuntu/ lucid-updates/restricted Translation-es
Ign http://archive.ubuntu.com/ubuntu/ lucid-updates/universe Translation-es
Ign http://archive.ubuntu.com/ubuntu/ lucid-updates/multiverse Translation-es
Ign http://packages.medibuntu.org/ lucid/free Translation-es
Des:8 http://archive.ubuntu.com lucid-security Release.gpg [198B]
Ign http://archive.ubuntu.com/ubuntu/ lucid-security/main Translation-es
Ign http://archive.ubuntu.com/ubuntu/ lucid-security/restricted Translation-es
Obj http://ppa.launchpad.net lucid/main Packages
Ign http://archive.ubuntu.com/ubuntu/ lucid-security/universe Translation-es
Ign http://archive.ubuntu.com/ubuntu/ lucid-security/multiverse Translation-es
Obj http://archive.ubuntu.com lucid-backports Release.gpg
Ign http://archive.ubuntu.com/ubuntu/ lucid-backports/restricted Translation-es
Des:9 http://archive.canonical.com lucid/partner Packages [15,4kB]
Ign http://archive.ubuntu.com/ubuntu/ lucid-backports/main Translation-es
Ign http://archive.ubuntu.com/ubuntu/ lucid-backports/multiverse Translation-es
Ign http://archive.ubuntu.com/ubuntu/ lucid-backports/universe Translation-es
Ign http://packages.medibuntu.org/ lucid/non-free Translation-es
Des:10 http://ppa.launchpad.net lucid/main Packages [1198B]
Des:11 http://dl.google.com stable/main Packages [765B]
Obj http://archive.ubuntu.com lucid Release
Des:12 http://archive.ubuntu.com lucid-updates Release [44,7kB]
Obj http://packages.medibuntu.org lucid Release
Des:13 http://archive.canonical.com lucid/partner Sources [7225B]
Obj http://packages.medibuntu.org lucid/free Packages
Des:14 http://archive.ubuntu.com lucid-security Release [44,7kB]
Obj http://packages.medibuntu.org lucid/non-free Packages
Obj http://archive.ubuntu.com lucid-backports Release
Obj http://archive.ubuntu.com lucid/main Packages
Obj http://archive.ubuntu.com lucid/restricted Packages
Obj http://archive.ubuntu.com lucid/main Sources
Obj http://archive.ubuntu.com lucid/restricted Sources
Obj http://archive.ubuntu.com lucid/universe Packages
Obj http://archive.ubuntu.com lucid/universe Sources
Obj http://archive.ubuntu.com lucid/multiverse Packages
Obj http://archive.ubuntu.com lucid/multiverse Sources
Des:15 http://archive.ubuntu.com lucid-updates/main Packages [535kB]
Des:16 http://archive.ubuntu.com lucid-updates/restricted Packages [3998B]
Des:17 http://archive.ubuntu.com lucid-updates/main Sources [208kB]
Des:18 http://archive.ubuntu.com lucid-updates/restricted Sources [1850B]
Des:19 http://archive.ubuntu.com lucid-updates/universe Packages [245kB]
Des:20 http://archive.ubuntu.com lucid-updates/universe Sources [84,6kB]
Des:21 http://archive.ubuntu.com lucid-updates/multiverse Packages [10,5kB]
Des:22 http://archive.ubuntu.com lucid-updates/multiverse Sources [5073B]
Des:23 http://archive.ubuntu.com lucid-security/main Packages [246kB]
Des:24 http://archive.ubuntu.com lucid-security/restricted Packages [14B]
Des:25 http://archive.ubuntu.com lucid-security/main Sources [72,8kB]
Des:26 http://archive.ubuntu.com lucid-security/restricted Sources [14B]
Des:27 http://archive.ubuntu.com lucid-security/universe Packages [107kB]
Des:28 http://archive.ubuntu.com lucid-security/universe Sources [28,1kB]
Des:29 http://archive.ubuntu.com lucid-security/multiverse Packages [4557B]
Des:30 http://archive.ubuntu.com lucid-security/multiverse Sources [1750B]
Obj http://archive.ubuntu.com lucid-backports/restricted Packages
Obj http://archive.ubuntu.com lucid-backports/main Packages
Obj http://archive.ubuntu.com lucid-backports/multiverse Packages
Obj http://archive.ubuntu.com lucid-backports/universe Packages
Descargados 1693kB en 15s (112kB/s)
Leyendo lista de paquetes... Hecho
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
E: No se pudo encontrar el paquete boot-repair-ubuntu
erik@erik:~$

YannBuntu
December 21st, 2011, 09:21 AM
Hello


the update-manager cannot find the package.
(...)
sudo apt-get install boot-repair-ubuntu
(...)

Because you are trying to install a package that does not exist any more: boot-repair-ubuntu. (on which website did you find reference to this package? this package is very old and obsolete)

The package to install is: "boot-repair". (for up-to-date instructions, please see https://help.ubuntu.com/community/Boot-Repair )

freacert
December 21st, 2011, 10:03 AM
Hello

Because you are trying to install a package that does not exist any more: boot-repair-ubuntu. (on which website did you find reference to this package? this package is very old and obsolete)

The package to install is: "boot-repair". (for up-to-date instructions, please see https://help.ubuntu.com/community/Boot-Repair )

Thanks Yann!!

I am trying to find where i found reference to this wrong package. But i would say i just followed the first post in the thread, now i see that is updated... Anyway, googling "sudo apt-get install boot-repair-ubuntu" with "" gives me still too many pages which make reference to this package.

YannBuntu
December 21st, 2011, 10:41 AM
i will ask some websites to update, but i can't do it for all of them.
As a general advice, i recommend you to always check the official website of the applications you want to install.

freacert
December 21st, 2011, 10:58 AM
I made comments on two of those websites, just a little drop of help....

YannBuntu
December 21st, 2011, 11:01 AM
Thanks for your help :)

sailor420
December 31st, 2011, 11:28 PM
OK, I've got an interesting issue.

Just used boot-repair to fix my grub2 after re-installing Windows. Booted off a USB flash drive loaded with Ubuntu 11.10, then installed boot-repair from the PPA, and ran.

Now, I get a read error when grub starts, *unless* I leave the USB key in the machine. If the USB key is in the machine, it's fine.

This is obviously somewhat less than ideal. Any suggestions on how to fix this? I tried booting into Ubuntu (installed on the disk, not running off the USB), ejecting the USB key, then installing and running boot-repair, but that didn't do anything either.

I'm stumped--suggestions?

drs305
December 31st, 2011, 11:31 PM
OK, I've got an interesting issue.

Just used boot-repair to fix my grub2 after re-installing Windows. Booted off a USB flash drive loaded with Ubuntu 11.10, then installed boot-repair from the PPA, and ran.

Now, I get a read error when grub starts, *unless* I leave the USB key in the machine. If the USB key is in the machine, it's fine.

This is obviously somewhat less than ideal. Any suggestions on how to fix this? I tried booting into Ubuntu (installed on the disk, not running off the USB), ejecting the USB key, then installing and running boot-repair, but that didn't do anything either.

I'm stumped--suggestions?

Without seeing specific information, you should be able put grub on your main drive's MBR from a running Ubuntu with (X being the drive letter):

sudo grub-install /dev/sdX
sudo update-grub
Note that this will overwrite the Windows bootloader information on the MBR, if it exists. Normally Grub can handle booting Windows without any problem, but you should realize that Grub will take control if you install it to the same drive as Windows.

sailor420
January 1st, 2012, 01:01 AM
Thanks. Unfortunately, that doesnt seem to be working either--booted up into Ubuntu, ejected the USB key, ran grub-install on /dev/sda (SSD drive that has my Windows install on it), ran update-grub, which found Windows and Ubuntu, then rebooted--but got the same read error. Put the USB key back in and reboot, and its fine.

drs305
January 1st, 2012, 01:04 AM
Thanks. Unfortunately, that doesnt seem to be working either--booted up into Ubuntu, ejected the USB key, ran grub-install on /dev/sda (SSD drive that has my Windows install on it), ran update-grub, which found Windows and Ubuntu, then rebooted--but got the same read error. Put the USB key back in and reboot, and its fine.

From Boot Repair you can run the Boot Info Script. If you post the contents of RESULTS.txt (easier for us) or paste the link where the results can be viewed we might be able to see what is happening.

sailor420
January 1st, 2012, 01:28 AM
OK done: http://paste.ubuntu.com/789290/

Thanks for the help!

drs305
January 1st, 2012, 02:35 AM
OK done: http://paste.ubuntu.com/789290/

Thank you for posting the script results.

Did you install Grub to sdc and do you have your BIOS set to boot the sdc drive (640GB) first?

sailor420
January 1st, 2012, 04:16 PM
I believe it installed to all of the drives. I'm set to boot from SDA, which is my SSD first. Should this be changed?

drs305
January 1st, 2012, 04:36 PM
I believe it installed to all of the drives. I'm set to boot from SDA, which is my SSD first. Should this be changed?

Although the boot info script is an excellent tool. It says the sda drive is looking for Ubuntu on partition 5 of the same drive but sometimes the information in the first section is a bit ambivalent I would try changing the BIOS boot order to sdc and see if it boots.

sailor420
January 1st, 2012, 04:52 PM
Ugh, still nothing--tried setting SDC and SDB as first boot disk in BIOS, and it still gave me the "Loading operating system... Read Error" if the USB key wasn't inserted... Sigh.

drs305
January 1st, 2012, 05:45 PM
Ugh, still nothing--tried setting SDC and SDB as first boot disk in BIOS, and it still gave me the "Loading operating system... Read Error" if the USB key wasn't inserted... Sigh.

Since this thread is supposed to be about Boot Repair, it might be best if you start your own thread. You are likely to get more viewers in a new thread. Either include the link to the pastebin or post the contents.

You can provide a link to this thread if you like, but explain your situation in the new post.

If there is something Boot Repair can do that you haven't tried I'm sure YannBuntu will post in this thread.

sailor420
January 1st, 2012, 06:35 PM
OK, done. Hopefully someone will be able to figure this out... It's got me baffled.

New thread: http://ubuntuforums.org/showthread.php?p=11579345#post11579345

YannBuntu
January 8th, 2012, 12:09 AM
Dear all,
Some users report lately that Boot-Repair's update may fail (via Update Manager or when running Boot-Repair's self-update). If you have this problem too, here is how to solve it:

type in a terminal (Ctrl+Alt+T) the 2 following commands :

for i in boot-repair clean clean-gui clean-ubiquity-common boot-repair-common boot-sav-gui boot-sav glade2script;do sudo apt-get purge -y $i;done
then

sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update; sudo apt-get install -y boot-repair && boot-repair

inorganic
January 9th, 2012, 10:15 AM
boot-repair appears to be a really excellent application. However, I just had a very scary experience with this application and want to report my experience and hopefully inspire the creators to change the way it works a bit, and also get people to perform a sanity check on my experience.

First, here was my situation. I had a 1TB seagate SATA drive that contained only ubuntu linux 10.4 LTS and no other operating systems. The partitions were:


891GB /
32GB /backup
8GB swap


I'm about 99.9% certain / and /backup were ext3 partitions, because I created this hard disk drive within a few days of ubuntu 10.40 being released, and I don't even recall ext4 being available then.

Somehow my MBR got smashed a couple days ago. I ended up ordering a whole new set of parts to fix and upgrade my computer, though it turned out that wasn't necessary. In case it matters, the new parts are: gigabyte 990FXA-UD7 motherboard, AMD 3.6GHz 8150 FX 8-core CPU, mushkin 2133MHz 8GB DDR3 RAM, 3TB @ 7200RPM seagate hard drive. The rest of the components were not changed (power-supply, DVD burner, nvidia GTX285 graphics card, etc).

I fiddled the BIOS to boot off the DVD, then booted the ubuntu installation DVD and performed the normal installation process to get ubuntu 10.4 LTS installed on the new 3TB hard disk drive. When that was finished, I powered it down, removed the ubuntu DVD, and it booted up just fine.

Then I disconnected the SATA3 cable to the 3TB drive and connected it to the old 1TB drive that stopped booting a couple days earlier. The system would then not boot up, just like before I rebuilt it.

Then I reset the computer and booted up into ubuntu on the DVD (the "live" or "try-it-out" version, or whatever it's called). Then I selected "Places -> Computer" and looked to see whether I could see the 1TB disk drive that would not boot. I could indeed, and the directory tree looked just fine. It appeared like nothing was missing. This led me to believe the MBR was busted, and/or the grub loader.

Then I put the ubuntu installation DVD in the DVD drive and tried again. It came up in with the usual screen that asked whether to boot ubuntu off the DVD, perform a memory test, or boot off the 1TB hard disk drive. When I told it to boot off the defective 1TB hard disk drive, it booted up just fine. This virtually proved my theory that only the MBR and/or grub loader was busted.

I spent a couple days searching for ways to fix my MRB. I found lots of talk about "grub-install" and various schemes with "dd", but I was never able to find out for 100% certain that no more than the first 446 bytes would be written with those techniques, and it was clear that the entire partition table would be destroyed if more than 446 bytes were written.

So I kept searching and eventually found the boot-repair application. So I downloaded it and ran it to take a peek at the drives and see what I could see.

I guess stupidly (as it turned out), I activated the "advanced features" checkbox, then looked around the GUI for what the application would do. In the end, I checked the options to create the "bootinfo summary" report, but UN-checked both "reinstall GRUB" and "restore MBR".

Then I clicked the "apply" button.

Later, when I ran gparted, I noticed with terror that my / and /backup partitions were now labeled as being ext4, not ext3 !!! What the frack, I thought. It wasn't supposed to change anything! Oh, freaking no!!! What have I done?

Anyway, I shutdown, removed the ubuntu installation DVD, then started the computer. To my amazement and relief, the freaking computer booted up ubuntu and everything seems to work.

Somehow, the MBR got fixed... even though both "reinstall GRUB" and "restore MBR" were NOT selected. Also, the "GRUB location", "GRUB options" and "MBR options" tabs were greyed out, further implying they were irrelevant. I wrote down the URL where the "bootinfo summary" was uploaded, and it is indeed there: http://paste.ubuntu.com/797990 . I also note that it did not display a "nothing was changed" dialog like is displayed when I simply cancel out of the "boot-repair" application without doing anything.

Maybe or probably I should have selected the button that creates the "bootinfo summary" on the main dialog window [non-advanced features]. However, later I tried that and it too doesn't display a "nothing was changed" dialog after the application ends... so I don't know what to think. That second bootinfo log is http://paste.ubuntu.com/798027 in case it matters. However, when I start the "boot-repair" application, do nothing and just quit out, it does display that "nothing was changed" dialog. Hmmmm.

So, my two issues and questions are:

#1: Why did it repair my the MBR [and/or GRUB] on my disk drive when I had both those options unchecked?

#2: Why did the two ext3 partitions on the hard drive all of a sudden become ext4 partitions after running boot-repair? Remember, that's what gparted says too, not just the "bootinfo summary". I suppose there is some tiny chance that I had ext4 partitions all along, but I really don't think so. Like I said, I don't think ext4 existed (in non-beta) when I created that disk drive in April 2010.

-----

Anyway, it looks like boot-repair did exactly what I needed, and it is a very cool application. However, I think this behavior I observed needs to be fixed! It shouldn't modify the MBR and/or GRUB unless the related check-boxes are selected. And if it is changing ext3 to ext4... what's that all about?

oldfred
January 9th, 2012, 05:26 PM
You may have had ext4 partitions? Ubuntu updated grub legacy to boot with ext4 in 9.04 ( I think ) as that was the last version with grub legacy. With 9.10 grub2 became the standard, but you can still use grub legacy with all versions of Ubuntu.

If you had a boot script or fdisk printout from before then we would know for sure.

edit:
https://wiki.ubuntu.com/LucidLynx/ReleaseNotes
The default file system for installations of Ubuntu 10.04 LTS is ext4

Sometimes changing BIOS boot order, rebooting and other odd things have made a system boot that did not. Not the usual case, but some have reported it working on a reboot. There were some issues where partitions needed a change (write of a file) to fix an odd issue. Boot-repair does writes and that may have been just enough, again not common.

Do not use dd to copy anything from your 1GB drive to your 3GB drive as the 3GB is gpt and the 1TB is MBR. They are so different in internal structures that low level copy with dd can cause huge problems.

You have NTFS partitions on your 3TB gpt drive? Windows will only install in UEFI mode on a gpt drive.

YannBuntu
January 9th, 2012, 08:05 PM
Hello
additional information:

Then I put the ubuntu installation DVD in the DVD drive and tried again. It came up in with the usual screen that asked whether to boot ubuntu off the DVD, perform a memory test, or boot off the 1TB hard disk drive. When I told it to boot off the defective 1TB hard disk drive, it booted up just fine. This virtually proved my theory that only the MBR and/or grub loader was busted.
I think that proves that your MBR and GRUB were already fine at this time. (so before you used Boot-Repair)
As Oldfred wrote, there may be some other problem which may be linked to BIOS. Please tell us if your boot problem happens again.


my / and /backup partitions were now labeled as being ext4, not ext3 !!!

I confirm what Olfred said: Ubuntu uses ext4 per default, so what you observed is normal.
And i can add that Boot-Repair does not have any option to change ext3 to ext4.


it did not display a "nothing was changed" dialog like is displayed when I simply cancel out of the "boot-repair" application without doing anything.

This is normal behaviour of Boot-Repair. It displays "nothing was changed" only when we click on "cancel".
But for information, creating a BootInfo Summary does not change anything too.


#1: Why did it repair my the MBR [and/or GRUB] on my disk drive when I had both those options unchecked?

See above: your MBR (and GRUB) was already ok.
Boot-Repair does not touch the MBR when those 2 options are unchecked.


#2: Why did the two ext3 partitions on the hard drive all of a sudden become ext4 partitions after running boot-repair?

when you reinstalled Ubuntu 10.04, it used ext4 by default. ext3 came from upgrades from your previous install.

Anyway, thanks for your feedback.

inorganic
January 9th, 2012, 11:45 PM
You may have had ext4 partitions? Ubuntu updated grub legacy to boot with ext4 in 9.04 ( I think ) as that was the last version with grub legacy. With 9.10 grub2 became the standard, but you can still use grub legacy with all versions of Ubuntu.

If you had a boot script or fdisk printout from before then we would know for sure.

edit:
https://wiki.ubuntu.com/LucidLynx/ReleaseNotes
The default file system for installations of Ubuntu 10.04 LTS is ext4

It is possible I chose ext4 when I installed 10.04 LTS. However, I am always very wary to adopt anything even remotely newish or beta when it comes to filesystems --- too much depends on correct operation. However, it is possible. Note that I never just accept the default partitions when I create a new installation of linux. I always go through and manually select everything. But it is still possible that I selected ext4, though I could swear I've seen ext3 many times in the past 2 years I've had it. But maybe not. BTW, did ubuntu create any file that I might still be able to find that states what my original filesystems were? If so, maybe it is still around somewhere.


Sometimes changing BIOS boot order, rebooting and other odd things have made a system boot that did not. Not the usual case, but some have reported it working on a reboot. There were some issues where partitions needed a change (write of a file) to fix an odd issue. Boot-repair does writes and that may have been just enough, again not common.

Remember the following. After I found I could not boot that 1TB drive any more, I ordered a new motherboard, CPU, RAM, disk drive, and so forth because I didn't know what was wrong. After I assembled the new system with new motherboard with very new BIOS (EFI this time), that drive would STILL not boot. So then I booted off the ubuntu installation DVD and installed ubuntu on the 3TB drive, which booted fine. So we have to explain why that 1TB drive did not boot even on the new motherboard and BIOS... while the 3TB drive happily did. Also recall that I could start to boot off of the ubuntu installation DVD, but at the initial screen choose "boot from primary drive", and that would boot into the old 1TB drive that wouldn't otherwise boot. That's why I figured it had to be something extremely early in the boot process, like the MBR.


Do not use dd to copy anything from your 1TB drive to your 3TB drive as the 3TB is gpt and the 1TB is MBR. They are so different in internal structures that low level copy with dd can cause huge problems.

Good thing I didn't try that, huh?


You have NTFS partitions on your 3TB gpt drive? Windows will only install in UEFI mode on a gpt drive.

No, I have two computers. The other one is a ******* xp64 computer and this one we've been talking about is pure ubuntu64 10.04 LTS. It has never had anything to do with ******* on it... it is a pure ubuntu64 linux system, period. No dual boot, ever. I would never trust ******* on my linux systems. No way!

Thanks for your comments.

inorganic
January 9th, 2012, 11:56 PM
Hello, additional information:

I think that proves that your MBR and GRUB were already fine at this time. (so before you used Boot-Repair). As Oldfred wrote, there may be some other problem which may be linked to BIOS. Please tell us if your boot problem happens again.


Can you help me understand how that could be? Remember, I purchased a whole new motherboard, CPU and RAM because I didn't realize it was only the 1TB drive that was preventing the computer from booting up. When I switched out the old MSI motherboard and installed the new gigabyte motherboard with a very much newer BIOS and tried to boot the 1TB drive the behavior did not change at all (no bootup). Therefore, I can't see how this behavior is somehow specific to the motherboard or BIOS. Also note that I didn't change anything in the BIOS just before the computer stopped booting (not for months at least).


I confirm what Olfred said: Ubuntu uses ext4 per default, so what you observed is normal. And i can add that Boot-Repair does not have any option to change ext3 to ext4.

This is possible. My memory has never been that great.



This is normal behaviour of Boot-Repair. It displays "nothing was changed" only when we click on "cancel". But for information, creating a BootInfo Summary does not change anything too.

Okay. I'd suggest displaying that dialog in every situation that "nothing was changed".



See above: your MBR (and GRUB) was already ok. Boot-Repair does not touch the MBR when those 2 options are unchecked.

Well, then all we can say is "magic definitely happened". All I did was run boot-repair and presto, chango... all of a sudden it would boot again. Go figure.



When you reinstalled Ubuntu 10.04, it used ext4 by default. ext3 came from upgrades from your previous install.

ext4 may be default, but I always set up my partitions manually when I create a new system, and I sure thought I remembered choosing ext3. But like I said above, my memory of tiny details from 2 years ago isn't very good, so I'll accept that maybe I did select ext4. I agree that it would "just be too strange" for what happened... unless you purposely added code to do that, which would be very odd. And sure enough, you didn't.


Anyway, thanks for your feedback.

And thank you for a very spiffy little application. It is very useful.

BTW, if I had selected "repair MBR" option, would it have written exactly 446 bytes, or would it have written the whole 512 bytes or more? After reading so much about the MBR in the past few days, I'm kind of curious. Thanks.

YannBuntu
January 10th, 2012, 03:10 PM
Hello


Can you help me understand how that could be?

I'm afraid i am not strong enough for this. My guess was a Bios problem, but you say it is not, so.. i think it would be easier to understand the problem if you could reproduce it.


I'd suggest displaying that dialog in every situation that "nothing was changed".

Good idea, thanks. I'll do it soon.


BTW, if I had selected "repair MBR" option, would it have written exactly 446 bytes, or would it have written the whole 512 bytes or more?

Good question, i'm surprised nobody asked it before. I confirm it only changes the first 446 bytes.
And for information, Boot-Repair performs a backup of the entire MBR (512 bytes+ space before the first partition) before any operation.
You can also manually backup it via the "Backup partition tables, bootsectors and logs" button:

http://pix.toile-libre.org/upload/img/1326203507.png (http://pix.toile-libre.org/?img=1326203507.png)

YannBuntu
January 13th, 2012, 03:05 PM
Hello
Some new features in Boot-Repair :

Add or move the boot flag on a chosen primary partition (special thanks to Oldfred) :

http://pix.toile-libre.org/upload/img/1326203507.png



Easily use the last version (GIT) of Boot-Info-Script :

http://pix.toile-libre.org/upload/img/1326204755.png

and also:


I'd suggest displaying that dialog in every situation that "nothing was changed".

DONE. Thanks Inorganic!

Sp4iK
January 16th, 2012, 12:06 PM
Hello, I just found this amazing app that has saved my life 'cause I lost my MBR and it was able to repair it and point it to the correct partition with grub.

Now I would like to know two things.
First, is Boot-Repair going to support Burg? I've recently installed it and I love to have that boot interface.
Second, is Boot-Repair able to move /boot to another partition? I found "Separate /boot partition" option but I haven't found any documentation about the specifics on advanced options so I don't want to mess if I'm not sure of what every option does.

YannBuntu
January 16th, 2012, 06:43 PM
Hi Sp4iK,


is Boot-Repair going to support Burg?

As long as it is not in Debian's repositories, i don't even think about it.
Furthermore, Boot-Repair is designed for REPAIRING, not CUSTOMIZING.



is Boot-Repair able to move /boot to another partition?

No.
The /boot partition contains a /boot/grub sub-folder, and some other files (kernel files..)
The "Separate /boot partition" option of Boot-Repair just mounts the selected partition on /boot during GRUB2 re-installation. Which means that it will just recreate the /boot/grub sub-folder, not the other files.
Indeed i was thinking of adding another option to recreate those "other files", but i don't know how to do it, if someone has an idea don't hesitate to propose it :)

rootmaster23
January 18th, 2012, 04:52 PM
YOU're THE MAN!

I have to use Windows for only one Program i use for work from time to time and this s***ty OS deleted my MBR!
After Boot Repair I had to restore Win on an earlier restore Point but now everything works and most important my Ubuntu is running again!

Thank you for that great program!!\\:D/

No one can do it better!!!

uh-huh
January 25th, 2012, 12:43 AM
boot-repair works great. I know because I used it before. Now when I tried using it I get "command not found". So I tried re-installing it


cordyceps@gnubu:~$ sudo apt-get install boot-repair
[sudo] password for cordyceps:
Reading package lists... Done
Building dependency tree
Reading state information... Done
boot-repair is already the newest version.
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
boot-repair : Depends: boot-sav-gui but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

$sudo apt-get -f install
<snip>
The following NEW packages will be installed:
boot-sav-gui
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
1 not fully installed or removed.
Need to get 0 B/229 kB of archives.
After this operation, 1,655 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
(Reading database ... 190678 files and directories currently installed.)
Unpacking boot-sav-gui (from .../boot-sav-gui_3.11-0ppa2~oneiric_all.deb) ...
dpkg: error processing /var/cache/apt/archives/boot-sav-gui_3.11-0ppa2~oneiric_all.deb (--unpack):
trying to overwrite '/usr/share/locale/fr/LC_MESSAGES/cleancommon-translations.mo', which is also in package boot-repair-common 3.0-0ppa52~oneiric
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/boot-sav-gui_3.11-0ppa2~oneiric_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
cordyceps@gnubu:~$

There's something similar in a bug-report I saw, but it was in French, which I don't know.

FWIW: I'm using Lubuntu-11.10. Not sure if related, but I noticed the problem after a dist-upgrade and the boot-menu was missing my other OS -- had to use the grub> prompt. I also tried purging whatever was left of the previous install but it didn't help ;(


FWIW.2 If I run sudo boot-repair a little gui window opens that says "please wait while updating" then this:
<snip>
Package clean-gui is not installed, so not removed
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
boot-repair : Depends: boot-sav-gui but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package /usr/bin
cp: cannot stat `/var/log/boot-sav/clean_sources': No such file or directory
/usr/bin/boot-repair: line 68: ./glade2script.py: No such file or directory
cordyceps@gnubu:~$

And IRC #ubuntu is no help at all ;(

YannBuntu
January 25th, 2012, 01:00 AM
Hello,
this should work:


sudo apt-get purge -y boot-repair clean clean-gui clean-ubiquity-common boot-repair-common
then

sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update; sudo apt-get install -y boot-repair && boot-repair

uh-huh
January 25th, 2012, 04:02 AM
I think it's fixed! Thanks a lot Yann! This is a very useful bit of software. I love the pastebin at the end, very thoughtful;)

I won't reboot until I have to go over to the gentoo side of this box, might be a couple of days. I'll post an update then.

sav2005
January 25th, 2012, 06:02 AM
Boot-repair is taking over an hour to scan my system and has not yet moved from the "Scanning Systems" dialog to the Interactive GUI. I have a 160G System Drive, 2 x 500G Data drives. Windows7 on hda0, /boot on hda1 (4G ext4), swap on hda2, / on hdc1, /home on /hdc2 (ext 4), Windows data on hdb1 (fat32).

Is this time usual - it's still asking me to wait a few seconds? I'm running from the CD and I've tried about 3 times so far.

YannBuntu
January 25th, 2012, 12:21 PM
@sav2005: hello. This is not normal. Please could you reproduce the bug, then send me by email (yannubuntu ATT gmail DOTT com) a ZIP (or TAR) of your /var/log/bot-sav folder ?

Ceriel Nosforit
January 25th, 2012, 07:49 PM
This software keeps bailing me out of trouble. I just want to say thanks! :KS

(though this BootInfo summary thing is taking an awfully long time to complete... >_<)

ED>
closed it and ran it again directly from the menu - no problem and quick execution

uh-huh
January 26th, 2012, 06:53 PM
I won't reboot until I have to go over to the gentoo side of this box, might be a couple of days. I'll post an update then.

Like a charm! Grub2 is a beast and you have tamed it. Salud!

coolparth
January 26th, 2012, 07:39 PM
Hi,

When trying to upgrade to Ubuntu 10.04 from 9.10 on a machine with a LVM partition, i started getting the "Kernel panic - not syncing: VFS: Unable to mount root fs" issue..

In order to attempt a repair, i tried to use boot-repair... but it keeps getting stuck after the first scan itself..

First is shows the message :
"This will install the [lvm2] packages. Do you want to continue?"

When i click ok, after some time it shows the message :
" Please install the [lvm2] packages. Then try again."

When i click ok it just closes.. What could be wrong ?

Btw if you can help me in any other way, here is the output of my bootinfo sript results
file



Boot Info Script 0.60 from 17 May 2011


============================= Boot Info Summary: ===============================

=> Grub2 (v1.97-1.98) is installed in the MBR of /dev/sdd and looks at sector
1 of the same hard drive for core.img. core.img is at this location and
looks in partition 5 for /grub.

sdd1: __________________________________________________ ________________________

File system: LVM2_member
Boot sector type: -
Boot sector info:

sdd2: __________________________________________________ ________________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sdd5: __________________________________________________ ________________________

File system: ext2
Boot sector type: Unknown
Boot sector info:
Operating System:
Boot files: /grub/grub.cfg /grub/core.img

tws-100-root': __________________________________________________ _______________

File system:
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: unknown filesystem type ''

tws-100-swap_1': __________________________________________________ _____________

File system:
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: unknown filesystem type ''
mount: unknown filesystem type ''

============================ Drive/Partition Info: =============================

Drive: sdd __________________________________________________ ___________________

Disk /dev/sdd: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdd1 * 63 155,798,369 155,798,307 8e Linux LVM
/dev/sdd2 155,798,370 156,296,384 498,015 5 Extended
/dev/sdd5 155,798,433 156,296,384 497,952 83 Linux


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL


/dev/sdd1 TgpjvO-T238-R2Gh-JsBG-xcDv-vA8s-pVSwic LVM2_member
/dev/sdd5 48dd331a-3b6b-4dc2-a429-e6093fba0661 ext2

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/sdd5 /media/48dd331a-3b6b-4dc2-a429-e6093fba0661 ext2 (rw,nosuid,nodev,uhelper=udisks)



============================= sdd5/grub/grub.cfg: ==============================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod lvm
insmod ext2
set root=(tws-100-root)
search --no-floppy --fs-uuid --set fa0fb1ba-8b82-4902-aaae-9cbc8cd6706f
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.32-38-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.32-38-generic root=/dev/mapper/tws--100-root ro quiet splash
}
menuentry "Ubuntu, Linux 2.6.32-38-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.32-38-generic root=/dev/mapper/tws--100-root ro single
}
menuentry "Ubuntu, Linux 2.6.31-23-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.31-23-generic root=/dev/mapper/tws--100-root ro quiet splash
initrd /initrd.img-2.6.31-23-generic
}
menuentry "Ubuntu, Linux 2.6.31-23-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.31-23-generic root=/dev/mapper/tws--100-root ro single
initrd /initrd.img-2.6.31-23-generic
}
menuentry "Ubuntu, Linux 2.6.31-22-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.31-22-generic root=/dev/mapper/tws--100-root ro quiet splash
initrd /initrd.img-2.6.31-22-generic
}
menuentry "Ubuntu, Linux 2.6.31-22-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.31-22-generic root=/dev/mapper/tws--100-root ro single
initrd /initrd.img-2.6.31-22-generic
}
menuentry "Ubuntu, Linux 2.6.31-20-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.31-20-generic root=/dev/mapper/tws--100-root ro quiet splash
initrd /initrd.img-2.6.31-20-generic
}
menuentry "Ubuntu, Linux 2.6.31-20-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.31-20-generic root=/dev/mapper/tws--100-root ro single
initrd /initrd.img-2.6.31-20-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.31-14-generic root=/dev/mapper/tws--100-root ro quiet splash
initrd /initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,5)
search --no-floppy --fs-uuid --set 48dd331a-3b6b-4dc2-a429-e6093fba0661
linux /vmlinuz-2.6.31-14-generic root=/dev/mapper/tws--100-root ro single
initrd /initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -1 ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
--------------------------------------------------------------------------------

=================== sdd5: Location of files loaded by Grub: ====================

GiB - GB File Fragment(s)

74.323258877 = 79.803991552 grub/core.img 2
74.391074657 = 79.876808192 grub/grub.cfg 1
74.315532207 = 79.795695104 initrd.img-2.6.31-14-generic 34
74.336310863 = 79.818006016 initrd.img-2.6.31-20-generic 40
74.350810528 = 79.833574912 initrd.img-2.6.31-22-generic 41
74.365232944 = 79.849060864 initrd.img-2.6.31-23-generic 38
74.297540188 = 79.776376320 vmlinuz-2.6.31-14-generic 16
74.301002026 = 79.780093440 vmlinuz-2.6.31-20-generic 17
74.339796543 = 79.821748736 vmlinuz-2.6.31-22-generic 22
74.346179485 = 79.828602368 vmlinuz-2.6.31-23-generic 18
74.360760212 = 79.844258304 vmlinuz-2.6.32-38-generic 20

======================== Unknown MBRs/Boot Sectors/etc: ========================

Unknown BootLoader on sdd5

00000000 3f e0 a6 6b b9 2a 00 00 63 61 6e 6e 6f 74 20 62 |?..k.*..cannot b|
00000010 65 61 72 20 6f 72 20 73 74 61 6e 64 62 65 20 75 |ear or standbe u|
00000020 6e 65 71 75 61 6c 20 74 6f 76 65 72 79 65 78 74 |nequal toveryext|
00000030 72 65 6d 65 6c 79 00 e9 98 bf 20 e9 98 bf 00 00 |remely.... .....|
00000040 b0 e0 a6 6b b9 2a 00 00 58 e0 a6 6b b9 2a 00 00 |...k.*..X..k.*..|
00000050 00 00 00 00 00 00 00 00 70 e0 a6 6b b9 2a 00 00 |........p..k.*..|
00000060 a3 e0 a6 6b b9 2a 00 00 ab e0 a6 6b b9 2a 00 00 |...k.*.....k.*..|
00000070 74 6f 6f 20 6e 75 6d 65 72 6f 75 73 20 74 6f 20 |too numerous to |
00000080 6d 65 6e 74 69 6f 6e 20 69 6e 64 69 76 69 64 75 |mention individu|
00000090 61 6c 6c 79 20 6f 72 20 6f 6e 65 20 62 79 20 6f |ally or one by o|
000000a0 6e 65 00 e9 98 bf 20 e9 98 bf 00 00 00 00 00 00 |ne.... .........|
000000b0 10 e1 a6 6b b9 2a 00 00 c8 e0 a6 6b b9 2a 00 00 |...k.*.....k.*..|
000000c0 00 00 00 00 00 00 00 00 e0 e0 a6 6b b9 2a 00 00 |...........k.*..|
000000d0 07 e1 a6 6b b9 2a 00 00 0f e1 a6 6b b9 2a 00 00 |...k.*.....k.*..|
000000e0 73 65 69 7a 65 20 74 68 65 20 6f 70 70 6f 72 74 |seize the opport|
000000f0 75 6e 65 20 6d 6f 6d 65 6e 74 6c 6f 73 65 20 6e |une momentlose n|
00000100 6f 20 74 69 6d 65 00 e9 98 bf 20 e9 98 bf 00 00 |o time.... .....|
00000110 80 e1 a6 6b b9 2a 00 00 28 e1 a6 6b b9 2a 00 00 |...k.*..(..k.*..|
00000120 00 00 00 00 00 00 00 00 40 e1 a6 6b b9 2a 00 00 |........@..k.*..|
00000130 75 e1 a6 6b b9 2a 00 00 7d e1 a6 6b b9 2a 00 00 |u..k.*..}..k.*..|
00000140 63 61 6e 20 73 74 69 6c 6c 20 62 65 20 63 6f 6e |can still be con|
00000150 73 69 64 65 72 65 64 20 6d 61 79 20 61 66 74 65 |sidered may afte|
00000160 72 20 61 6c 6c 20 62 65 20 61 63 63 65 70 74 65 |r all be accepte|
00000170 64 20 61 73 00 e9 98 bf 20 e9 98 bf 00 00 00 00 |d as.... .......|
00000180 d8 e1 a6 6b b9 2a 00 00 98 e1 a6 6b b9 2a 00 00 |...k.*.....k.*..|
00000190 00 00 00 00 00 00 00 00 b0 e1 a6 6b b9 2a 00 00 |...........k.*..|
000001a0 cb e1 a6 6b b9 2a 00 00 d3 e1 a6 6b b9 2a 00 00 |...k.*.....k.*..|
000001b0 66 72 65 71 75 65 6e 74 6c 79 6f 66 74 65 6e 61 |frequentlyoftena|
000001c0 74 20 61 6e 79 20 74 69 6d 65 00 e9 98 bf 20 e9 |t any time.... .|
000001d0 98 bf 00 00 00 00 00 00 20 e2 a6 6b b9 2a 00 00 |........ ..k.*..|
000001e0 f0 e1 a6 6b b9 2a 00 00 00 00 00 00 00 00 00 00 |...k.*..........|
000001f0 08 e2 a6 6b b9 2a 00 00 13 e2 a6 6b b9 2a 00 00 |...k.*.....k.*..|
00000200

Unknown BootLoader on tws-100-root'


Unknown BootLoader on tws-100-swap_1'


=============================== StdErr Messages: ===============================

unlzma: Decoder error
skip_dev_dir: Couldn't split up device name tws-100-root'
Volume group name tws-100-root' has invalid characters
Skipping volume group tws-100-root'
skip_dev_dir: Couldn't split up device name tws-100-root'
Volume group name tws-100-root' has invalid characters
Skipping volume group tws-100-root'
skip_dev_dir: Couldn't split up device name tws-100-root'
Volume group name tws-100-root' has invalid characters
Skipping volume group tws-100-root'
hexdump: /dev/mapper/tws-100-root': No such file or directory
hexdump: /dev/mapper/tws-100-root': No such file or directory
skip_dev_dir: Couldn't split up device name tws-100-swap_1'
Volume group name tws-100-swap_1' has invalid characters
Skipping volume group tws-100-swap_1'
skip_dev_dir: Couldn't split up device name tws-100-swap_1'
Volume group name tws-100-swap_1' has invalid characters
Skipping volume group tws-100-swap_1'
skip_dev_dir: Couldn't split up device name tws-100-swap_1'
Volume group name tws-100-swap_1' has invalid characters
Skipping volume group tws-100-swap_1'
hexdump: /dev/mapper/tws-100-swap_1': No such file or directory
hexdump: /dev/mapper/tws-100-swap_1': No such file or directory

uh-huh
January 26th, 2012, 09:03 PM
Hi,

When trying to upgrade to Ubuntu 10.04 from 9.10 on a machine with a LVM partition, i started getting the "Kernel panic - not syncing: VFS: Unable to mount root fs" issue..


Kernel panics are usually a driver issue. boot-repair won't help here I don't think.

YannBuntu
January 26th, 2012, 09:31 PM
@coolparth: uh-huh is right, Boot-Repair won't repair the kernel panic.

To solve the "lvm2 problem" : before running Boot-Repair, please type the following command in a terminal:

sudo apt-get install -y lvm2

(if any error, please indicate it here)