Unable To Install Tumbleweed, RPM Displays Error

English Install/Boot/Login
#1

Hello,
While trying to install tumbleweed, midway through RPM shows this error:

Subprocess failed. Error: RPM failed: Unable to create control pipe.

This is actually a part of a larger error message, which complains that the installation of a package had failed. Depending upon the time at which the RPM error shows up, it can be for any package (libwpe-1_0-1 in this case). Trying to ignore the error doesn’t work because all subsequent package installations also fail with the previous RPM error.

I am using the latest snapshot of the NET installer and have verified the image with the given check sums and it’s signature. To make sure that my USB drive wasn’t failing, I also tried a different one with the same results. My previous install had gone through without any issues, searching about this error online didn’t give me any appropriate answers either.

Any help on this would be greatly appreciated.

#2

Smells like an installer defect. You could try an older NET .iso from http://download.opensuse.org/history/, or the full DVD .iso, if necessary with no internet connection, to avoid automatic download and use of the latest installer version.

What are you trying to install onto?

#3

What are you trying to install onto?

You mean the drive? it’s a Crucial MX500 500 GB SATA SSD.

Smells like an installer defect.

I did check the mailing list, the forums and the sub reddit, but didn’t find any other users facing this issue. Don’t really know if this is something unique to me or not. What does this Unable to create control pipe error mean though?

Also, is it fine to use an older installer image? I mean, would it create further issues down the road?

#4

I meant all the hardware involved, mainly CPU, chipset, network bits & storage, plus its age.

I don’t recall ever seeing it. I would think it about trying to write where/when writing is disallowed.

It shouldn’t matter, as long as you can get it to run. The installer is heavily YaST, so the installation will replace the YaST that’s on the installation media, either during installation if network is available during installation, or at first zypper dup after installation is complete.

Also you could try installing something totally different, if you have anything handy, or running smartctl on the Crucial, to see if it may be defective.

#5

I meant all the hardware involved, mainly CPU, chipset, network bits & storage, plus its age.

The system in question, is an Intel NUC7CJYHN, with a Celeron J4025] processor and 8 GB of ram. For installation, I am using a wired connection. As for the age, it is a pretty recent machine, being launched in the year 2021. The BIOS is also running the latest updated revision.

I don’t recall ever seeing it. I would think it about trying to write where/when writing is disallowed.

Exactly, I couldn’t get any information about this error online. Seems like an extremely rare one.

It shouldn’t matter, as long as you can get it to run. The installer is heavily YaST, so the installation will replace the YaST that’s on the installation media, either during installation if network is available during installation, or at first zypper dup after installation is complete.

Okay, got it now. Thanks for the clarification.

Also you could try installing something totally different, if you have anything handy, or running smartctl on the Crucial, to see if it may be defective.

I tried installing Endeavour OS, which is based on Arch Linux and the installation went through, without any hiccups. As per the SSD being defective, well it is pretty new actually, just purchased it last week. Since the Endeavour OS install went fine, I don’t think that it is related to the drive.

At this point, just like what you said earlier, it looks like an installer defect to me. Will try an older build and update you soon.

#6

Is there a way for me to get the ISO file of the 20230110 snapshot? that version was the one I was running before the reinstall. On the download history page, there are no actual ISO files, just the old packages.

#7

I didn’t remember anything about the .isos not being hosted. :stuck_out_tongue:

Loader directories there contain the installation linux and initrd. If the PC still has a functional Grub on it, you can use it to load them and initialize an installation. e.g.

menuentry "Install openSUSE TW via HTTP" {
	search --no-floppy --label --set=root vol-label
	linuxefi	/ostw/linux install=http://download.opensuse.org/tumbleweed/repo/oss hostname=myhost ifcfg=*="192.168.1.11/24,192.168.1.1,1.1.1.1 1.0.0.1,my.net isp.net" video=1440x900 XVideo=1440x900 lang=en
	initrdefi	/ostw/initrd
}

Linuxrc lists the cmdline options.

#8

I didn’t remember anything about the .isos not being hosted. :stuck_out_tongue:

Oh, so that was the reason :smile:

Loader directories there contain the installation linux and initrd. If the PC still has a functional Grub on it, you can use it to load them and initialize an installation. e.g.

menuentry “Install openSUSE TW via HTTP” { search --no-floppy --label --set=root vol-label linuxefi /ostw/linux install=http://download.opensuse.org/tumbleweed/repo/oss hostname=myhost ifcfg=*=“192.168.1.11/24,192.168.1.1,1.1.1.1 1.0.0.1,my.net isp.net” video=1440x900 XVideo=1440x900 lang=en initrdefi /ostw/initrd }

Linuxrc lists the cmdline options.

Unfortunately, the error happens during the package download / install phase. GRUB is only configured later on, during the final stages of the installation. I’m going to try to install it again, after resetting my BIOS, to see if that helps. Would update soon.

#10

was key to my post. A stanza like I included would have to be manually inserted into existing grub.cfg, or in custom.cfg, or somewhere in /etc/grub.d/, to launch an older installer version, that would, with any luck, not produce those errors.

#11

Don’t know if it is because of the latest snapshot or the BIOS reset, but this time the installation went without any hiccups. Thank you very much for your support @mrmazda

#12

I have similar problem loading Opensuse tumbleweed from UEFI Cruzer created form download from latest version onto PC based on gigabyte H410M DS2V motherboard and two HDD one 2TB and the other 4TB I am attempting to load to the 2nd HDD partition 2 formatted with BTRS. About 4.0 Gb into load I receive “installation of package Messa-dri failed”. Error RPM failed exit status 1 Ignore just continues with similar errors

Any other suggestions?

#13

Please do not hang your “similar” problem at the end of an old thread, but start a new one dedicated to your problem.