PDA

View Full Version : [SOLVED] USB 18.04 install does not detect Windows 7 (EFI)



pjstock
November 15th, 2018, 09:41 PM
I was about to install Ubuntu 18.04 from a USB stick onto a machine with WIndows 7 already installed (and which I would like to keep) But at Step 1 I am getting a message that no other operating system was detected.

I have read a number of the many threads related to this same issue, but could not make much sense of them.

My Windows 7 is showing the 250GB drive with a 100MB EFI System Partition and 232 GB as NTFS.

What am I doing wrong? do I have the wrong version of Ubuntu on the stick?
After about 7 Ubuntu installs, this is a new roadblock to me. (though my past success is likely more due to good luck than good management.)

Peter

oldfred
November 15th, 2018, 10:17 PM
I would use Windows to shrink the NTFS partition and reboot immediately to make sure it has run chkdsk.
Do you have Windows hibernation on? Windows 7 does not have the Windows 10 default of fast start up/hibernation.

The Ubuntu installer is both UEFI and BIOS boot.
If Windows is UEFI, you want to install Ubuntu in UEFI boot mode.
How you boot install media from UEFI, BIOS or UEFI is then how it installs.

Be sure to have good backups and a Windows repair or recovery disk.

More info on UEFI installs in link in my signature.

