Hello,
I have 3 disks in my PC:
After finished installing eos on third drive, it’s boot menu doesn’t contain entry to boot manjaro, only itself and Windows. os-prober doesn’t see disk no. 3. What could be the problem?
TIA
Are they installed with a mix of UEFI and MBR/Legacy boot? That is one common reason.
Hi dalto,
Thanks for answering. No UEFI, all is MBR.
Could you show the output of commands
lsblk -fm
sudo fdisk -l
Output of lsblk -fm
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS SIZE OWNER GROUP MODE
sda 465.8G root disk brw-rw----
├─sda1 ntfs System Reserved
│ 3E70ACFF70ACBF51 50M root disk brw-rw----
├─sda2 ntfs DACCAF82CCAF5811 465.2G root disk brw-rw----
└─sda3 ntfs 387CA62A7CA5E33C 509M root disk brw-rw----
sdb 465.8G root disk brw-rw----
├─sdb1 8M root disk brw-rw----
└─sdb2 btrfs manjaro-kde-new
b95dbb5a-4238-4278-b36d-4f67a0e5970d 128G root disk brw-rw----
sr0 1024M root optic brw-rw----
nvme0n1
│ 953.9G root disk brw-rw----
├─nvme0n1p1
│ 8M root disk brw-rw----
├─nvme0n1p2
│ swap 1 33641584-96bc-48b6-8784-879ef8787d70 [SWAP] 24G root disk brw-rw----
├─nvme0n1p3
│ ext4 1.0 a9e26cd7-9833-4b29-bdef-c34e8651e205 60G root disk brw-rw----
├─nvme0n1p4
│ ext4 1.0 data c8511f1c-8320-4744-b479-0f6c89d7de0a 60G root disk brw-rw----
├─nvme0n1p5
│ btrfs endeavouros-kde
│ 1f8e097f-556c-48b0-b28d-efad820e7c28 109.9G 7% /var/log 120G root disk brw-rw----
│ /home
│ /var/cache
│ /
└─nvme0n1p6
ext4 1.0 empty 7f0fa63c-6cb1-4261-b97d-31876e510a6a 60G root disk brw-rw----
Output of fdisk -l
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SPCC M.2 PCIe SSD
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: 622A1FA0-226E-654D-81BB-7DDBF1E64CF4
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 18431 16384 8M BIOS boot
/dev/nvme0n1p2 1950076928 2000408575 50331648 24G Linux swap
/dev/nvme0n1p3 251660288 377489407 125829120 60G EFI System
/dev/nvme0n1p4 1824247808 1950076927 125829120 60G Linux filesystem
/dev/nvme0n1p5 18432 251660287 251641856 120G EFI System
/dev/nvme0n1p6 377489408 503318527 125829120 60G EFI System
Partition table entries are not in disk order.
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850
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: 0x18a47f29
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 104447 102400 50M 7 HPFS/NTFS/exFAT
/dev/sda2 104448 975725196 975620749 465.2G 7 HPFS/NTFS/exFAT
/dev/sda3 975726592 976769023 1042432 509M 27 Hidden NTFS WinRE
Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850
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: 802A8A4D-CCC3-475C-9D5A-91182C92A7D4
Device Start End Sectors Size Type
/dev/sdb1 2048 18431 16384 8M BIOS boot
/dev/sdb2 18432 268453887 268435456 128G BIOS boot
Your Manjaro is installed on a BTRFS filesystem.
You would need a patched os-prober to detect the systems installed on BTRFS.
Something like the following package from AUR:
Or build Manjaro’s own and install it on EnOS:
Please note that if you choose the second option, you would need to keep track of the updates yourself.
Another option would be to let Manjaro be in charge of the booting process.
Changing the boot drive order in BIOS is obviously the simplest solution. I was just curious about the problem. Thanks.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.