From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 215353] New: VMWare LVM partitions not recognized, sees base disk, fails to Boot
Date: Fri, 17 Dec 2021 20:36:40 +0000 [thread overview]
Message-ID: <bug-215353-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215353
Bug ID: 215353
Summary: VMWare LVM partitions not recognized, sees base disk,
fails to Boot
Product: SCSI Drivers
Version: 2.5
Kernel Version: 5.4.126+
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: DC395X
Assignee: scsi_drivers-dc395x@kernel-bugs.osdl.org
Reporter: richr410@yahoo.com
Regression: No
Hello,
VMWare LVM partitions are not recognized by the 5.4.126+ LT kernels; it sees
the base /dev/sda disk, but thats its, stalls, fails to Boot trying to access
"/dev/mapper/...."
Kernels 5.4.125 and prior DO WORK, but 5.4.126+ DO NOT.
I have been able to isolate the kernel failing to commit
"1e209effe36cbf0a939844bcf9defd3fe1e2f593" in LT kernel 5.4.126.
[And Yes the "rd.lvm.lv=" and VG/LV names match the grub line (ie. lvs -o
vg_name,lv_name)]
So commit "1e209effe36cbf0a939844bcf9defd3fe1e2f593" BREAKS kernel recognition
of VMWare LVM partitions (but yes kernel DOES see /dev/sda but thats it).
This is on ESX 6.7.
Thanks
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2021-12-17 20:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 20:36 bugzilla-daemon [this message]
2021-12-17 21:00 ` [Bug 215353] VMWare LVM partitions not recognized, sees base disk, fails to Boot bugzilla-daemon
2021-12-20 19:43 ` bugzilla-daemon
2022-01-19 20:06 ` bugzilla-daemon
2022-01-19 21:34 ` Martin K. Petersen
2022-01-19 20:07 ` bugzilla-daemon
2022-01-19 20:07 ` bugzilla-daemon
2022-01-19 20:33 ` bugzilla-daemon
2022-01-19 21:35 ` bugzilla-daemon
2022-01-19 22:48 ` bugzilla-daemon
2022-01-19 23:20 ` bugzilla-daemon
2022-01-21 20:10 ` bugzilla-daemon
2022-02-01 18:15 ` bugzilla-daemon
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=bug-215353-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.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).