ubi-partman crashes with exit code 141 during live install

[executorvs]

Binary package hint: ubiquity

I am still encountering a bug similar to Bug #730209 as of the April 10th daily-live build. I am reporting it in a seperate bug report because the other is marked as having been fixed.
Click the install ubuntu icon from within the live session, then click the forward button, make sure you've got three green checks, and then click forward again. at this point ubi-partman crashes with exit code 141. This has been a problem since at least Tuesday's daily, which is the earliest I've tried.

[executorvs (executorvs)]

I should add I was running the live session from a thumb drive on an Acer timeline 5810tz-4274

[Sérgio Faria (sergio91pt)]

Regarding my comment (#32) on Bug #730209 I had all 4 master partitions created with no logical one and about 1mb unpartitioned.

After replacing one partition with an extended, I was able to reach the partition choice step without crashing

[executorvs (executorvs)]

I believe my laptop also has 4 primary partitions. I will check a little later today.

[executorvs (executorvs)]

After removing one of my 4 primary partitions I did not encounter this bug. I am using the i-386 desktop iso.

[executorvs (executorvs)]

also just recreated the bug on my desktop.

[Victor Vargas (kamus)]

I am facing the same behaviour with my new laptop HP DM1 and Natty Alpha 2

[Nishant (nishant-singh28)]

Same problem here today. I have 3 Primary partitions, one of them being a /boot. 2 are for data. The 4th partition is split into 2, one for /home and other for /. No swap since I have enough RAM. Can't delete any data partitions, and I do not want to touch my /home. What's the solution in this scenario?
I was trying out Natty Beta 2 amd64 on a Dell Studio 1555.

[Andrea (adbello)]

Same problem on Samsung NP-130; after having removed one of the 4 primary partitions, no more crash and successfully installed.

[Geoff (palmerg)]

I too have four primary partitions and had the some problem trying to install Lubuntu. In the end I tried ubuntu-10.10-netbook. It installed correctly, allowed me to allocate and format the extended partition (into / and /home), and once that was done I was able to install Lubuntu.

(Note that trying Natty kicked up the same "ubi-partman" error.)

[justAnotherUser (jan-eichstaedt)]

I'm getting the same bug with Natty Beta 2 amd64 on a MSI GE620 with 4 ntfs partitions /dev/sda1 .. 4 and no matter how to start the installation process.

[justAnotherUser (jan-eichstaedt)]

After deleting one partition (leaving 3 ntfs partitions) the installation went beyond the point where ubi-partman had failed. Still installing, fingers crossed!

[Victor Vargas (kamus)]

for the record, I deleted my recovery partition and after that all the installation process finished successfuly

[Evan (ev)]

Can someone please confirm that this is happening with the final 11.04 image, when it is released later today? I tried with a candidate CD, but was unable to reproduce it.

[colin murphy (cdmurph32)]

I recieved the same bug with the final 11.04 image with 4 primary partitions. I deleted the swap partition and did not re-encounter the bug.

[Jorge L Tupac-Yupanqui (jltupac)]

Same problem installing 11.04 on a PCChips motherboard, Celeron CPU, HDD0 with 2 partitions and 10.10 installed, HDD1 with 2 partitions and Windows 7 installed. Will try deleting HDD0 partitions.

[Ryan Knapp (rpk5000)]

This bug affects me as well.

Attempted to install x64 desktop version of 11.04 final (pulled ~10:00pm EDT yesterday).

Received error on the checking prereqs screen (where it displays checkboxes for internet connected, enough free space available, etc), after hitting next. Installer hangs, and then after a brief period displays the error message.

Hardware:
P67A-UD7-B3 motherboard
128GB Vertex 3 ssd, 1TB HD, and 300GB HD. Windows 7 installed on SSD partition. There is a partition on the 300GB HD that is RAW that I intended to install Ubuntu onto. Aside from that partition I can't clear out or recreate any of the other partitions.

[Gabriel Charlet (gabriel-charlet)]

I have had the same problem.
I have a mini Dell 10v (Atom N270, SSD 8G) which was working by Ubuntu 8.04 preinstalled by Dell (slightly modified compared to 8.04 and no possibility to upgrade the system).
So I tried ubuntu 11.04 and it worked fine.

When I decided to install it, I decided to suppress Ubuntu 8.04 because the computer has only a small 8G SSD (pata possibly). Ubuntu proposed to make a single partition (from the 3 initially present).
Just after the screen where keyboard is selected, everything was blocked. And I have then seen this message "ubi-partman failed with exit code 141".
I have now no more system working on the computer...

[justAnotherUser (jan-eichstaedt)]

The installation of 11.04 went smooth for me. I had 4 preexisting partitions prior to that install, 3 ntfs, one ext4 (11.04b2). Perhaps the problem showes only with 4 (or more) _ntfs_ partitions?

[kd4pba (kd4pba)]

Just an observation,

I ran into the same problem.

I have multiple SATA drives, with Multiple partitions, including NTFS,
EXT3 and Riser. I don't like doing upgrades so I elected to wipe the
existing Ubuntu install.
I ran into the same problem when trying the live installer. I used the
Disk utility to mount the partition I wanted to install on which in my
case was /dev/sda5. After I had the partition mounted I started the
live install and of course it warned me that a partition was mounted
and unmounted it. After that the install proceeded. That seems to have
fixed it.

[Ryan Knapp (rpk5000)]

Followup on my previous comment:

Given the other comments here, I removed one of my hard drives, leaving me with 4 partitions, 3 ntfs partitions, and one RAW partition that I intended to install ubuntu on. I tried mounting and unmounting the disks, as described by kd4pba, without success. Noticing that I couldn't mount the raw file system when trying to mount, I thought that might be the problem. I formatted the RAW partition with ext4, and ran the installer again. No error! :)

[naguz (naguz-gmx)]

I can also confirm that this is indeed a problem with the final 11-04 AMD64-image.

I posted details here at first: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/730209/comments/38

IMHO this should be a critical bug. As the alternate cd fails after the partitioning step when run from usb (probaly because it uses on of the partitions as a temp dir) and the netinstall image takes a good 90 minutes to complete an install (not to mention it is very beginner-unfriendly), the install functionality should really just work off of the live cd.

[naguz (naguz-gmx)]

It seems there might be a problem with my partitions on the drive, however. cfdisk gives me an error about enlarged logical partitions overlapping - at least it gives me USEFUL feedback.

[GreatBunzinni (greatbunzinni)]

I've experienced this bug while installing both Kubuntu11.04 and Ubuntu11.04 through desktop edition ISOs.

[GreatBunzinni (greatbunzinni)]

Meanwhile, Kubuntu 10.10 through a Desktop ISO installs without a single problem.

[axelsvag (darinsson)]

I have exactly the same problem as all of you. I got a travelmate 2313 with sis graphics so I thought it had something to with that. But the problem is the same on both ubuntu, xubuntu, lubuntu 11.04 and linux mint 11. On 10.10 everything works

[latent_biologist (beaudealy)]

I got this same error on the 11.04 desktop final release (32bit). Downloaded the alternate install and discovered the same problem, but was tipped off to what was causing it when the alternate install asked if I wanted to use my SATA device, though I didn't have one attached to the board (installing to an 80GB pata). In the alternate install, if I choose to ignore the sata device (really only seeing the empty controller). Then I'm able to install no problem.
Maybe we need an option to ignore sata or try again with sata disabled for the standard desktop release?

[TraceyC (grrlgeek)]

Still having this problem with the 11.04 Live CD installer for Lubuntu. The error appears any time I try to use a partition & choose XFS. It does not happen if I choose ext4. Attached is the syslog.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD). Please retry your installation with new media and if it still fails I'd recommend testing your CD drive with other media. In the event that is is not in fact an error with your installation media please set the bug's status back to New. Thanks and good luck!

[GreatBunzinni (greatbunzinni)]

I can't speak for everyone, but I suspect that my problem was caused by bad RAM, which also caused a set of other unrelated problems. I won't test it if that's the cause, because I don't have the time or the resources to run the install processes on two different distributions. Yet, maybe some other user who also experienced this problem can test this.

Nevertheless, there is a problem with ubi-partman, specificallly it's cryptic error codes which don't say anything at all. it would be nice if some work was invested in it so that a user could have a clue regarding what went wrong with their installation.

[Launchpad Janitor (janitor)]

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

[Ritesh Chowdhry (ritesh313)]

Changing status to new as this bug is affecting me. It's been around 6 days, I have tried installing Ubuntu 20.04, 19.04 with no success and then I tried 16.04 in which I got this "ubi-partman crashes with exit code 141" error.
My system details:
Trying to dual boot with Windows 10
HP pavilion 15-ab notebook
8GB RAM
I have one 500 GB SSD (recently installed) and a 1TB HDD
While creating I created 30 GB for / and 16 GB swap area and then around 70 GB /home space. I have tried creating this only on my SSD and also some on SSD and some on HDD.
I already formatted my HDD (now don't have any partition on it) and it's in basic mode (not dynamic). SSD just has one partition for windows.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.