Ubuntu 10.04 Installer crashes with Raid0

[Giulio Pasqualetti]

Binary package hint: ubiquity

Traceback (most recent call last):
 File "/usr/lib/ubiquity/bin/ubiquity", line 524, in <module>
  main(oem_config)
 File "/usr/lib/ubiquity/bin/ubiquity", line 511, in main
  install(query=options.query)
 File "/usr/lib/ubiquity/bin/ubiquity", line 242, in install
  ret = wizard.run()
 File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 460, in run
  self.progress_loop()
 File "/usr/lib/ubiquity/ubiquity/frontend/kde_ui.py", line 863, in progress_loop
  (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
 File "/usr/share/ubiquity/install.py", line 2566, in <module>
  install.run()
 File "/usr/share/ubiquity/install.py", line 1681, in configure_bootloader
  self.db.input('critical', bootdev)
 File "/usr/lib/python2.6/dist-packages/debconf.py", line 65, in <lambda>
  lambda *args, **kw: self.command(command, *args, **kw))
 FIle "/usr/lib/python2.6/dist-packages/debconf.py", line 86, in command
  status = int(status)
ValueError: invalid literal for int() with base 10: "

First, sorry for my bad English
I found this error while I was intalling Kubuntu 10.04 amd64 by the cdrom installer. I think the most important problem is grub-installer, because I am in RAID0 mode and it tries to install the bootloader in /dev/sda instead of the right place (/dev/mapper/...).
I suppose there is the same problem in Ubuntu.

/var/log/syslog
/var/log/partman

[David Morton (damorton)]

I have this exact problem also, but the problem did not occur when I installed Kubuntu 9.10 from the cd onto '/dev/mapper/nvidia_fdabdcca5', a partition on my NVidia raid0 shared with WindowsXP on '/dev/mapper/nvidia_fdabdcca1'.

When I installed 10.04 I selected '/dev/mapper/nvidia_fdabdcca5' as / for the installation in the 'Prepare partitions' window so as to wipe 9.10 and do a clean install. In the 'Ready to install' window I clicked on the 'Advanced' tab, left 'Install boot loader' ticked, and changed from '/dev/sda' to '/dev/mapper/nvidia_fdabdcca' in the drop down box. The installation failed at 'Running grub-install /dev/sda' ??? even though I had changed the selection in the 'Ready to install'-'Advanced 'tab. I tried again to be sure, and the same occurred.

Just to test the theory, I ran the installation of 9.10 again, and this time clicked the 'Advanced' tab to see what the selections were. 'Install boot loader' was ticked by default, and '/dev/mapper/nvidia_fdabdcca' was the default entry in the drop down box, there was no entry at all for '/dev/sda' (which is what is expected).

It seems the grub-installer does not get the correct information required to install grub in 10.04.

A work-around, install 9.10 then upgrade to 10.04. This works but is not satisfactory if you have already downloaded the 10.04 iso file and want to use that.

[David Morton (damorton)]

I have experienced this problem also when installing Kubuntu 10.04 on a partition of my NVidia raid0 shared with Windows XP.

There was no problem installing Kubuntu 9.10 from CD. The installer created '/dev/mapper/nvidia_fdabdcca5' as / and '/dev/mapper/nvidia_fdabdcca6' for swap, and correctly identified '/dev/mapper/nvidia_fdabdcca1' as ntfs.

When it came to installing Kubuntu 10.04, at the 'Prepare partitions' window, I selected '/dev/mapper/nvidia_fdabdcca5' as / to wipe the 9.10 installation. At the 'Ready to install' window I clicked on 'Advanced'. 'Install boot loader' was left ticked but I changed default '/dev/sda' to '/dev/mapper/nvidia_fdabdcca'.

The installation failed at 'Running grub-install /dev/sda' with the error message "Executing 'grub-install /dev/sda failed. This is a fatal error."

Why did the grub-installer try /dev/sda??? I ran the installer again double checking the settings in 'Advanced', but it failed once more.

I installed Kubuntu 9.10 again as detailed in paragraph 2. This time I looked at the selections in 'Advanced'. 'Install boot loader' was ticked and '/dev/mapper/nvidia_fdabdcca' was the default setting, there was no /dev/sda setting available.

It would appear the grub-installation routine does not correctly identify the setting selected in the 'Advanced' tab when installing Kubuntu 10.04.

As a work-around, install Kubuntu 9.10 then upgrade to 10.04, but this is not satisfactory if you have already downloaded the 10.04 iso image and want a clean installation.

[Brian Murray (brian-murray)]

Exception during installation:
May 3 18:21:49 ubuntu python: Traceback (most recent call last):
May 3 18:21:49 ubuntu python: File "/usr/share/ubiquity/install.py", line 2566, in <module>
May 3 18:21:49 ubuntu python: install.run()
May 3 18:21:49 ubuntu python: File "/usr/share/ubiquity/install.py", line 418, in run
May 3 18:21:49 ubuntu python: self.configure_bootloader()
May 3 18:21:49 ubuntu python: File "/usr/share/ubiquity/install.py", line 1681, in configure_bootloader
May 3 18:21:49 ubuntu python: self.db.input('critical', bootdev)
May 3 18:21:49 ubuntu python: File "/usr/lib/python2.6/dist-packages/debconf.py", line 65, in <lambda>
May 3 18:21:49 ubuntu python: lambda *args, **kw: self.command(command, *args, **kw))
May 3 18:21:49 ubuntu python: File "/usr/lib/python2.6/dist-packages/debconf.py", line 86, in command
May 3 18:21:49 ubuntu python: status = int(status)
May 3 18:21:49 ubuntu python: ValueError: invalid literal for int() with base 10: ''
May 3 18:21:49 ubuntu python:

[Simon Quigley (tsimonq2)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 574706

and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

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