Peppermint OS Community Forum

Support => Installation => Topic started by: Slim.Fatz on July 08, 2019, 11:50:11 am

Title: Problem with legacy installation: no EFI partition [ABANDONED]
Post by: Slim.Fatz on July 08, 2019, 11:50:11 am
Hi,

I'm trying to install Peppermint Ten (64bit) on a notebook computer that has a harddisk with Peppermint 7 (and, until now, also Peppermint 8.5 on another partition, but I think that is now history). The bios is set to "Legacy" in the boot section. When I select "Do something else" during the installation, then select the partition to install Peppermint Ten, tell the installer to format that partition to Ext4 and to use it as the root (/), and tell it to place GRUB in /dev/sda, then click on the Install button, I get a warning that no EFI partition was found. True: I never have had one and all installations have been without any problems. And I admit: I know basically nothing about UEFI or EFI, as all of my machines are rather old (except for this one -- but, as I mentioned, I've always installed things on it in Legacy boot mode and never was asked by an installer to create an EFI partition for GRUB).  :)


 After aborting the installation, I repeated all of this several times, always with the same result. I thought, "Well, let's give it a try anyhow. Maybe that message was there before for the other installations (done several years ago) and I just forgot about having seen it back then."  :-\


 So I hit the continue button and the install seemed to continue well ... until finally it aborted with a message that GRUB could not be installed, again because of the EFI partition missing (or something to that extent). I now have left the machine running in the Live session (fearing that the old GRUB in the MBR is now toast) and hope that someone can tell me how to save this installation by getting GRUB installed in the MBR or even if that is necessary, or whatever ...  ??? ::)

Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 08, 2019, 04:08:35 pm
So what happens if you run:
Code: [Select]
sudo update-grub
in Peppermint 7 ?

Does PM10 get added to GRUB ?
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 08, 2019, 05:31:50 pm
Hi PCNetSpec,

Thank you for the reply. I have not tried that because I am afraid that the previous GRUB has been destroyed -- and then I would not be able to boot anything (unless I understand this all incorrectly). I guess I will have to bite the bullet and give that a try. I'll let you know the results tomorrow -- I'm going to bed now. If you think that the previous GRUB is toast, let me know (I'll check the forum tomorrow before attempting to boot into that computer's installation(s) and will report back how it goes).

But why have I had this problem? There does not seem to be any switch to indicate to the installer that one desires to perform a legacy install. And on other computers (where I have installed Peppermint 10) this was never an issue -- and they were all using legacy boots.  :-\

Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 08, 2019, 07:23:36 pm
I thought you suggested Peppermint 7 was still bootable ?

If so, boot to it, and run:
Code: [Select]
sudo update-grub
and see if the Peppermint 10 installation gets detected and added to it's GRUB menu.



Generally if the LiveUSB is booted in UEFI mode, it'll attempt to install in UEFI mode

If the LiveUSB is booted in Legacy BIOS mode, it'll attempt to install in Legacy BIOS mode

So the switch is how you boot the Live session and is BIOS bound .. there's no switch in Ubiquity, because it requires the BIOS be set right too, and then there's no need for a switch.

Assuming you're doing an automated install with no pre-existing partitions, and the correct partition table type.
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 03:35:31 am
Hi PCNetSpec,

Sorry about the misunderstanding. Here is how I did things:

1. I first tried running the installer and (when I saw the warning that no EFI partition was found) I backed out of the installer and rebooted the computer, checking the BIOS setting and confirmed that it was still set to Legacy.

2. I then rebooted and ran the installer again with the same warning (no EFI found), but this time I ignored the warning and continued because I knew that the BIOS setting was Legacy. I chose to install Peppermint Ten to the partition that had contained Peppermint 8.5 (which also controlled GRUB) telling the installer to reformat that partition using ext4 file system and to mount (or use) it as the root partition for Peppermint Ten.

So then the installer ran for a while, I watched the usual slide show, and then it aborted with the failure message about not being able to install GRUB because of the missing EFI.

After the attempted install aborted, I was returned to the live session (where the computer still is because I was unsure about whether it would be able to be booted again if I turned it off). I'm thinking that the MBR might be corrupt, but do not know how to check for that from within the live session (or how I could salvage things if it is broken). Any ideas?  :-\

I have thought about running the installer again just to see if it properly detects the old partition scheme, and then backing out of it and back to the live session. I guess that would not be harmful in any way ...  :-\   


