Support Requests - CLICK TO READ BEFORE POSTING


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

The boot entry was not created
#1

System Specs
Operating System – Linux LiteLinux Lite 8.0
CPU / ProcessorIntel Celeron N3050
Memory (RAM)4 GB
StorageHard Drive (HDD)
Graphics (GPU)IGPU
I installed linux lite 8.0 successfully , its boot files were created too , but the boot entry was not created.
I tried reinstalling it but it didn't work either.
Reply
#2

It is hard to suggest anything based on the information provided so far.

What exactly do you mean by a boot entry and how does your system use boot entries ?
What actually happens when you boot ?
What do you expect should happen when you boot ?

Which options did you select at the partitioning stage of the install ?

stevef
clueless
Reply
#3

1.By boot entries I meant boot options we see in bios or directly pressing F12(in my case).
2.When I boot it directly boots into windows.
3.I expect grub to appear and show entry for both the OS.
4.I made a common efi partition for linux-lite and win 10 of 512mb ; win 10 files were already there so I chose manual partitioning and selected the same efi partition and gave it the mountpoint /boot/efi.

Just so u know this is not caused by windows cuz i tried clean installing it still same issue.

[Image: 1.png]
See no boot option for Linux-lite.

[Image: 2.png]
see the files are there
Reply
#4

Have you tried to use the 'Install Alongside' option instead of 'Manual Partitioning' ?

Abhi_245 Wrote:Just so u know this is not caused by windows cuz i tried clean installing it still same issue.
When you did this, was it using 'Erase Disk' ?

stevef
clueless
Reply
#5

Nopes haven't tried install alongside option , cuz I'm not sure if it deletes a existing partition or not.

Not using clean disk, cuz I have some data in a partition; I just removed all window partiton.
Reply
#6

Suspect there is a problem with some aspect of the manual partitioning.
Manual partitioning allows multiple combinations of filesystem, partition table, boot mode etc.  Unless you are 100% sure of what you are doing, it can easily result in a system that doesn't boot.

If you have important data in an existing partition, it must be backed up safely before doing anything.

The 'install alongside' option should allow you to shrink existing partitions to create room and then put Lite in the space.  Calamares (the installer program) allows you to view what changes it will make before anything is actually changed.

stevef
clueless
Reply
#7

(09-04-2026, 04:53 PM)Abhi_245 Wrote:  1.By boot entries I meant boot options we see in bios or directly pressing F12(in my case).
2.When I boot it directly boots into windows.
3.I expect grub to appear and show entry for both the OS.
4.I made a common efi partition for linux-lite and win 10 of 512mb ; win 10 files were already there so I chose manual partitioning and selected the same efi partition and gave it the mountpoint /boot/efi.

Just so u know this is not caused by windows cuz i tried clean installing it still same issue.
[...]

Partition table

The information you provided is lacking an essential aspect:
What type of partition table do you have? Is it MS-DOS or is it GPT?
Instalation paths are different.
I recommend you to read carefully the following:
https://wiki.linuxliteos.com/en/install
Especially, watch closely the screenshots after the partitioning table.
Although it is somehow less obvious, there are details that are different in the scenario of installing on a GPT media (HDD, SSD) versus a MSDOS one. Meaning that if the partition table is MSDOS, the partitioning scheme (the disk slices are...) is different from a GPT partition table.

Dual boot:
Unfortunately, I guess what you want to do, is more difficult than it looks.
After failing many times (due to an incomplete/inappropriate driver support for Radeon 780M), I discovered that the "Manual Partitioning" path, has something unexpected for me and somehow abnormal: it requires a clean boot partition (the FAT 32, 512 MB one).
What changes were made at the upstream level in Ubuntu, is above my understanding.
Now to get back to the Windows problem, it looks that you tried to install Linux Lite OVER Windows.
When the Partition Manager finds some data on the /dev/sda1 (the FAT 32 partition), instead of writing the mount point /boot/efi, it skips writing this which leads to the result you got. 
So, dual booting, as it seems, requires a different approach.

Installing both
While I never use dual boot (a too long history to tell...), I had to learn to do it in time.
So, while the common scenario was "Setup Windows, THEN Linux", since the new Ubuntu came out, it looks that things need to be reversed.
Install FIRST Linux, THEN Windows. See what happens.

As I see things, stevef offered a solution that might work (at least it should!): "Install alongside..." and looks an easier path.
So, instead of venturing on an unknown territory, before testing the above solution, test "Install alongside..."

Partitions formatting 
Earlier in this conversation, you mentioned your concern regarding some partitions that you want to keep for the data they contain.
Well, relax! You can mount any partition you want automatically, without the risk of losing data!
For more than 14 years, I use three partitions I want to have mounted at boot time so, I set the mount points accordingly at the installation stage. One of them is /home, which allows me to keep all Apps' settings and DE settings, regardless the number of clean installs I perform over time.
All you need to do is set the mount points and leave unchecked the CheckBox "Format partition".
The only partition that requires formatting, is the main one (/). All the others, can remain untouched, unless you want them explicitly formatted.

Now, if your system is old and has a BIOS firmware, you need to do a special type of partitioning and formatting.
If this is the case, mention this in a reply if you need help to do this. It might be more difficult, but in the end, I guess all can be done.


Intel Celeron N3050
Unfortunately, i have no idea what type of firmware has your machine.
My ASUS X200MA which is 2014, has a UEFI firmware so I presume your machine (2015), should have a UEFI firmware too.
In this case, you don't need any complicated partitioning and formatting.

Final touch

My final recommendation is to go on the "Install alongside..." scenario.
Some people here went on this path and they succeeded. So you should.
However, if anything goes sideways, you have the alternatives above.
In any case, you should backup the partitions you want to keep untouched, just in case. Data recovery is better than losing whatever data you have.

Good luck!
Besrt regards!

"It's easy to die for an idea. It's way harder TO LIVE for your idea!"
Current Machine:
Dell Precision T1700, 16 GB RAM, SSD Kingston A400, 480 GB.
Laptop:
ASUS X200MA , Intel® Celeron® N2830, 2 GB RAM, SSD Kingston A400, 480 GB.
Reply
#8

stevef , I tried install alongside but it didnt work either , but calamares did allow to see which things will be changed.
Further I tried to resolve this issue using AI , it said to add a boot option pointing to boot files of linux-lite.

Şerban S. , my laptop uses GPT partition table, and UEFI boot.
I tried clean installing as well without any windows partition , but it didnt work; it directly said no bootable device found.

yeah the system is old , inspiron 3552 (2016), and the latest bios firmware is of  2018 Apr.
Reply
#9

Abhi_245 Wrote:I tried install alongside but it didnt work either
Exactly the same as before or different ?

Abhi_245 Wrote:Further I tried to resolve this issue using AI , it said to add a boot option pointing to boot files of linux-lite.
Not sure what AI means by a 'boot option pointing to boot files'.  Did you follow the AI suggestion ?

stevef
clueless
Reply
#10

yup same as before every file created but no boot options.

I didn't use the command it gave me. could u review it ?
Code:
sudo efibootmgr -c -d /dev/sda2 -p 1 -L "Linux Lite" -l '\EFI\Linux_Lite\grubx64.efi'

it also said if secure boot is on , we can use shimx64.efi instead of grubx64.efi
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)