mjhjmtu

This particular system is acting peculiar and i've not seen this before. System is running CentOS and is a VM on VMWare. I increased the space on the drive from 100GB to 130GB. When I went in to the system, I can see the new space when runnning fdisk but, I dont see any partitions on /dev/sdb.

Disk /dev/sdb: 139.6 GB, 139586437120 bytes
255 heads, 63 sectors/track, 16970 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/sys-swap: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/sys-root: 106.3 GB, 106266886144 bytes
255 heads, 63 sectors/track, 12919 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Running fdisk on that disk returns:

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x8926c36c.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
 switch off the mode (command 'c') and change display units to
 sectors (command 'u').

Command (m for help): p

Disk /dev/sdb: 139.6 GB, 139586437120 bytes
255 heads, 63 sectors/track, 16970 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8926c36c

Device Boot Start End Blocks Id System

There are no partitions listed there at all. Even if its VG, I still normally see 8e as the type and some info on it. When I run vgdisplay it also looks a little weird. Doesn't seem to give me the full path and just lists the VG as "sys".

VG Name sys
System ID 
Format lvm2
Metadata Areas 1
Metadata Sequence No 12
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 99.97 GiB
PE Size 32.00 MiB
Total PE 3199
Alloc PE / Size 3199 / 99.97 GiB
Free PE / Size 0 / 0 
VG UUID E3jBIZ-BbxE-CnJg-IwBi-mXaP-xrN2-JbjXmY 

Am I just missing or forgetting something and this is totally normal and I should just go through fdisk and create and new partition, run pvcreate and extend it with vgextend, etc?

Thanks in advance for your time! I'm not sure if im missing something... just looks weird. Also, here is mount to see the drive types:

/dev/mapper/sys-root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs 
(rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

Was able to extend the volgroup by creating a new disk on the VM and handling it all normally with fdisk, pvcreate, etc.