Rokinys
Posts: 12
Joined: Thu Aug 30, 2018 6:10 am

Can't find or boot to Solus after installation

Wed Dec 05, 2018 10:10 pm

I booted via the USB stick and managed to install Solus along side Windows 10 with the installation process (allocated some space for Solus). After rebooting my laptop, it straight away booted to Windows. After checking the boot options, I cant seem to find anything to boot to Solus. Can someone give step-by-step guide how to make the dual boot option and actually boot to Solus?

donblanco
Posts: 13
Joined: Mon Dec 03, 2018 8:14 pm

Re: Can't find or boot to Solus after installation

Thu Dec 06, 2018 3:52 am

I am having the exact same issue. Lots of details here: https://www.reddit.com/r/SolusProject/c ... _to_win10/

gohlip
Posts: 36
Joined: Sun Jul 15, 2018 5:47 pm

Re: Can't find or boot to Solus after installation

Thu Dec 06, 2018 6:03 am

First, details.
1. Is windows in uefi or bios-legacy?
2. Is/are disk in gpt or msdos?
3. Is Solus installation in uefi or bios-legacy?
4. If uefi, is $esp specified in installation as /boot in fat32 format?
And did you format this $esp during installation? (Do not format!)
Is this $esp more than 350 MB?
Are you using the same $esp as windows?
5. If bios-legacy, did you specify 'setting grub' (mbr) to primary disk?

Boot up livecd, at terminal provide (print) output of
a. sudo parted -l
b. sudo blkid
c. sudo efibootmgr -v
(you may have to install package 'efibootmgr' first)

At livecd, go to file manager and go to installed OS partition and print out contents of its /etc/fstab


To @solus_developers,
o suggest efibootmgr package be included in uefi installation.
o suggest systemd-boot (bootctl package) be automatically installed in uefi installation
as like grub is installed in bios-legacy installation
bootctl is in all systemd uefi but not installed in solus
That would ensure there is a 'solus' entry in efibootmgr
Thanks.

ps: I'm okay with solus using systemd-boot, but if there's too much hassles, (uefi) grub is very easy for users especially with dual-booting with other linux OS's.
I understand clr-manager is meant to make things easier, but for users not doing exactly per the installation wiki, it is much of a hassle.
Furthermore, (if dual-booting) asking users to go to boot set-up (F8~F12) to boot OS's is not exactly 'user-friendly'.

donblanco
Posts: 13
Joined: Mon Dec 03, 2018 8:14 pm

Re: Can't find or boot to Solus after installation

Thu Dec 06, 2018 1:06 pm

gohlip wrote:
Thu Dec 06, 2018 6:03 am
First, details.
1. Is windows in uefi or bios-legacy?
2. Is/are disk in gpt or msdos?
3. Is Solus installation in uefi or bios-legacy?
4. If uefi, is $esp specified in installation as /boot in fat32 format?
And did you format this $esp during installation? (Do not format!)
Is this $esp more than 350 MB?
Are you using the same $esp as windows?
5. If bios-legacy, did you specify 'setting grub' (mbr) to primary disk?
1 uefi
2 gpt
3 Good question. It never showed up in uefi
4 The installer gives no options for this - in uefi it forces install of bootloader - how or where it actually does it is a mystery
- the EFI partition was 260mb i think
- it was not formatted during install - existing Windows boot info remained intact - Solus boot info was never added

I've since just wiped the drive and installed Solus, giving up on dual-boot for now.

Rokinys
Posts: 12
Joined: Thu Aug 30, 2018 6:10 am

Re: Can't find or boot to Solus after installation

Thu Dec 06, 2018 6:55 pm

A. sudo parted -l :

Model: ATA SAMSUNG MZYTY256 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 473MB 472MB ntfs Basic data partition hidden, diag
2 473MB 578MB 105MB fat32 EFI system partition boot, esp
3 578MB 595MB 16.8MB Microsoft reserved partition msftres
4 595MB 215GB 215GB ntfs Basic data partition msftdata
6 215GB 217GB 2000MB linux-swap(v1)
7 217GB 255GB 38.0GB ext4
5 255GB 256GB 868MB ntfs hidden, diag

Model: Kingston DataTraveler GE9 (scsi)
Disk /dev/sdb: 7862MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
2 69.6kB 42.0MB 41.9MB primary esp

