Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] Linux 5.4.10_2 can't boot
Date: Sat, 11 Jan 2020 15:18:03 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18233@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

New issue by Eluminae on void-packages repository

https://github.com/void-linux/void-packages/issues/18233

Description:
Hello there ! Got a little problem today

In one of my machines, linux 5.4.10_1 boot but not the 5.4.10_2

I don't think this is a grub problem cause I still can boot 5.4.10_1 but maybe the machine setup is important.

This machine is mounted using LVM on LUKS. It is probably related cause my other pc still boot.

```
$ lsblk
NAME
sda
└─crypthdd
  └─hddvg-home
nvme0n1
├─nvme0n1p1
├─nvme0n1p2
└─nvme0n1p3
  └─luks-4c477d16-5ff7-4b97-9c23-d0ba73d71e7e
    ├─ssdvg-root
    └─ssdvg-swap
```
```
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=4 slub_debug=P pci=nomsi page_poison=1 rd.vconsole.keymap=fr rd.lvm=1 rd.luks.uuid=4c477d16-5ff7-4b97-9c23-d0ba73d71e7e rd.luks.crypttab=1 rd.luks.timeout=180 boot=UUID=1b652115-ca90-4ba4-819f-4bd79bcc00c7 root=UUID=973685ed-ac1e-48fa-bd82-d156cc80a12a resume=UUID=ac8e07e0-257a-484e-8a41-ec2b76251ea5"
```

I normally am prompted for the luks key and then, the key for the second disk is available to mount the home partition. 

I don't really know what informations you should need. Feel free to ask !

Ty a lot, kiss

             reply	other threads:[~2020-01-11 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-11 14:18 voidlinux-github [this message]
2020-01-12 16:54 ` voidlinux-github
2020-01-13  7:31 ` voidlinux-github
2020-01-16 12:36 ` voidlinux-github
2020-01-16 12:36 ` [ISSUE] [CLOSED] " voidlinux-github

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18233@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).