F5F Stay Refreshed Software Operating Systems Bootloader not found during fresh installation of Pop OS

Bootloader not found during fresh installation of Pop OS

Bootloader not found during fresh installation of Pop OS

M
Machi_Gamz
Member
204
01-13-2023, 05:04 AM
#1
Hi there, I just finished a fresh setup on an older Asus T100TA and finally got Pop OS running after manually setting up the partitions. This was a one-time install after wiping out the old Windows drive. I’m having trouble booting now and think it might be linked to Systemd-boot. I’m trying to follow the instructions online, but the disks listed on the device are named mmcblk1 and there’s no nvme0n1* or sda* shown in the support docs. The disks I see are mmcblk1p1, p2, p3, p4. When starting the EFI boot via systemd-boot, I get an error saying 'unknown filesystem type' and a 'swap' filesystem. I’m not too familiar with Linux, so any advice would be greatly appreciated! pop-os@pop-os:/dev$ sudo parted -ls
M
Machi_Gamz
01-13-2023, 05:04 AM #1

Hi there, I just finished a fresh setup on an older Asus T100TA and finally got Pop OS running after manually setting up the partitions. This was a one-time install after wiping out the old Windows drive. I’m having trouble booting now and think it might be linked to Systemd-boot. I’m trying to follow the instructions online, but the disks listed on the device are named mmcblk1 and there’s no nvme0n1* or sda* shown in the support docs. The disks I see are mmcblk1p1, p2, p3, p4. When starting the EFI boot via systemd-boot, I get an error saying 'unknown filesystem type' and a 'swap' filesystem. I’m not too familiar with Linux, so any advice would be greatly appreciated! pop-os@pop-os:/dev$ sudo parted -ls

M
milk30
Junior Member
15
01-18-2023, 10:32 AM
#2
This setup uses eMMC storage instead of standard NVME or SATA drives. It means your system integrates a flash-based memory, not the typical disk interfaces. Could you clarify what issues you're experiencing? Are you encountering boot errors or unexpected behavior? If you're using a live USB, ensure the directory is empty unless you manually mount the EFI partition afterward. Also, note that /boot/efi is typically mounted automatically during startup. If it fails to find the drive at runtime, a corrupted fstab file might be the cause. Would you like me to help you retrieve the contents of your /etc/fstab file?
M
milk30
01-18-2023, 10:32 AM #2

This setup uses eMMC storage instead of standard NVME or SATA drives. It means your system integrates a flash-based memory, not the typical disk interfaces. Could you clarify what issues you're experiencing? Are you encountering boot errors or unexpected behavior? If you're using a live USB, ensure the directory is empty unless you manually mount the EFI partition afterward. Also, note that /boot/efi is typically mounted automatically during startup. If it fails to find the drive at runtime, a corrupted fstab file might be the cause. Would you like me to help you retrieve the contents of your /etc/fstab file?

C
CaptianTimo
Member
159
01-20-2023, 12:20 AM
#3
Thank you for your response! I’m now familiar with the disk types in use. I’m starting the boot to the Live disk. During the install process, I don’t see any errors—just a hang. Pressing F2 brings me back to the BIOS menu. The boot options list both the Live USB and the POP OS install. I’m quite puzzled about mounting procedures. Should I check the fstab file at the moment of booting or first prepare the partition before mounting? If I mount the boot partition, how do I proceed with navigation afterward? Apologies ahead of time. My fstab entry is: overlay / overlay rw 0 0 tmpfs /tmp tmpfs nosuid,nodev 0 0
C
CaptianTimo
01-20-2023, 12:20 AM #3

Thank you for your response! I’m now familiar with the disk types in use. I’m starting the boot to the Live disk. During the install process, I don’t see any errors—just a hang. Pressing F2 brings me back to the BIOS menu. The boot options list both the Live USB and the POP OS install. I’m quite puzzled about mounting procedures. Should I check the fstab file at the moment of booting or first prepare the partition before mounting? If I mount the boot partition, how do I proceed with navigation afterward? Apologies ahead of time. My fstab entry is: overlay / overlay rw 0 0 tmpfs /tmp tmpfs nosuid,nodev 0 0

S
SynneK
Member
185
01-20-2023, 02:07 AM
#4
S
SynneK
01-20-2023, 02:07 AM #4

X
XJustPizzaX
Member
114
01-23-2023, 06:20 AM
#5
Thank you for walking me through the steps of grg 994. I completed each part without any issues. However, the system still won’t boot. The Linux Boot Manager appears in the BIOS, but there’s no output when starting up, and selecting it brings me back to the BIOS again. It’s frustrating since everything seemed fine earlier.
X
XJustPizzaX
01-23-2023, 06:20 AM #5

Thank you for walking me through the steps of grg 994. I completed each part without any issues. However, the system still won’t boot. The Linux Boot Manager appears in the BIOS, but there’s no output when starting up, and selecting it brings me back to the BIOS again. It’s frustrating since everything seemed fine earlier.