[Bug 684280] Re: Ubiquity cannot install if you are booting LiveCD directly from ISO
OpenITeX
684280 at bugs.launchpad.net
Tue Oct 21 18:16:01 UTC 2014
Still present in ubuntu-14.04-desktop iso, booted from grub2.
No way to continue with installation cause "/isodevice cannot be
unmounted" (the operation of which is not even needed).
Not "invalid" or "fixed" not even in any of this bugs duplicates.
Wonder why this has ever been closed, even if it has been around for
atleast 4 years in each and every Ubunut installatiion .iso image.?
The quality of Ubuntu distributions is getting worse and worse every
year.. And seems that rven this severe installation bugs are not fixed
:(
** Tags added: installer ubuntu-14.04
--
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/684280
Title:
Ubiquity cannot install if you are booting LiveCD directly from ISO
Status in Ubiquity:
New
Status in “ubiquity” package in Ubuntu:
Invalid
Status in Baltix GNU/Linux:
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 ==========
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/ubiquity/+bug/684280/+subscriptions
More information about the foundations-bugs
mailing list