[Boot-Repair] Graphical tool to repair the PC boot in one click

[oldfred]

You cannot edit grub.cfg. Any update-grub will overwrite that and any kernel, grub or some other updates will trigger a update-grub. So you changes are only temporary.

UEFI seems to remember things on its own. To uninstall you have to remove the Ubuntu partition, remove the ubuntu folder in the efi partition and then go into UEFI "Boot maintenance manager" or "UEFI Shell" and edit/remove the saved entries. And reset UEFI to use the Windows efi file as the default boot. For those where the efi files were renamed by Boot-Repair, they need to run Boot-Repair and un-rename them or restore files.

[fonsi2099]

dual boot 13.04 + 12.04 How can login in my first OS 13.04

I have deleted my /boot partition of 13.04 and I have rewritten it accidentally with/boot partition of 12.04 by re- installing 12.04, now I have two OS 13.04 and 2nd OS 12.04 but I have not dual-boot in grub menu I see only 12.04 not choice for 13.04. how can I log in my partition of 13.04?
"
lts-Aspire-S3:~$ sudo update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.5.0-30-generic
Found initrd image: /boot/initrd.img-3.5.0-30-generic
Found linux image: /boot/vmlinuz-3.5.0-23-generic
Found initrd image: /boot/initrd.img-3.5.0-23-generic
Found memtest86+ image: /memtest86+.bin
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
ERROR: sil: invalid metadata checksum in area 3 on /dev/sda
Found Ubuntu 13.04 (13.04) on /dev/sda2
done"

lts-Aspire-S3:~$ sudo fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004ed07

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 976895 487424 83 Linux
/dev/sda2 976896 49805311 24414208 83 Linux
/dev/sda3 49807358 625141759 287667201 5 Extended
/dev/sda5 49807360 166991871 58592256 83 Linux
/dev/sda6 166993920 264648703 48827392 83 Linux
/dev/sda7 264650752 362305535 48827392 83 Linux
/dev/sda8 362307584 420903287 29297852 83 Linux
/dev/sda9 459964416 538087423 39061504 83 Linux
/dev/sda10 538089472 577148927 19529728 83 Linux
/dev/sda11 577150976 608399359 15624192 83 Linux
/dev/sda12 608401408 625141759 8370176 82 Linux swap / Solaris
/dev/sda13 420904960 459956223 19525632 83 Linux

Partition table entries are not in disk order

Disk /dev/sdb: 2 MB, 2097152 bytes
255 heads, 63 sectors/track, 0 cylinders, total 4096 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xffffffff

Disk /dev/sdb doesn't contain a valid partition table

Thank you for any help.

[oldfred]

@fonsi2099
Please do not post same question in two threads. We all are voluteers and need to know what has already been suggested not to duplicate efforts.
From you other post, I created your own thread.
http://ubuntuforums.org/showthread.php?t=2147277

[LightningHall]

You cannot edit grub.cfg. Any update-grub will overwrite that and any kernel, grub or some other updates will trigger a update-grub. So you changes are only temporary.

UEFI seems to remember things on its own. To uninstall you have to remove the Ubuntu partition, remove the ubuntu folder in the efi partition and then go into UEFI "Boot maintenance manager" or "UEFI Shell" and edit/remove the saved entries. And reset UEFI to use the Windows efi file as the default boot. For those where the efi files were renamed by Boot-Repair, they need to run Boot-Repair and un-rename them or restore files.

Duly noted!

I have run into a problem... My battery won't charge. It gets the "plugged in not charging" bubble in W8. I've looked up ways for relieving this elsewhere which entails a dance of unplug/plug remove battery etc, just wondering if this is a result of the dual boot?

[oldfred]

I have seen one or two threads with that in the title but would not expect that to be a dual boot issue. With dual boot there really is no part of one system that sees another.
But we said that with a modem years ago, and it turned out modem saved settings from one system and the other did not correctly reset on reboot. I think it was Windows not resetting so Linux had to reset on boot & shutdown as fix.

[LightningHall]

Oh computers, they do whatever the heck they please some times.

One more thing that I forgot... Windows will not shut down now. It says it's shutting down and goes to the splash screen (or whatever the heck you call it; pre-login screen). More specifically screen goes black, I move mouse, it goes to splash screen. I have to hold the power button to get out of Windows. I did close my lid which sends it to "sleep" mode, before I closed Windows down and experienced this behavior.

[oldfred]

I shut down XP over a year ago.

You may have to ask in a Windows forum.
http://www.eightforums.com/

[sudodus]

I would try to repair the file system of the Windows partition using the Windows tool for it

In XP it is

chkdsk /f

and in newer versions graphical user interface versions to check and repair the file system (which I think run chkdsk under the hood). You find that GUI tool from the control panel.

This repair will be done the next time you boot (reboot) Windows.It is a good 'first aid'.

[LightningHall]

I would try to repair the file system of the Windows partition using the Windows tool for it

In XP it is

chkdsk /f

and in newer versions graphical user interface versions to check and repair the file system (which I think run chkdsk under the hood). You find that GUI tool from the control panel.

This repair will be done the next time you boot (reboot) Windows.It is a good 'first aid'.

chkdsk. bootrec. all those didn't work. I deleted the Ubuntu partition, re-allocated it for Windows usage. Go figure, Windows wouldn't boot. I went into dos and deleted Ubuntu folder. Still no luck. So I googled, as one does, and found this: http://superuser.com/questions/46076...efi-bootloader which solved my problem. Mad props to that User.

I thank you all so very much for all your help. I'm going to try and re-dualboot W8 and Ubuntu and hopefully not fudge anything up some time in the future. Any suggestions on a page that shows the exact steps to go through?

Once again... thank you very VERY much!

How to mark this as solved?

[oldfred]

You have to have your own thread to be able to mark it solved.