Dual boot Windows 8 and Precise -Dell XPS 8500

**unconcrete** · January 22nd, 2013

At first, I've reinstalled 12.04.1 from my usb as usual. Then I've repeated the boot repair in the same way I did the first time (recommended). I've entered ubuntu and I've upgraded it to 12.10. By the way I hope to install the correct Grub. Upgrade accomplished.
This is the Grub2 menu created by boot-repair:
===================================
Ubuntu
Ubuntu advanced options (?)
Windows UEFI bootmgfw.efi (?)
Windows Boot UEFI Loader (?)
EFI/Dell/Boot/bootmgfw.efi (?)
EFI/Dell/Boot/bootx64.efi (?)
System Setup (?)
===================================
the last time I installed ubuntu the only entries were
UBUNTU
WINDOWS
MEMORY TEST
Of the 7 entries of Grub2 I know only the first one. My goal is always to dualboot the two os. I'd like to know the correct entries to do that.
I've tried to edit the efi files by doing [sudo gedit ...*.efi] but the file is not text as sources.list or similar files. I don't know what really are these objects and what they do.

Sincerely.

**oldfred** · January 22nd, 2013

Boot repair adds two entries to 25_Custom for efi boot. There are two Windows files. bootmgrw.efi and bootx64.efi. These are not editable.
Grub2's os-prober which runs as part of every sudo update-grub was adding incorrect entries that tried to directly boot to the Windows partitions the way BIOS entires do. But your look from the title as a lot different. Did grub finally fix the bug?

grub2's os-prober creates wrong style (BIOS) chain boot entry
https://bugs.launchpad.net/ubuntu/+s...2/+bug/1024383
Type of entry that does not work:
'Windows ...) (on /dev/sdXY)'

**unconcrete** · January 26th, 2013

Originally Posted by oldfred

Boot repair adds two entries to 25_Custom for efi boot. There are two Windows files. bootmgrw.efi and bootx64.efi. These are not editable.
Grub2's os-prober which runs as part of every sudo update-grub was adding incorrect entries that tried to directly boot to the Windows partitions the way BIOS entires do. But your look from the title as a lot different. Did grub finally fix the bug?

grub2's os-prober creates wrong style (BIOS) chain boot entry
https://bugs.launchpad.net/ubuntu/+s...2/+bug/1024383
Type of entry that does not work:
'Windows ...) (on /dev/sdXY)'

Sorry for the late answer.
I've read the Launchpad article and it is interesting but I am not use to manage with system configuration, since most of the things that the article reports are actually very difficult to understand. I don't like to create a bigger damage, by trying options I don't know.
However I've understood the os prober has found wrong information. It is better to fix these info or disable os prober?
Here, I've I've found this hint. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679817 Msg. 12.
" My work around was to disable os-prober in grub by adding the line
GRUB_DISABLE_OS_PROBER=true
at the end of /etc/default/grub then I created a custom entry for windows 7 by adding

menuentry "Windows 7" --class windows --class os {
set root='(hd0,gpt3)'
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}

to /etc/grub.d/40_custom and then updating grub by
update-grub."

Is it correct in your opinion? And also, I have Windows 8 not 7.
This can create additional problems?

Regards.

In order to give a better help this is the boot info created by Bot-repair.
http://paste.ubuntu.com/1572572/

**oldfred** · January 26th, 2013

If you look at line 487 Boot-Repair has added a correct Windows boot stanza. Whether set root = or search are just two different ways to set root. Generally the search to use UUID is preferred as with multiple drives or even plugging in a flash drive may change drive order hd0 becomes hd1 where UUID does not change.

Code:

### BEGIN /etc/grub.d/25_custom ###

menuentry "Windows UEFI bootmgfw.efi" {
search --fs-uuid --no-floppy --set=root CAF1-3431
chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}

I turn off os-prober. You could turn it back on if grub fixes bug in the future and then you will not need the 25_custom that Boot-Repair has created.
gksudo gedit /etc/default/grub
GRUB_DISABLE_OS_PROBER=true
or turn off executeable bit
sudo chmod a-x /etc/grub.d/30_os-prober
# then run
sudo update-grub

That will help clean up menu, but will not fix any boot issues.

Perhaps you need this? But I would fully backup entire efi partition first.

