/sda1 file system "not known" after Ubuntu installation from stick

oschu · 08-07-2022, 07:07 AM

Cannot boot - "no bootable device"
After almost 40 years of Windows I'am stuck with first Ubuntu installation. Don't find a log file on the stick.
Personal log in German see annexed txt file, disk partitioons see jpg.
Is the bios_grub marked partition the same as MBR in Windows? How can I fix this?
Obviously thankful for help...
Oschu

fatmac · 08-07-2022, 09:20 AM

/dev/sda1 is bios_boot, a 1MB partition needed by grub - /dev/sda1 is the FAT partition needed by GRUB for its boot loader files, this should be marked as boot &, (I think, CSP, or something like that) - /dev/sda3 is your actual installation of Linux. Check that the flags have been set correctly.

Translation :=

Quote:

Download Ubuntu 22.04 LTS ISO file from Heise Download
Download UnetBootIn from Heise Download
14 GB stick formatted FAT32, made bootable with UnetBootIn and loaded with Ubuntu
Stick plugged into Acer Aspire 7720, restart
Start from USB CDROM: does not work
Start from USB HDD: works
I choose "Normal installation" and "Use LVM"
Installation seems to start. After a short time, a pattern appears across the entire screen, the stick is addressed again and again and you then hear the disk as if a very long installation process is running in the background
I leave the machine several
Running for hours, still the same - termination of the exercise
Try again, but select "minimal installation" and without LVM
Installation starts, the whole installation process is easy to follow on the screen
After installation: restart IDE0, result:
Broadcom UNDI PXE-2.1 v9.4.5
PXE-E61: Media Test Failure, check cable
PXE-M0F: Exiting Broadcom PXE ROM
No bootable device -- insert boot disk and press any key

Older Gparted (from CD) shows the attached picture. What to do to solve the problem on /sda1?

Looking at the last few lines. it looks like your computer is trying to boot over the internet, it's looking for a server with the PXE boot files.

I'm thinking you may have downloaded the wrong .iso, you want ubuntu-22.04-desktop-amd64.iso

yancek · 08-07-2022, 06:56 PM

sda1 is actually a bios_boot unformatted partition which is used to do a Legacy/CSM install on a GPT drive. It contains the Grub core.img file as boot files have become too large to fit in an MBR. If you do an EFI install (you have an EFI partition sda2) and you don't need sda1.

If you boot in UEFI mode in the BIOS firmware, Ubuntu will install in UEFI mode and create the EFI partition for its EFI boot files on that partition. Windows on an EFI install does the same creating a microsoft diretory there while Ubuntu creates an ubuntu directory so they do not overwrite each other.

Quote:

Is the bios_grub marked partition the same as MBR in Windows?

No,it isn't and the MBR was used by different operating systems on older computers. Most computers in the last decade use UEFI, windows started with windows 8.

Boot the Ubuntu installer and mount sda2, the EFI partition. You should see an ubuntu directory with several files.
Check your BIOS firmware and turn off Legacy/CSM and make sure UEFI is enabled. It usually is by default.
If you are not able to resolve this problem, go to the site below and download and run boot repair per the instructions on the site. Use the 2nd option described on the page. Do NOT try to make any repairs but select the option to Create BootInfo Summary and post the link here.

https://help.ubuntu.com/community/Boot-Repair

oschu · 08-09-2022, 11:20 AM

Many thanks! Info was fast and precise. Situation now:

If started via installation stick I can get into Ubuntu - seems to be installed nicely. The start is the only sticking point. And:

EFI mode is not supported by this BIOS.

Disk Repair says: change to EFI (see foto of end of report. I cannot add the report file because the DiskRepair stick is not visible in my Windows10 at this point in time).

Options:
- change BIOS (no real chance of success) [or use another machine]
- has anybody ever figured out a workaround for this? I guess I should not be the only guy who had this problem...
- fall back to earlier Ubuntu version that supports MBR (which one? needed in this specific case: file management, Firefox, LibreOffice)

The workaround option would be most attractive.

I'm looking forward to your advice. Many thanks in advance!
Oschu

yancek · 08-09-2022, 06:11 PM

Your drive must be GPT. Use the Ubuntu USB and open a terminal and run the command below which will show whether it is.

Quote:

sudo parted -l

Lower Case Letter L in the command

You have a bios_boot as well as an EFI partition so that would indicate at least 2 installs. Ubuntu won't usually create an EFI partition if your computer is not EFI capable. How old is this computer? Do you see any reference to EFI or UEFI in the BIOS?

Quote:

If started via installation stick I can get into Ubuntu - seems to be installed nicely.

If you are booting from the USB you are in the 'live' system and not an installed OS.

Quote:

the Disk Repair stick is not visible in my Windows10 at this point in time).

You don't need windows, boot the Ubuntu USB stick and use the 2nd option on the boot repair page I suggested previusly. If you can connect to the internet from the USB it will be a better option.

Quote:

fall back to earlier Ubuntu version that supports MBR

Ubuntu does support MBR (Legacy installs) on the current version, that's not the problem. You can do a Legacy install on a gpt drive in Linux, you can't in windows which may be what is confusing you. And why can't you change the BIOS settings? You should try enabling Legacy/CSM and boot in Legacy mode to see if that works. You would have had to accept the default settings for the bootloader during one of your installs.

You forgot to post the contents of the EFI partition. Do you have an ubuntu directory there?