[Bug 1155216] Re: Unable to umount isodevice

Tony Cooper 1155216 at bugs.launchpad.net
Sat Mar 30 11:08:41 UTC 2019


I am booting my own casper based Ubuntu 18.04 LTS ISO image from a disk
partition and also ran into  this problem with toram apparently not
working (well not completely at least).

The issue is the loopback devices are keeping the source disk active.
Doing a forced umount doesn't help as the system still things the disk
is mounted and won't let you fsck it.

So I did losetup -a, located the offending device, in my case loop0 had
/recovery mapped, and then I did losetup -d /dev/loop0 and it unmounted
and I was able to fsck the underlying partition.

HTH.

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

Title:
  Unable to umount isodevice

Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  When installing from an iso file, with grub's loopback option,
  Ubiquity displays a message stating the isodevice cannot be unmounted,
  even when the isofile is not located on the same harddrive as the
  installation target.

  sudo umount -l -r -f /isodevice

  solves this problem, so Ubiquity should be able to issue this command
  by itself, without any user action.

  Arbiel

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



More information about the foundations-bugs mailing list