UPDATE: I had a momentary flash of seemingly functional neurons and in the live session I opened a terminal window and entered:

Code: [Select]
sudo fdisk -l 
but got this output:

Code: [Select]
fdisk: error while loading shared libraries: /lib/x86_64-linux-gnu/libfdisk.so.1: cannot read file data: Input/output error

Undaunted (as fools usually are, even in the face of disturbing events), I then started the app Disks (found in Menu > Accessories) and found that it shows the HDD appearing as it did before running the installation, with the partition sizes, etc. appearing to be normal.  8)


So does this look like I can risk rebooting?


Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: zebedeeboss on July 09, 2019, 05:49:33 am
When you booted from the  USB

Did you choose USB or USB UEFI or were you not presented with two options?

Each machine will handle booting from USB differently.   My machine presents a little menu and I arrow down and choose USB UEFI ( a bite like a grub menu)

Regards Zeb...
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 06:07:08 am
Hi zebedeeboss,

Thanks for your attention. I had the little boot menu, but it only had USB (without any further USB options, such as UEFI), or the HDD.

I've now opened nemo in the live session, mounted the new installation partition and at first it all looks fine. But then in my new /home/<username> there are only the eight hidden files and folders that also appear in /etc/skel. Maybe the other folders (Desktop, Documents, Pictures, Videos, Templates, etc) will appear if I can boot into it the first time -- or I could just make them myself. I'll await the wise advice of PCNetSpec before attempting to reboot.

I really don't care if the new install is cr*p -- I just want to be able to boot into my old faithful Peppermint 7 and could always try to rescue the new install somehow from there.  ;)


Thanks again, zeb !! 

Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: pin on July 09, 2019, 06:24:27 am
Hi Slim,
Are you in need of saving some stuff first?
You can always use supergrub2 from here, https://www.supergrubdisk.org/super-grub2-disk/ to install grub.
Alternative, use the live-usb, chroot into the installed system and re-install grub.

Hope you get this sorter.
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 06:36:01 am
Hi pin,

Thank you for your time. I'm sure there are some things I would like to not have deleted on the other partitions. But my guess is that the files are not really in danger if I chroot into the new install or into Peppermint 7 and re-install GRUB ... I suppose it would have to be the new install because it is the partition that is marked as bootable -- but maybe that is not relevant. I just don't know for sure.  :-\


Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: pin on July 09, 2019, 06:44:11 am
Which partition is bootable?
Can you show us your partition layout?
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 07:31:23 am
Hi pin,

The partition with the new installation of Peppermint Ten is bootable.

Spoiler (click here to view / hide)
Partition 1 : ext4 : Peppermint 7
Partition 2 : Extended partition
Partition 5 : ext4 : Data partition
Partition 6 : swap
Partition 7 : ext4 : Arch Linux
Partition 8 : ext 4 : Peppermint Ten (bootable)
[close]
Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 09, 2019, 09:10:52 am
Well this bothers me
Quote
fdisk: error while loading shared libraries: /lib/x86_64-linux-gnu/libfdisk.so.1: cannot read file data: Input/output error
have you tried reinstalling
Code: [Select]
sudo apt-get install --reinstall libfdisk1
then trying
Code: [Select]
sudo fdisk -l
again ?
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 09:31:08 am
Hi PCNetSpec,

Thanks for the reply! I finally took the chance that it might work and shut the computer down, removed the live session USB and rebooted, only to get this error:

Code: [Select]
error: file '/boot/grub/i386-pc/normal.mod' not found.Entering rescue mode...grub rescue>
So then I shut the computer down again, inserted the live session USB and, once in the live session,

Code: [Select]
sudo fdisk -l
worked. Everything looks like it always did in the output, with /dev/sda8 being the bootable partition where I installed Peppermint Ten. So I opened the terminal and did the usual chroot steps to reinstall grub to /dev/sda only to get this on the last entered command:

Code: [Select]
root@peppermint / # grub-install /dev/sda 
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
So, although the BIOS setting for boot is Legacy, it still seems to be booting the live session USB as if the BIOS setting were UEFI.  :o
Maybe I should try using some other distro's live session USB and repeat the chroot/grub-install dance?  :-\

