Those instructions would only apply to UEFI. I assume you are in the context of CSM or the classic BIOS behavior which boots from MBR.
But you can confirm that if you want. I would start by making sure you are referencing the correct storage device:
lsblk -d -o NAME,SIZE,MODEL,TRAN
Find the device you have installed StartOS onto, and take note of its “NAME”. Typically it will be either “sda” or “nvme0n1”, but it can vary depending on the configuration of the drives and their technology. BTW, you will probably also see your USB thumb drive in the list (typically “sdc”), so make sure you identify the correct one (note the “SIZE”, “MODEL”, and “TRAN” values to help you properly identify it)
Once you have identified the device where you have installed StartOS to, then run the following command (replace “DEVICE” with your device – typically “sda” or “nvme0n1”):
sudo fdisk -l /dev/DEVICE
You should get an output something like:
Disk /dev/nvme0n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: FOOBAR BAZ 4TB
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: 12345678-90AB-CDEF-1234-567890ABCDEF
Device Start End Sectors Size Type
/dev/nvme0n1p1 34 204833 204800 100M EFI System
/dev/nvme0n1p2 204834 2301985 2097152 1G Linux filesystem
/dev/nvme0n1p3 2301986 33759265 31457280 15G Linux root (x86-64)
/dev/nvme0n1p4 33759266 7814037133 7780277868 3.6T Linux LVM
(the device names may be different). If the “Disklabel type” shows “dos”, then the EFI process mentioned earlier in this thread by BlissHodl is not applicable. If instead it shows “gpt” and first row in the table says it is type “EFI System” like in my example above, then the process is applicable, and you may just need to adjust the paths that you are using.
Thank you!
I have a classic BIOS and created an UBUNTU Live USB-Stick, using MBR to access terminal.
My device is sda (without a number, as in the guide) I’m going to try that.
Disklabel type is gpt and EFI System.
Looks like that partition is empty. Since this is the partition that it would normally boot from, it won’t be able to boot with nothting there. Different problem than the OP (seems like something went wrong with the installation, I guess). Indeed it is odd that you say your installer booted via MBR, but the installation created a gpt disk label and EFI System partition. Unfortunately, I don’t know enough about StartOS to assist further on this one.
Maybe we can check if it is really mounted (or maybe it is mounted somewhere else). After running the “sudo mount /dev/sda1 /mnt” command, see what output you get from:
Weird. I assume it worked before? Do you get the same error after reboot? If so, try re-installing StartOS, then boot up into the Ubuntu USB thumb drive again, and before running any other commands, see what you get with:
Yes it worked before. I reinstalled StartOS and booted into Ubuntu USB-Stick.
With the first 2 commands I got some output. And an error on the 3. command:
You missed the forward slash in front of “/mnt”. But anyway I can see from the first output that in fact /dev/sda1 is not type “EFI System” like you mentioned it was before. It now says “BIOS boot” the way I would expect it to. Maybe StartOS will boot now?
Sorry, I don’t understand what you mean by “finding” the EFI-System entry. In your screenshot there are 4 partitions. “BIOS boot” (8M), “Linux filesystem” (1G), “Linux root (x86-64)” (16G) and “Linux LVM” (1.8T). That looks like a normal legacy BIOS setup, not an UEFI system. In any case, the process outlined by the OP is not applicable in a non-EFI setup.
What do you see with the monitor hooked up when you boot StartOS (without the USB thumb drive)? Of course, that will only be testable if StartOS doesn’t have a problem with the monitor (it does on some systems).
Yeh, not sure. That output looks like a shutdown sequence, not a startup sequence. I don’t see anything useful in there myself (including what might have triggered it to shut down, which would have been earlier in the output presumably).
I see. To be clear, I wasn’t interested in what happens when it shuts down, though, but rather what happens when it starts up (from the hard drive, not from the installer). What do you get if you power down, unplug all of the USB thumb drives (including the installer), hook up the monitor, and then power on the device? What does the monitor show at this point (prior to shutting down again)?
