What do I select for “GRUB install devices” after an update?




Last Updated August 08, 2017 19:02 PM

After running Update Manager, a debconf window (titled "Configuring grub-pc"), popped up, requiring me to select the appropriateGRUB install devices for my system. I've made no changes to grub or the filesystem recently, and I don't remember what options I selected last time I did make a change.

How do I know what to select? I'm assuming the wrong answer could render my system unable to boot.

Here's the debconf dialog:

Here's the window and text that is displayed when selecting "help" :

Answers 2

In your case, the correct selection is /dev/sda, the first one. It's the first and only hard disk in your system, whereas /dev/sda1 is a partition on that hard disk. You can install grub on a partition, but it's a "BAD idea".

If you had multiple hard drives and partitions, first find out where your root partition is:


(See also:...

0 0
The /dev/sda, /dev/sdb, etc are the disks, in order how BIOS detects them on the board they get named a, b, c, etc.

If it has a number after the letter, then it's a partition on that disk. So, sda5 for example is partition #5 on the first disk.

The grub2 bootloader usually goes to the MBR of the disk, not to a partition. And it would usually be the first disk, sda, but this can vary with multiple disks and depending how your system is set up.

So, you can try /dev/sda first. Note that in a textual menu the selection is usually done with Space, not Enter. You hit Space so that a * mark appears to mark it as selected, and then you hit Enter to continue. Otherwise if you only hit Enter it can continue with nothing...

0 0

Thanks for the responses. I was updating the system after GalliumOS notified me there were updates to install, one of which was grub. And, I was posting with my MacBook because I didn't realize that the update didn't completely subsume my system (like Windows or Mac).

I'm not sure if it's EFI or MBR. I know the only way to install Linux on a Chromebook with a Braswell processor is to use a script by Mr. Chromebox to Install/Update the RW_LEGACY Firmware. There is only a 16 gb eMMC hard drive and the only linux distro that will give me sound and a working keyboard and touchpad is GalliumOS.

The output of fdisk -l is:

Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size...

0 0

I see with the latest dist-upgrade there is a new Grub. Which is ok but this time it was a bit different so I followed the prompts to do a No. I then asked for Grub Install Devices. I have three options 1) /dev/sda (599932)MB; Logical Volume; 2) - /dev/sda (535 MB: /dev/sda1) and 3) /dev/dm-o (103079 MB; pve-root)

I checked on my other server that has not been upgraded yet and check in /boot/grub/grub.cfg to get a hint as they they are the same servers and running Proxmox 3.3.

I am inclined to check /dev/sda Logical Volume) but really don't want to botch a production server.

Normally grub picks up on an upgrade where it was originally loaded?

Here is original Config

Filesystem 1K-blocks Used Available Use% Mounted on
udev 10240 0 10240 0% /dev
tmpfs 3293060 380 3292680 1% /run
/dev/mapper/pve-root 99083868 3400168 90650536 4% /
tmpfs 5120 0 5120 0%...

0 0

How to select GRUB install device

By Wyldeplayground | December 30, 2011 | Category Uncategorized

By David Vogel

I apologize in advance for asking a question I suspect is very, very simple. I just got a dedicated server running Ubuntu and I’m using SSH to access it. I ran sudo apt-get dist-upgrade and got the following error message: “The Grub boot loader was previously installed to a disk that is no longer present or whose normally unique indentifier was changed for some reason. It is important to make sure that the installed grub stays in sync with other components such as the grub-cfg or with newer linux images it will have to load, and so you should check again, to make sure that GRUB is installed to the appropriate boot devices.”

The forum won’t let me post an image since I’m a new user, but I uploaded a screenshot of what I’m seeing here: http://www.livingtheanswer.org/misc/grub.jpg

After a bit of research, I know I need to install to...

0 0

This page details the procedures for installing and reinstalling GRUB 2. The information applies to most versions of GRUB 2, but is specifically written for version 1.99. GRUB 1.99 is included on Ubuntu releases 11.04 (Natty Narwhal) and later. For more information on a variety of GRUB 2 topics, please visit the GRUB2 main page. For information on converting to or from GRUB Legacy, please view the Grub2/Upgrading community doc.

The GRUB 2 bootloader is included on all currently-supported versions of the Ubuntu family. GRUB 2 can accomodate traditional computer firmware such as BIOS as well as the newer EFI/UEFI standards. It is compatible with MBR, GPT and other partitioning tables.

All references to GRUB pertain to GRUB 2. Where GRUB 0.97 is discussed, it will be referred to by version number or as GRUB Legacy.