Or do you have any trick for booting the Peppermint Ten USB in Legacy mode?  ???

 
UPDATE: I'm beginning to believe that the live session USB is not in order (i.e. corrupt): I cannot start firefox (I could on the last several boots into the live session) as it crashes before even appearing on screen, throwing out a Mozilla Crash Reporter window with "We're Sorry (blah, blah)."

Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 09, 2019, 10:12:35 am
I'd still like to see the output from:
Code: [Select]
sudo fdisk -l
and
Code: [Select]
blkid
(even from a LiveUSB if necessary)
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 10:41:55 am
OK. I just burned a new fresh DL of Peppermint Ten and will provide you with the output in several hours: I must leave right now. Be back in 2 hours or so.

Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 09, 2019, 10:50:14 am
Okay, have fun doing whatever you're doing .. later Slim :)
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 01:50:23 pm
Hi PCNetSpec,

Back again (and it was rather fun: I picked up a case of (organic-)wine that a friend brought back for me from a trip to southern France; then I bought a six pack of Benediktiner Helles Lagerbier on the way home; and now I'm enjoying a great dry gin martini -- at least something in life is working well, even if my Peppermint Ten install efforts are not  :D ).


Ok, so I burned the fresh DL of Peppermint Ten to the USB, booted it and attempted the chroot/grub-install dance again -- unfortunately with the same error: cannot find EFI directory. So why did the installation of earlier Peppermint versions not fail on this computer??  :-\ Something must have been changed in the Ubuntu installation code.


On to business: the new live session is also acting crazy!! I cannot start firefox
Code: [Select]
/usr/sbin/firefox: line 1: 2645 Bus error   env GTK_THEME=Peppermint-10-Red-Mixed /usr/bin/firefox "$@"
and I cannot start the text editor to show you the complete output of fdisk -l:
Code: [Select]
xed: error while loading shared libraries: /usr/lib/x86_64-linux-gnu/xed/libxed.so: cannot read file data: Input/output error
I don't know about you, but I'm beginning to worry.  ;)


Do you think that my USB stick is defective?
 
Tell me what you want to see from the outputs of fdisk -l and blkid and I will copy that over in my next reply.

Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 09, 2019, 02:03:00 pm
I'm more inclined to think the HDD (or at least the filesystem) is defective/corrupt.

(or maybe memory)

[EDIT]

Ignore that, YES if xed now isn't working from the LiveUSB (and it was before) then it's likely a USB I/O issue .. try another USB stick
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 02:56:59 pm
Hi PCNetSpec,

New USB, more or less the same problems/errors -- but I can start firefox (using it now in the live session to write this) and xed. So here are the outputs:

Spoiler (click here to view / hide)
root@peppermint / # sudo fdisk -l
Disk /dev/loop0: 1,4 GiB, 1472348160 bytes, 2875680 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/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000229af

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1            2048  62525040  62522993 29,8G 83 Linux
/dev/sda2        62525041 976771071 914246031  436G  5 Extended
/dev/sda5        62525043 844761959 782236917  373G 83 Linux
/dev/sda6       968536064 976771071   8235008  3,9G 82 Linux swap / Solaris
/dev/sda7       906981768 968526719  61544952 29,4G 83 Linux
/dev/sda8  *    844763136 906981766  62218631 29,7G 83 Linux

Partition 2 does not start on physical sector boundary.
Partition 5 does not start on physical sector boundary.
Partition table entries are not in disk order.




Disk /dev/sdb: 29,8 GiB, 32008830976 bytes, 62517248 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: 0x6b8b4567

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1  *        0 3057663 3057664  1,5G  0 Empty
/dev/sdb2         924    5595    4672  2,3M ef EFI (FAT-12/16/32)


Disk /dev/zram0: 483,4 MiB, 506900480 bytes, 123755 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 483,4 MiB, 506900480 bytes, 123755 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram2: 483,4 MiB, 506900480 bytes, 123755 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram3: 483,4 MiB, 506900480 bytes, 123755 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
[close]
and:

