*** This bug is a duplicate of bug 953875 ***
https://bugs.launchpad.net/bugs/953875
I was confronted with this bug simply because I checked Encrypt home folders
during a fresh installation of Ubuntu LTS 14.04 .
There seems to be a certain amount of unwillingness to resolve this issue
*** This bug is a duplicate of bug 953875 ***
https://bugs.launchpad.net/bugs/953875
*** This bug is a duplicate of bug 953875 ***
https://bugs.launchpad.net/bugs/953875
which is actually squashed now. The working version of cryptswap is
available when you install 15.04.
For example,
*** This bug is a duplicate of bug 953875 ***
https://bugs.launchpad.net/bugs/953875
** Also affects: ecryptfs
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 953875 ***
https://bugs.launchpad.net/bugs/953875
** This bug has been marked a duplicate of bug 953875
Encrypted swap no longer mounted at bootup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Don't get me wrong. I read this bug report, and I see that there are
many comments that point forward to squashing the bug.
The previous post (#42) describes a work-around method that works today
with Lubuntu Vivid. It does not contain what will be used to squash the
bug. See the following link
I can confirm that *offset=8* in the line in */etc/crypttab* makes
cryptswap survive reboots. I have tested it in Lubuntu Vivid 32-bit.
I used the simple method described in comment #3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that *offset=8* in the line in */etc/crypttab* makes
cryptswap survive reboots. I have tested it in Lubuntu Vivid 32-bit.
I used the simple method described in comment #3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Now our solution - provided for *systemd* computers:
*/etc/fstab*
# LABEL=COMMON-SWAP none swapsw 0 0
uncomment swap-volume only!
*/etc/crypttab*
# target name source device key file options
cryptswap1 LABEL=COMMON-SWAP /dev/urandom
Okay, so I believe that I fixed the issue without using upstart. This
version instead uses sysvinit instead. Please let me know what you
think. This would fix the issue for the installer if it was added to the
iso.
You can also use it to fix your current system by doing the following:
Delete all
Stay with script for upstart version as provided with #32
Due to *systemd* will work no longer with *init.d* anyway.
The version #39 makes nothing else then to provide the *crysetup* in
background only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So, from what I can tell, this is the only way to do it while working
with an init upstart system. I suppose that when ubuntu makes that
change, I'll just have to write another patch. I do believe archlinux
had was having a similar problem with crypttab and uuid's. They use
systemd but, they just
So from what I can tell this is the only way to do it while working with
an init upstart system. I suppose that if ubuntu makes that change, I'll
just have to write another patch. I do believe archlinux had was having
a similar problem with crypttab and uuid's and they use systemd.
Although they
Well that's too bad. I'll try to find a way that doesn't use upstart
then. Thanks for the information! I'll keep you guys posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
Yes this patch is working - but under *upstart* only.
Using the coming up systemd feature this patch will destroy more than
the patch helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
The attachment ecryptfs-setup-swap (patched) seems to be a patch. If
it isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Yes that is a patch for the ecryptfs-setup-swap script. If ubuntu were
to use it to replace the current ecryptfs-setup-swap in the installation
iso we would no longer have this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ecryptfs
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after reboot
To manage notifications
** No longer affects: ecryptfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after reboot
To manage notifications about this bug go to:
Hi there, I believe I patched the issue in ecryptfs-setup-swap which causes
this problem in the first place.
This program now sets the swap's fstab to noauto, crypttab offset to 6, and
creates a file in /etc/init which mounts the swap partition automatically as
soon as it's ready.
I beleve
I would also like to add that this attachment is basically just
automating #22's solution to the problem.
** Patch removed: ecryptfs-setup-swap (patched)
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1310058/+attachment/4309697/+files/ecryptfs-setup-swap
** Attachment added:
Hey.
I have a way to work around this in 14.04, 14.10, and 15.04:
COMPLETE FIX -- Ubuntu Utopic Unicorn 14.10 -- The disk drive
dev/mapper/cryptoswap1 is notready yet or not present (Also works for
14.04 and 15.04)
https://gist.github.com/v6/42a46943d1a50aa4fd66
--
You received this bug
I'm in the same situation as Ryokenau.
Back to Dekker500's comment #19, does this only occur when you check the
installer options for encrypted filesystem and encrypted home?
In other words, if you run the installer and select Erase disk and install
Ubuntu and check Encrypt the new Ubuntu
A note of warning:
Without swap, you are used to your laptop suspending to RAM when closing
the lid.
@Wetware Random Number Generator (tnrng)
wrote on 2014-10-10: #22
My final solution to this problem:
This causes laptops to try to hibernate when you close the lid. Failing.
Losing all
About power management settings being ignored, please ask on the forum
of Ubuntu (or the distro you are using) or open a new bug. It should be
unrelated to this bug, you just never saw this problem because you were
never able to hibernate at all.
That hibernate fails, is yet another different
As for #17, in my experience swap was activated sometimes, but not
always, during reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after reboot
To
What happened on Trusty was that cryptswap started using UUID instead of
/dev/sdXY names, and the encryption with a random key overwrites the
partition's UUID unless an offset in crypttab is used. So I wouldn't tag
it as a duplicate of a Precise bug, a whole new problem was created by
switching to
Yes, Albert, you are right. My last precise/cryptab backup says:
cryptswap1 /dev/sdaX /dev/urandom swap,cipher=aes-cbc-essiv:sha256
My problem with trusty seems to be two different bugs happening at the
same time. The first, the UUID problem, that is solved with offset = 6
mkswap, and the
I would keep the two problems in separate bugs, since they do not have
the same cause. This is the bug for the problems with the partition UUID
and the crypttab file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, I've seen a similar bug in Precise for quite a long time:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/571682
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/798086
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/953875
Ubuntu Trusty 14.04.1
$ free --human
total
Mem: 15.7G
-/+ buffers/cache: 985M
Swap: 0.0B
$ swapon --summary
FilenameTypeSizeUsedPriority
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-
My final solution to this problem:
DON'T DISABLE /etc/init.d/cryptdisks-early !
1. DEACTIVATE AUTOMATIC MOUNTING OF CRYPTSWAP1:
Modify /etc/fstab changing the line:
/dev/mapper/cryptswap1 none swap sw 0 0
to
/dev/mapper/cryptswap1 none swap noauto,sw 0 0
and modify /etc/crypttab changing
** Changed in: ecryptfs-utils (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after reboot
To manage notifications
Ouch. This was painful to resolve.
The workarounds proposed do not work out of the box when encountered
after a default installation of 14.04.01 using encrypted fs and home
directory. Under those conditions, the encrypted swap is named ubuntu
--vg-swap_1. Following the instrucions in post 3, 9,
@ syscon-hh
I can confirm your workaround #3.
UUID alongside offset=8 is working well in my case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after
** Also affects: ecryptfs
Importance: Undecided
Status: New
** No longer affects: ecryptfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after
I followed through all the comments, but I've still run into problems
after rebooting.
Comment #3 by syscon-hh https://bugs.launchpad.net/ubuntu/+source
/ecryptfs-utils/+bug/1310058/comments/3 and Albert's detailed
instructions
Alberts hint in #9 is correct. I've just fixed this issue on my system:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/953875/comments/17
Most verbose and explanatory comment:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1301383/comments/6
--
You received this bug
Hello everyone, I reached here from bug Bug #1301383.
I'd like to know if this issue is gonna be adressed by the time 14.04.1 comes
out, since installing it as is today doesn't enable the SWAP partition...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@ syscon-hh: or did you mean offset=8,skip=0? I will test that too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after reboot
To manage notifications
@ syscon-hh: I do not see any difference using it with offset=8 or
offset=8,skip=0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after reboot
To manage
@ Albert - both options should be used alternatively only:
* offset=8
or
* skip=8
never both in one line.
for further Informations see man cryptsetup - options
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ syscon-hh: in that case, offset=8 works, skip=8 does not. So offset=8
it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after reboot
To manage
Turns out Raring does not use UUID's here but /dev/sdXY names. That
explains why it used to work (and silently the mint 16 system on sdb
here has been using the swap of the hot-pluggable sda drive with trusty-
based mint 17 on it...)
--
You received this bug notification because you are a member
@ syscon-hh: offset=8 appears to work, skip=8 does not help to preserve
the UUID after a reboot (skip without a value is ignored by
cryptdisks_start).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Trusty, blkid is also unable to read the UUID of a swap partition of a
Raring system, while that swap is working fine on Raring.
I will check tomorrow what blkid does on Raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@syscon-hh: I hope to be able to test your 'skip' option tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Title:
ecryptfs-setup-swap hints after reboot
To manage notifications about
This bug also affected me with Ubuntu 14.04 and encrypted home-
directory. The swap partition existed but was not mounted as a crypted
swap.
My workaround:
Changing /etc/crypttab in (e.g.):
#cryptswap1 UUID=a81fe18e-0f2a-4571-adeb-a80d57015549 /dev/urandom
swap,cipher=aes-cbc-essiv:sha256
I had the same problem after installing Kubuntu 14.04 64bit. During the
installation process I mounted an existing home partition encrypted with
ecryptfs. Result: The swap partition was not available/mounted. After
manually implementing syscon-hh's solution in the first post, all is
well.
--
You
I should have added that sudo blkid reported a different UUID for the
swap partition than the one used in /etc/crypttab. Replacing that one
with the UUID reported by blkid did not solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
A possible workaround inside the script /usr/bin/ecryptfs-setup-swap
could be:
***
# Add crypttab entry
echo cryptswap$i UUID=$uuid /dev/urandom
swap,offset=8,cipher=aes-cbc-essiv:sha256 /etc/crypttab
***
Please test the supplement offset=8 as a sufficient space to avoid the
UUID
** Description changed:
After changing the the script
- * /usr/bin/ecryptfs-setup-swap
+ * /usr/bin/ecryptfs-setup-swap
* from old version with:
*
- # Add crypttab entry
- echo cryptswap$i $swap /dev/urandom swap,cipher=aes-cbc-essiv:sha256
/etc/crypttab
+ #
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ecryptfs-utils (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
52 matches
Mail list logo
