Logical Volumes (LVM): safe to filter /dev/mmcblk0rpmb?

Omnia hardware Omnia HW tweaks
1

Having just added a SSD, I set up a large partition on it up as a Physical Volume (PV) for LVM.

This gives me more flexibility when adding and resizing swap or mountpoints.

But, I get this
root@turris:~# pvcreate /dev/sda1
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: I/O error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: I/O error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: I/O error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: I/O error
Physical volume “/dev/sda1” successfully created.
root@turris:~#

Before I start messing about LVM filters, I have a couple questions:

  1. AFAICT, mmcblk0rpmb is the eMMC, I suspect I am not allowed to read from it, correct?
  2. is it fine to blacklist /dev/mmcblk0rpmb or do you use LVM in any way for the as shipped OS?

PCFE

2

It should be fine. TurrisOS does not use LVM, it’s just plain BTRFS partition covering the whole eMMC storage.

3

thanks for the info.

I’ve added
filter = [ "r|/dev/mmcblk0rpmb|" ]
inside the devices section of /etc/lvm/lvm.conf and (as expected) lvscan and pvscan no longer complain about /dev/mmcblk0rpmb

1 Like