B. sudo blkid:

/dev/sdb1: UUID="2018-09-20-12-35-59-00" LABEL="SolusLiveBudgie" TYPE="iso9660" PTUUID="0aa33ddf" PTTYPE="dos" PARTUUID="0aa33ddf-01"
/dev/loop0: TYPE="squashfs"
/dev/loop1: UUID="05010816-082a-41ce-af7a-4939890d7c38" TYPE="ext4"
/dev/loop2: UUID="05010816-082a-41ce-af7a-4939890d7c38" TYPE="ext4"
/dev/sda1: UUID="0094048694048100" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="aeb8c02d-5a56-45cd-8451-f760e231de9c"
/dev/sda2: UUID="B45F-F500" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="df439bb4-83a5-4de3-8315-b77fc603e5f7"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="2678366d-0a8c-4884-9f27-3672605f670e"
/dev/sda4: UUID="BAB06225B061E7F9" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="f5af9d12-a7fb-4276-800a-6d43a48bb66c"
/dev/sda5: UUID="8E522C89522C785B" TYPE="ntfs" PARTUUID="ed8177e7-1644-45dc-8671-6c72082b11c0"
/dev/sda6: UUID="61e93267-ae25-4a09-b873-c9bef85353c3" TYPE="swap" PARTUUID="db351bed-94d3-489f-a7a9-c001053833d5"
/dev/sda7: UUID="8be28588-0381-4489-9bc7-d45f4ce3b6bc" TYPE="ext4" PARTUUID="a47c08ca-2fb5-45b7-8b48-caa11060ed2d"
/dev/sdb2: SEC_TYPE="msdos" LABEL="SOLUSESP" UUID="42E7-E769" TYPE="vfat" PARTUUID="0aa33ddf-02"
/dev/mapper/live-base: UUID="05010816-082a-41ce-af7a-4939890d7c38" TYPE="ext4"

C. sudo efibootmgr -v:

BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0003,0005,2001,2003,2002
Boot0000* EFI USB Device (KingstonDataTraveler GE9) PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,MBR,0xaa33ddf,0x88,0x14000)RC
Boot0001* EFI Network 0 for IPv4 (FC-45-96-8E-54-3F) PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(fc45968e543f,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
Boot0002* EFI Network 0 for IPv6 (FC-45-96-8E-54-3F) PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(fc45968e543f,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0003* Windows Boot Manager HD(2,GPT,df439bb4-83a5-4de3-8315-b77fc603e5f7,0xe1800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0004* Lenovo Recovery System HD(7,GPT,a8aa9de8-401d-4bcc-bb4a-d186e1603021,0x1daff000,0x1f4000)/File(\EFI\Microsoft\Boot\LrsBootMgr.efi)RC
Boot0005* ubuntu HD(2,GPT,df439bb4-83a5-4de3-8315-b77fc603e5f7,0xe1800,0x32000)/File(\EFI\ubuntu\shimx64.efi)
Boot000A* Lenovo Recovery System HD(6,GPT,a8aa9de8-401d-4bcc-bb4a-d186e1603021,0x1daff000,0x1f4000)/File(\EFI\Microsoft\Boot\LrsBootMgr.efi)RC
Boot000B* EFI Network 0 for IPv4 (FC-45-96-8E-54-3F) PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(fc45968e543f,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
Boot000C* EFI Network 0 for IPv6 (FC-45-96-8E-54-3F) PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(fc45968e543f,0)/IPv6([::]:<->[::]:,0,0)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC


Content of fstab:

# /etc/fstab: static file system information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>

# /dev/ROOT / ext3 noatime 0 1
# /dev/SWAP none swap sw 0 0
# /dev/fd0 /mnt/floppy auto noauto 0 0
none /proc proc nosuid,noexec 0 0
none /dev/shm tmpfs defaults 0 0
# /dev/sda7 at time of installation
UUID=8be28588-0381-4489-9bc7-d45f4ce3b6bc / ext4 rw,relatime,errors=remount-ro 0 1

gohlip
Posts: 36
Joined: Sun Jul 15, 2018 5:47 pm

Re: Can't find or boot to Solus after installation

Fri Dec 07, 2018 9:21 am

Rokinys, you have given fstab of livecd. We need fstab of installed Solus in sda7.
Then we can provide further commands for you to boot.
We need this to proceed. Also confirm you do not have Ubuntu anymore.
We may need this (ubuntu) efibootentry to boot Solus.
Solus does not generate a efibootentry.

Rokinys
Posts: 12
Joined: Thu Aug 30, 2018 6:10 am

Re: Can't find or boot to Solus after installation

Fri Dec 07, 2018 3:51 pm

gohlip wrote:
Fri Dec 07, 2018 9:21 am
Rokinys, you have given fstab of livecd. We need fstab of installed Solus in sda7.
Then we can provide further commands for you to boot.
We need this to proceed. Also confirm you do not have Ubuntu anymore.
We may need this (ubuntu) efibootentry to boot Solus.
Solus does not generate a efibootentry.

This is what it says when going to sda7:

# /etc/fstab: static file system information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>

# /dev/ROOT / ext3 noatime 0 1
# /dev/SWAP none swap sw 0 0
# /dev/fd0 /mnt/floppy auto noauto 0 0
none /proc proc nosuid,noexec 0 0
none /dev/shm tmpfs defaults 0 0
# /dev/sda7 at time of installation
UUID=8be28588-0381-4489-9bc7-d45f4ce3b6bc / ext4 rw,relatime,errors=remount-ro 0 1

also, no ubuntu. I had elementary os prior.

gohlip
Posts: 36
Joined: Sun Jul 15, 2018 5:47 pm

Re: Can't find or boot to Solus after installation

Fri Dec 07, 2018 6:42 pm

Right, you did not set $esp as boot. You need to add this into the fstab of sda7
1. Add this into fstab
UUID= B45F-F500 /boot vfat defaults,noatime 0 2
2. Then at livecd, install 'efibootmgr' package.
3. At livecd terminal.
sudo bootctl install --path=/dev/sda2
sudo efibootmgr -c -d /dev/sda -p 2 -L "solus" -l "/EFI/systemd/systemd-bootx64.efi"
4. sudo mount /dev/sda7 /mnt
sudo mount /dev/sda2 /mnt/boot
sudo cp /mnt/boot/EFI/systemd/systemd-bootx64.efi /mnt/boot/efi/ubuntu/shimx64.efi
5. at terminal,
sudo efibootmgr
Copy down what is solus entry number, say it is 000x
Then
sudo efibootmgr -o 000x,0005,0003

Good luck.

Rokinys
Posts: 12
Joined: Thu Aug 30, 2018 6:10 am

Re: Can't find or boot to Solus after installation

Fri Dec 07, 2018 7:05 pm

gohlip wrote:
Fri Dec 07, 2018 6:42 pm
Right, you did not set $esp as boot. You need to add this into the fstab of sda7
1. Add this into fstab
UUID= B45F-F500 /boot vfat defaults,noatime 0 2
2. Then at livecd, install 'efibootmgr' package.
3. At livecd terminal.
sudo bootctl install --path=/dev/sda2
sudo efibootmgr -c -d /dev/sda -p 2 -L "solus" -l "/EFI/systemd/systemd-bootx64.efi"
4. sudo mount /dev/sda7 /mnt
sudo mount /dev/sda2 /mnt/boot
sudo cp /mnt/boot/EFI/systemd/systemd-bootx64.efi /mnt/boot/efi/ubuntu/shimx64.efi
5. at terminal,
sudo efibootmgr
Copy down what is solus entry number, say it is 000x
Then
sudo efibootmgr -o 000x,0005,0003

Good luck.
It say when trying to add the line: Could not save the file “/run/media/live/8be28588…c7-d45f4ce3b6bc/etc/fstab”. You do not have the permissions necessary to save the file. Please check that you typed the location correctly and try again. And should it look like this?:


# /etc/fstab: static file system information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>

# /dev/ROOT / ext3 noatime 0 1
# /dev/SWAP none swap sw 0 0
# /dev/fd0 /mnt/floppy auto noauto 0 0
none /proc proc nosuid,noexec 0 0
none /dev/shm tmpfs defaults 0 0
# /dev/sda7 at time of installation
UUID=8be28588-0381-4489-9bc7-d45f4ce3b6bc / ext4 rw,relatime,errors=remount-ro 0 1
UUID= B45F-F500 /boot vfat defaults,noatime 0 2


Return to “Installation”