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

[oldfred]

@maximilian.krause

I do not know why you are getting the mount errors. It seems script may be trying to mount some partitions twice?

You do not have UEFI. The efi partition looks like it is just a vendors utility partition. Some get flagged as efi but are not really for UEFI booting. No 32 bit version will boot UEFI anyway. And UEFI needs gpt partitioning.

It did not run df -h, so I cannot see where files are on drive, but a few BIOS have issues with boot files over 100GB on drive. Primarily USB drives but maybe some others. I might just try a smaller / (root) or separete /boot partition that is fully inside the first 100GB. If you have to shrink the NTFS more, you can, but then make a NTFS data partition for shared data after the / or /home partitions. About half the users with large / beyond 100GB have been able to test if it works just by shrinking current / so it is entirely inside the first 100GB of drive.

[maximilian.krause]

hmm, to get / into the first 100GB wont work too easy... i didn't want to reinstall Windows. a seperate boot-partition would be easier if it wont have to be too big. Will 15GB suffice? Or will it need less? Sorry, I'm a newbie to Linux systems, can i specify a partition to be /boot during Lubuntu installation? (probably, i think i will just try right now) this will then have to work with logical partitions because I'm not really sure if my system support EFI. (thanks for the fast reply!) EDIT: the bootloader will still have to install to /dev/sda (meaning the physical device), or not?

---

RE-EDIT: didn't work... I tried a partition for /boot (250MB for safety, read somewhere that 100-200MB are normal), i was to 100% within the first 100GB on the disc, on reboot and loading Lubuntu: just a black screen. I had that before, right after installation. reboot would lead me to the BusyBox-problem i described above.

[oldfred]

UUIDs are supposed to be better, but a couple of cases users have converted to the older way with a device setting like /dev/sda3. If you get grub menu use e for edit to test this change. If it works we can do some other things to make it permanent.

menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e5ed86df-1d33-4c52-949b-af0a4417d4e7' {
recordfail
	load_video
	gfxmode $linux_gfx_mode
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  e5ed86df-1d33-4c52-949b-af0a4417d4e7
	else
	  search --no-floppy --fs-uuid --set=root e5ed86df-1d33-4c52-949b-af0a4417d4e7
	fi
	linux	/boot/vmlinuz-3.11.0-13-generic root=UUID=e5ed86df-1d33-4c52-949b-af0a4417d4e7 ro   quiet splash $vt_handoff
	initrd	/boot/initrd.img-3.11.0-13-generic
}

If you reinstalled with a separate /boot the first set root (hd0,2) needs to be the /boot partition.
And then the root= need to be your / (root) partition probably now sda3?
So it should look more like this:
linux /boot/vmlinuz-3.11.0-13-generic root=/dev/sda3 ro quiet splash $vt_handoff




Also you have the gma500, I guess it has some idiosyncrasies.
Ubuntu 12.04 has been officially released and, with minor adjustments, the intel gma500 video card is working out of the box.
http://blog.bodhizazen.net/linux/ubu...-boot-options/

Welcome to the new support thread for the GMA500 (Poulsbo) graphics card.
http://ubuntuforums.org/showthread.php?t=1984236

Intel GMA500 "Poulsbo" video hardware
https://wiki.ubuntu.com/HardwareSupp...oCardsPoulsbo/

[maximilian.krause]

Since those are logical partitions now they are (hd0,msdos5) and /dev/sda6 in this case, but yes, i tried that.

I edited the line "linux ..." and hit CTRL-x to boot,but same problem (now says "/dev/sda6" does not exist)

also by default it says "/vmlinuz...." instead of "/boot/vmlinuz....". "/boot/vm..." wont work, because there is nothing to find there. is that strange? (i did reinstall, like i said before, should i try boot-repair again to make this boot info?)

concerning the graphics: worked fine when booting live from USB-stick. native resolution worked fine, even jmol worked without any problem (chemical model viewer)

[oldfred]

Path is different with a separate /boot partition and I am not sure of details as I never used a /boot partition. When in a /boot partition it does not have the /boot in the path that it would need if in / (root).

For whatever reason they make the live installer work just fine with a low level default graphics driver, but then when the installer runs it may install a different driver. But if it works then you do not have that issue. We need to get there first.

I am running out of ideas, post a new link to the BootInfo report. If you run repairs from Boot-Repair be sure to check the separate /boot partition.

Update. This thread suggests additional boot parameters that are somewhat unique to your type machine.
http://ubuntuforums.org/showthread.php?t=1837473

[maximilian.krause]

Seperate /boot partition was already checked. Should i also check "Enable ATA support" (if i correctly translated from the German entry I'm reading), because the disk seems to be ATA?

Haha, thats interesting with the drivers, because my touchpad wont work during installation of the system, only keyboard. Its a bit of a nuisance since i already reinstalled a few times to test different setups of partitions... If nothing works i will try to reinstall again without /boot partition and then try to call the device with the oldfashioned way (/dev/sdaX). But for now just boot-repair ( http://paste.ubuntu.com/6501561 ) and then probably with ATA support

EDIT: now that I reflect upon it, the /boot partition could have been a useless approach concerning the possible "first 100GB problem", because its a logical partition crammed into one primary partition with the others for linux (otherwise i'd have to delete another primary partition... and i don't know whats inside them)... if i have time tomorrow i will try to put an empty HDD into the EeePC and install Lubuntu as the only OS on that disc. though i hope this wont do the trick, because this could than possibly propose the same problem if windows wasn't installed on a partition within the first 100GB (supposed i would then reinstall it...).

For now thank you very much for your kind help!

[juanluisrp]

@oldfred

@juanluisrp

Do you still have secure boot on?
It looks like Ubuntu is installed in UEFI mode but not with secure boot. If secure boot is on then only Windows will boot.

Secure boot is off. Also BIOS has UEFI mode actived.

[oldfred]

Not sure what else to suggest.

Did you see the update I added in post #1605. That suggested some boot parameters that I have not seen before.

[piutegunnut2]

I attempeted a boot repair fix and it did not fix my issues with a computer. I believe it is running 12.04 ubuntu. It boots to terminal and won't let me reset the password in sudo iether. Here is the URl httppastebin.ubuntu.com64999381. Any help would be great. it is a h61 1155 board running it and is running onboard graphics. g620 cpu. It is a friends and they messed it up this last week.

[oldfred]

@piutegunnut2
Pastebin link is not working, please post a working link.