touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

> 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, there might be a faster and also more useful way. First, stop
only the swap partition and luks device:

   sudo systemctl stop systemd-cryptsetup@sda2_crypt.service

Now /dev/mapper/ should not have sda2_crypt any more, just sda3_crypt
(for the root partition). Then you can run the commands in
/run/systemd/generator/systemd-cryptsetup@sda2_crypt.service manually
with extra debugging:

   sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-cryptsetup attach sda2_crypt /dev/sda2 none luks,swap,discard
   (enter passphrase)
   sudo /lib/systemd/systemd-cryptsetup detach sda2_crypt
   # now check if the signature is still correct:
   sudo blkid -p /dev/sda2

You can try running this several times until it destroys your partition
(FTR, I ran it successfully some 20 times). Does that reproduce the bug
for you? If so, please copy&paste the output from the command cycle that
did the destruction. If not, then I guess it's something else in the
boot process, and then please reboot until it happens and attach the
journal output from this boot.

Thanks!

> Furthermore, I have another problem: When doing a regular boot, but
boot process hangs after systemd listed the names of several services

Please file a separate bug report about that.
/usr/share/doc/systemd/README.Debian.gz describes how to debug such
shutdown hangs. In particular, boot with enabling the debug shell, and
when it hangs switch to it and check for running services and also save
the journal. Thanks!

-- 
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 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm usually using a setup with three partitions on a disk

  Partition 1:  plain ext4 boot partition mounted on  /boot
  Partition 2:  luks-encrypted swap
  Partition 3: luks-encrypted btrfs for /  /home ...

  both mentioned in /etc/crypttab like

  sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
  sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

  
  With several machines I have installed 15.10 beta on and in several cases I experienced the problem that the swap is not activated at boot time and that /dev/disks/by-uuid does not contain a link to the swap partition, and the previously created luks-encrypted swap is destroyed after boot: It is not a luks partition anymore and filled with random (presumably encrypted) bytes without structure. 

  I first thought that this is a problem of the setup process, and
  repaired the swap manually. But then I found the partition destroyed
  again. This happend several times on several machines.

  I am not sure yet what exactly would destroy the partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cryptsetup 2:1.6.6-5ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct 14 18:12:58 2015
  InstallationDate: Installed on 2015-10-08 (5 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab:
   sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
   sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506139/+subscriptions