Boot-Repair - Updated Jan 1, 2013 to not rename first time, but rename if first time Windows does not boot. Post 706 and 711
http://ubuntuforums.org/showthread.p...769482&page=71
Boot-Repair copied /EFI/ubuntu/grubx64.efi to /EFI/Boot/bootx64.efi (in case the BIOS is hard-coded to boot into /EFI/Boot/bootx64.efi or secure boot
signed GRUB file shimx64.efi.

To perform this, just run Boot-Repair --> Adv options --> tick "Backup and rename EFI files" --> Apply
Then reboot the PC and please tell us what you observe.

**unconcrete** · January 26th, 2013

Originally Posted by oldfred

If you look at line 487 Boot-Repair has added a correct Windows boot stanza. Whether set root = or search are just two different ways to set root. Generally the search to use UUID is preferred as with multiple drives or even plugging in a flash drive may change drive order hd0 becomes hd1 where UUID does not change.
...
I turn off os-prober. You could turn it back on if grub fixes bug in the future and then you will not need the 25_custom that Boot-Repair has created.
gksudo gedit /etc/default/grub
GRUB_DISABLE_OS_PROBER=true
or turn off executeable bit
sudo chmod a-x /etc/grub.d/30_os-prober
# then run
sudo update-grub

That will help clean up menu, but will not fix any boot issues.
Perhaps you need this? But I would fully backup entire efi partition first.

Boot-Repair - Updated Jan 1, 2013 to not rename first time, but rename if first time Windows does not boot. Post 706 and 711
http://ubuntuforums.org/showthread.p...769482&page=71
Boot-Repair copied /EFI/ubuntu/grubx64.efi to /EFI/Boot/bootx64.efi (in case the BIOS is hard-coded to boot into /EFI/Boot/bootx64.efi or secure boot
signed GRUB file shimx64.efi.

To perform this, just run Boot-Repair --> Adv options --> tick "Backup and rename EFI files" --> Apply
Then reboot the PC and please tell us what you observe.

I've turned off the os prober, the executable bit and updated grub.
At reboot actually I see the same 7 odd entries:
1) Ubuntu
2) ubuntu advanced options - older kernels
3) Windows UEFI bootmgfw.efi ??
4) Windows Boot UEFI Loader ??
5) EFI/DELL/Boot/bootmgfw.efi ??
6) EFI/DELL/Boot/Bootx64.efi ??
7) System Setup - dear old Bios
-----------------------------------
You have found a good entry for Windows in my Bootinfo. How can I set it to work as the correct entry in the grub2 menu? Have I to edit particular configuration files or It's better to use Boot -repair?
If with grub2 the only system to edit the menu is boot repair or other package, I've already saved a backup of my mbr/grub in a usb flash. I need a more detailed info about the advanced options for my case.
In the attach image I show the advanced option untouched. If some option must be grayed and other added, please tell me how to do.
Otherwise, If you think it's better to edit particular config files I need to know their name.
P.S.: my new bootinfo after grub-upfate: http://paste.debian.net/229026/
Thanks.

**oldfred** · January 26th, 2013

Those are all efi files that Boot-Repair found in your efi folder. They should all boot and also be options to boot from when you are in your UEFI/BIOS menu directly.

If none of them work, then you may have the UEFI/BIOS that only boots Windows and needs the renaming that Boot-Repair can do. Posted above.

**unconcrete** · January 27th, 2013

Originally Posted by oldfred

Those are all efi files that Boot-Repair found in your efi folder. They should all boot and also be options to boot from when you are in your UEFI/BIOS menu directly.
If none of them work, then you may have the UEFI/BIOS that only boots Windows and needs the renaming that Boot-Repair can do. Posted above.

Red Alert.
As suggested I have used boot repair to change names. As usual the grub has been uninstalled and reinstalled with the option to rename efi entries.
The result is a disaster.
Now no os is avalaible. Only <no bootable device avalaible press a key to retry.> Nothing happens: the monitor is dead. I don t know what happened. Please I need an help. at least I d like to have one of my os working.
The last report of boot repair is the following: http://paste.ubuntu.com/1576098/
Regards.
A note:before the system loss its configuration, as i choose the entry ubuntu as usual, unlike ubuntu starts with its gui, a command line appaired claiming me for user name and password. Without any reason. That happened two times,and after I can reply you only by my usb/flash.

**oldfred** · January 27th, 2013

If you get grub menu and can choose Windows or Ubuntu, and get to login password you have mostly booted, but may have video issues.
Are you then able to get to command line?
You also should be able to boot recovery mode and it may make necessary updates.

What video chip/card do you have?
How to set NOMODESET and other kernel boot options in grub2 - both liveCD & first boot, but different
http://ubuntuforums.org/showthread.php?t=1613132
https://help.ubuntu.com/community/BootOptions

It seems to be having some issues with sdd your 3TB drive with one very large NTFS partition. Several have posted with issues where Windows did not create a valid gpt partition table.
Download gdisk from repository on live flash drive or install if you can get into it.
GPT fdisk Tutorial -srs5694 in forums
http://ubuntuforums.org/showthread.php?t=1439794
http://www.rodsbooks.com/gdisk/

You also have a small SSD as Intel SRT? Some have had issues when the SRT is one and drive still has RAID meta data.
Intel Smart Response Technology
http://www.intel.com/p/en_US/support...ts/chpsts/imsm
Some general info in post #3
http://ubuntuforums.org/showthread.php?t=2071242
Intel SRT - Dell XPS Screen shots of Intel SRT screens
http://ubuntuforums.org/showthread.php?t=2038121
http://ubuntuforums.org/showthread.php?t=2036204
Details in post #10 on an install that worked
http://ubuntuforums.org/showthread.php?t=2020155
Dell XPS Intel SRT issue on hibernating post #25
http://ubuntuforums.org/showthread.php?t=1932965
Some info on re-instating details in post #9
http://ubuntuforums.org/showthread.php?t=2038121
http://ubuntuforums.org/showthread.php?t=2070491

Disable the RAID, for me it was using the Intel rapid management thingy and telling it to disable the acceleration or the use of the SSD. If you have a different system, just disable the RAID system then install Ubuntu. Once installed you can then re-enable it.

You will need to use the dmraid command prior to running the Ubuntu Installer so that it will be able to see the partitions on the drive because otherwise with the raid metadata in place it will see the drive as part of a raid set and ignore its partitions.

**unconcrete** · January 27th, 2013

No more.
I have no grub menu (wright or wrong) no bootable partitions. Only a black screen.
My video card is nvidia. I'm not working from my home so i haven't the detailed version. I'll give information about as soon as possible.
Anyway I don't understand what error I've done with boot-repair. I can try to reinstall but I think the problems will be the same.
Sincerely.
this is the reuslt of gdisk:
-------------------------------
sudo gdisk -l /dev/sda
...
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 0FF7F015-4185-4E5A-8BBC-98945CDB443E
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907024613
Partitions will be aligned on 2048-sector boundaries
Total free space is 1921132477 sectors (916.1 GiB)

Number Start (sector) End (sector) Size Code Name
1 2048 1026047 500.0 MiB EF00 EFI system partition
2 1032192 1114111 40.0 MiB FFFF Basic data partition
3 1114112 1376255 128.0 MiB 0C01 Microsoft reserved part
4 1376256 2400255 500.0 MiB 2700 Basic data partition
5 2400256 1971529727 939.0 GiB 0700 Basic data partition
6 3892652032 3907022598 6.9 GiB 2700 Microsoft recovery part
ubuntu@ubuntu:~$

**oldfred** · January 27th, 2013

gdisk says sda is ok, but BootInfo seemed to have an issue with sdd. Try gdisk on it.

I have an older nVidia and have since they incorporated drivers into kernel needed nomodeset to boot liveCD and on first boot in grub menu. If grub menu does not show, does holding shift key from BIOS/UEFI until menu appears show menu?

If a video issue in grub, Boot-Repair has a gfxmode setting that it will do. Grub tries to use video from install but if that is not working then grub may have issues showing menu.

Default is 640x480 which should work for everyone, or you can change to your exact configuration.
Boot-Repair --> Advanced options --> GRUB options tab --> tick the "Uncomment GFXMODE" option --> Apply
Boot-Repair --> Advanced options --> GRUB options tab --> tick "Add kernel option: nomodeset" --> Apply