pjstock
November 15th, 2018, 10:52 PM
this windows is a brand new install from the guy I bought the PC from (he's a tech hobbyist). So there is nothing on the new system. No backup required. (and I very very very rarely use Windows once I have Ubuntu running, so it's just a convenience to know it's there.)
By how much could I reasonaly shrink the NTFS partition? by... 20GB? Less?

re: Hibernation. In Power Options in Windows both Turn Off Display and Sleep options were/are enabled (for after 10 minutes and 30 minutes respectively) . I will set them to NEVER now.
(but how does Hibernation come into play if I am Restarting in order to boot from the USB stick?)

is UEFI the same as EFI?
How do I specify UEFI or BIOS for this: "How you boot install media from UEFI, BIOS or UEFI is then how it installs"

But let me read your More Info on UEFI boot install first.....


Many thanks

Dumb,
I now see that the 232gb is all Windows 7. and I can only shrink that to about half that size. Do I go for the maximum shrink?

oldfred
November 16th, 2018, 04:28 AM
Windows really wants 30% free, so that is the minimum you should shrink to.
Some have had to use third party tools, but turning off several things may allow you to shrink it more.

Shrink or Resize the Windows 8, 7 or Vista Partition or Drive
http://www.thpc.info/how/shrink_partition_in_windows_7_vista.html
How to Get Around Windows’ “Shrink Volume” Inadequacy Problems
http://www.howtogeek.com/howto/windows-vista/working-around-windows-vistas-shrink-volume-inadequacy-problems/
Hiberfile in Windows 7 & 8 often prevents shrink
http://www.sevenforums.com/tutorials/819-hibernate-enable-disable.html

pjstock
November 16th, 2018, 03:43 PM
and if I shrink the Windows 7 partition, do you think that will help Ubuntu recognize the W7 when I try to install Ubuntu? (I guess I do it and find out.)
I am simply not knowledgable enough to understand all the steps required to manually do a dual OS install. I have (sadly) come ot rely on the automatic detection of Ubuntu. It's worked so well the.... 7 or so times I've installed Ubuntu in the past.
Peter

oldfred
November 16th, 2018, 06:24 PM
With Windows 7 normally hibernation is not an issue, just the newer Windows with fast start up.
But some other things like NTFS needing chkdsk or if you converted partitions to dynamic (LDM in Linux if gpt) from basic will prevent the Linux NTFS driver from seeing Windows.
Post these:
sudo fdisk -lu
sudo parted -l
sudo gdisk -l /dev/sda

pjstock
November 16th, 2018, 07:00 PM
I have not yet installed Ubuntu 18.04 on the new system yet. I am still doing preperatory steps before trying to shrink that Windows 7 partition.

Shall I run Ubuntu off the stick and run those commands and report? will that show anything?

Peter

oldfred
November 16th, 2018, 08:09 PM
Yes, use Ubuntu live installer in live mode and see what those commands say?

Also if you use gparted from live installer, it may show red or yellow icon next to NTFS partition and click (right click?) on icon may show error message.
Often error messages are rather general.

pjstock
November 17th, 2018, 04:39 PM
thank you.
I ran PerfectDisk and it seemed VERY effective. I was able to shrink the WIndows 7 partition to about 30% of the total (so about 72Gb)
On retrying the Ubuntu Install Ubuntu still does not "detect" my WIndows 7. But on trying SomethingElse I see what looks like an unused 172GB "Free Space" area.
Can I "direct" ubuntu to install there and thereby leave the WIndows 7 Intact and unaffected? or do I have to do some other steps first? (I was tempted to say To Heck WIth it and just use WIndows, but on doing the Live Install of Ubuntu I am reminded of how much I like it.)

In any event, here are the results of those commands you suggested (I hope this is clear and helps)


ubuntu@ubuntu:~$ sudo fdisk -lu
Disk /dev/loop0: 1.8 GiB, 1864450048 bytes, 3641504 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 /dev/loop1: 86.9 MiB, 91099136 bytes, 177928 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 /dev/loop2: 34.7 MiB, 36323328 bytes, 70944 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 /dev/loop3: 140.9 MiB, 147722240 bytes, 288520 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 /dev/loop4: 2.3 MiB, 2433024 bytes, 4752 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 /dev/loop5: 13 MiB, 13619200 bytes, 26600 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 /dev/loop6: 14.5 MiB, 15196160 bytes, 29680 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 /dev/loop7: 3.7 MiB, 3887104 bytes, 7592 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

The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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
Disklabel type: gpt
Disk identifier: 23EB170D-A19B-4E25-BB48-CCC2773C9D5F

Device Start End Sectors Size Type
/dev/sda1 2048 206847 204800 100M EFI System
/dev/sda2 206848 468991 262144 128M Microsoft reserved
/dev/sda3 468992 145876991 145408000 69.3G Microsoft basic data

Disk /dev/sdb: 7.7 GiB, 8242855936 bytes, 16099328 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
Disklabel type: dos
Disk identifier: 0x663eb4c4

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 0 3815135 3815136 1.8G 0 Empty
/dev/sdb2 3737268 3741939 4672 2.3M ef EFI (FAT-12/16/32)
ubuntu@ubuntu:~$ sudo parted -l
Error: The backup GPT table is corrupt, but the primary appears OK, so that will
be used.
OK/Cancel? ok
Model: ATA WDC WD2500AAKX-7 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot, esp
2 106MB 240MB 134MB Microsoft reserved partition msftres
3 240MB 74.7GB 74.4GB ntfs Basic data partition msftdata


Warning: The driver descriptor says the physical block size is 2048 bytes, but
Linux says it is 512 bytes.
Ignore/Cancel? ignore
Model: Generic Flash Disk (scsi)
Disk /dev/sdb: 33.0GB
Sector size (logical/physical): 2048B/512B
Partition Table: mac
Disk Flags:

Number Start End Size File system Name Flags
1 2048B 6143B 4096B Apple
2 1913MB 1916MB 2392kB EFI


ubuntu@ubuntu:~$ sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.3

Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged

************************************************** **************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
************************************************** **************************
Disk /dev/sda: 488397168 sectors, 232.9 GiB
Model: WDC WD2500AAKX-7
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 23EB170D-A19B-4E25-BB48-CCC2773C9D5F
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 488397134
Partitions will be aligned on 2048-sector boundaries
Total free space is 342522157 sectors (163.3 GiB)

Number Start (sector) End (sector) Size Code Name
1 2048 206847 100.0 MiB EF00 EFI system partition
2 206848 468991 128.0 MiB 0C01 Microsoft reserved ...
3 468992 145876991 69.3 GiB 0700 Basic data partition
ubuntu@ubuntu:~$

oldfred
November 17th, 2018, 05:45 PM
The error on the sector size is from flash drive and is normal.
But this is an issue and needs to be fixed.

Error: The backup GPT table is corrupt, but the primary appears OK, so that will
be used.

repair gpt:
http://www.rodsbooks.com/gdisk/repairing.html

(http://www.rodsbooks.com/gdisk/repairing.html) sudo gdisk /dev/sda
Command (? for help):
(http://www.rodsbooks.com/gdisk/repairing.html) Use gdisk and verify partitions are correct with p, or v to review issues, and use w to write the partition table. If not correct just use q to quit. That should update primary, backup & protective MBR

(http://www.rodsbooks.com/gdisk/repairing.html)

pjstock
November 17th, 2018, 11:09 PM
how do I know if partitions are correct?
when I run that gdisk command and then p and v I get:



ubuntu@ubuntu:~$ sudo gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.3

Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged

************************************************** **************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
************************************************** **************************

Command (? for help): p
Disk /dev/sda: 488397168 sectors, 232.9 GiB
Model: WDC WD2500AAKX-7
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 23EB170D-A19B-4E25-BB48-CCC2773C9D5F
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 488397134
Partitions will be aligned on 2048-sector boundaries
Total free space is 342522157 sectors (163.3 GiB)

Number Start (sector) End (sector) Size Code Name
1 2048 206847 100.0 MiB EF00 EFI system partition
2 206848 468991 128.0 MiB 0C01 Microsoft reserved ...
3 468992 145876991 69.3 GiB 0700 Basic data partition

Command (? for help): v

Partition(s) in the protective MBR are too big for the disk! Creating a
fresh protective or hybrid MBR is recommended.

Identified 1 problems!

Command (? for help): w

Partition(s) in the protective MBR are too big for the disk! Creating a
fresh protective or hybrid MBR is recommended.

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N):



do I proceed? (there is nothing on the new system that I need to save, except the W7 install, which would be a hassle to reinstall.)

oldfred
November 17th, 2018, 11:21 PM
I would say yes, but you really should have Windows 7 backed up before any major system change, anyway.

With gpt the protective MBR is really only used to have one entry saying drive is gpt. That is so old tools will see drive is partitioned and not immediately try to change it.
There were some places like on a Mac with EFI/gpt and older Windows in BIOS/MBR where hybrid partitioning was used. But hybrid not recommended as keeping then in sync was often an issue.

pjstock
November 17th, 2018, 11:28 PM
here goes nothing.


Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sda.
Warning! An error was reported when writing the partition table! This error
MIGHT be harmless, or the disk might be damaged! Checking it is advisable.

Command (? for help): p
Disk /dev/sda: 488397168 sectors, 232.9 GiB
Model: WDC WD2500AAKX-7
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 23EB170D-A19B-4E25-BB48-CCC2773C9D5F
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 488397134
Partitions will be aligned on 2048-sector boundaries
Total free space is 342522157 sectors (163.3 GiB)

Number Start (sector) End (sector) Size Code Name
1 2048 206847 100.0 MiB EF00 EFI system partition
2 206848 468991 128.0 MiB 0C01 Microsoft reserved ...
3 468992 145876991 69.3 GiB 0700 Basic data partition

Command (? for help): v

Partition(s) in the protective MBR are too big for the disk! Creating a
fresh protective or hybrid MBR is recommended.

Identified 1 problems!

Command (? for help):


hmm, I'm not sure that did anything.
how do I "check it" as it suggests? or do I still have an error?

oldfred
November 18th, 2018, 12:48 AM
I thought gdisk would just write new correct data to protective MBR as well.
recovery/transformation command (? for help): o

http://www.rodsbooks.com/gdisk/hybrid.html
But we do not want main menu o or create new gpt, if used just exit without write:
Typing o at the recovery & transformation prompt displays the MBR data, and you can see the hybrid partition definitions. (Caution: The o command, when typed at the main menu, creates a fresh GPT, including a new protective MBR.)

pjstock
November 18th, 2018, 02:51 AM
so, should I type O?
(sorry but I am so far over my head now that all I can do is follow instructions and report back. which I know is dumb. but that's where I am.)

I started to do the O command, but got cold feet.


Command (? for help): o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): n

Command (? for help):

oldfred
November 18th, 2018, 05:33 AM
Good thing you stopped.
You want to be at this menu:
recovery/transformation command (? for help): o
as instructions say if at main menu, it creates new gpt partition table from MBR which we do not want.

pjstock
November 18th, 2018, 01:55 PM
you are a patient fellow. thank you.

how do I get to that menu:
recovery/transformation command (? for help): o

But otherwise,(and this morning I will read more of that Rod Smith post about GPT) is this GPT error you are helping me with:
A) a Linux/Ubuntu thing?
B) a Windows 7 thing?
or C) just a general base system thing common to both.?

