Couldn't find EFI system partition.

penny-farthing · Feb 12, 2024

I have a computer configured in dual-boot with Solus and Windows.
It has 2 hard discs:

a SDD on which the 2 operating systems are installed,
a HDD for user files (/home) and swap.
Solus and Windows behave separately each on their side.

However, the following command found in the help of Solus gives this result:

administrateur@solus-budgie ~ $ bootctl status | grep "Secure Boot"
Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.
   Secure Boot: disabled (setup)

Do I have to worry about it?

administrateur@solus-budgie ~ $ lsblk -f
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                         
├─sda1
│    vfat   FAT32       2EC8-1B40                                           
├─sda2
│    ext4   1.0         c3c9274c-5ef1-40c6-a218-155c5bacac2e    6,3G    80% /
├─sda3
│                                                                           
├─sda4
│    ntfs               801CF4941CF48706                                    
├─sda5
│    ntfs               FE4292174291D4AD                                    
├─sda6
│    ntfs               C898785F98784DC6                                    
└─sda7
     ntfs               8C907256907246AC                                    
sdb                                                                         
├─sdb1
│    ext4   1.0         3edffafe-629e-44d5-a649-372b808279b2  187,8G    74% /home
├─sdb2
│                                                                           
└─sdb5
     swap   1           aaf8bb80-1bbc-410d-9d03-34a7c14d365c                [SWAP]
sr0                                                                         
administrateur@solus-budgie ~ $

