Yess That means EFI is working and grub is installed
Now it doesnāt find something suitable to boot.
sudo os-prober
and
sudo update-grub
Maybe that was it then?
Yess That means EFI is working and grub is installed
Now it doesnāt find something suitable to boot.
sudo os-prober
and
sudo update-grub
Maybe that was it then?
[manjaro@manjaro ~]$ sudo os-prober
/dev/nvme0n1p4:Manjaro Linux (20.1):ManjaroLinux:linux
[manjaro@manjaro ~]$ sudo update-grub
/usr/bin/grub-probe: error: failed to get canonical path of `overlay'.
I have chroot then update-grub, but on reboot, boot rescure ā¦ Iām going to sleep, thank you very much for your support, TO ALL. I keep hope for tomorrow ā¦ bye
I donāt know what to do, does anyone have an idea?
Iām a little lost whatās the situation right now.
You seem to have executed the commands from the installation media but without chroot.
Do you still have the efivars error message when you run update-grub
in chroot?
Is your installation media recent?
What happens if you run the following outside chroot?
sudo modprobe efivars
ls /sys/firmware/efi/efivars/
After some tests, it seems on a dualboot with efi manjaro-chroot -a
doesnāt work. Here is a is tutorial how to chroot manually: GRUB/Restore the GRUB Bootloader - Manjaro Linux
That worked thenā¦
Quote:
And if you get something like
grub-install: error: failed to get canonical path of `unionā.
means that probably you forgot to chroot.
https://wiki.manjaro.org/index.php?title=GRUB/Restore_the_GRUB_Bootloader#Note
What do you mean? How doesnāt work?
It seems manjaro-chroot canāt recognize the correct partitions in a dualboot setup with windows on efi. At least not on my laptop and i have done a normal installation with calamares, nothing special. I have done it manually step by step, then it worked.
Need to check how exactly manjaro-chroot works there. BIOS mode works great.
Need to do more testsā¦
But do you mean the bug where you have to select Manjaro in a list, where is marked as 0 but actually you have to select 1?
Or what is the error?
My system is Dual boot with Windows in UEFI and I donāt have any problem (besides that). Also in VMs works the same way
At least i am not an expert on dualbootsā¦
Ah you mean it is the number is wrong? That could explain it. Thanks. I just used the tools as a normal user would do.
Yes there have been a known bug for a long time. I sent a patch and it seems that itās already fixed in the Gitlab, but it still havenāt made it to the ISOs.
[manjaro@manjaro ~]$ sudo modprobe efivars
modprobe: FATAL: Module efivars not found in directory /lib/modules/4.4.33-1-MANJARO
[manjaro@manjaro ~]$ ls /sys/firmware/efi/efivars/
AMD_PBS_SETUP-a339d746-f678-49b3-9fc7-54ce0f9df226 LoaderInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
AMD_RAID-fe26a894-d199-47d4-8afa-070e3d54ba86 LoaderTimeExecUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
AmdSetup-3a997502-647a-4c82-998e-52ef9486a247 LoaderTimeInitUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
AmiHardwareSignatureSetupUpdateCountVar-81c76078-bfde-4368-9790-570914c01a65 LoaderTimeMenuUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
AMITCGPPIVAR-a8a2093b-fefa-43c1-8e62-ce526847265e LoadUserSFlag-78429c2e-f1f5-4fe0-be3d-dc064fad5c04
AMITSESetup-c811fa38-42c8-4579-a9bb-60e94eddfb34 MaximumTableSize-4b3082a3-80c6-4d7e-9cd0-583917265df1
ApSyncFlagNv-ad3f6761-f0a3-46c8-a4cb-19b70ffdb305 MemoryOverwriteRequestControl-e20939be-32d4-41be-a150-897f85d49829
Boot0008-8be4df61-93ca-11d2-aa0d-00e098032b8c MemoryOverwriteRequestControlLock-bb983ccf-151d-40e1-a07b-4a17be168292
Boot000D-8be4df61-93ca-11d2-aa0d-00e098032b8c MFlashVersionVariable-fd6b0489-d401-40c2-98b1-b1300b048711
Boot000E-8be4df61-93ca-11d2-aa0d-00e098032b8c MonotonicCounter-01368881-c4ad-4b1d-b631-d57a8ec8db6b
Boot000F-8be4df61-93ca-11d2-aa0d-00e098032b8c msiDispatcherImageList-26817ae9-ca17-80d5-ab93-2f682e69efa9
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c MsiOcBackup-ba6510ad-1972-4d84-b28e-00e5fc8245cb
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c MsiOcCpuMemInfo-4ba187df-3bad-41b2-b73b-3d3dc1cc6387
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c MsiOcInfoFlag-48419251-dd85-4597-84b4-11182014adde
BugCheckCode-ba57e015-65b3-4c3c-b274-659192f699e3 MsiOcMemECCInfo-78876464-9753-a77a-7607-652533891231
BugCheckParameter1-ba57e015-65b3-4c3c-b274-659192f699e3 MsiOcMemPatchID-78876464-9753-a77a-7607-652533891231
BugCheckProgress-ba57e015-65b3-4c3c-b274-659192f699e3 MsiOcMemRGBInfo-78876464-9753-a77a-7607-652533891231
CACHE-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 MsiOcMemSpdCheckSum-78876464-9753-a77a-7607-652533891231
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c MsiOcMemSpdData-78876464-9753-a77a-7607-652533891231
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c MsiOcMemSpdXMPInfo-78876464-9753-a77a-7607-652533891231
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c msiOcProFileStringCount-857fbb9e-8a3b-97ce-ae58-2515e09922bb
CurrentPolicy-77fa9abd-0359-4d32-bd60-28f4e78f784b NetworkStackVar-d1405d16-7afc-4695-bb12-41459d3695a2
db-d719b2cb-3d3a-4596-a3bc-dad00e67656f OA3MSDMvariable-01368881-c4ad-4b1d-b631-d57a8ec8db6b
dbDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c OfflineUniqueIDRandomSeedCRC-eaec226f-c9a3-477a-a826-ddc716cdc0e3
dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f OfflineUniqueIDRandomSeed-eaec226f-c9a3-477a-a826-ddc716cdc0e3
dbxDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c OldLegacyDevOrder-a56074db-65fe-45f7-bd21-2d2bdd8e9652
DefaultBootOrder-45cf35f6-0d6e-4d04-856a-0370a5b16f53 OsIndications-8be4df61-93ca-11d2-aa0d-00e098032b8c
DefaultLegacyDevOrder-3c4ead08-45ae-4315-8d15-a60eaa8caf69 OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8c
DeploymentModeNv-97e8965f-c761-4f48-b6e4-9ffa9cb2a2d6 PK-8be4df61-93ca-11d2-aa0d-00e098032b8c
DmiArray-4b3082a3-80c6-4d7e-9cd0-583917265df1 PKDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c
DmiVar0100010400-4b3082a3-80c6-4d7e-9cd0-583917265df1 PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
DmiVar0100010500-4b3082a3-80c6-4d7e-9cd0-583917265df1 PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
DmiVar0100010700-4b3082a3-80c6-4d7e-9cd0-583917265df1 PNP0400_0_NV-560bf58a-1e0d-4d7e-953f-2980a261e031
DmiVar0100010800-4b3082a3-80c6-4d7e-9cd0-583917265df1 PNP0501_0_NV-560bf58a-1e0d-4d7e-953f-2980a261e031
DmiVar0200020400-4b3082a3-80c6-4d7e-9cd0-583917265df1 ProFileAutoSaveInfo-515b6cdf-bbe7-4509-83cc-d725903d522a
DmiVar0200020500-4b3082a3-80c6-4d7e-9cd0-583917265df1 SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c
DmiVar0200020700-4b3082a3-80c6-4d7e-9cd0-583917265df1 SecureBootSetup-7b59104a-c00d-4158-87ff-f04d6396a915
DmiVar0300030400-4b3082a3-80c6-4d7e-9cd0-583917265df1 Setup-80e1202e-2697-4264-9cc9-80762c3e5863
DmiVar0300030700-4b3082a3-80c6-4d7e-9cd0-583917265df1 Setup-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c
ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c SignatureSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c
FBSelect-3fae9ba1-a3f1-42eb-b6f2-b616ea57db9d SmbiosEntryPointTable-4b3082a3-80c6-4d7e-9cd0-583917265df1
FixedBoot-de8ab926-efda-4c23-bbc4-98fd29aa0069 SmbiosEntryPointTableF000-4b3082a3-80c6-4d7e-9cd0-583917265df1
FPDT_Volatile-01368881-c4ad-4b1d-b631-d57a8ec8db6b SmbiosScratchBuffer-4b3082a3-80c6-4d7e-9cd0-583917265df1
GSEHWInfo-8a989680-e651-4c51-a2af-3cdb1a4ab5b0 StdDefaults-4599d26f-1a11-49b8-b91f-858745cff824
HiiDB-1b838190-4625-4ead-abc9-cd5e6af18fe0 Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c
KEK-8be4df61-93ca-11d2-aa0d-00e098032b8c TPMPERBIOSFLAGS-7d3dceee-cbce-4ea7-8709-6e552f1edbde
KEKDefault-8be4df61-93ca-11d2-aa0d-00e098032b8c TpmServFlags-7d3dceee-cbce-4ea7-8709-6e552f1edbde
Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c UnlockIDCopy-eaec226f-c9a3-477a-a826-ddc716cdc0e3
LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c UsbSupport-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
LegacyDevOrder-a56074db-65fe-45f7-bd21-2d2bdd8e9652 VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8c
LoaderEntrySelected-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f WMIAcpiMemAddr-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
LoaderFirmwareInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f WriteOnceStatus-4b3082a3-80c6-4d7e-9cd0-583917265df1
LoaderFirmwareType-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f XhciDID-a7e92950-4ec9-4502-8576-f851308f8c18
LoaderImageIdentifier-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
What installation media are you using? That seems old. If I can recall, you were already told to use a more up-to-date installation media. Iām not sure if part of your problems are caused right now by this.
I made a bootable key with the latest manjaro, it didnāt want to boot.
BUT, I havenāt tried since ā¦
My bluray player is going to get bored of all these reboots, āhey, you install it or not that fucking manjaro!ā
mount: /new_root: wrong fs type; bad option, bad superblock on overlay, missing codepage, or helper program, or other error.
bailling out, you are on your own. Good luck.
sh: can't acces tty; job control turned off
Sameā¦
Well, I put my āhomeā aside, if I do a new installation, and I put my āhomeā back in place, can I find my previous configuration?
And if not, what is the best solution to have something close to my previous config?
Is that what you get trying to boot your usb? How have you made your usb? I recommend Ventoy
sudo dd bs=4M if=/path/to/manjaro.iso of=/dev/sd[drive letter] status=progress oflag=sync
With my live key I get to the ālive grubā? is after i have the error message.
This is a normal user
[manjaro@manjaro ~]$
and this is root:
[manjaro /]#
and especially when you run manjaro-chroot this must be red.
I researched all your code now. Here you are root in the first post:
but after that everything seems to be executed as normal user without chroot. ???
Here an example:
Run this in chroot.