How could it be A) related to Linux/Ubuntu when I haven't even installed any Ubuntu yet? Am just running it Live?

oldfred
November 18th, 2018, 03:54 PM
Was drive MBR before?
It is a partitioning thing.
Perhaps some older partitioning tools in Windows wrote MBR info, then Windows install in UEFI converted to gpt.
With gpt there is both a primary partition table & a backup partition table at end of drive, so usable part of drive is slightly smaller.

From the main menu, the r command takes you to the recovery menu.
Use ? to see commands.


fred@Bionic-Z170N:~$ sudo gdisk /dev/sdc
[sudo] password for fred:
GPT fdisk (gdisk) version 1.0.3

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): ?
b back up GPT data to a file
c change a partition's name
d delete a partition
i show detailed information on a partition
l list known partition types
n add a new partition
o create a new empty GUID partition table (GPT)
p print the partition table
q quit without saving changes
r recovery and transformation options (experts only)
s sort partitions
t change a partition's type code
v verify disk
w write table to disk and exit
x extra functionality (experts only)
? print this menu

Command (? for help):

pjstock
November 18th, 2018, 04:04 PM
sorry (dumb) found the r = recovery option as I read further.
so, go "o" in recovery?

I'm not too fussed about making an error as there is nothing on this system except the base W7 installation. which I could get reinstalled if I mess things up here.

