Installer crash LVM volume [Solved]

Hi,

Today I’ve tried to install new 13.12 release of Netrunner (stable). Installer crashes at my machine after following actions:

  1. Using manual partitioning disk
  2. Using different volumes for /, /home, /tmp , /usr and so on. They’re all based on lvm logical volumes created before installation
  3. Assigning more than 4 mount points to volumes and define type of new filesystems
  4. Crashed before some delay without any notifications.

This thing was not fixed since previous release. I’m experienced Linux user and can do other manipulations before install, that’s not problem. I just want you to know about this. If you need some feedback from me or close this thread due to well-known problem state, please notify.

Thanks :rolleyes:

What version (32 or 64bit)?
What machine do you use, does it have 1GB RAM?
Could you check with “df -h” the memory just before the partition page in the installer comes up?

If this problem existed before it might be aswell an upstream (means ubiquity) issue. Did you already reported that particulary problem to upstream or found a bug report about it ?

Hi,

-I use 64 bit version
-8 Gb of physical RAM

Looks like it’s really problem with ubiquity, for now I found only this related bug:

https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1226912

It’s not absolutely my problem, in this example ubiquity won’t start anyway, but I see related errors.
[hr]

Hi,

Yeah, looks like problem related particularly with ubiquity. I’ll try solutions listed in bug report, maybe it can help me.

Thanks
[hr]

New messages that I didn’t see before:

Traceback (most recent call last):
File “/usr/lib/ubiquity/ubiquity/frontend/kde_components/PartitionModel.py”, line 111, in parent
parentItem = childItem.parent()
AttributeError: ‘Partition’ object has no attribute ‘parent’

Looks like it’s really bug. Thank you for help.

Guys, thank you for help. That is not ubiquity bug, since ubiquity doesn’t supports LVM fully. But ubiquity can normally install distribution on lvm volumes, perhaps there is one important thing - LVM PHYSICAL VOLUME PARTITION MUST HAVE PROPER TYPE. For example:

netrunner@netrunner:~$ sudo fdisk -l /dev/sda

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x2a004729

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 432127 215040 83 Linux
/dev/sda2 432128 839292927 419430400 8e Linux LVM ----- this LVM partition (physical volume) has proper type (8e Linux LVM)

netrunner@netrunner:~$ sudo fdisk -l /dev/sda

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x2a004729

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 432127 215040 83 Linux
/dev/sda2 432128 839292927 419430400 83 Linux ----- this LVM partition contains logical volumes and has wrong type (83 Linux) what used for simple physical partitions

In second case installer fails after assigning 4 or more mountpoints to LVM volumes (sometimes before 2). I tested it only on my laptop but looks like this is root cause of issue.

Simple attentiveness may solve many problems :smiley: