ubi-partman failed with exit code 141

I can confirm the bug, I've just tried with the Lucid Alpha downloaded today.

I was planning on installing on a 40Gb drive to wiped completely using manual partitioning, with 10Gb as "/", 2Gb as swap and the remainder as "/home" . Both "/" and "/home" were being formatted as ext4.

The contents of /var/log/syslog are:- (The problem shows up about 19:20:12 in the log)

Feb 21 19:19:34 ubuntu kernel: imklog 4.2.0, log source = /proc/kmsg started.
Feb 21 19:19:34 ubuntu rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="2247" x-info="http://www.rsyslog.com"] (re)start
Feb 21 19:19:34 ubuntu rsyslogd: rsyslogd's groupid changed to 102
Feb 21 19:19:34 ubuntu rsyslogd: rsyslogd's userid changed to 101
Feb 21 19:19:34 ubuntu rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpuset
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpu
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] Linux version 2.6.32-14-generic (buildd@vernadsky) (gcc version 4.4.3 (Ubuntu 4.4.3-2ubuntu2) ) #20-Ubuntu SMP Sat Feb 20 05:38:50 UTC 2010 (Ubuntu 2.6.32-14.20-generic)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] KERNEL supported cpus:
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] Intel GenuineIntel
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] AMD AuthenticAMD
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] NSC Geode by NSC
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] Cyrix CyrixInstead
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] Centaur CentaurHauls
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] Transmeta GenuineTMx86
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] Transmeta TransmetaCPU
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] UMC UMC UMC UMC
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-provided physical RAM map:
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 000000001fe70000 (usable)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 000000001fe70000 - 000000001fe72000 (ACPI NVS)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 000000001fe72000 - 000000001fe93000 (ACPI data)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 000000001fe93000 - 000000001ff00000 (reserved)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 00000000fecf0000 - 00000000fecf1000 (reserved)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] DMI 2.3 present.
Feb 21 19:19:34 ubuntu kernel: [ 0.000000] last_pfn = 0x1fe70 max_arch_pfn = 0x100000
...

After coming out of the install ubuntu option and being dropped to the livecd desktop, I was able to use gparted to manually create the partitions and then click the install ubuntu icon from the desktop, select the partitions manually created and the installation has continued as expected.

Joyce, could you please start the installer with 'ubiquity -d' from a terminal window, and reproduce this problem (just reproducing the first problem you ran into will be fine - all I need is for you to get to the point where it says "ubi-partman failed with exit code 141", then exit the installer)? Once you've done that, please attach /var/log/syslog, /var/log/partman, and /var/log/installer/debug to this bug report. It's important that you attach all those files.

Oh, you might as well try it with today's daily build as well, as there've been fixes since the 20th.

I hit the same problem with cdimages/ubuntu-netbook/daily-live/20100222 on armel (imx51)

Here are my logs.

The interesting bit seems to be:

[installer/debug]:

Feb 23 10:02:18 ubiquity: Partman: state = [['', None, None]]
Feb 23 10:02:18 ubiquity: Partman: auto_state = None
Exception caught in process_line:
Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 134, in process_line
    return self.dbfilter.process_line()
  File "/usr/lib/ubiquity/ubiquity/debconffilter.py", line 281, in process_line
    if not input_widgets[0].run(priority, question):
  File "/usr/lib/ubiquity/plugins/ubi-partman.py", line 2206, in run
    self.frontend.installation_medium_mounted(
AttributeError: Wizard instance has no attribute 'installation_medium_mounted'
Feb 23 10:02:18 ubiquity: ['log-output', '-t', 'ubiquity', '--pass-stdout', 'sh', '-c', '/usr/share/ubiquity/activate-dmraid && /bin/partman'] exited with code 141

Hi Colin,

>you might as well try it with today's daily build as well

I'll start download now, start it in a virtual machine and try your command line tonight and come back here with the results. Since the other day I had installed the alternate version in Virtualbox.

(Bye the way, this bothers me when I want to use the guest-additions features to go to and fro with the mouse and do some copy/paste between the guest and the host : I can't get the guest-additions to work properly, whether installing Virtualbox packages from repositories or the Ubuntu package for Karmic -latest available, 3.1.4- at Virtualbox site - and I suppose it's not a bug, but a matter of something in versions that mismatch... concerning virtual machines, I use only Virtualbox : no vmware no qemu... )

Hi,

I just started the install with "sudo ubiquity -d".

It has crashed same way as the first time. Just after, I sent the requested files to the host machine with scp and I enclose them three here in an archive.

After that I had the idea to click on "try again" and this time, instead of being on the "manual partitioning" option, it was on the automatic position, which I left on because I was curious to see what, and now : _it is installing_.

I'm not sure of the result yet, because the install is not finished at the moment. Just that one question comes to me : I'm installing on a virtual disk that is not bigger than 4250MB... Is there a feature in ubiquity that tests the available disk space when one installs ?

After that, migrationassistant failed with the same exit code. I attach the same files again, incase something in them changed since the preceeding error.

I got this error using the Xubuntu DesktopCD lucid-desktop-amd64.iso dated 2010-02-23.1. I am attaching the logs from the attempted installs. This error came up for both Manual and AutoResize partitioning in VirtualBox.

Since there was no /var/log/installer/syslog, I am including the /var/log/syslog file instead.

Please could everyone other than Joyce who's experiencing this problem (i.e. Dave and Charlie) file a separate bug? This symptom is a relatively generic one and may arise from multiple causes.

After analysing Joyce's logs, I believe that this is the same as bug 527057. I just committed a fix for that, and will try to get it into alpha 3, though it may end up in the next daily build after that.

Charlie's logs point to the same problem, although since he did not run ubiquity in debug mode it's hard to be absolutely sure of this.

Dave's logs indicate a different problem, namely bug 524169, which was fixed in ubiquity 2.1.25.

Hi,

I met again with the same error while trying to install 2010 March 10th Ubuntu desktop version 64bits to Samsung N210 Netbook that has a N450 cpu (64bits).

I attach the 3 files as preceeding time, after I tried again with the debug option from console : "sudo ubiquity -d".

I attach some files with the specs of the machine as well.

Thanks.

I have the same problem.