oldfred
November 18th, 2018, 04:10 PM
I want to see what is in the MBR that it says it is too large for drive. So yes in the recovery mode.
But not sure how to fix it, if gdisk will not auto write a new MBR.

post this also:
sudo sfdisk -d /dev/sda

pjstock
November 18th, 2018, 04:12 PM
Oh, just ran gdisk again and it seems to be looking better


sudo gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.3

The protective MBR's 0xEE partition is oversized! Auto-repairing.

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): v

No problems found. 342522157 free sectors (163.3 GiB) available in 2
segments, the largest of which is 342520143 (163.3 GiB) in size.

Command (? for help):


what do you think? Can I proceed with installing Ubuntu? if so how (at that "something else" prompt which shows me the various partitions)?

i think I found a good tutorial for doing this install. I shouild be able to follow along from here.,
But thank you SOOOO much for getting me to this clean start point.
Peter

Sorry Oldfred, but I am back.
I thought I was good to go with the Ubuntu Install. I created a / particiton of 30Gb for the OS, 15GB for the swap and a seperate /home partitioni.
but at the first step of the install I am getting an error:
"The installer encountered an error copying files to the hard disk:
[Errno 5] input/output error...."

and a message suggesting the CD/DVD might be faulty or the HDD is old an in need of replacement.

I'll speak to the fellow from whom I got this rebuilt system and I'll check the "health" of the HDD. But might this be a result of the changes you have been guiding me through? is there anything I should check from this side?

a Short Selftest on this disk shows "Overall Assessment: Disk is OK" and temperature 35C/95F and OK

Peter

oldfred
November 18th, 2018, 05:44 PM
If drive says ok, then that should not be the issue.

Did then gdisk write a correct MBR at some point, and just give message as warning?
But I am pretty sure that was original issue with installer not working. It does not like drive issues.

You do not need swap partition, with 18.04. It uses a swap file of 2GB. But it will use swap partition if one is found.
But swap of 15GB is overkill. Hibernation not really recommended and Ubuntu boots fast enough that hibernation does not save much.

I stopped using DVDs, years ago. I burned too many coasters (bad burns). Actually did use one as a coaster for a while.
I use flash drives and newest system does not even have DVD drive.

Check that download is correct.
https://help.ubuntu.com/community/HowToMD5SUM

We have seen users have issues with one installer or another or one flash drive or another. Even in past with some brands of DVD.
Be sure with DVD to burn at slowest rate available. That often gives a better or more reliable burn.

pjstock
November 18th, 2018, 08:10 PM
I did an check of the MD5SUM from my original ISO to what 18.04 should be and they match.
I am creating a USB stick version for the install.

should I try recreating the USB stick?

Hmmm surious. when I LIve Boot the reburned USB stick and use Gparted to try to recover that Swap area, I get a Libparted Error message "the backup GPT table is corrupt, but the primary appears OK, so that will be used"

So maybe I still have GPT problems. I will try that gdisk command again to verifiy.

oldfred
November 18th, 2018, 08:22 PM
I have not had issues with flash drives. But there is a Microcenter computer store nearby and they sell their own brand at counter when you check out. I now cannot keep track of all my flash drives as I was buying one every time I went to store.

Some just have issue with flash drive, some with the installer used. Or maybe just redoing it worked?
Installation/FromUSBStick - with lots of details on various USB drive issues by sudodus
http://ubuntuforums.org/showthread.php?t=2196858
External SSD & flash drive issues by TheFu
https://ubuntuforums.org/showthread.php?t=2390247&p=13760330#post13760330
Post #14 some flash drives that did not work
http://ubuntuforums.org/showthread.php?t=2120196
More tests Flash drives post #5 - C.S.Cameron
http://ubuntuforums.org/showthread.php?t=2130234
Brand of flash does seem to make a difference. One user's experience liked 32G Sandisk
http://ubuntuforums.org/showthread.php?t=2120196&p=12577208#post12577208

