crash when installing kubuntu on Z620 with SSDs in RAID0

[Karljohan Lundin Palmerius]

I'm trying to install Kubuntu 14.04 Beta1 on a Z620 with two SSDs in a RAID0 configuration. I've had problems with the partitioner crashing for me, however I managed to solve that by manually cleaning out all Windows partitions on the HDD (that I will use as /home). Now the installer proceeds past the partitioner and successfully copies files. The crash occurs after installing language packages.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.17.8
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CasperVersion: 1.337
CurrentDesktop: KDE
Date: Fri Mar 28 11:15:17 2014
InstallCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartUbiquity: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[Brian Murray (brian-murray)]

From Syslog:

Mar 28 10:14:49 kubuntu grub-installer: info: Installing grub on '/dev/sda'
Mar 28 10:14:49 kubuntu grub-installer: info: grub-install does not support --no-floppy
Mar 28 10:14:49 kubuntu grub-installer: info: Running chroot /target grub-install --force "/dev/sda"
Mar 28 10:14:49 kubuntu grub-installer: Installing for i386-pc platform.
Mar 28 10:14:51 kubuntu grub-installer: Installation finished. No error reported.
Mar 28 10:14:51 kubuntu grub-installer: info: grub-install ran successfully
Mar 28 10:14:51 kubuntu ubiquity: Can't read partition table from /dev/sda
Mar 28 10:14:51 kubuntu /plugininstall.py: log-output -t ubiquity umount /target/cdrom
Mar 28 10:14:51 kubuntu finish-install: Disabling CD in sources.list
Mar 28 10:14:51 kubuntu /plugininstall.py: Exception during installation:
Mar 28 10:14:51 kubuntu /plugininstall.py: Traceback (most recent call last):
Mar 28 10:14:51 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1780, in <module>
Mar 28 10:14:51 kubuntu /plugininstall.py: install.run()
Mar 28 10:14:51 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 78, in wrapper
Mar 28 10:14:51 kubuntu /plugininstall.py: func(self)
Mar 28 10:14:51 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 242, in run
Mar 28 10:14:51 kubuntu /plugininstall.py: self.configure_bootloader()
Mar 28 10:14:51 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1042, in configure_bootloader
Mar 28 10:14:51 kubuntu /plugininstall.py: self.db.input('critical', bootdev)
Mar 28 10:14:51 kubuntu /plugininstall.py: File "/usr/lib/python3/dist-packages/debconf.py", line 62, in <lambda>
Mar 28 10:14:51 kubuntu /plugininstall.py: lambda *args, **kw: self.command(command, *args, **kw))
Mar 28 10:14:51 kubuntu /plugininstall.py: File "/usr/lib/python3/dist-packages/debconf.py", line 83, in command
Mar 28 10:14:51 kubuntu /plugininstall.py: status = int(status)
Mar 28 10:14:51 kubuntu /plugininstall.py: ValueError: invalid literal for int() with base 10: ''
Mar 28 10:14:51 kubuntu /plugininstall.py:

[Karljohan Lundin Palmerius (karljohan)]

I don't know what /dev/sda points at but I tried to install / on the RAID drive, which had a mapper name, and /home/ under /dev/sdc (if I remember it correctly). Could /dev/sda (and /dev/sdb) be the SSD(s) in their unraided form? I'm pretty sure I did NOT select /dev/sda for bootloader.

[Simon Quigley (tsimonq2)]

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 1298908

and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

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