mdadm fails to load arrays after fresh 10.04.1 alternate installation on certain mainboards due to lvm containers beeing to big.

Bug #662691 reported by soppal
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After a fresh installation of ubuntu 10.04.1 alternate on following machine:
System:
- gigabyte ga-x58a, ud3r, x58
- intel core i7-930
- 2x ocz platinum low-voltage dimm kit 4gb pc3-10667u
- 2x 500 gb sata2 wd5002abys
- asus engt240, 1024 ddr3

Configuration
2x 500G discs containg two raid1 arrays:
md0: sda1 and sdb1 both 1GB
md1: encrypted LVM container that takes the rest of the available space hosting:
  - 4GB swap
  - 50GB /
  - the rest /mnt/data

Problem:
- ubuntu 10.04.1 alternate installer makes lvm container that is to big to be enabled after booting.

My Usecase:
- The Installation works out fine and everything seems to be in order, after booting the first time and entering the encryption passphrase ubuntu complains about not beeing able to enable the lvm volume /mnt/data that takes the rest of the containers size. by checking the error messages and numbers i found out that the blocks available to the lvm volume /mnt/data are more than there are available. I had this problem so far only with the above mentioned hardware configuration, with older hardware the exact same disc configuration (two raid 1's on two discs, ...) works without any problems so far.

My Solution:
downsizing the 2nd raid device and the last volume of the LVM container by 1GB each resolves the problem.

Revision history for this message
komputes (komputes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 662691
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → cryptsetup (Ubuntu)
Changed in cryptsetup (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cryptsetup (Ubuntu) because there has been no activity for 60 days.]

Changed in cryptsetup (Ubuntu):
status: Incomplete → Expired
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.