Need advice: lsblk dreams up partitions? #2178
Replies: 4 comments 2 replies
-
Afaik these partitions should come from the kernels partition parser itself, not util-linux.
Try Are these partitions detected on every boot/hotplug? |
Beta Was this translation helpful? Give feedback.
-
lsblk does not parse anything; it reads all info from /sys. The kernel displays partitions as a subdirectory (e.g. see |
Beta Was this translation helpful? Give feedback.
-
I just found references to this bug in the kernel: https://bugzilla.kernel.org/show_bug.cgi?id=211015, https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1531404 |
Beta Was this translation helpful? Give feedback.
-
I just worked around my issue by converting my LUKS2 pbkdf from
Apparently that changed the LUKS header enough so that Atari is no longer confused. I'm closing this, thanks for your input everyone! |
Beta Was this translation helpful? Give feedback.
-
I've got an SSD that I use LUKS2 on, and in that LUKS there is a filesystem (directly, without partition table, as I believe). However, lsblk prints this:
Now I wonder where do
/dev/sdb1
and/dev/sdb2
parts stem from? And where do their capacities live? As you can see the 3,6T is taken up by/dev/mapper/sdb_crypt
already, so I'd say it's impossible to fit another 240,9G and 690,7G in.I have two HDDs in the same system which I created the same way (I believe), but years earlier. They do not exhibit this behavior, e.g.
This is how I'd expect
/dev/sdb
to look like too.Fdisk doesn't show any partition tables:
Parted doesn't seem to find a partition table either:
So where do the ghost partitions come from? And how do I get rid of them in a safe way?
I have xxx'ed out some irrelevant data.
Beta Was this translation helpful? Give feedback.
All reactions