md126 rather than UUID

Package: grub-common; Maintainer for grub-common is (unknown); Source for grub-common is src:grub2.

Reported by: rm.riches@jacob21819.net

Date: Tue, 3 Nov 2020 04:48:02 UTC

Severity: critical

Tags: debian

Merged with 519

Found in version 2.02~beta3-5+deb9u2

Fixed in version 2.06-3

Done: Mark Hindley <mark@hindley.org.uk>

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#518: possible related to check for LVM
Reply-To: "Robert M. Riches Jr." <rm.riches@jacob21819.net>, 518@bugs.devuan.org
Resent-From: "Robert M. Riches Jr." <rm.riches@jacob21819.net>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: devuan-dev@lists.dyne.org
X-Loop: owner@bugs.devuan.org
Resent-Date: Wed, 04 Jan 2023 04:06:02 +0000
Resent-Message-ID: <handler.518.B518.167280507222179@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: followup 518
X-Devuan-PR-Package: grub-common
X-Devuan-PR-Keywords: 
References: <160437773675.19278.9973454300726259478.reportbug@one.localnet>
Received: via spool by 518-submit@bugs.devuan.org id=B518.167280507222179
          (code B ref 518); Wed, 04 Jan 2023 04:06:02 +0000
Received: (at 518) by bugs.devuan.org; 4 Jan 2023 04:04:32 +0000
Delivered-To: bugs@devuan.org
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 04 Jan 2023 04:04:32 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id FAkeIsH6tGMtcwAAmSBk0A
	(envelope-from <rm.riches@jacob21819.net>)
	for <bugs@devuan.org>; Wed, 04 Jan 2023 04:04:17 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 7A5991267; Wed,  4 Jan 2023 04:04:17 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=136.175.108.248; helo=mail-108-mta248.mxroute.com; envelope-from=rm.riches@jacob21819.net; receiver=<UNKNOWN> 
Received: from mail-108-mta248.mxroute.com (mail-108-mta248.mxroute.com [136.175.108.248])
	by email.devuan.org (Postfix) with ESMTPS id B62E5CCC
	for <518@bugs.devuan.org>; Wed,  4 Jan 2023 04:04:12 +0000 (UTC)
Received: from mail-111-mta2.mxroute.com ([136.175.111.2] filter006.mxroute.com)
 (Authenticated sender: mN4UYu2MZsgR)
 by mail-108-mta248.mxroute.com (ZoneMTA) with ESMTPSA id 1857af35b9f000011e.001
 for <518@bugs.devuan.org>
 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256);
 Wed, 04 Jan 2023 04:04:07 +0000
X-Zone-Loop: 05d79d749034f5e4ea45662025d6086dd99350443458
X-Originating-IP: [136.175.111.2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=jacob21819.net; s=x; h=From:Message-Id:Subject:To:Date:Sender:Reply-To:Cc:
	MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID:
	Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc
	:Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:
	List-Subscribe:List-Post:List-Owner:List-Archive;
	bh=r7RlqOLlyP6qiE9fF+RMTw99KujT19zd2oSkegCh80s=; b=VbuC/XR7wzC15xC+Y49B5Q4DJj
	kiXuxLcvcbC8wsFH35oa4+8kHsbgLVtv9A/3rWaj1rNqiocEvhvkiSEkNFRMSLhHHPDwZg+Kp+Qra
	xAFdOOB7Tzu0CxheRnHInrnRw/QczCzHwYqKLCSB7yGYMauDC0vjNLOCfxa1JlkSJkZqIHL1STd2P
	Th6g8ub1K2OufXQul7my3z2EtrvCRsBLG6VPLWQRHRtSpazyqaY0H/pFK8j1PpzvgwWdm6xHG2dVP
	o0EnpRt3brSjuWlElfRR/yE/MYr0bKSnv5gHH/wNEgBxCubK5KTgOhV4l76W5sN1y3M1IDKVz+5Fm
	5StdNjug==;
Date: Tue, 03 Jan 2023 20:04:03 -0800
To: 518@bugs.devuan.org
User-Agent: s-nail v14.9.22
Message-Id: <20230104040403.65F2C283920@one.localnet>
From: "Robert M. Riches Jr." <rm.riches@jacob21819.net>
X-Authenticated-Id: rm.riches@jacob21819.net

After a year or so of being affected by this bug, I discovered
a message that appears while doing "apt-get upgrade" for a new
kernel.  The message says that LVM was found to not be installed
or running, and the Grub install/update process is switching to
raw device mode.  It may well be that the switch to raw device
mode is what is causing it to overlook /dev/md12*.

I'm currently running a freshly-installed Chimaera and using
LVM, and have not seen this bug manifest on that installation.

Send a report that this bug log contains spam.

Devuan bug report logs - #518 grub-common: grub.cfg is written with /root=/dev/md127 or /root/dev/md126 rather than UUID

Devuan bug report logs - #518
grub-common: grub.cfg is written with /root=/dev/md127 or /root/dev/md126 rather than UUID