Bsrgvty

How come people say “Would of”?

Why was M87 targetted for the Event Horizon Telescope instead of Sagittarius A*?

Why do we hear so much about the Trump administration deciding to impose and then remove tariffs?

Why didn't the Event Horizon Telescope team mention Sagittarius A*?

How to deal with fear of taking dependencies

Which Sci-Fi work first showed weapon of galactic-scale mass destruction?

Am I thawing this London Broil safely?

Is this app Icon Browser Safe/Legit?

A poker game description that does not feel gimmicky

What do the Banks children have against barley water?

Why is the maximum length of OpenWrt’s root password 8 characters?

What is the meaning of Triage in Cybersec world?

What is the accessibility of a package's `Private` context variables?

Can you compress metal and what would be the consequences?

Origin of "cooter" meaning "vagina"

Landlord wants to switch my lease to a "Land contract" to "get back at the city"

Is flight data recorder erased after every flight?

How to support a colleague who finds meetings extremely tiring?

Return to UK after being refused entry years previously

Does the shape of a die affect the probability of a number being rolled?

Can one be advised by a professor who is very far away?

"as much details as you can remember"

Are there any other methods to apply to solving simultaneous equations?

Aging parents with no investments

Bios 'no bootable device' after Ubuntu Server 18.04.2 LTS installation

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

Good day, everyone.

I'm desperately asking for help on topic.

Running a PC on Intel Atom 64bit with BIOS, not UEFI.

After what seems a successful installation of Ubuntu Server and reboot with USB stick removed, I keep getting this 'no bootable device' message.

Drive is recognized in BIOS and is 1st in boot order.

Tried installing w and w/t LVM. Full disk usage - need only this OS..

So, somehow during Ubuntu Server installation GPT gets applied as default and cannot be avoided explicitly... Curse it..

I've tried formatting disk via ZAPping GPT with gdisk /dev/sda etc. and applying MBR table with fdisk /dev/sda etc.

As a result I've got an empty unallocated MBR disk shown as of DOS (or smth like that) type in fdisk -l.

This should be correct as my Live USB with Debian IS of the same DOS type and boots without any problems....

BUT...still succeeding Ubuntu Server reinstallation applies that damned GPT on the disk......

Next time I'll try to return MBR, install US without automatic making drive bootable and, I don't know, write GRUB to /boot?

I suppose it's a very poor form of question, so any info will be added on demand as I'm unsure what to provide.

boot server bios

share|improve this question

edited 2 days ago

Denis.Z

asked Apr 3 at 10:51

Denis.ZDenis.Z

11

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  If you partition in advance and use gpt, you have to have a bios_grub partition for BIOS boot or an ESP - efi system partition for UEFI boot. There are some advantages to gpt, but gpt is required for drives over 2TiB and really should only be used with UEFI. You only install grub to MBR of a drive like sda, never to partition like sda1. If gpt, you still install to gpt's protective MBR, but gpt does not have sectors just after MBR, so bios_grub is where it writes core.img. Listing of gpt partitions may show MBR with one gpt partition which is the protective MBR so old tools do not erase it.
  
  – oldfred
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @oldfred, thanks for your assistance, but the more I read, the more I get confused, especially by the GPT part :) I'd tried to install GRUB to /dev/sda on GPT disk after Us installation as you've said via these instructions, as only chroot helped, but still no luck.. And now I blame GPT auto partitioning during install. Tonight I've got an idea to fully install Debian and to examine HDD situation afterwards, because Debian boots just fine....
  
  – Denis.Z
  yesterday
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If doing an install with gpt partitioning you need bios_grub partition or ESP. If command line you need to create partition with parted or gdisk. If drive is blank installer will create the correct partition. And gpt is required for large drives, but optional for smaller ones. But MBR is now 35 years old and has many kluges to keep it working. I consider it better to use gpt and have used it since 2011, but had to always add the bios_grub partition for my old BIOS system, and now an ESP for my new UEFI systems. rodsbooks.com/gdisk
  
  – oldfred
  yesterday
  

  
  
  
  

add a comment | 

0

Good day, everyone.

I'm desperately asking for help on topic.

Running a PC on Intel Atom 64bit with BIOS, not UEFI.

