Installer hides the master device for dmraid 10 (1+0) configurations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
parted (Ubuntu) |
In Progress
|
High
|
Phillip Susi |
Bug Description
When using dmraid 0+1, several devices appear in /dev/mapper to describe the strips that form the legs of the mirror, and the mirror itself. The installer only gives the choice of using the two stripes that form the legs, and not the whole mirror. For example, in /dev/mapper:
nvidia_bfcdciea-0 and nvidia_bfcdciea-1 are the stripes, which are then mirrored to create nvidia_bfcdciea. The partitions are then detected on nvidia_bfcdciea as nvidia_
Workarounds
===========
Build a new libparted during the install:
- boot the live cd
- open a terminal and do:
$ sudo apt-get build-dep parted
$ cd /tmp
$ apt-get source parted
edit debian/
look for the line
+ if (_is_dmraid_
(its about 20 lines into the patch)
and change it to be
+ if (1) {
Then run
$ dpkg-buildpackage -rfakeroot -us -uc
and finally
$ sudo dpkg -i ../libparted0de
To test the workaround is in place run
$ sudo parted_devices
This should now show (too many) devices but include the root one (e.g. /dev/mapper/
Run ubiquity and the install will now let you choose the right device.
description: | updated |
Changed in parted (Ubuntu): | |
assignee: | nobody → Phillip Susi (psusi) |
importance: | Medium → High |
status: | Triaged → In Progress |
summary: |
- Installer does not give correct choice of device to install to when - using dmraid 0+1 + Installer hides the master device for dmraid 10 (1+0) configurations |
description: | updated |
This is probably a duplicate of bug #534743. Can you try booting with the nosplash break nodmraid options, then when you hit the busybox prompt, run dmraid -ay then exit. If the system boots up normally at that point then it's that bug and I will mark this as a duplicate.