PDA

View Full Version : [UbuntuGnome] grub2 boot problems



mkobx
April 3rd, 2015, 02:26 PM
Hi guys,

unfortunately I crashed somehow my dualboot-sys (Win8.1 & Ubuntu 14.04), so I was always just booting into win, the grub2 bootmgr was never shown.
So I tried several approaches to fix it(run boot repair & so on...), but nothing helped, so I decided to reinstalled ubuntu, which I did by using the ubuntugnome 14.04(I didn't touched win).

But it didn't solved my issue, I'm always booting into win.
Below I post my boot-info generated by my last run of boot-repair(http://paste.ubuntu.com/10730305/).

I hope somebody can help me to solve my issue. :-)
PS: I search for similar solutions but I didn't found something useful.


Some techinical details:
I got an sony vaio pro SVP1321S1EBI
Using 64Bit at Win & Ubuntugnome


Boot Info Script e7fc706 + Boot-Repair extra info
============================= Boot Info Summary: ===============================

=> No boot loader is installed in the MBR of /dev/sda.
=> Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sdb.

sda1: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sda2: __________________________________________________ ________________________

File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /EFI/Boot/bkpbootx64.efi /EFI/Boot/bootia32.efi
/EFI/Boot/bootx64.efi /EFI/ubuntu/MokManager.efi
/EFI/ubuntu/grubx64.efi /EFI/ubuntu/shimx64.efi
/EFI/Microsoft/Boot/bootmgfw.efi
/EFI/Microsoft/Boot/bootmgr.efi
/EFI/Microsoft/Boot/memtest.efi
/boot-sav/log/2015-03-30__17h36boot-repair09/sda2/bootx
64.efi
/boot-sav/log/2015-03-30__18h20boot-repair16/sda2/bootx
64.efi
/boot-sav/log/2015-04-03__12h03boot-repair02/sda2/bootx
64.efi

sda3: __________________________________________________ ________________________

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

sda4: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Windows/System32/winload.exe

sda5: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sda6: __________________________________________________ ________________________

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

sda7: __________________________________________________ ________________________

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

sdb1: __________________________________________________ ________________________

File system: vfat
Boot sector type: SYSLINUX 4.07 2013-07-25
Boot sector info: Syslinux looks at sector 61002 of /dev/sdb1 [B]for its
second stage. SYSLINUX is installed in the /uui
directory. No errors found in the Boot Parameter Block.
Operating System:
Boot files: /boot/grub/grub.cfg /casper/vmlinuz.efi
/EFI/BOOT/grubx64.efi

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

Drive: sda __________________________________________________ ___________________

Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 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

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 1 250,069,679 250,069,679 ee GPT


GUID Partition Table detected.

Partition Start Sector End Sector # of Sectors System
/dev/sda1 2,048 616,447 614,400 Windows Recovery Environment (Windows)
/dev/sda2 616,448 821,247 204,800 EFI System partition
/dev/sda3 821,248 1,083,391 262,144 Microsoft Reserved Partition (Windows)
/dev/sda4 1,083,392 165,261,311 164,177,920 Data partition (Windows/Linux)
/dev/sda5 249,147,392 250,068,991 921,600 Windows Recovery Environment (Windows)
/dev/sda6 165,261,312 184,793,087 19,531,776 Swap partition (Linux)
/dev/sda7 184,793,088 249,147,391 64,354,304 Data partition (Linux)

Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 14.9 GiB, 16008609792 bytes, 31266816 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

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 * 2,048 31,266,815 31,264,768 c W95 FAT32 (LBA)


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 0C4403264403125E ntfs Wiederherstellung
/dev/sda2 B803-D3B3 vfat
/dev/sda3
/dev/sda4 160C05280C050489 ntfs Windows
/dev/sda5 12B43EB5B43E9AE5 ntfs
/dev/sda6 f49001a5-7fb4-4bc0-bedf-05e569594562 swap
/dev/sda7 592ec12d-c032-43d5-b5f3-5fb57cda71b8 ext4
/dev/sdb1 14F1-183C vfat UUI

========================= "ls -l /dev/disk/by-id" output: ======================

total 0
lrwxrwxrwx 1 root root 9 Apr 3 12:42 ata-SAMSUNG_MZNTD128HAGM-00000_S15YNYAD918691 -> ../../sda
lrwxrwxrwx 1 root root 10 Apr 3 12:42 ata-SAMSUNG_MZNTD128HAGM-00000_S15YNYAD918691-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 3 12:41 ata-SAMSUNG_MZNTD128HAGM-00000_S15YNYAD918691-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 3 12:41 ata-SAMSUNG_MZNTD128HAGM-00000_S15YNYAD918691-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr 3 12:42 ata-SAMSUNG_MZNTD128HAGM-00000_S15YNYAD918691-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Apr 3 2015 ata-SAMSUNG_MZNTD128HAGM-00000_S15YNYAD918691-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Apr 3 2015 ata-SAMSUNG_MZNTD128HAGM-00000_S15YNYAD918691-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Apr 3 2015 ata-SAMSUNG_MZNTD128HAGM-00000_S15YNYAD918691-part7 -> ../../sda7
lrwxrwxrwx 1 root root 9 Apr 3 12:41 usb-SanDisk_Cruzer_Switch_4C530009011220117154-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Apr 3 2015 usb-SanDisk_Cruzer_Switch_4C530009011220117154-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Apr 3 12:42 wwn-0x50025385000cc8fb -> ../../sda
lrwxrwxrwx 1 root root 10 Apr 3 12:42 wwn-0x50025385000cc8fb-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Apr 3 12:41 wwn-0x50025385000cc8fb-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Apr 3 12:41 wwn-0x50025385000cc8fb-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Apr 3 12:42 wwn-0x50025385000cc8fb-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Apr 3 2015 wwn-0x50025385000cc8fb-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Apr 3 2015 wwn-0x50025385000cc8fb-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Apr 3 2015 wwn-0x50025385000cc8fb-part7 -> ../../sda7

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

Device Mount_Point Type Options

/dev/loop0 /rofs squashfs (ro,noatime)
/dev/sda5 /media/ubuntu-gnome/12B43EB5B43E9AE5 fuseblk (rw,nosuid,nodev,allow_other,default_permissions,b lksize=4096)
/dev/sda7 /media/ubuntu-gnome/592ec12d-c032-43d5-b5f3-5fb57cda71b8 ext4 (rw,nodev,nosuid,uhelper=udisks2)
/dev/sdb1 /cdrom vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,ioc harset=iso8859-1,shortname=mixed,errors=remount-ro)

