** Changed in: casper (Ubuntu)
Assignee: Mate Kukri (mkukri) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684280
Title:
casper toram forgets to disconnect loop device
To manag
Confirmed that install indeed fails if I repeat comment #34 but erase
entire sda instead of just sda3.
** Changed in: casper (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
re-opening to test the case when the entire drive is to be formatted
instead of just one partition.
** Changed in: casper (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Okay I think we can add a `detach` option to casper to allow for this
usecase.
I don't think this a bug strictly speaking, but there is a legitimate
usecase for the feature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I'm using the "toram" option to start Ubuntu based installations from
already existing installations directly from the hard drive. Reasons for
that is that I want to be able to perform a clean installation by
completely wiping the hard drive after the ISO has been loaded into RAM.
For example, if
But I don't think this is strictly a bug, but I think detaching if toram
is in bootargs is probably fine, i'll take another look at this later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684280
Tit
My initial concern was to install dual boot linux from Booting the live
ISO toram from Windows C:
But this could also apply to installing from an existing linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I am not sure if modifying the same partition the ISO is actively being
used from should be supported.
Or are you wanting this to only work when the ISO is used from RAM only?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Thanks for your feedback
In my test the ISO would be on sda3 to reproduce
And you would need to try to resize sda3 from the live ISO to see the
problem occur
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
So I've tried to reproduce this on Oracular 24.10 with the Flutter
desktop installer, and I belive this is no longer a problem.
I've create a disk like:
- sda1 - vfat - /boot/efi
- sda2 - ext4 - /boot + Oracular ISO
- sda3 - ext4 - ubuntu partition
Booting the ISO via grub using:
set isofile=o
** Changed in: casper (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684280
Title:
casper toram forgets to
This should be fixed, because when you boot an ISO file from your hard
drive and load Ubuntu to RAM, you are not able to do any repartitioning,
installing etc to the hard drive from where the ISO was loaded from when
it stays mounted. I have tested this on a Ubuntu installation with LVM
hard drive
Issue is still occurring on ubuntu-20.04.3-live-server-amd64.
Unfortunately having difficulty unmounting the iso file with the
following two commands,
losetup -d /dev/loop0
umount /isodevice
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
When booting Kubuntu 20.04.1 (LTS) iso the workaround of detaching
/dev/loop0 device and then unmounting /isodevice was required, as in
comment #27. Then setup finished.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Description changed:
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
Just an Update : umount -lfd was not enough
So I'm trying to embed a startup script in a Live custom ISO :
losetup -d /dev/loop0
umount -lfd /isodevice
And it works
** Description changed:
Binary package hint: ubiquity
Ubiquity cannot install if you are booting LiveCD directly from IS
Still on 20.04.1 ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684280
Title:
casper toram forgets to disconnect loop device
To manage notifications about this bug go to:
https://bugs.launchpad.
Any update on this small but big win fix ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684280
Title:
casper toram forgets to disconnect loop device
To manage notifications about this bug go to:
h
Even better option of umount : -d ( detach loop devices )
So sudo umount -lfd /isodevice
should be the way.
** Description changed:
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 t
Did you try to force umount at line
https://git.launchpad.net/ubuntu/+source/casper/tree/scripts/casper?h=ubuntu
/focal-devel#n200
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684280
Title:
casper
** Tags removed: maverick
** Tags added: bionic focal
** Description changed:
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 se
Regarding comment #20, 2019-10-03,
I tried this patch and umount -d ${copyfrom} seems like it should
unmount the loopback device, but it does not.
Yet this works:
root@xubuntu:~# losetup -d /dev/loop0
root@xubuntu:~# umount /isodevice
I am still looking that this, but was curious if anybody el
Here's a patch for casper to delete the loopback after copying:
diff --git a/scripts/casper b/scripts/casper
index 5861ced..fa06c0d 100644
--- a/scripts/casper
+++ b/scripts/casper
@@ -191,7 +191,7 @@ copy_live_to() {
if [ -e ${copyfrom}/.disk ]; then
cp -a ${copyfrom}/.disk ${copyto
Yes; the install only fails if the iso file is on your hard disk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/684280
Title:
casper toram forgets to disconnect loop device
To manage notifications
Philip Susi: Confirmed with the Bionic live CD:
root@xubuntu:~# cat /proc/cmdline
BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper
iso-scan/filename=/linux/xubuntu-18.04-desktop-amd64.iso toram
root@xubuntu:~# umount /isodevice
umount: /isodevice: target is busy.
root@xubuntu:~# losetup -d /dev/l
25 matches
Mail list logo
