ubi partman failed with exit code 10.

brij-linux

New Member
Joined
Mar 12, 2022
Messages
3
Reaction score
0
Credits
30
i downloaded the ubuntu 21.10 and saved in my laptops hard drive later burned it using balena etcher to my external 1tb hard drive. then I boot my laptop through the external hard drive and went with install ubuntu instead of try ubuntu, and at the end was stuck with a error ubi partman crashed what must I do plz help.
 

Attachments

  • WhatsApp Image 2022-03-12 at 8.19.53 AM.jpeg
    WhatsApp Image 2022-03-12 at 8.19.53 AM.jpeg
    55.5 KB · Views: 587


G'day brij-linux, Welcome to Linux.org

The instructions below are the ones to follow.

ubi-partman failed with exit code 10 - ubuntu 18.04
http://askubuntu.com/questions/1032905/ddg#1033275

Do the following (for beginners):

I assume you already have a flash usb with ubuntu .iso

  1. Boot your usb on try ubuntu
  2. Ubuntu Software > install Gparted
  3. Open gparted, right click on you desired partition to install Ubuntu > new > New Size : 200 MiB; filw system: fat32; > Add ; Something like this should be done:
  4. Right click on EFI partition just created, Manage flags > boot
  5. Apply changes on gparted then exit gparted
  6. Install Ubuntu, when appears where to install choose something else>
  7. double click on efi partition, choose EFI
  8. Double click on desired partition to install ubuntu, choose ext4, mount point "/"
  9. Install
 
Last edited:
Hi Condobloke!

I'm trying to install Ubuntu 20.04 on my lattop and getting this same error. To be honest it's a reinstall, because I had everything working and then messed it up by deleting a partition in the Disks app - my fault.

Anyway, I don't care too much about saving data I just want a system which will boot. The laptop is alittle unusual in that it has a 256GB SSD and a 1TB HDD - I want to boot off the SSD to make the boot a bit faster.

The SSD is UEFI (I have to admit I don't really understand that) - but I know I had the system booting and working fine (Ubuntu only) for 2 years until I muffed it a couple of days ago.

I followed your instructions and made a small EFI partition (it's actually 512Mb) bootable
I noticed that the rest of the disk (ext4) is also bootable
But rerunning the installation I still get the same error - I looked at the syslog in var/log and if I understand correctly, the relevant lines are:

Code:
Jul 20 07:55:24 ubuntu ubiquity[23896]: switched to page prepare
Jul 20 07:55:29 ubuntu ubiquity: No drivers found for installation.
Jul 20 07:55:29 ubuntu ubiquity[23896]: debconffilter_done: ubi-prepare (current: ubi-prepare)
Jul 20 07:55:29 ubuntu ubiquity[23896]: Step_before = stepPrepare
Jul 20 07:55:29 ubuntu activate-dmraid: No Serial ATA RAID disks detected
Jul 20 07:55:30 ubuntu ubiquity: umount: /target: target is busy.
Jul 20 07:55:30 ubuntu ubiquity[23896]: debconffilter_done: ubi-partman (current: ubi-partman)
Jul 20 07:55:30 ubuntu ubiquity[23896]: dbfilter_handle_status: ('ubi-partman', 10)
Jul 20 07:55:36 ubuntu ubiquity[23896]: dbfilter_handle_status: response -7
Jul 20 07:55:36 ubuntu ubiquity[23896]: log-output -t ubiquity debconf-copydb configdb targetdb -p ^oem-config/ --config=Name:targetdb --config=Driver:File --config=Mode:0644 --config=Filename:/target/var/cache/debconf/config.dat
Jul 20 07:55:36 ubuntu ubiquity[23896]: log-output -t ubiquity debconf-copydb configdb targetdb -p ^keyboard-configuration/ --config=Name:targetdb --config=Driver:File --config=Mode:0644 --config=Filename:/target/var/cache/debconf/config.dat
Jul 20 07:55:37 ubuntu ubiquity[23896]: log-output -t ubiquity debconf-copydb configdb targetdb -p ^console-setup/ --config=Name:targetdb --config=Driver:File --config=Mode:0644 --config=Filename:/target/var/cache/debconf/config.dat
Jul 20 07:55:37 ubuntu ubiquity:                      USER        PID ACCESS COMMAND
Jul 20 07:55:37 ubuntu ubiquity: /target:
Jul 20 07:55:37 ubuntu ubiquity:            
Jul 20 07:55:37 ubuntu ubiquity:  root    
Jul 20 07:55:37 ubuntu ubiquity:  swap  /target/swapfile
Jul 20 07:55:37 ubuntu ubiquity:      
Jul 20 07:55:37 ubuntu ubiquity:        
Jul 20 07:55:37 ubuntu ubiquity:    
Jul 20 07:55:37 ubuntu ubiquity:  root      mount
Jul 20 07:55:37 ubuntu ubiquity: /target
Jul 20 07:55:37 ubuntu ubiquity: kernelkernel
Jul 20 07:55:37 ubuntu ubiquity[23896]: log-output -t ubiquity fuser -cv /target
Jul 20 07:55:37 ubuntu ubiquity: umount: /target: target is busy.
Jul 20 07:55:37 ubuntu ubiquity[23896]: log-output -t ubiquity umount /target
Jul 20 07:55:37 ubuntu systemd[2020]: vte-spawn-783f789f-64f5-46f5-b66d-a0514d925e37.scope: Succeeded.
Jul 20 07:55:41 ubuntu dbus-daemon[2041]: [session uid=999 pid=2041] Activating service name='org.gnome.Nautilus' requested by ':1.100' (uid=999 pid=15207 comm="/usr/bin/gnome-shell " label="unconfined")
Jul 20 07:55:41 ubuntu dbus-daemon[2041]: [session uid=999 pid=2041] Successfully activated service 'org.gnome.Nautilus'
Jul 20 07:55:41 ubuntu nautilus[26096]: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Any idea what I'm doing wrong?
Thanks so much mate!
 
Last edited by a moderator:
Please start a new topic.

This topic was started back in March.....so will have very few followers/advisors

Fresh topic HERE
 

Members online


Top