sdb1p1 shows that it has been created as LVM. However, when I try to create a physical volume with pvcreate /dev/sdb1 command so that I can be able to create logical volumes: the output is: Can't open /dev/sdb1 exclusively. Mounted filesystem?

Please help, I am still a newbie!.

This is the output on my screen


Device Boot Start End Blocks Id System
/dev/sdb1p1 63 16064 8001 8e Linux LVM

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
[root@Angels ~]# vgcreate /dev/sdb1
Please enter a physical volume path
Run `vgcreate --help' for more information.
[root@Angels ~]# pvcreate /dev/sdb1
Can't open /dev/sdb1 exclusively. Mounted filesystem?

Which of those recommendations did you follow? There is apparently something in use on /dev/sdb the caused the automatic loading of the new partition table to fail. The output from "lsblk -f /dev/sdb" (run as root) might be helpful. Wrap it in [CODE] ... [/CODE] tags, please, to preserve formatting.

I rebooted the system with partprobe and init 6 but it did not help. I will try your suggestion. thanks.

I ran the command above "lsblk -f /dev/sdb" and it is not showing up LVM has been created.

This is the screen:

sdb
├─sdb1 ext4 4ba75c2b-55d4-44c3-a25b-a3aa8a0e92ed /newday
├─sdb2 LVM2_member BWqQLM-UiKd-0OMj-FLpZ-6pJ9-jUAG-A0PfAv
│ └─vg01-lv01 (dm-1)
ext4 551e026d-89a9-43c1-b735-5602998eaa8b /timeless
├─sdb3 LVM2_member fHYRKf-u40n-3LQ7-7uD5-aENa-M1Jk-nHQmxV
│ └─vg02-lv02 (dm-0)
ext4 3b2594e3-74fb-4979-a352-9e309a612f3c /today
└─sdb4 ext4 0db5f476-5299-4040-9e32-ae2d7b391211 /testfile

Well, that's pretty obvious. Partition sdb1 has an ext4 filesystem that is currently mounted on /newday. You can't convert it to an LVM physical volume without unmounting it, and that conversion would destroy the current content.

That's presumably not what you intended, so just what are you trying to do? Taking an existing, formatted partition and making it part of an LVM volume group is not a simple process.

In addition, a device ID of /dev/sdb1p1 usually means you created a partition within a partition. Most likely caused by using the command fdisk /dev/sdb1 instead of fdisk /dev/sdb. This is why lsblk did not show /dev/sdb1 as LVM.

Hi Tinatach,

Welcome to LQ!