[Bug 828330] [NEW] inconsistent use of (fake-) raid0 naming / wubi "no root file system is defined"

[SkyHigh]

Public bug reported:

Concerns: Windows7 wubi installation Ubuntu 11.04, on raid0

inconsistent use of (fake-) raid0 naming / wubi "no root file system is defined"
Concerns: Windows7 wubi installation Ubuntu 11.04, on raid0

Recently I downloaded Wubi for 11.04 and ran into the same problem
alright like others where the installation hung with "no root file
system is defined" after the usual rebooting as part of the install
process.

After quite some debugging in my case the root cause of the problem
seems to be the inconsistent use of (fake-) raid0 naming. /proc/mounts
refers to /dev/dm-<n> for the raid volume and partitions, while partman
uses the <mount> command/mtab syntax and refers to mapper devices
/dev/mapper/isw_..._XXX<n>. In a couple of places /proc/mounts is used
to find the device belonging to a certain mountpoint, but this yields
/dev/dm-XXX which partman is not able to find in its "mapper" based
administration.

A more extensive description of my findings is in Question 168097

I adapted two partman files to create a workaround, and with those
adaptions the installation completed succesfully. It concerns /bin
/autopartition-loop and /lib/partman/display.d/10initial_auto . The
diffs for the workaround are attached.

And by the way, not as part of the bug but for the execution of the
workaround: in order to complete the installation I copied these two
adapted files to c:\ubuntu\install\custom-installation\hooks and added
the following commands to the end of casper-bottom.sh to update the
original files on the fly with the adapted ones when booting during the
wubi install process (during the casper part of the installation this
wubi/ubuntu directory is mounted, while the iso is copied to the ram
drive and mounted at /root)

cp /custom-installation/hooks/lpd-10initial_auto /root/lib/partman/display.d/10initial_auto
chmod a+x /root/lib/partman/display.d/10initial_auto

cp /custom-installation/hooks/bin-autopartition-loop /root/bin/autopartition-loop
chmod a+x /root/bin/autopartition-loop

By the way, I did not add the syslog and partman log, as the
installation did succeed with the workaround. If you still need these
files then I will try to retrieve them.

** Affects: ubiquity (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: raid wubi

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/828330

Title:
  inconsistent use of (fake-) raid0 naming / wubi "no root file system
  is defined"

Status in “ubiquity” package in Ubuntu:
  New

Bug description:
  Concerns: Windows7 wubi installation Ubuntu 11.04, on raid0

  inconsistent use of (fake-) raid0 naming / wubi "no root file system is defined"
  Concerns: Windows7 wubi installation Ubuntu 11.04, on raid0

  Recently I downloaded Wubi for 11.04 and ran into the same problem
  alright like others where the installation hung with "no root file
  system is defined" after the usual rebooting as part of the install
  process.

  After quite some debugging in my case the root cause of the problem
  seems to be the inconsistent use of (fake-) raid0 naming. /proc/mounts
  refers to /dev/dm-<n> for the raid volume and partitions, while
  partman uses the <mount> command/mtab syntax and refers to mapper
  devices /dev/mapper/isw_..._XXX<n>. In a couple of places /proc/mounts
  is used to find the device belonging to a certain mountpoint, but this
  yields /dev/dm-XXX which partman is not able to find in its "mapper"
  based administration.

  A more extensive description of my findings is in Question 168097

  I adapted two partman files to create a workaround, and with those
  adaptions the installation completed succesfully. It concerns /bin
  /autopartition-loop and /lib/partman/display.d/10initial_auto . The
  diffs for the workaround are attached.

  And by the way, not as part of the bug but for the execution of the
  workaround: in order to complete the installation I copied these two
  adapted files to c:\ubuntu\install\custom-installation\hooks and added
  the following commands to the end of casper-bottom.sh to update the
  original files on the fly with the adapted ones when booting during
  the wubi install process (during the casper part of the installation
  this wubi/ubuntu directory is mounted, while the iso is copied to the
  ram drive and mounted at /root)

  cp /custom-installation/hooks/lpd-10initial_auto /root/lib/partman/display.d/10initial_auto
  chmod a+x /root/lib/partman/display.d/10initial_auto

  cp /custom-installation/hooks/bin-autopartition-loop /root/bin/autopartition-loop
  chmod a+x /root/bin/autopartition-loop

  By the way, I did not add the syslog and partman log, as the
  installation did succeed with the workaround. If you still need these
  files then I will try to retrieve them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/828330/+subscriptions