Install mdadm into target if installing on a RAID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
As part of the ongoing discussion about dropping alternates [1] I wanted to find out whether it's currently possible at all to install on a RAID with Ubiquity. Turns out it is possible [2], but there are two post-installation steps which are not obvious and should be fixed.
Creating partitions with gparted and building a RAID with mdadm on the live system works well. Ubiquity detects the devices and you can partition /dev/md0 and install on it just fine. The trouble starts because you need to install mdadm into the target system, for which I ran the following steps:
* mount /dev/md0p1 /target, chroot /target
* apt-get install mdadm; that fails because /etc/resolv.conf is empty (yay resolvconf), so exit chroot, apt-get download mdadm, copy to /target/tmp, chroot again, dpkg -i
* that fails because it cannot access /dev etc, so back out of the chroot, bind-mount /dev/, back into the chroot, dpkg --configure -a, get scared by the warnings about not being able to load MD suppport (turns out they are harmless)
It would be nice if Ubiquity could install mdadm into the target system together with its other setup if any of the target partitions is /dev/md*.
[1] https:/
[2] https:/
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity (not installed)
ProcVersionSign
Uname: Linux 3.5.0-12-generic x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 29 07:13:52 2012
EcryptfsInUse: Yes
InstallCmdLine: noprompt cdrom-detect/
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in ubiquity (Ubuntu): | |
importance: | Undecided → High |
For the record, the second issue is bug 1043096.