An error occurred during installation

Bug #1788315 reported by Vencislav
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Incomplete
Undecided
Unassigned
subiquity
Fix Released
Undecided
Unassigned

Bug Description

An error has occurred
curtin command install
 preparing for installation
 configuring storage
  running 'curtin block-meta simple'
  curtin command block-meta
   removing previous storage devices

Please report this error in Launchpad

Colin Watson (cjwatson)
affects: launchpad → curtin
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

I'm sure smosre/rharper will know better what to ask for, but aren't there more logs associated that should be added to the report?

Revision history for this message
Ryan Harper (raharper) wrote :

Hi,

Thanks for taking time to report the issue. Can you provide some more information on where you encountered this issue? Was it while using the Ubuntu Server installer?

Changed in curtin:
status: New → Incomplete
Revision history for this message
Vencislav (akametala) wrote :

Yes i did a install of ubuntu server installer inside a KVM running on RouterOS.
After I start the installer again from scratch everything did work fine.

Revision history for this message
Vencislav (akametala) wrote :

More info:
The installer started fine.
One i enter all the info on the GUI (username etc.) it pop up to report the bug.
The only option i did have was to view log (which i typed here) and to reboot the machine (vm).

Revision history for this message
Hristian (hristian-carabulea) wrote :

The installation process for ubuntu server 18.04 gives me error. "curtin block meta customer". curtin command block meta. remove previous storage devices.

error log "OSError:(Error 6) no such device or address: "/dev/sda2"
Stderr: ''

I restarted the installation process from DVD multiple times to no avail. I cannot get over this error.

------------------

Side comment: I am trying to reinstall Ubuntu Server after my current server does not work any longer with LXD LXC containers. I updated the kernel to 4.18.5, and my lxd container does not start any longer. Apparently a known bug already but not fixed. And during the 4.18.5 kernel installation I saw some nvidia errors. I have an old amd board. No graphic board, uses on board video, from what I remember.

And now, when I start the server and hold the shift key down to go into grub to go back to an older Kernel version, I cannot move up and down in the grub menu using any keys, up and down arrows, pg up and down, etc.

So, problems in different Ubuntu areas, Kernel, installation package, LXD LXC functioning with Kernel 4.18.5, etc. It seems, no matter what I do, I cannot have a running Ubuntu 18.04 server.

I am not that smart, but if I can help somehow, please do let me know. I would love to help, just not sure if I am able to.

Thanks again for all the good work otherwise.

Revision history for this message
Hristian (hristian-carabulea) wrote :

P.S. Hi. I know I am not the only one affected by this bug, since google-ing it shows otherwise. And I found a work-around solution:

1. After error occurs, go into the command line.

sudo fdisk -l # to see the drive name and partitions
sudo parted # get into the program to handle partitions
p # type p to show the existing partitions and their numbers.
rm 1 # type rm 1 to remove partition 1. Type rm x until all partitions are deleted, where x is parti#
q # type q to exit
sudo fdisk -l # type this to see again if all partitions were deleted.

Revision history for this message
Ryan Harper (raharper) wrote :

I've added the subiquity project which is the installer for 18.04.

If you've not already tried, 18.04.1 has an updated version of the installer and may include a fix for the issue you're seeing. Please test with 18.04.1 and report whether you get the same error or something else.

http://releases.ubuntu.com/18.04/

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

I'm going to close this bug on the grounds that there were fixes that _may_ have helped in the latest point releases. If not, please open new bugs.

Changed in subiquity:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.