Not all disk space available after installation

A

audunms

Guest
Hello, and sorry for what is probably a very newbie question.

I installed Proxmox 2.1 on a single server, whith 2 SATA hard drives installed.

After installing, I added the second hard drive with "pvcreate /dev/sdb", "vgcreate satadisk2 /dev/sdb" and added a LVM Group in the web interface where I selected the "satadisk2" as Volume Group. This second hard drive displays all the space on the physical disc as available:
Capture.PNG

However, the first disk (local), which was selected under installation, displays only half of the disk's around 170GB as available:
Capture2.PNG

In case this is of any help, here is the output when running fdisk -l via ssh:
Disk /dev/sda: 180.0 GB, 180045766656 bytes
255 heads, 63 sectors/track, 21889 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: 0x000268b6


Device Boot Start End Blocks Id System
/dev/sda1 * 1 66 523264 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 66 21890 175301632 8e Linux LVM


Disk /dev/sdb: 180.0 GB, 180045766656 bytes
255 heads, 63 sectors/track, 21889 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/sdb doesn't contain a valid partition table


Disk /dev/dm-0: 44.8 GB, 44828721152 bytes
255 heads, 63 sectors/track, 5450 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/dm-0 doesn't contain a valid partition table


Disk /dev/dm-1: 22.4 GB, 22414360576 bytes
255 heads, 63 sectors/track, 2725 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/dm-1 doesn't contain a valid partition table


Disk /dev/dm-2: 95.1 GB, 95089065984 bytes
255 heads, 63 sectors/track, 11560 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/dm-2 doesn't contain a valid partition table


Greatly appreciate any help.
 
the gui shows just the size of your root partition.

to check and understand your disk layout, see the following commands:

Code:
df -h

lvs

pvs
 
Thank you for your answer.

From what "df -h" gives me, is it correct to assume that ~88GB is available for ISO's and Virtual Machines (/dev/mapper/pve-data?), and the rest is used for temp files + host usage (/dev/mapper/pve-root?)? If so, are the amount of disk dpace used for the latter two sensible, or could/should they be adjusted?



Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-root 42G 4.0G 36G 11% /
tmpfs 16G 0 16G 0% /lib/init/rw
udev 16G 248K 16G 1% /dev
tmpfs 16G 16M 16G 1% /dev/shm
/dev/mapper/pve-data 88G 3.2G 85G 4% /var/lib/vz
/dev/sda1 495M 56M 415M 12% /boot
/dev/fuse 30M 12K 30M 1% /etc/pve
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!