I also applies when you have a swap partition and root is luks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771962
Title:
hanging at boot for about 30 seconds since upgrade to bionic
To manage n
Note that this also applies if your swap is on ZFS. Ubuntu will attempt
to use it automatically and cause a 30 second delay as the swap
partition will not be available during early boot. Ie.
I: The initramfs will attempt to resume from /dev/zd0
I: (UUID=a0c4e220-8b9f-447b-b2e2-d2abeb2f6c39)
I: Set
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.1
---
initramfs-tools (0.130ubuntu3.1) bionic; urgency=medium
* hooks/resume: don't generate RESUME config pointing to randomly-crypted
swap devices. LP: #1771962.
-- Steve Langasek Fri, 08 Jun 2018
21:29:19 -
I have run through the test case as described and confirmed that the
updated initramfs-tools in bionic-proposed eliminates this 30-second
wait in the initramfs. In my test VM, the rootfs is now mounted at 6.8s
(and the swap is activated at 13.0s).
** Tags removed: verification-needed verification
Hello Zwylicht, or anyone else affected,
Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pack
initramfs-tools (0.130ubuntu7) cosmic; urgency=medium
* hooks/resume: don't generate RESUME config pointing to randomly-crypted
swap devices. LP: #1771962.
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because y
** Description changed:
- Since upgrade to Bionic ubuntu is hanging at boot for about 30s. A
- `dmesg` shows
+ [SRU Justification]
+ A regression in initramfs-tools causes it to autogenerate config in the
initramfs saying to resume from any available swap devices, even if the swap
device is ephe
Thanks. This will obviously never work for resume, since the encryption
key is not saved anywhere across boot, so the scripts need to detect
this case and avoid adding a resume setting in this case.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Triaged
--
You recei
Yes, it is randomly-encrypted:
cryptswap1 /dev/sda4 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
On 07.06.2018 07:04, Steve Langasek wrote:
> Thanks. What are the options for /dev/mapper/cryptsetup1 in
> /etc/crypttab? Is this a randomly-encrypted swap partition?
>
--
You received this bug
Thanks. What are the options for /dev/mapper/cryptsetup1 in
/etc/crypttab? Is this a randomly-encrypted swap partition?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771962
Title:
hanging at boot
If I remember correctly resume was set to cryptswap partition. When
doing so again (`RESUME=UUID=xxx`) invocation of `update-initramfs -uk
all` gives
```
W: initramfs-tools configuration sets
RESUME=UUID=9792e199-e275-4547-b9ce-c4e507e8bd5d
W: but no matching swap device is available.
```
The de
If I remember correctly resume was set to cryptswap partition. When
doing so again (`RESUME=UUID=xxx`) invocation of `update-initramfs -uk
all` gives
```
W: initramfs-tools configuration sets
RESUME=UUID=9792e199-e275-4547-b9ce-c4e507e8bd5d
W: but no matching swap device is available.
```
The de
please also provide full dmesg output from a boot in which the problem
has been reproduced.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771962
Title:
hanging at boot for about 30 seconds since up
As I understand, you had an /etc/initramfs-tools/conf.d/resume file on
your system that pointed to an invalid location. When was this file
created? What were its contents? Do you know why the contents were
invalid?
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
This is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447 and
solution is setting `RESUME=none` in `/etc/initramfs-tools/conf.d` as
described in https://askubuntu.com/questions/1029598/xubuntu-18-04
-kernel-takes-long-to-boot
No problem with 16.04 though. Never been.
--
** Tags added: xenial2bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771962
Title:
hanging at boot for about 30 seconds since upgrade to bionic
To manage notifications about this bug go to:
16 matches
Mail list logo