administrateur@solus-budgie ~ $ efivar --list
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderTimeExecUSec
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderEntrySelected
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderEntries
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderDevicePartUUID
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderImageIdentifier
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderFeatures
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderFirmwareType
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderFirmwareInfo
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderInfo
4a67b082-0a4c-41cf-b6c7-440b29bb8c4f-LoaderTimeInitUSec
605dab50-e046-4300-abb6-3dd810dd8b23-MokListTrustedRT
605dab50-e046-4300-abb6-3dd810dd8b23-SbatLevelRT
605dab50-e046-4300-abb6-3dd810dd8b23-MokListXRT
605dab50-e046-4300-abb6-3dd810dd8b23-MokListRT
1b838190-4625-4ead-abc9-cd5e6af18fe0-HiiDB
7b77fb8b-1e0d-4d7e-953f-3980a261e077-AfterReadyToBoot
8be4df61-93ca-11d2-aa0d-00e098032b8c-BootCurrent
8be4df61-93ca-11d2-aa0d-00e098032b8c-LangCodes
8be4df61-93ca-11d2-aa0d-00e098032b8c-PlatformLangCodes
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-SetupHandles
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-AmiGopPolicySetupData
8be4df61-93ca-11d2-aa0d-00e098032b8c-ErrOutDev
8be4df61-93ca-11d2-aa0d-00e098032b8c-BootOptionSupport
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConInDev
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0510_0_VV
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0501_1_VV
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0501_0_VV
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0400_0_VV
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0604_0_VV
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOutDev
d73446d9-7724-4ca2-83a6-7cf79b3cf661-VgaCtlrInfo
3c388db1-33dd-4b78-afb6-66a8bb9d6dfc-VgaDisplayOutSelect
6b9cfdf4-fcd2-4ea2-d796-7fd06c91f491-ME VAR SHADOW
dd41adf5-4368-4654-b1ca-46a6b98d9e84-EasySmartFanAddress
dd41adf5-4368-4654-b1ca-46a6b98d9e84-EasyHealthAddress
dd41adf5-4368-4654-b1ca-46a6b98d9e84-EasyVoltageAddress
8be4df61-93ca-11d2-aa0d-00e098032b8c-USB_POINT
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-UsbMassDevValid
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-UsbMassDevNum
8be4df61-93ca-11d2-aa0d-00e098032b8c-OsIndicationsSupported
e6a01b2b-a795-41f0-85a0-53acaab21d97-SetupXtuBufferAddress
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-NBPlatformData
01368881-c4ad-4b1d-b631-d57a8ec8db6b-OA3MSDMvariable
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-SetupPlatformData
aade07e9-b7f0-4c62-9e0f-41ba268adaae-TPM_HW_VV
83a8a2a2-dc50-4f8d-8e48-ebc8f89c1566-FIDLOC
e6c2f70a-b604-4877-85ba-deec89e117eb-PchS3Peim
4bafc2b4-02dc-4104-b236-d6f1b98d9e84-S3SS
8be4df61-93ca-11d2-aa0d-00e098032b8c-SetupMode
8be4df61-93ca-11d2-aa0d-00e098032b8c-SecureBoot
8be4df61-93ca-11d2-aa0d-00e098032b8c-SignatureSupport
80e1202e-2697-4264-9cc9-80762c3e5863-Setup
87f22dcb-7304-4105-bb7c-317143ccc23b-MrcS3Resume
e20939be-32d4-41be-a150-897f85d49829-MemoryOverwriteRequestControl
b05e6b5f-6ed8-4015-b5c5-b1049faf3e5b-Profile0
b05e6b5f-6ed8-4015-b5c5-b1049faf3e5b-Profile-1
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot001B
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-27-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-26-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-25-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-24-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-23-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-22-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-21-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-20-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-19-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-18-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-17-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-16-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-15-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-14-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-13-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-12-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-11-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-10-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-9-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-8-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-7-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-6-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-5-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-4-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-3-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-2-1-1705074323-C
cfc8fc79-be2e-4ddc-97f0-9f98bfe298a0-dump-type0-1-1-1705074323-C
ba57e015-65b3-4c3c-b274-659192f699e3-BugCheckParameter1
ba57e015-65b3-4c3c-b274-659192f699e3-BugCheckCode
ba57e015-65b3-4c3c-b274-659192f699e3-BugCheckProgress
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-Setup
8be4df61-93ca-11d2-aa0d-00e098032b8c-BootOrder
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot001A
3c4ead08-45ae-4315-8d15-a60eaa8caf69-DefaultLegacyDevOrder
a56074db-65fe-45f7-bd21-2d2bdd8e9652-OldLegacyDevOrder
a56074db-65fe-45f7-bd21-2d2bdd8e9652-LegacyDevOrder
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0002
8be4df61-93ca-11d2-aa0d-00e098032b8c-OsIndications
b540a530-6978-4da7-91cb-7207d764d262-FastBootOption
77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_Lsa_Ppl_Config
01368881-c4ad-4b1d-b631-d57a8ec8db6b-MonotonicCounter
8be4df61-93ca-11d2-aa0d-00e098032b8c-Timeout
fe47349a-7f0d-4641-822b-34baa28ecdd0-UIT_DATA
fe47349a-7f0d-4641-822b-34baa28ecdd0-UIT_HEADER
d719b2cb-3d3a-4596-a3bc-dad00e67656f-dbx
a9b5f8d2-cb6d-42c2-bc01-b5ffaae4335e-PBRDevicePath
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0000
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0018
77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_RvkSiStatus
b05e6b5f-6ed8-4015-b5c5-b1049faf3e5b-Profile-3
b05e6b5f-6ed8-4015-b5c5-b1049faf3e5b-Profile-2
77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_DriverSiStatus
eaec226f-c9a3-477a-a826-ddc716cdc0e3-OfflineUniqueIDRandomSeedCRC
eaec226f-c9a3-477a-a826-ddc716cdc0e3-OfflineUniqueIDRandomSeed
eaec226f-c9a3-477a-a826-ddc716cdc0e3-UnlockIDCopy
77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_EntRevokeSiStatus
77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_ATPSiStatus
77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_WinSiStatus
77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_SkuSiStatus
77fa9abd-0359-4d32-bd60-28f4e78f784b-Kernel_SiStatus
77fa9abd-0359-4d32-bd60-28f4e78f784b-CurrentPolicy
8be4df61-93ca-11d2-aa0d-00e098032b8c-BootOrder1
a56074db-65fe-45f7-bd21-2d2bdd8e9652-LegacyDevOrder1
9d0da369-540b-46f8-85a0-2b5f2c301e15-EfiTime
2a64d079-aceb-4ad9-afd5-252e35ba994a-EasyTuneSetupAddress
d1405d16-7afc-4695-bb12-41459d3695a2-NetworkStackVar
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-UsbSupport
c811fa38-42c8-4579-a9bb-60e94eddfb34-AMITSESetup
8be4df61-93ca-11d2-aa0d-00e098032b8c-PlatformLang
4c19049f-4137-4dd3-9c10-8b97a83ffdfa-MemoryTypeInformation
4c19049f-4137-4dd3-9c10-8b97a83ffdfa-PreviousMemoryTypeInformation
c020489e-6db2-4ef2-9aa5-ca06fc11d36a-AcpiGlobalVariable
af9ffd67-ec10-488a-9dfc-6cbf5ee22c2e-AcpiGlobalVariable
b80a8e5b-c02a-4a31-ae12-58e46e803e89-HardwareConfigData
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-BiosSetupType
8be4df61-93ca-11d2-aa0d-00e098032b8c-Lang
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-HswMitAttrib
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-AdvMitAttrib
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-MemMitAttrib
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-ProcMitAttrib
45cf35f6-0d6e-4d04-856a-0370a5b16f53-DefaultBootOrder
8be4df61-93ca-11d2-aa0d-00e098032b8c-ErrOut
5a47386b-4c41-43b6-a140-824b0260ca8d-Ps2KeyboardDetectRecord
09b5c46a-0f41-4cee-84ff-f3660a0b08d6-Ps2MouseDetectRecord
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0510_0_NV
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0501_1_NV
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0501_0_NV
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0400_0_NV
560bf58a-1e0d-4d7e-953f-2980a261e031-PNP0604_0_NV
4b681db5-de3a-46ea-8e0c-a2f7eae1c4b8-ME VARIABLE
40312829-7891-4abd-b200-0c541b061939-MemCeil.
a31b27a4-cae6-48ff-8c5a-294221e6f389-PchInitPei
de565cd0-b278-4d59-8681-d23578dcad48-OemIdCheck
01f33c25-764d-43ea-aeea-6b5a41f3f3e8-SbAslBufferPtrVar
e1e2a446-0365-4c65-919c-0371c3f9f5ff-PegGen3PresetSearchData
ec87d643-eba4-4bb5-a1e5-3f3e36b20da9-NumOfPState
1456cc6e-22ac-5289-33ba-2e13bbdabaee-CPUS3APICID
f3ed95df-828e-41c7-bca0-16c41965a634-TcgInternalSyncFlag
01368881-c4ad-4b1d-b631-d57a8ec8db6b-FPDT_Variable
e6c2f70a-b604-4877-85ba-deec89e117eb-PchInit
78ce2354-cfbc-4643-aeba-07a27fa892bf-WdtPersistentData
dde1bc72-d45e-4209-ab85-14462d2f5074-HobRomImage
4599d26f-1a11-49b8-b91f-858745cff824-StdDefaults
administrateur@solus-budgie ~ $

