ubiquity crashed with InstallStepError in configure_bootloader() on a fakeRaid system (nforce4)

[F.G.]

Binary package hint: ubiquity

grub advanced setting of step7 in ubiqity set to /dev/mapper/nvidia_dgfffeba (fakeRAID with two 4GB IDE disk in striping).
/boot partition on a third disk (90MB on /dev/sdb1). I choose this because of the many previous problem with grub2 using a simpler configuration.

ProblemType: Crash
Architecture: i386
Date: Mon Jan 25 12:31:29 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: ubiquity 2.0.8
ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
ProcEnviron: Error: [Errno 13] Permission denied: '/proc/3386/environ'
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
SourcePackage: ubiquity
Title: ubiquity crashed with InstallStepError in configure_bootloader()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

XsessionErrors:
 (gnome-settings-daemon:3198): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:3198): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:3257): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:3285): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Colin Watson (cjwatson)]

Could you give this a try with a current Lucid daily build (not an alpha release; Alpha 2 is too old for this)? We've made some improvements recently which should help with DM-RAID systems.

[F.G. (fabio-giglio)]

Colin Watson wrote:
> Could you give this a try with a current Lucid daily build (not an alpha
> release; Alpha 2 is too old for this)? We've made some improvements
> recently which should help with DM-RAID systems.
I'm sorry, but I have been busy in the last month.
Furthermore the cd-rom device is no more recognised by the system since I installed karmic on the RAID. As soon as I find some spare time, I will try to work out the cd-rom issue to test lucid.

However the main problem with RAID on karmic (whose installer supported very well the raid in opposition to 8.04) it is grub2: the crash I reported happened only one time (and I made several install).
In the end the workaround I found is to put the /boot out of the RAID array. So I succeded to boot even with grub2 and replace it with grub-legacy. If I hadn't done this, after the grub2 update the system wouldn't have rebooted.

[Brian Murray (brian-murray)]

The grub-installer error from syslog is:

Jan 25 11:30:12 ubuntu grub-installer: info: Installing grub on '/dev/mapper/nvidia_dgfffeba'
Jan 25 11:30:12 ubuntu grub-installer: info: grub-install supports --no-floppy
Jan 25 11:30:12 ubuntu grub-installer: info: Running chroot /target grub-install --no-floppy "/dev/mapper/nvidia_dgfffeba"
Jan 25 11:30:17 ubuntu grub-installer: grub-setup: error: no mapping exists for `nvidia_dgfffeba'
Jan 25 11:30:17 ubuntu grub-installer: error: Running 'grub-install --no-floppy "/dev/mapper/nvidia_dgfffeba"' failed.

[dino99 (9d9)]

This version has expired long ago; no more supported