After what seems a successful installation of Ubuntu Server and reboot with USB stick removed, I keep getting this 'no bootable device' message.

Drive is recognized in BIOS and is 1st in boot order.

Tried installing w and w/t LVM. Full disk usage - need only this OS..

So, somehow during Ubuntu Server installation GPT gets applied as default and cannot be avoided explicitly... Curse it..

I've tried formatting disk via ZAPping GPT with gdisk /dev/sda etc. and applying MBR table with fdisk /dev/sda etc.

As a result I've got an empty unallocated MBR disk shown as of DOS (or smth like that) type in fdisk -l.

This should be correct as my Live USB with Debian IS of the same DOS type and boots without any problems....

BUT...still succeeding Ubuntu Server reinstallation applies that damned GPT on the disk......

Next time I'll try to return MBR, install US without automatic making drive bootable and, I don't know, write GRUB to /boot?

I suppose it's a very poor form of question, so any info will be added on demand as I'm unsure what to provide.

boot server bios

share|improve this question

edited 2 days ago

Denis.Z

asked Apr 3 at 10:51

Denis.ZDenis.Z

11

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  If you partition in advance and use gpt, you have to have a bios_grub partition for BIOS boot or an ESP - efi system partition for UEFI boot. There are some advantages to gpt, but gpt is required for drives over 2TiB and really should only be used with UEFI. You only install grub to MBR of a drive like sda, never to partition like sda1. If gpt, you still install to gpt's protective MBR, but gpt does not have sectors just after MBR, so bios_grub is where it writes core.img. Listing of gpt partitions may show MBR with one gpt partition which is the protective MBR so old tools do not erase it.
  
  – oldfred
  2 days ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @oldfred, thanks for your assistance, but the more I read, the more I get confused, especially by the GPT part :) I'd tried to install GRUB to /dev/sda on GPT disk after Us installation as you've said via these instructions, as only chroot helped, but still no luck.. And now I blame GPT auto partitioning during install. Tonight I've got an idea to fully install Debian and to examine HDD situation afterwards, because Debian boots just fine....
  
  – Denis.Z
  yesterday
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  If doing an install with gpt partitioning you need bios_grub partition or ESP. If command line you need to create partition with parted or gdisk. If drive is blank installer will create the correct partition. And gpt is required for large drives, but optional for smaller ones. But MBR is now 35 years old and has many kluges to keep it working. I consider it better to use gpt and have used it since 2011, but had to always add the bios_grub partition for my old BIOS system, and now an ESP for my new UEFI systems. rodsbooks.com/gdisk
  
  – oldfred
  yesterday
  

  
  
  
  

add a comment | 

Good day, everyone.

I'm desperately asking for help on topic.

Running a PC on Intel Atom 64bit with BIOS, not UEFI.

After what seems a successful installation of Ubuntu Server and reboot with USB stick removed, I keep getting this 'no bootable device' message.

Drive is recognized in BIOS and is 1st in boot order.

Tried installing w and w/t LVM. Full disk usage - need only this OS..

So, somehow during Ubuntu Server installation GPT gets applied as default and cannot be avoided explicitly... Curse it..

I've tried formatting disk via ZAPping GPT with gdisk /dev/sda etc. and applying MBR table with fdisk /dev/sda etc.

As a result I've got an empty unallocated MBR disk shown as of DOS (or smth like that) type in fdisk -l.

This should be correct as my Live USB with Debian IS of the same DOS type and boots without any problems....

BUT...still succeeding Ubuntu Server reinstallation applies that damned GPT on the disk......

Next time I'll try to return MBR, install US without automatic making drive bootable and, I don't know, write GRUB to /boot?

I suppose it's a very poor form of question, so any info will be added on demand as I'm unsure what to provide.

boot server bios

share|improve this question

edited 2 days ago

Denis.Z

asked Apr 3 at 10:51

Denis.ZDenis.Z

11

share|improve this question

edited 2 days ago

Denis.Z

asked Apr 3 at 10:51

Denis.ZDenis.Z

11

share|improve this question

edited 2 days ago

Denis.Z

asked Apr 3 at 10:51

Denis.ZDenis.Z

11

asked Apr 3 at 10:51

Denis.ZDenis.Z

11

asked Apr 3 at 10:51

Denis.ZDenis.Z

11