Spoiler (click here to view / hide)
root@peppermint / # sudo blkid/dev/sda1: UUID="af3003a8-dd0f-4130-89c8-759c166b227c" TYPE="ext4" PTTYPE="dos" PARTUUID="000229af-01"
/dev/sda5: LABEL="data" UUID="3aca02db-0ebf-446e-bc7f-4f540fba7289" TYPE="ext4" PARTUUID="000229af-05"
/dev/sda7: UUID="cea1ce2b-95ec-47c7-8fba-2cda25e0ec85" TYPE="ext4" PARTUUID="000229af-07"
/dev/sda8: UUID="3f71d648-f7b6-4dd1-bfb7-546c26f78817" TYPE="ext4" PARTUUID="000229af-08"
/dev/loop0: TYPE="squashfs"
/dev/sda6: UUID="af3c8372-93b5-49ec-92d9-680d251921e6" TYPE="swap" PARTUUID="000229af-06"
/dev/sdb1: UUID="2019-05-13-13-12-11-00" LABEL="Peppermint Ten" TYPE="iso9660" PTUUID="6b8b4567" PTTYPE="dos" PARTUUID="6b8b4567-01"
/dev/sdb2: SEC_TYPE="msdos" UUID="044E-AC17" TYPE="vfat" PARTUUID="6b8b4567-02"
/dev/zram0: UUID="104ec437-dfe5-4340-bb46-3d4f07d12ba5" TYPE="swap"
/dev/zram1: UUID="18a81d52-4424-48c3-9be3-0b9dc95cd6b3" TYPE="swap"
/dev/zram2: UUID="5208fb04-0339-4ceb-88b1-60dda15d0dd6" TYPE="swap"
/dev/zram3: UUID="a4165e8d-9e2f-47ef-bdf6-9251ec379b73" TYPE="swap"
[close]
I hope that this is something that can be resolved.  :(


Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 09, 2019, 03:55:33 pm
Okay can you give us the make/model of computer (so I can look for the manual), because for some reason the LiveUSB appears to be booting in UEFI mode.

Oh, and what are you using to create the LiveUSB ?
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 09, 2019, 04:19:16 pm
Hi PCNetSpec,

Computer: acer  Extensa 2510. Here is the inxi info:

Spoiler (click here to view / hide)
peppermint@peppermint ~ $ inxi -Fz
System:    Host: peppermint Kernel: 4.18.0-18-generic x86_64 bits: 64 Desktop: N/A
           Distro: Peppermint Ten
Machine:   Device: laptop System: Acer product: Extensa 2510 v: V1.09 serial: N/A
           Mobo: Acer model: BA50_HB v: V1.09 serial: N/A
           UEFI: Insyde v: V1.09 date: 07/11/2014
Battery    BAT1: charge: 46.6 Wh 100.0% condition: 46.6/55.9 Wh (83%)
CPU:       Dual core Intel Core i3-4030U (-MT-MCP-) cache: 3072 KB
           clock speeds: max: 1900 MHz 1: 1150 MHz 2: 1156 MHz 3: 1169 MHz
           4: 1121 MHz
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           Display Server: x11 (X.Org 1.20.1 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.00hz
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 4.5 Mesa 18.2.8
Audio:     Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel
           Card-2 Intel Haswell-ULT HD Audio Controller driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.18.0-18-generic
Network:   Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
           driver: r8169
           IF: enp1s0f1 state: down mac: <filter>
           Card-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
           driver: ath9k
           IF: wlp2s0 state: up mac: <filter>
Drives:    HDD Total Size: 532.1GB (2.1% used)
           ID-1: /dev/sda model: WDC_WD5000LPVX size: 500.1GB
           ID-2: USB /dev/sdb model: USB_Flash_Drive size: 32.0GB
Partition: ID-1: / size: 1.9G used: 160M (9%) fs: overlay dev: N/A
           ID-2: swap-1 size: 4.22GB used: 0.00GB (0%) fs: swap dev: /dev/sda6
           ID-3: swap-2 size: 0.51GB used: 0.00GB (0%) fs: swap dev: /dev/zram0
           ID-4: swap-3 size: 0.51GB used: 0.00GB (0%) fs: swap dev: /dev/zram1
           ID-5: swap-4 size: 0.51GB used: 0.00GB (0%) fs: swap dev: /dev/zram2
           ID-6: swap-5 size: 0.51GB used: 0.00GB (0%) fs: swap dev: /dev/zram3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 47.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 194 Uptime: 1:34 Memory: 699.4/3867.3MB
           Client: Shell (bash) inxi: 2.3.56
[close]
I used mintstick from another installation of Peppermint Ten to create the live session usb.

Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 09, 2019, 05:32:51 pm
Okay that's odd, according to the manual this system doesn't even appear to support UEFI :-\
https://www.acer.com/ac/en/ID/content/support-product/5343;-;

When you boot the LiveUSB, do you see the GRUB menu, or the graphical "Try Peppermint / Install Peppermint" screen (with the Peppermint logo) ?

And whilst booted to the LiveUSB, what's the output from
Code: [Select]
[ -d /sys/firmware/efi ] && echo "Booted as UEFI" || echo "Booted as Legacy BIOS"



Just thinking out loud here...

Maybe you could boot the LiveUSB .. install Boot Repair
https://help.ubuntu.com/community/Boot-Repair

then use it to fix GRUB



If not, we're gonna need to chroot in and reinstall grub.

Do you know which partition contains the Peppermint 10 installation that failed at grub installation ?
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 10, 2019, 02:53:08 am
Hi PCNetSpec,

When booting the live session I get a GRUB menu with a black sort of leather-looking background (so it seems to be a graphical screen), but there is no Peppermint logo. In the BIOS settings, under the entry Boot, there is a choice to use UEFI (which I do not select).

The requested output:

Code: [Select]
Booted as UEFI
Strange but true ...  ???


WRT your talking to yourself at the end of your last message: I almost had done this at the beginning, but decided to wait and see if there is something else to do first (and, I must admit, I've never used the program Boot Repair before).


Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: pin on July 10, 2019, 06:52:36 am
Wouldn't it be better to try to put the boot flag on the PM7 partion, re-install grub on that and reformat the PM10 partion??
Just thinking out loud...
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 10, 2019, 07:11:07 am
Hi pin,

Great idea! I like that. And then run the live session installer again, format the P10 partition (just to be safe), install to it again and then put the GRUB in the P10 partition?


I think I will try this.  :)


Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition
Post by: PCNetSpec on July 10, 2019, 12:18:24 pm
In your BIOS, under the "BOOT" tab, is there a "Boot Mode" option that is currently set to [UEFI] ?

Nothing is mentioned in the manual about UEFI, but I gather it was a Win8 PC, and it obviously can boot UEFI

You need to find how to boot the LiveUSB in legacy BIOS mode

https://www.youtube.com/watch?v=ojW_UnN9enw

https://www.youtube.com/watch?v=NwzlN0qppqM
Title: Re: Problem with legacy installation: no EFI partition
Post by: Slim.Fatz on July 12, 2019, 03:57:08 am
Hi PCNetSpec,

Sorry for the late reply but I was out of town for a short while.

Thanks again for your time and effort. It is most probably true that back when I bought this laptop Win8 was typically installed by default. But when I purchased this laptop I purchased it precisely because the dealer could deliver it without any OS (although it turned out to have a pretty much useless and specked-down Linux of some sort -- whose name I no longer remember -- and I immediately installed PeppermintOS and eliminated the original from the HDD).

Unfortunately, the two videos that you found only show and describe what I have been doing all along. As an alternative I decided to try several other Linux distros to see if the same problem occurs. With two Ubuntus (minimal and Xubuntu) and with an Arch derivative that uses the Calamares installer the exact same thing occurs (no EFI partition found error).

I was about to give up and either try installing the Boot Repair utility or try performing the suggestion from pin (moving the boot flag to my Peppermint 7 partition, installing GRUB to the MBR from there and then checking whether I could boot into the Peppermint Ten installation).

But then I thought I would try one last distro and DL'ed MX Linux 18.3. And presto! No problem, it installed without hesitation and runs perfectly.  :o So I guess I'll mark this as ABANDONED and fool around with MX Linux for a bit (when I am not in Peppermint Ten on my other machines).  ::) ;D


Thanks again for the time and effort from yourself and pin. I'm sorry it didn't really help us in any way WRT others having this problem (but until now, no one else has mentioned it as being an issue  :-\ ).


Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition [ABANDONED]
Post by: pin on July 12, 2019, 04:10:51 am
As far as I'm concerned, NO problem  ;)
I was actually at the airport on my way to Portugal when this all started  :) ...visiting family and some holiday after that.

Some early EFI machines seem to behave rather strange. I've had a few installs with a similar issue, although setting the boot to legacy mode has always fixed it. Don't really know what has happened in your case  :-\

Enjoy your multiboot  :D
Title: Re: Problem with legacy installation: no EFI partition [ABANDONED]
Post by: Slim.Fatz on July 12, 2019, 04:46:25 am
Hi pin,

Enjoy your time with the family and don't forget to get in some R&R too!  :D


Regards,

-- Slim
Title: Re: Problem with legacy installation: no EFI partition [ABANDONED]
Post by: alynur on July 18, 2019, 09:48:50 am
I seem to remember, pretty strange for me, about somebody wanting to install without installing grub. Isn't there a code that can be run while in the live session to tell umbiguity(?) to install without grub?