pjstock
November 18th, 2018, 08:37 PM
Progress!! I don't know if it was the reburned USB stick or that I formatted the 30GB partition I allocated for Ubuntu but I am past the first few steps and it seems to be installing!.
As trecherous as it sometimes seems, I love Ubuntu. I don't know why. it feels.... liberating.
fingers crossed. I'll let you know when she's done (you deserve at least that satisfaction.)
can I donate somewhere to this Forum's efforts? I take so much help and give nothing. I feel bad.

Hmmm, well the install says it was succesful, but on reboot I don't get that list of boot options I usually do.
In fact I cannot find any way to boot into Ubuntu instead of windows.
am I missing something?

oldfred
November 18th, 2018, 09:40 PM
Lets see where you are at:

May be best to see details, use ppa version with your live installer or any working install, not older Boot-Repair ISO:
Please attach link to the summary report, the auto fix sometimes can create more issues.
https://help.ubuntu.com/community/Boot-Repair

pjstock
November 18th, 2018, 09:42 PM
I am trying Boot Repair (to apparently repair the GRUB?)
But Boot Repair is telling me I am Live Booted into Legacy mode and not Uefi mode.
I have tried BIOS settings to specify UEFI boot mode, but from the usb stick it seems to always go to BIOS mode.
How do I force a LIveBoot from USB ini UEFI mode so that I can at least try Boot Repair.

I am trying to create new Forced to UEFI USB stick but I am only seeing MBR as Partition scheme and not GPT (as indicated in the Rufus instructions.)

Man this seems hard.....

If you mean run Boot Repair, I cannot. It fails and says I need to be in UEFI mode. (and I cannot figure out how to do that.)

oldfred
November 18th, 2018, 09:52 PM
The flash drive can be either MBR or gpt and booted in UEFI or BIOS boot mode. Some installer may configure one way or the other.
The installer boots in UEFI mode using grub and in BIOS mode using syslinux.
And from UEFI you select which way to boot installer.
Your UEFI should show two boot options, one clearly UEFI, and other just name of flash drive/PMAP.

But if UEFI Secure Boot on, you will not get UEFI (without Secure boot) or BIOS/CSM/Legacy boot option.
And many UEFI have UEFI on/off or CSM/Legacy on/off. Some are separate settings some combined in not particularly logical order. My UEFI settings are under a CSM menu item???
And most have separte settings to allow USB boot. BIOS/CSM may work in CSM mode, but UEFI may only work if USB boot setting on.
CSM - UEFI Compatibility Support Module (CSM), which emulates a BIOS mode

How you boot install media UEFI or BIOS/CSM is then how it installs. So if you booted installer in BIOS mode it installed in BIOS mode. And then UEFI boot would not see a BIOS install. You technically can dual boot, but UEFI and CSM are not compatible, once you start booting from UEFI you cannot switch to other mode. Or grub only can offer to boot other installs in same boot mode.

pjstock
November 18th, 2018, 09:59 PM
when I used the USB stick to Live Boot, I have to hold F12 for Boot Options.
there I see three scetions: LEGACY BOOT, UEFI BOOT and Other Options.

I only see one (1x) USB boot option. and that is in the Legacy Boot section.
In UEFI Boot section it shows:
- WIndows Boot Manager (which I presume would boot to WIndows. and does)
- UEFI: INT13 (RAID, 0x80) (which boots to Windows)
- UEFI: INT13 (,0x81) and this choice bombs on lack of resources or similar

oldfred
November 18th, 2018, 10:05 PM
Check UEFI settings for UEFI and CSM/Legacy/BIOS.
Make sure UEFI Secure Boot is off, and UEFI is on.
And check USB settings in UEFI.

What brand/model system?

pjstock
November 18th, 2018, 10:06 PM
I am trying another ISO burner that is allowing me a GPT partition style option. Let's see if that allows me to actually live boot as UEFI.

Dell Optiplex 990

I don't see any of those options for UEFI in the Bios Settings.

arrgggh, and that new UEFI enable USB goot stick, when I try to boot to it (though USB is still only showing under Legacy) the system hangs.

ubfan1
November 18th, 2018, 11:43 PM
Maybe the RAID setup is causing problems. Dell offers some setup instructions, but only up through 16.04. I know nothing about RAID, so no suggestions from me.

