** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1506139
Title:
15.10beta crashes encrypted swap partit
I'm also having this issue with Ubuntu 16.04.2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1506139
Title:
15.10beta crashes encrypted swap partition
Status in systemd
** Changed in: systemd (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1506139
Title:
15.10beta crashes encrypte
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
Further observations:
I meanwhile figured out three modes:
1) putting the swap flag into /etc/crypttab -> crashes the partition
every now and then, but not always.
2) removing the flag from /etc/crypttab, but keeping it in /etc/fstab and
keeping it in
/etc/initramfs-tools/conf.d/resume:
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1506139
Title:
15.10beta crashes encrypted swap partition
OK, I've finally found the problem(s). Was a bunch of little nasty
problems, that's why it was difficult to debug.
1)
The 15.10 beta installer had filled /etc/initramfs-tools/conf.d/resume
with
RESUME=UUID=a18e9ec9-1255-4dda-8298-8e10bdbe6835
which is never updated after first installation. Si
More info from the source code of systemd-cryptsetup:
else if (streq(option, "luks"))
arg_type = CRYPT_LUKS1;
...
} else if (STR_IN_SET(option, "plain", "swap", "tmp"))
arg_type = CRYPT_PLAIN;
so the swap argument overwrites the luks argument and resets the ecr
OK,
I have debugged this down and got big steps further in identifying the
problem.
An important step for debugging was to learn how to debug systemd.
http://freedesktop.org/wiki/Software/systemd/Debugging/
was quite helpful, that
systemctl enable debug-shell.service
helps a lot. Aft
I've noticed something and I guess that both my problems - swap problem
and systemd hanging while booting - are closely related.
Why?
The system does not hang at boot, when I choose the recovery mode from
grub, and in the recovery mode select "network" to enable networking.
Important: before act
> This time, sda2 has survived as a valid and operating luks partition.
Then the journal won't show the bits where it destroys it (but it's
still useful for comparison). I'd like to see a journal when it does
destroy the device. One way would be to just keep rebooting until that
happens.
However,
OK, freshly rebootet. This time, sda2 has survived as a valid and
operating luks partition.
crypttab and fstab not changed.
# swapon -s
FilenameTypeSizeUsedPriority
/dev/dm-1 partition 163082200
OK, I am back at my home machine: The problem occured again, the machine
destroyed again luks on /dev/sda2.
Furthermore, I have another problem: When doing a regular boot, but boot
process hangs after systemd listed the names of several services (in
most cases networking.service is the last printe
> From your description it sounds like something is destroying sda3
itself (i. e. the outer encrypted LUKS partition), *not* the unencrypted
sda3_crypt, right?
Right.
I've created the partitions with the graphical xubuntu installer from
xubuntu 15.10 beta 1 cdrom put on a usb stick, and created b
I tried to reproduce this on today's ubuntu desktop amd64 image
(20151014). I think I set up partitions like you described: 1 GB /boot
on partition 1, 1 GB LUKS on partition 2 (and put swap on vda2_crypt), 8
GB LUKS on partition 3 (and put btrfs / on vda3_crypt).
Both during install and after a fe
Well, life would be much easier if there was some usable documentation
about what's going on within systemd.
By the way, I did not put in that 'swap' option manually, it was
inserted by the xubuntu 15.10 beta installer on cdrom/usb image. If you
choose to encrypt a partition and put a swap inside,
The systemd package has taken over the handling of /etc/crypttab at boot
from cryptsetup (without much coordination AFAICS), and it sounds like
its interpretation of the crypttab is buggy.
"swap" is not synonymous with "random", and should not result in the
device being clobbered, which is what is
17 matches
Mail list logo
