dmraid is not installed for HW RAID+LVM setup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubiquity (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I am currently trying LVM. My motherboard has hardware RAID controller, which combines two harddisks (RAID0 I believe, but that does not really matter)
After circumventing bug 1038522, the installer finished, but when I booted into the freshly installed system, some LVM partitions were not available. The partition on which the OS is installed on my new SSD (which is not part of the RAID array), so that is the reason I guess that the OS was able to partially boot. The missing LVM partitions are stored on the RAID array.
After some Internet searching I noticed that the dmraid package was missing. After installing the missing package (and dependencies) using a Live CD, the mounting problems vanished and the new installation (from which I am writing this report) seems to be working properly.
Earlier (when not using LVM) this was not a problem.
I guess the LVM 'masks' the underlying RAID, so the installer did not notice the RAID configuration (or thinks it is not used).
Resulting the dmraid package not being installed...
I am using the KUbuntu installer as provided on the KUbuntu Live CD 13.10. I do not know whether this is a KUbuntu specific problem, or whether it also occurs with the Ubuntu installer.
| Simon Quigley (tsimonq2) wrote | #1 |
| Changed in ubiquity (Ubuntu): | |
| status: | New → Incomplete |
| Maarten Bezemer (veger) wrote | #2 |
| Changed in ubiquity (Ubuntu): | |
| status: | Incomplete → Invalid |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect https:/
and any other logs that are relevant for this particular issue.