ref: https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/1317437
possibly related to this bug:
The kernel parameter 'rw' was required to make loopinstalled (wubi)
ubuntu 14.04 boot. I have a small fix for the initramfs-tools that fixes
this.
The loop device that root.disk was
Looks like a related (possibly smae) has emerged in ubuntu 14.10
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/1317437
It seems that not only does the host file system have to be rw but also
the loop file. The ticket above shows that by changing the kernel
parameter from ro-rw corrects
Did a quick test: In a loopmounted ubuntu 13.10 installation:
boot into a fresh loopmounted install of ubuntu 13.10
drop to the root shell in recovery mode
try to remount the loop file system as rw (sucess).
This fails with loopmounted installs of Ubuntu 14.04.
--
You received this bug
** Branch linked: lp:ubuntu/initramfs-tools
--
Cannot remount loopfiles
https://bugs.launchpad.net/bugs/201750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Changing priority since the partial fix, although not very elegant, does
address the issue, and I have not seen many complaints that can be
linked to this bug
** Changed in: wubi
Importance: High = Low
--
Cannot remount loopfiles
https://bugs.launchpad.net/bugs/201750
You received this bug
** Changed in: wubi
Target: 8.10 = None
--
Cannot remount loopfiles
https://bugs.launchpad.net/bugs/201750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: wubi
Target: None = 8.10
--
Cannot remount loopfiles
https://bugs.launchpad.net/bugs/201750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Summary changed:
- Cannot remount loopfiles inside of vfat
+ Cannot remount loopfiles
--
Cannot remount loopfiles
https://bugs.launchpad.net/bugs/201750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Resetting status to in progress, since a proper fix would involve being
able to actually remount filesystems.
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Released = In Progress
--
Cannot remount loopfiles inside of vfat
https://bugs.launchpad.net/bugs/201750
You received this bug
This bug was fixed in the package initramfs-tools - 0.85eubuntu33
---
initramfs-tools (0.85eubuntu33) hardy; urgency=low
* Edit scripts/local with patch from
https://bugs.edge.launchpad.net/wubi/+bug/201750 comment 1
Cannot remount loopfiles inside of vfat
The
I did some preliminary tests with blockdev (which was suggested to me by
Colin Watson) and added some code to mounthost (Mounthost is the init.d
scripts that takes care of remounting the host directory for
loopinstallations, see http://bazaar.launchpad.net/~ubuntu-
** Changed in: wubi
Status: Confirmed = In Progress
--
Cannot remount loopfiles inside of vfat
https://bugs.launchpad.net/bugs/201750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: wubi
Importance: Undecided = High
Status: New = Confirmed
--
Cannot remount loopfiles inside of vfat
https://bugs.launchpad.net/bugs/201750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I think that the issue is due to the fact that the ro/rw status of a
loopdevice is set once that is created and cannot be changed later on.
So if /host is ro or if the loop device is created via losetup ro or if
it is created implictily via mount -o loop,ro, then it will not be
possible to
The workaround involves mounting all loopinstallations rw to begin with:
--- local 2008-03-13 11:15:50.346417000 +
+++ local.new 2008-03-13 11:16:44.140677000 +
@@ -62,7 +62,7 @@
[ $quiet != y ] log_end_msg
if [ ${readonly} = y ] \
- ([ -z $LOOP ] || [
** Description changed:
Binary package hint: initramfs-tools
Loopfiles inside of vfat cannot be remounted rw. This preventfs people
from booting off loopinstallations in vfat. At the moment there is an
exception in scripts/local to mount ntfs filesystems rw by default since
those too
** Description changed:
Binary package hint: initramfs-tools
Loopfiles inside of vfat cannot be remounted rw. This preventfs people
from booting off loopinstallations in vfat. At the moment there is an
exception in scripts/local to mount ntfs filesystems rw by default since
those too
This work-around allows a FAT32 install to boot successfully. The
questin is however, whether we want to support FAT32 installs, and
whether there is a more sane approach.
--
Cannot remount loopfiles inside of vfat
https://bugs.launchpad.net/bugs/201750
You received this bug notification because
18 matches
Mail list logo