GRUB 2 installation is automatically incorporated into a normal Ubuntu installation. Input required by the user for the initial setup is very...

0 0

I have a box with Ubuntu 12.04, and just did a apt-get upgrade. I'm presented with a dialogue to update my GRUB bootloader, but with the following message:

The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason. It is important to make sure that the installed GRUB core image stays in sync with GRUB modules and grub.cfg. Please check again to make sure that GRUB is written to the appropriate boot devices. If you're unsure which drive is designated as boot drive by your BIOS, it is often a good idea to install GRUB to all of them. Note: it is possible to install GRUB to partition boot records as well, and some appropriate partitions are offered here. However, this forces GRUB to use the blocklist mechanism, which makes it less reliable, and therefore is not recommended. GRUB install devices: [ ] /dev/sda (3000592 MB; ST3000DM001-9YN166) [ ] /dev/sdb (3000592 MB; ST3000DM001-9YN166) [ ] /dev/md1...
0 0
0 0

I recently installed a lot of updates for Ubuntu 10.10, since 11.04 didn't work on my system (Lenovo x201).

Today after the update, grub still exists and lists all OS on boot-up. Starting Windows 7 is no problem but starting Ubuntu just does not work. When starting Ubuntu the system comes to the loading screen, but it shows no HDD activity (no HDD-activity light). It just stays that way.

I really need to get the system running ASAP.

I already tried this HowTo but it didnt worked.

fdisk -l

Disk identifier: 0x8bd47c21 Device Boot Start End Blocks Id System /dev/sda1 1 21624 173688832 7 HPFS/NTFS Partition 1 does not end on cylinder boundary. /dev/sda2 * 30739 38914 65659904 7 HPFS/NTFS Partition 2 does not end on cylinder boundary. /dev/sda3 21624 30739 73219073 5 Extended /dev/sda5 21624 30134 68358144 83 Linux /dev/sda6 30134 30739 4859904 82 Linux swap / Solaris Partition table entries...
0 0

It’s holiday season and so I got a hold of playing some games longly missed on Windows. Booting Windows 10 certainly unveiled several pending updates (Antivirus, Geforce, Windows updates). Since Windows 10 does not explicitly tell about big updates anymore I just did let it reboot several times, waiting for manual grub selection then.

Though this time the update essentially broke GRUB. “error: unknown filesystem. Entering rescue mode…” is certainly not what I expect from a Windows 10 update. After googling a bit I found this thread including an explanation as well as a solution for the problem: The Windows 10 update adds yet another hidden partition, but essentially rewrites the partition table which then breaks GRUB finding the correct /boot partition containing grub2/. Congrats Microsoft!

So, Windows 10 “Upgrade to Windows 10 Home, version 1511, 10586” breaks grub2 because boot block grub2 still thinks it should boot grub2 from (hd0,msdos2) when it now needs to boot...

0 0

As is known, after the installation/reinstallation of


on the computer where it was previously installed

Linux system

, or multiple systems, selfish Windows


"erases" the

GRUB boot loader

, and when the computer will only boot Windows, without being able to boot the OS/Linux system.

In the network there are many statements on the subject restore GRUB after installing Windows, but personally I have a method that works.

Necessary conditions:

Mandatory connection to the Internet.
The image of Linux Mint/Ubuntu, which is installed on the computer, recorded on a disk or flash drive.

1. Inserted into the computer's disk or flash drive with the distribution, restart, and a bootable Linux system in Live mode.

During installation of any program in the Live mode, the terminal will not be prompted for a password, but the program will be installed!

Installation latest version into Linux Mint:

0 0

Grub 2, the Ubuntu and Linux Mint’s default bootloader typically gets overridden when you install Windows as a dual-boot OS. To make Ubuntu and its derivatives boot again, you need to reinstall (repair/restore) Grub using a bootable Ubuntu/LinuxMint CD or USB.

Typically you’ll get the following error boot screen:

error: no such partition. grub rescue> _

Tutorial Objectives:

Reinstall Grub 2 when Ubuntu or Linux Mint won’t boot Enjoy!

To get started, insert your Ubuntu USB into computer and boot up. When you’re in, follow the steps below to reinstall grub 2:

1. Open Gparted Partition Editor from Unity Dash to check out which partition your Ubuntu/Linux Mint system installed. It is usually a EXT4 Partition.

In my case, there’re 3 Ext4 partitions. We can check the user names on each partition after step 2 by command cd /mnt/ && ls home/

gparted partition editor

2. Press Ctrl+Alt+T on keyboard to open terminal. When it opens, run...

0 0