oldfred
April 3rd, 2015, 03:02 PM
I have never seen this file before & I have seen a lot of installs. Did you install a 32 bit UEFI version?
EFI/Boot/bootia32.efi

It looks like you have done one of the rename fixes. Sony's modify UEFI internally to only boot the Windows description, so you have to do one of several work arounds.


BootOrder: 000B,0007,0008,000A,0006,0001
Boot0001* Windows Boot Manager HD(2,96800,32000,31e8b984-b784-4947-a0b7-24bd7f46b9df)File(EFIubuntugrubx64.efi)WINDOWS.... .....x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...t................
Boot0006* Windows Boot Manager HD(2,96800,32000,31e8b984-b784-4947-a0b7-24bd7f46b9df)File(EFIMicrosoftBootbootmgfw.efi)
Boot0007* Windows Boot Manager HD(4,108800,ed73800,04ce33f7-8a9b-4234-8a63-0784b1331602)File(EFIBootbootx64.efi)
Boot0008* Windows Boot Manager HD(4,108800,ec92800,04ce33f7-8a9b-4234-8a63-0784b1331602)File(EFIBootbootx64.efi)
Boot000A* Windows Boot Manager HD(4,108800,9c92800,04ce33f7-8a9b-4234-8a63-0784b1331602)File(EFIBootbootx64.efi)



1 says Windows but is grub
6 is the real Windows boot, unless you also renamed bootmgfw.efi
7,8, & A are the hard drive boot entry bootx64.efi

Many with Sony rename the hard drive boot entry to make it work.
One Sony user

The trick was to manually copy the ubuntu Boot directory in place of the \EFI\Boot Directory, and rename shimx64.efi to \EFI\Boot\bootx64.efi (not \EFI\Microsoft\Boot\bootmgfw.efi )

HOWTO: Sony Vaio Pro 13 DualBoot (Win 8 + Ubuntu Trusty 14.04) SecureBoot Wifi LVM
http://ubuntuforums.org/showthread.php?t=2227580
Sony Vaio Pro 13 - To get into UEFI press this "Assist" button BEFORE starting
http://askubuntu.com/questions/458413/how-to-fix-dual-booting-windows-8-and-ubuntu-14-04-on-a-sony-vaio
Issues on rename
https://bugs.launchpad.net/boot-repair/+bug/1315490

Other workarouds:
http://ubuntuforums.org/showthread.php?t=2234019
http://askubuntu.com/questions/150174/sony-vaio-with-insyde-h2o-efi-bios-will-not-boot-into-grub-efi

mkobx
April 3rd, 2015, 07:46 PM
Hi oldfed,

no i didnt install 32 bit UEFI version, I do not know from where the bootia32.ef comes from.
Once a time I reinstalled Win, might be due thus that I maybe didnt cleaned up UEFI bevor installing an win64 version.

But finally I resolved the issue!
Many, many thanks to you !!!! :D:D

My final solution is, which works -->
1. copied shimx64.efi to efi/boot and renamed it to bootx64.efi
2. copied shimx64.efi to /efi/Microsoft/Boot/ and renamed it to bootmgfw.efi

It might be a little bit mixed up, but it works! Tanks again :D

oldfred
April 4th, 2015, 12:19 AM
If you rename bootmgfw.efi, a Windows update will overwrite that and revert booting to Windows.
And if grub has major update you will have to copy grub or shim again.

To boot Windows if you renamed bootmfgw.efi, then you have to create a new grub menu entry to boot that renamed file to be able to boot Windows. We do not now normally suggest renaming bootmgfw.efi. If you do not rename it, then you can directly boot Windows from UEFI menu.