The BIOS seems to me correctly configured in EFI:

I lack expertise in this area and don't want to make any mistakes. Any help would be appreciated.

Thank you in advance.

alfisya · Feb 13, 2024

Is your computer boots fine? AFAIK with clr-boot-manager, when system succesfully boot to desktop it detach the boot partition from your root system. So, if you want to check what is inside your boot partition, you have to mount it first. As long your computer works fine, I think you can ignore this.

[deleted] · Feb 13, 2024

What are you trying to accomplish? What help center article are you referring to?

penny-farthing · Feb 13, 2024

[deleted]

Solus Help Center is a good teaching tool that I appreciate, as it enables me to learn about terminal commands that provide interesting information about my computer and which may be useful for writing a post on this forum.

For instance, with the following command:
sudo fdisk -l /dev/sdX
I was able to check that my SSD was in GPT, and discover that my HDD was in MBR.

To get back to your question, I read this page from the Solus Help Center:
https://help.getsol.us/docs/user/quick-start/installation/secure-boot

where I found this terminal command:
bootctl status | grep "Secure Boot"
which returned the anomaly message detailed above.

I checked that BIOS was in EFI (see screenshots above).

Looking in Nemo, I've found a folder called boot, but it's empty (no efi sub-folder either).

Not knowing if this is normal (although Solus (like Windows) launches fine), I thought I'd mention it here in the hope that someone more up to date on these matters will be able to answer my question.
I'm just trying to understand, that's all.

And thanks in advance for your feedback.

penny-farthing · Feb 21, 2024

alfisya

I finally found the solution to my problem and here is how I did:

First of all, I created in the boot folder, a subdossary efi.

Then, with the help of the blkid terminal command, allowing me to obtain the UUID of my partition sda1, I updated the file etc/fstab by adding the following line:
UUID = 2ec8-1b40 /boot auto defaults umask = 0 0 0

Finally, in the bios of my Gigabyte motherboard, in the Bios Features section:

I passed CSM Support to Never, which allowed me to access the update of Secure Boot ;
then Secure Boot went to Enable after I validated the Load Default Boot Keys option in the Key Management section ;
so, I left the BIOS with saving my updates, which led me to the Enrolling The Solus Certificate screen ; then I followed the instructions described in the help of Solus (cf. link indicated above)
I finally rebooted the computer and the terminal command:
bootctl status | grep "Secure Boot"
now displays me:
Secure Boot: Enabled (User)
Note that the boot folder now includes:
a folder EFI,
a folder loader,
a file System Volum Information,
and a solus-enroll-me.cer file.

Thank you for trying to find a solution to my request.
I would have one last question to ask you before closing this post.

Is it preferable that my HDD (my data) is configured in GPT like my SSD (my operating systems), or does it not matter?
(actually, my HDD is configured in BIOS, and the cohabitation with my SDD does not seem any problem)

Waiting for your feedback,
Best regards.

alfisya · Feb 21, 2024

Is it preferable that my HDD (my data) is configured in GPT like my SSD (my operating systems), or does it not matter?

I honestly don't know. Unless your system doesn't support GPT, I don't see any reason to format a harddrive in MBR. Really, I don't know.

penny-farthing · Feb 22, 2024

alfisya

I probably misunderstood you.

My SDD (my operating systems) is configured in GPT and I intend to leave it like this.
On the other hand, my HDD (my data) is configured in MBR: can it stay like this or, should I also consider converting it to GPT?

It was the meaning of my question, excuse me if I had not been clear enough.

alfisya · Feb 22, 2024

alfisya As long your computer works fine, I think you can ignore this.

Like my first answer to your post, as long as everything works fine just leave it as is. I myself not that familiar with the technical benefit of GPT over MBR. Here is a quote from a nice article :

If one of your drives is currently using an MBR partition table, you might be asking yourself if you should upgrade to the newer GPT standard.

In short, probably not. As the saying goes, if it ain't broke, don't fix it.

It's very easy to ruin the MBR sector of the drive, making it impossible to boot up again. Then you'll either need to create a recovery USB drive with Windows or Linux and try to repair the MBR, or completely wipe the drive and reinstall the operating system.

Cheers!

penny-farthing · Feb 27, 2024

alfisya

Thank you for your comments, so I will follow your recommendations and close this post.