grub-install doesn't include raid5rec.mod

Bug #1472384 reported by Lee Trager
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

I just did a fresh install of Ubuntu 14.04.2 using the official install medium onto my NAS. My NAS contains three drives which I run in a RAID5 configuration with LVM on top. I setup each drive to have a 128MB EFI partition which stores grubx64.efi and put the rest of the drive under the RAID5+LVM configuration. The Ubuntu 14.04.2 and 15.04 installs were happy to let me do that however when I try to boot into the freshly installed system the GRUB command prompt came up.

While I was able to see the LVM partitions using ls I couldn't access them because I needed raid5rec.mod. I booted into a live CD and used grub-mkimage to create a grubx64.efi image which had raid5rec.mod, and all the other modules I needed to boot, embedded into grubx64.efi.

Possible resolutions
1. Store all grub modules on the EFI partition
2. Modify grub-install to create grubx64.efi with all block/file system modules embedded into the image needed to access the partition which contains the grub modules
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.16.0-43-generic.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Card1.Amixer.info: Error: [Errno 2] No such file or directory
Card1.Amixer.values: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/NAS-SWAP
InstallationDate: Installed on 2015-07-07 (0 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.

 lxcbr0 no wireless extensions.
MachineType: ASUS All Series
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-43-generic.efi.signed root=/dev/mapper/NAS-ROOT ro nomdmonddf nomdmonisw
ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-43-generic N/A
 linux-backports-modules-3.16.0-43-generic N/A
 linux-firmware 1.127.12
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 3.16.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 05/14/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: AM1M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1M-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1472384

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Lee Trager (ltrager) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Lee Trager (ltrager) wrote : BootDmesg.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : Lspci.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : Lsusb.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : PciMultimedia.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : ProcModules.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : UdevDb.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : UdevLog.txt

apport information

Revision history for this message
Lee Trager (ltrager) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this only happen with 14.04.2 ? Can you see if this also happens with the daily Wily image?

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key
Revision history for this message
Lee Trager (ltrager) wrote :

With the latest Wily image I still get the same error.

Revision history for this message
Lee Trager (ltrager) wrote :

I've fixed the issue with the branch linked to above.

Revision history for this message
Lee Trager (ltrager) wrote :

Debian has accepted the patch and its included with 2.02~beta2-33

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.