r/voidlinux • u/jMultiversalGod • 9d ago

Void not wanting to appear.

I set up a install via xfce. I followed the wiki and I'm sure i did everything right, but for some god forsaken reason the void install (samsung ssd) will not appear. It does exist (chroot works and I've installed grub several times through there), but it just doesn't exist. Every time around I set up grub (it was in the installer! i did set up grub to install but that was ignored) efibootmgr let it show and then disapeared when I turn off the system to access it!. I've been at this for so long and it's getting painful.

fdisk output

[anon@void-live ~]$ sudo fdisk -l

Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors

Disk model: Samsung SSD 980 PRO 2TB

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: A09F45C9-DE8C-42A6-B33E-A29905DDE8F6

Device Start End Sectors Size Type

/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System

/dev/nvme0n1p2 1050624 3907028991 3905978368 1.8T Linux filesystem

Disk /dev/loop0: 1.16 GiB, 1243377664 bytes, 2428472 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 5.3 GiB, 5695864832 bytes, 11124736 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 298.09 GiB, 320072933376 bytes, 625142448 sectors

Disk model: WDC WD3200AAJS-0

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: 0F2BC613-6270-4854-886E-C510E44C58CB

Device Start End Sectors Size Type

/dev/sda2 32768 237567 204800 100M EFI System

/dev/sda5 78462976 624421545 545958570 260.3G Linux filesystem

Disk /dev/sdb: 3.66 GiB, 3932160000 bytes, 7680000 sectors

Disk model: Transcend 4GB

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: 0x51b3017a

Device Boot Start End Sectors Size Id Type

/dev/sdb1 * 0 2825759 2825760 1.3G 0 Empty

/dev/sdb2 156 65691 65536 32M ef EFI (FAT-12/16/32)

efibootmgr output

[anon@void-live ~]$ efibootmgr -v

BootCurrent: 0007

Timeout: 0 seconds

BootOrder: 0006,0007

Boot0001* Windows Boot Manager HD(2,GPT,ff007800-a60d-4e66-b9cb-45c31186163c,0x8000,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi0000424f

dp: 04 01 2a 00 02 00 00 00 00 80 00 00 00 00 00 00 00 20 03 00 00 00 00 00 00 78 00 ff 0d a6 66 4e b9 cb 45 c3 11 86 16 3c 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00

data: 00 00 42 4f

Boot0006* Windows Boot Manager HD(2,GPT,ff007800-a60d-4e66-b9cb-45c31186163c,0x8000,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000031000100000010000000040000007fff0400

data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 31 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00

Boot0007* UEFI: JetFlashTranscend 4GB 1100 PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/USB(0,0)/CDROM(1,0x9c,0x2b1d84)0000424f

dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 01 00 / 03 05 06 00 00 00 / 04 02 18 00 01 00 00 00 9c 00 00 00 00 00 00 00 84 1d 2b 00 00 00 00 00 / 7f ff 04 00

data: 00 00 42 4f

[anon@void-live ~]$

Disk /dev/loop0: 1.16 GiB, 1243377664 bytes, 2428472 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 5.3 GiB, 5695864832 bytes, 11124736 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 298.09 GiB, 320072933376 bytes, 625142448 sectors

Disk model: WDC WD3200AAJS-0

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: 0F2BC613-6270-4854-886E-C510E44C58CB

Device Start End Sectors Size Type

/dev/sda2 32768 237567 204800 100M EFI System

/dev/sda5 78462976 624421545 545958570 260.3G Linux filesystem

Disk /dev/sdb: 3.66 GiB, 3932160000 bytes, 7680000 sectors

Disk model: Transcend 4GB

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: 0x51b3017a

Device Boot Start End Sectors Size Id Type

/dev/sdb1 * 0 2825759 2825760 1.3G 0 Empty

/dev/sdb2 156 65691 65536 32M ef EFI (FAT-12/16/32)
Why? (and before you ask, yes I selected local when I did the void-installer).

4 Upvotes

permalink
reddit

You are about to leave Redlib

Do you want to continue?

https://www.reddit.com/r/voidlinux/comments/1vw5fm0/void_not_wanting_to_appear/
No, go back! Yes, take me to Reddit

100% Upvoted

u/Sad-Cod-9584 9d ago

been a while since I used grub, but have you tried grub install with the --removable parameter? Should set it up with standard uefi pathing so that it's recognized by pretty much all efi systems.

2

u/jMultiversalGod 9d ago

yeah tried removable, nothing

2

u/Sad-Cod-9584 9d ago

That is highly unusual. Does the efi boot menu list the disk that void is installed on? With removable, it should list that disk and be able to boot it.

you could try limine instead, it's what I currently use and a tiny testconfig should be easy to set up. just follow the installation guide and make sure to copy BOOTX64.efi to efi/EFI/BOOT/ Oh and be mindful about paths in the limine config file.

1

u/jMultiversalGod 9d ago

[root@void-live /]# grub-install --target=x86_64-efi \

--efi-directory=/boot/efi \

--removable \

--recheck

Installing for x86_64-efi platform.

Installation finished. No error reported.

[root@void-live /]# grub-mkconfig -o /boot/grub/grub.cfg

Generating grub configuration file ...

Warning: os-prober will not be executed to detect other bootable partitions.

Systems on them will not be added to the GRUB boot configuration.

Check GRUB_DISABLE_OS_PROBER documentation entry.

Adding boot menu entry for UEFI Firmware Settings ...

done

command i ran btw,

2

u/Blank-Inspection13 9d ago

in chroot do you also mount the /boot/efi partition ?
Check also with lsblk -f

1

u/jMultiversalGod 8d ago

oooooh no i did not. you're too late tho, already got manjaro

1

u/Blank-Inspection13 8d ago

Maybe next you can try Tumbleweed or Slowroll , but keep in mind - it's never too late to go back into the void

u/jMultiversalGod 9d ago

Ran fastfetch from within. Everything but swap being disabled was normal.

u/jMultiversalGod 9d ago

Reinstalled, efibootmgr let void appear but since i dont get nice things and i cannot use a good distro void dissappeared woo

u/jMultiversalGod 9d ago

yeah this is geniunely such an infuriating issue i've given up and gone to manjaro ): this is sad i love the idea of void and it being locked behind such a problem is awful

u/zlice0 9d ago

some bios'es are fuking stupid and only search for specific efi or require you to manually install/specify efi to boot from.

ive had to do something like these i think from the efi shell. been forever, and you do it once and never touch it again unless you nuke efi.

https://blog.stigok.com/2018/06/04/set-efi-boot-entries-uefi-shell.html

https://superuser.com/questions/1035522/how-to-add-booting-parameters-to-the-kernel-with-bcfg-from-the-efi-shell

1

u/jMultiversalGod 3d ago

its not the bios because manjaro worked like a dream

Void not wanting to appear.

You are about to leave Redlib