Ubuntu 12.04 install crashes

[Arthur Hartwig]

The installation from CD crashed while reporting installing system or soon after. The system was not connected to the Internet. I will retry with the system connected to the Internet. I connected to the internet after the report of the installation crashing and then clicked on the Send button to send the crash report but I don't know if the report was successfully sent.

I would be happy to attach the files /var/log/syslog and /var/log/partman but it is not clear how to attach multiple files so I will attach /var/log/syslog. Hope it is useful.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.10.16
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu5
Architecture: i386
CasperVersion: 1.315
Date: Fri Apr 27 12:01:52 2012
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu Foundations Team Bug Bot (crichton)]

Exception during installation:
Apr 27 01:00:20 ubuntu plugininstall.py: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Apr 27 01:00:20 ubuntu plugininstall.py:

[Arthur Hartwig (a-hartwig)]

I was doing a custom install with separate disk partitions for /boot, /home and /. I repeated the install with the /boot partition size 192MB instead of 40MB and the install successfully completed.

I presume the original install attempt failed due to /boot being too small. It is a pity the install wasn't more informative about what it was doing when it failed.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 220961, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.