invalid udev rules shipped in mdadm-udeb
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Bionic |
Fix Released
|
Critical
|
Unassigned | ||
Cosmic |
Fix Released
|
Critical
|
Unassigned |
Bug Description
[Impact]
* Upon installation, RAID devices are not automatically assembled by default as they used to be. Instead of being presented with an assembled RAID array for installation, one is presented with individual disks which probably is not desired by the user, as most of the time RAID arrays are intentional.
[Test Case]
* Create a VM with e.g. two disks assembled in a Linux RAID1 using mdadm and not otherwise partitioned / empty.
* Start the d-i based installer
* In the partitioning screen one should be presented with a raid device to partition, not individual disks.
[Regression Potential]
* This is a regression in the bionic release versus Xenial behaviour
* The udev rules as installed into the udeb package were not processed to substitute template variables for BINDIR location of the mdadm tools. Now the packaging was corrected to install identical udev rules into the deb and udeb package types.
[Other Info]
* Original bug report:
It is not possible to install Ubuntu on RAID device with IMSM/DDF metadata. The installer asks if such arrays should be activated but fails to do it.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: mdadm 4.0-1
ProcVersionSign
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jul 19 09:46:44 2017
InstallationDate: Installed on 2017-07-06 (12 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170702)
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MDadmExamine.
MDadmExamine.
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=
ProcMDstat:
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>
SourcePackage: mdadm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekG
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'
Changed in mdadm (Ubuntu Cosmic): | |
importance: | Undecided → Critical |
Changed in mdadm (Ubuntu Bionic): | |
importance: | Undecided → Critical |
status: | New → Confirmed |
summary: |
- Cannot install Ubuntu on IMSM/DDF RAID device + invalid udev rules shipped in mdadm-udeb |
description: | updated |
Changed in mdadm (Ubuntu Bionic): | |
status: | Confirmed → In Progress |
The problem is in the udev rules in the installer:
/lib/udev/ rules.d/ 63-md-raid- array.rules rules.d/ 64-md-raid- assembly. rules
/lib/udev/
There is a wrong path to mdadm which contains "BINDIR" instead of "/sbin". The same rule files in the installed system are fine.
There is a workaround to the problem:
1. Wait for installer "Configure network" screen.
2. Switch to other console.
sed -i 's/BINDIR/\/sbin/g' /lib/udev/ rules.d/ *-md-*
udevadm control --reload
3. Continue the installation.