grub-pc fails to upgrade with raid disks

Bug #1759877 reported by MarkS
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When performing a regular upgrade an upgrade to grub-pc was scheduled. When this got to configuring it reported "grub-install: error: disk `md0' not found." for all 4 /dev/sdX devices in the system. The 4 drives have a RAID1 array for /boot and a RAID5 LVM device for the rest of the storage, so grub needs to be installed in the boot sector for all four drives.

Running grub-install manually for the drives resutls in -

# grub-install /dev/sda
Installing for i386-pc platform.
grub-install: error: disk `md0' not found.

So, this doesn't fill me with confidence that the server is going to reboot nicely without intervention from a rescue disk.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: grub-pc 2.02~beta2-36ubuntu3.18
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Mar 29 16:06:26 2018
InstallationDate: Installed on 2012-03-20 (2199 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcEnviron:
 TERM=screen
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
SourcePackage: grub2
UpgradeStatus: Upgraded to xenial on 2016-08-08 (597 days ago)

Revision history for this message
MarkS (mark-marksyms) wrote :
Revision history for this message
MarkS (mark-marksyms) wrote :

This is the log from running

grub-install -v /dev/sda

It doesn't really give me any clues but maybe somebody else will spot what's wrong.

Revision history for this message
MarkS (mark-marksyms) wrote :

It turns out that mdadm had been uninstalled some two weeks prior to the most recent upgrade and so grub-install had no user space tools to query the RAID arrays. Reinstating mdadm fixed the problem.

Changed in grub2 (Ubuntu):
status: New → Invalid
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Thanks for letting us know!

This bug was identified automatically as a regression, so I'm adding 'bot-stop-nagging' tag here for the bot to also recognize it's not a regression from the current in-flight stable update.

tags: added: bot-stop-nagging
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.