[ BIENVENIDO | ENCUENTRA O COMPARTE SOLUCIONES ]
I M P O R T A N T E
REGLAS DEL FORO | PROBLEMAS DE INGRESO O CONTRASEÑA | DEEPINES CHANGE LOG | ÚLTIMOS MENSAJES
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.20.0-042000-lowlatency
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead.
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=f83cb128-f058-40f8-b8c0-ff1769a661e3)
I: Set the RESUME variable to override this.
La comunidad de PureOS dio esta respuesta. Simple pero útil:
It shouldn’t cause any troubles, you can try adding "CRYPTSETUP=y" in /etc/cryptsetup-initramfs/conf-hook and see if it will help.
Y si aún tuvieras líos, te dejo el enlace para que consultes esta wiki:
https://tracker.pureos.net/w/troubleshooting/cryptsetup_setting_deprecated/
Solução:
Edite o arquivo /etc/cryptsetup-initramfs/conf-hook.
Descomente o parãmetro #CRYPTSETUP= e coloque o valor y, ficando desta forma:
#
# Configuration file for the cryptroot initramfs hook.
#
#
# CRYPTSETUP: [ y | n ]
#
# Add cryptsetup and its dependencies to the initramfs image, regardless
# of _this_ machine configuration. By default, they're only added when
# a device is detected that needs to be unlocked at initramfs stage
# (such as root or resume devices or ones with explicit 'initramfs' flag
# in /etc/crypttab).
# Note: Honoring this setting will be deprecated in the future. Please
# uninstall the 'cryptsetup-initramfs' package if you don't want the
# cryptsetup initramfs integration.
#
CRYPTSETUP=y
#
# KEYFILE_PATTERN: ...
#
# The value of this variable is interpreted as a shell pattern.
# Matching key files from the crypttab(5) are included in the initramfs
# image. The associated devices can then be unlocked without manual
# intervention. (For instance if /etc/crypttab lists two key files
# /etc/keys/{root,swap}.key, you can set KEYFILE_PATTERN="/etc/keys/*.key"
# to add them to the initrd.)
#
# If KEYFILE_PATTERN if null or unset (default) then no key file is
# copied to the initramfs image.
#
# WARNING: If the initramfs image is to include private key material,
# you'll want to create it with a restrictive umask in order to keep
# non-privileged users at bay. For instance, set UMASK=0077 in
# /etc/initramfs-tools/initramfs.conf
#
Após tudo isso, execute novamente o command:
update-initramfs -u
E seja Feliz com seu deepin/debian.
olução:
Edite o arquivo /etc/cryptsetup-initramfs/conf-hook.
Descomente o parãmetro #CRYPTSETUP= e coloque o valor y, ficando desta forma:
#
# Configuration file for the cryptroot initramfs hook.
#
#
# CRYPTSETUP: [ y | n ]
#
# Add cryptsetup and its dependencies to the initramfs image, regardless
# of _this_ machine configuration. By default, they're only added when
# a device is detected that needs to be unlocked at initramfs stage
# (such as root or resume devices or ones with explicit 'initramfs' flag
# in /etc/crypttab).
# Note: Honoring this setting will be deprecated in the future. Please
# uninstall the 'cryptsetup-initramfs' package if you don't want the
# cryptsetup initramfs integration.
#
CRYPTSETUP=y
#
# KEYFILE_PATTERN: ...
#
# The value of this variable is interpreted as a shell pattern.
# Matching key files from the crypttab(5) are included in the initramfs
# image. The associated devices can then be unlocked without manual
# intervention. (For instance if /etc/crypttab lists two key files
# /etc/keys/{root,swap}.key, you can set KEYFILE_PATTERN="/etc/keys/*.key"
# to add them to the initrd.)
#
# If KEYFILE_PATTERN if null or unset (default) then no key file is
# copied to the initramfs image.
#
# WARNING: If the initramfs image is to include private key material,
# you'll want to create it with a restrictive umask in order to keep
# non-privileged users at bay. For instance, set UMASK=0077 in
# /etc/initramfs-tools/initramfs.conf
Após tudo isso, execute novamente o command:
update-initramfs -u
E seja Feliz com seu deepin/debian.