From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Sisyphus mailing list <sisyphus@lists.altlinux.org>
Subject: Re: [sisyphus] Ядро 5.4
Date: Sat, 28 Dec 2019 16:16:56 +0300
Message-ID: <20191228131656.GB25047@altlinux.org> (raw)
In-Reply-To: <CAPQ_kbKiHSMaaSxFXaNk_KJ5AqsCc_bf3vVTJ1ZaMrZnMYSadw@mail.gmail.com>
On Sat, Dec 28, 2019 at 02:04:37PM +0100, Pavel Nakonechnyi wrote:
> Приветствую,
>
> Сборка ядра 5.4.6-un-def-alt1 не может расшифровать раздел LUKS, что
> не составляет проблем для предыдущих версий (5.3.х un-def) и текущего
> 4.19 std-def.
>
> Ошибка:
> device-mapper: reload ioctl on failed: No such file or directory
> ERROR(luks): /dev/nvme0n1p6: unable to activate LUKS (rc=1)
>
> Информация о разделе:
> $ sudo cryptsetup status nvme0n1p6-luks
> /dev/mapper/nvme0n1p6-luks is active and is in use.
> type: LUKS1
> cipher: aes-cbc-essiv:sha256
> keysize: 256 bits
> key location: dm-crypt
> device: /dev/nvme0n1p6
> sector size: 512
> offset: 4096 sectors
> size: 614395904 sectors
> mode: read/write
>
> Требуется ли баг в багзилле? Нужна ли дополнительная информация?
Первое, что приходит в голову - это "strace -Z -y -eioctl"
для той операции, которая не прошла.
Только не присылайте, пожалуйста, вывод этой команды, если в нём есть
данные, компрометирующие luks-раздел.
--
ldv
prev parent reply other threads:[~2019-12-28 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 9:45 Aleksey Novodvorsky
2019-12-15 20:14 ` Шенцев Алексей
2019-12-15 20:22 ` Michael Shigorin
2019-12-15 20:44 ` Шенцев Алексей
2019-12-28 13:04 ` Pavel Nakonechnyi
2019-12-28 13:06 ` Michael Shigorin
2019-12-28 15:42 ` Pavel Nakonechnyi
2019-12-28 16:15 ` Dmitry V. Levin
2019-12-28 16:31 ` Dmitry V. Levin
2019-12-28 17:44 ` Pavel Nakonechnyi
2019-12-28 18:00 ` Dmitry V. Levin
2019-12-28 19:27 ` Pavel Nakonechnyi
2019-12-28 13:16 ` Dmitry V. Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191228131656.GB25047@altlinux.org \
--to=ldv@altlinux.org \
--cc=sisyphus@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Sisyphus discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
public-inbox-index sisyphus
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git