[Bug 557388] Re: Ubiquity crashes over recipe that leads to "Missing filesystem.size."

Geza Kovacs geza0kovacs at gmail.com
Thu Feb 16 06:12:59 UTC 2012


And I believe I now know what the scenario which is leading to this
error is. UNetbootin has an option to put the live environment (squashfs
and all) onto a hard drive partition (the hard drive install mode), so
that it can be booted in live mode. If a user has a single system
partition, puts the live Ubuntu environment onto that partition, and
attempts to boot it, it will boot into live mode correctly.

However, if the user launches the installer, then the only partition
which can be installed to is the same hard drive partition that the live
Ubuntu environment is running from. Hence, when the partitioner starts,
it will attempt to unmount that partition (which is currently mounted to
/cdrom), and this will of course fail because that's where
filesystem.casper et al reside. Hence the user gets the "Can't unmount
/cdrom" error. The user now manually unmounts /cdrom, starts the
installer, and gets this error.

So, I believe the solution would be to display an error message more
along the lines of "you can't install to the partition that you booted
the Ubuntu live environment from; please use a CDROM or USB drive to
install".

-- 
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/557388

Title:
  Ubiquity crashes over recipe that leads to "Missing filesystem.size."

Status in “ubiquity” package in Ubuntu:
  Fix Committed
Status in “unetbootin” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: ubiquity

  I'm having trouble getting a preseed to work with the new
  installer I believe the partition recipe is failing. It used to
  work on 9.04, now I get a "Missing filesystem.size." traceback from
  ubiquity (line 664).

  Here is the recipe :

  #  boot-root-home ::
  #    128 512 256 ext2
  #        $defaultignore{ }
  #        method{ format }
  #        format{ }
  #        use_filesystem{ }
  #        filesystem{ ext2 }
  #        mountpoint{ /boot }
  #        options/relatime{ relatime } .
  #    .
  #    500 4000 20000 $default_filesystem
  #        $lvmok{ }
  #        method{ format }
  #        format{ }
  #        use_filesystem{ }
  #        $default_filesystem{ }
  #        mountpoint{ / }
  #        options/relatime{ relatime } .
  #    .
  #    96 512 300% linux-swap
  #        $lvmok{ }
  #        method{ swap }
  #        format{ } .
  #    .
  #    100 10000 -1 $default_filesystem 
  #        $lvmok{ }
  #        method{ format }
  #        format{ }
  #        use_filesystem{ }
  #        $default_filesystem{ }
  #        mountpoint{ /home }
  #        options/relatime{ relatime } .

  
  Is it a bug or am I coding the preseed wrong ?

  If my preseed is wrong can you direct me towards uptodate
  documentation ?

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




More information about the foundations-bugs mailing list