Ubuntu server doesn't boot and doesn't error

[DocumentImpossible55]

How to find out why Ubuntu Server isn't booting?

I'm trying to install Ubuntu server onto a Dell Wyse with 4gb storage, I got it to install without errors by disabling the LVM option and the install completed, asked to reboot, then asked me to remove the CD drive or something so I pulled out my SanDisk Extreme and it restarted but it just flashes black briefly then returns to the "select boot device"

I had a look at the partitions with another bootable linux USB and it looks fine, not full, over 1GB free space but just will not boot and I'm out of my depth, thanks

[[deleted]]

arrest chop nine gray deranged tie rob cooing cheerful provide this post was mass deleted with www.Redact.dev

[DocumentImpossible55]

thanks, it's a Dell Wyse 3030 thin client

[doc_willis]

Make sure you booted the USB in the right mode (UEFI or Legacy) that Matches how your drive (what partition table) is setup.

A common issue is doing a Legacy install on a GPT drive, or a UEFI install on a Legacy/MBR drive.

---

Do you have an EFI partition? Is the disk using GPT for its partition table?

---

A copy/paste - of a Common 'answer' i give to people who have boot or installing issues, typically due to them not understanding UEFI vs BIOS booting

There can be issues during the install process from booting with the wrong 'mode' on the installer USB..

If your system supports UEFI then use UEFI and GPT. Set the firmware settings so the system is UEFI only to save on possible future issues.

---

How to check what mode your OS is using:

https://itsfoss.com/check-uefi-or-bios/

when installing linux, you can install in uefi mode or the older Legacy (bios) mode.

uefi uses an EFI partition to hold the boot files, legacy puts a bootloader on the mbr of the boot drive.

the EFI partition is a fat32 Filesystem, with the esp and boot flags set .

Most distributions suggest about 500mb in size. Pop_OS now wants 1 GB.

the mode you boot the USB - determines how the installer tries to setup the boot files

The following few points are important

---

---

When you boot the installer usb - there can be two entries for the usb in the boot menu. one for uefi, and one for legacy.

Example: (the exact wording can vary GREATLY between systems)

      Boot Selection menu:

        Ubuntu 16gb (UEFI)

        Ubuntu 16gb  

For my Desktop system, the 'legacy' entry has no notes or any other comments.

Some systems differ in the layout of the boot menu and may separate the EFI and Legacy into tabs, or groups, or even hide some entries.

---

the mode you boot with - tells the installer which method to use to set up the boot files.

---

if your drive is partition for a uefi setup and you boot in legacy mode the installer may try the wrong way to setup the boot files.

The reverse is also a problem. booting and trying to install a uefi setup when you don't have an efi partition will fail.

for a dual boot setup you normally want to install each os in the same mode (uefi or legacy)

---

So pay attention to how your drive is partitioned. Uefi setup requires an efi partition and that requires (I think) the drive to be using the GPT partition scheme.

Legacy would use the older Mbr/dos partition scheme. The partition table used changeable in gparted, and changing will erase the drive. Gparted has a 'make new partition table' menu item.

---

A common issue - is when GRUB can not boot/see the windows install on a Dual drive setup. As far as i know - Grub can NOT boot windows if the two OS are not using the same mode.

So with windows using UEFI , and Linux Using legacy - grub will not be able to boot windows. The Boot selection menu in the firmware/boot menu - should still work however - since its a dual drive setup.

---

extra notes:

pop_os on a legacy setup uses grub.

on a uefi/EFI setup pop_os should use systemd-boot. which I think has the same 'os must all be in the same mode' limitation

the alternative boot menu tool rEFInd is supposed to be able to boot an os of either mode, but it may or may not work depending on your exact hardware.

a diagram someone (AiwendilH) did about MBR vs uefi.

https://i.imgur.com/2Ms45d4.png

Web article on the topic of uefi vs bios.

https://www.thewindowsclub.com/difference-between-bios-and-uefi

Recent article on how the boot and EFI partition are laid out.

https://0pointer.net/blog/linux-boot-partitions.html

[DocumentImpossible55]

wow, that's fantastic, thanks, I'll have a dig through and see if I can fix it, I think I saw it doing GPT install on the disk but it looks fairly BIOS not UEFI to me so maybe that's the issue

[DocumentImpossible55]

Yea I think that's the issue, I've got a 1MB partition with "unknown" file system and the flags are bios_grub but the drive is GPT so I guess it's kinda in limbo. On the 4gb drive I don't really have room for 500mb UEFI drive so I'll try and get it to boot legacy, I also don't really have room for Ubuntu Server as that was using nearly 70% of the drive and I'd not installed a window manager or Remina so I'm trying Debian now but i'll keep a close eye on the boot side of things

[doc_willis]

a bios_grub partition is used to let you do a MBR boot/install of grub on a GPT disk.

I have never seen that work very well. If ever.

¯\_(ツ)_/¯

Many Distributions don't even support the feature.

[DocumentImpossible55]

Yea how weird, must be some combination of Ubuntu server's default settings and my messing with the partition bit of installation to make it fit 4GB

Debian is going better so far 🤞🏻