[Bug 684280] Re: casper toram forgets to disconnect loop device

[Glenn Washburn]

> Disconnecting the loop device may not always be desired after using
"toram": See
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/1960457/comments/33

That comment was very likely not in the context of "toram" usage. That
users requirements appear to be iso loopback loading access to
/isodevice from the overlay root.

I prefer a nodetach option as I think the expected use case (or maybe
just mine) for toram is to remove the usb device on which resides the
loopback loaded iso so that the device can be used elsewhere while the
live cd is running.

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

Title:
  casper toram forgets to disconnect loop device

Status in casper package in Ubuntu:
  Triaged
Status in Baltix:
  Invalid

Bug description:
  Binary package hint: ubiquity

  Ubiquity cannot install if you are booting LiveCD directly from ISO.

  Booting directly from GRUB to the ISO, mounts the ISO to /isodevice.

  Ubiquity will not install (even if on separate disk) if this is not
  unmounted.

  The result being that one cannot install Ubuntu in this method.

  This method can be used to create a recovery partition or a multi-usb
  bootable drive. For more explanation on how to do this:

  ========== START ==========

      * Run the following commands which will create the directory
  /boot/iso and download the iso file to that directory.

  $ sudo -s
  # mkdir /boot/iso
  # cd /boot/iso
  # wget http://releases.ubuntu.com/maverick/ubuntu-10.10-desktop-i386.iso

      * Add a custom menu entry in GRUB2 configuration file. Edit
  /etc/grub.d/40_custom as root to look like this:

  #!/bin/sh
  echo "Adding 40_custom." >&2
  exec tail -n +3 $0

  menuentry "Maverick CD Image ISO" {
  set isofile=/boot/iso/ubuntu-10.10-desktop-i386.iso
  loopback loop (hd0,1)$isofile
  linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile noprompt noeject
  initrd (loop)/casper/initrd.lz
  }

      * Afterwards, run update-grub for the changes to be propagated to
  /boot/grub/grub.cfg

  # update-grub
  Generating grub.cfg ...
  Found linux image: /boot/vmlinuz-...
  Found initrd image: /boot/initrd.img-...

  ========== STOP ==========

  ================== Workaround =================

  After casper copy to ram , it need to disconnect the loop device and
  unmount

  losetup -d /dev/loop0
  umount /isodevice

  ===========================================

  The result of booting from the ISO directly from GRUB, is that the CD
  is that the partition where the ISO is located is mounted to
  /isodevice.

  Ubiquity seems to want to have control of all disks and unmount all
  disks before it starts installing. In the images here you see the
  example is sda2 for / and sda for the MBR. I have also tried this with
  a secondary disk where sdb1 was to be used for / and sdb for the MBR
  and ubiquity still complained that it had to to unmount /isodevice,
  even though it is on sda1. Doesn't make much sense to unmount a disk
  if you will not be editing any part of it.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: ubiquity 2.4.8
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Thu Dec  2 16:34:42 2010
  LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity

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