oldfred
November 19th, 2018, 12:04 AM
That Dell is early UEFI, have you updated UEFI from Dell for your system?
Newer Dell have drives set for RAID, but need to be changed to AHCI, not sure about yours.

Dell UEFI Dual boot instructions using Something Else
https://www.dell.com/support/article/us/en/19/SLN301754/how-to-install-ubuntu-and-a-recent-windows-operating-system-as-a-dual-boot-on-your-dell-pc?lang=EN
https://www.dell.com/support/article/us/en/19/sln142679/how-to-enable-boot-from-dvd-option-with-uefi-boot-mode-enabled--windows-8--81--10-?lang=en

pjstock
November 19th, 2018, 04:41 PM
Hmmm, that's interesting reading.

In any event, I updated the Bios from ver. A20 to the most recent A24 (2018) and once that flash completed, there are some... interesting outcomes.
When the system rebooted, if I pushed it into the "One Time Boot Options" with F12, even though the Boot Options list didn't seem to have changed, the top line "Legacy boot"option is now my Ubuntu. which is great. (and it looks good.)
the first option in the Uefi Boot list goes to WIndows 7 (great.)
But if I just let the system boot normally, on it's own, the default OS goes to Windows7....

Wait a minute. If I go into BIOS Setup and change the boot sequence order.....

YES. by making "Legacy" the default Boot option it boots to Ubuntu!!
and if I need a One Time WIndows Boot I use F12 and force it to UEFI Windows Boot Manager! YES!
Excellent. We made it! you made it. (sorry to get effusive here.)

So I don't know exactly what happened here. Maybe you can summarize for other readers. But it seems that updating the Dell Bios to the most recent version did the trick. (though I am not sure what changed when that update was done. Do you?)

many many thanks Peter
A donation is on it's way!

oldfred
November 19th, 2018, 07:07 PM
Is Ubuntu then installed in BIOS/CSM/Legacy boot mode, not UEFI?
Grub will not offer to boot Windows 7 if not in same boot mode.

If drive is gpt, you can usually convert BIOS install on gpt drive to UEFI boot, just by reinstalling grub. You already have the required ESP - efi system partition to boot Windows 7 in UEFI mode.

Boot-Repair's advanced options can do that if you boot live installer in UEFI mode.

pjstock
November 19th, 2018, 07:12 PM
But I could not boot live in UEFI Mode. (or at least, when I tried using a USB boot stick that I thought was in UEFI mode, it just hung, did not Live Boot.)

Or, I still do not know how to Live Boot in UEFI mode (so that I can use Boot Repair.)

oldfred
November 19th, 2018, 07:16 PM
UEFI boot menu, f12 on Dell, should have two boot options for live installer.
One is UEFI:flash and other flash (BIOS) where flash is name or label of flash drive.

The Ubuntu installer is configured for both UEFI & BIOS boot.

If you only want UEFI boot, you can create an installer this way:
UEFI only bootable flash drive
http://ubuntuforums.org/showthread.php?t=2299040
(http://ubuntuforums.org/showthread.php?t=2299040)
If UEFI only, then can just extract ISO with 7-zip(or any other extraction tool) to FAT32 formatted drive with boot flag on FAT32 partition.
Will not boot in BIOS mode


(http://ubuntuforums.org/showthread.php?t=2299040)

pjstock
November 19th, 2018, 07:35 PM
in all this time, I have only every used the USB Live Boot in Legacy because that was the only place I saw "USB Boot".

Now, when I go F12 Boot Options with the USB Stick inserted I see that there are actually two new boot options in the list, one under Legacy Boot, the other under UEFI Boot
Under Legacy Boot there is one option labelled "USB Storage Device"
Under UEFI Boot the other is labelled: UEFI: INT13 (0,0x81) (which I presume is the USB stick, because it wasn't there when the USB stick was not inserted)

However, choosing that UEFI boot option [ INT13 (0,0x81) ] the boot hangs with an error "Failed to Set MokListRT: Out Of Resources."

Got it (I think). I had to add some UEFI Boot options and specify grbx64 on FS1 which I assume is the USB stick.

and now I appear to be Live Booted, I presume under UEFI.

should I reinstall Ubuntu at this point, as aa UEFI Live Boot?

that did it. the correct install (as UEFI) . 10sec startup menu popped right up!
excellent.
NOW I can get to migrating over.
thanks again.
Peter