• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

10.4.4 Disk Space Reporting Errors

O

OCSHOSTING

Guest
I thaught id pop on here before i call up my vendors..

We are currently about to start moving 30 control pannel servers over to plesk, but we have hit a snag, after purchasing 16 of the finest Quad Core AMD Servers, plesk has thrown a wobbler.

Server: Cent OS6 - Plesk Pannel 10.4.4
AMD Quad Core 2.5Ghz
8GB DDR
2 x 750GB SATA Software RAID 1

But as you can see from the attachment plesk has other ideas, and we just discovered CentOS knows whats inside....

[root@s16119868 ~]# fdisk -l

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 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: 0xf1049cec

Device Boot Start End Blocks Id System
/dev/sdb1 1 487 3911796 fd Linux raid autodetect
/dev/sdb2 488 731 1959930 82 Linux swap / Solaris
/dev/sdb3 732 121601 970888275 fd Linux raid autodetect

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 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: 0x64a12fa0

Device Boot Start End Blocks Id System
/dev/sda1 1 487 3911796 fd Linux raid autodetect
/dev/sda2 488 731 1959930 82 Linux swap / Solaris
/dev/sda3 732 121601 970888275 fd Linux raid autodetect

Disk /dev/md3: 994.2 GB, 994189508608 bytes
2 heads, 4 sectors/track, 242722048 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md3 doesn't contain a valid partition table

Disk /dev/md1: 4005 MB, 4005560320 bytes
2 heads, 4 sectors/track, 977920 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table

Disk /dev/mapper/vg00-usr: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 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/vg00-usr doesn't contain a valid partition table

Disk /dev/mapper/vg00-var: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 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/vg00-var doesn't contain a valid partition table

Disk /dev/mapper/vg00-home: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 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/vg00-home doesn't contain a valid partition table




Any Suggestions???? Same happens when we reimage to CentOS5 with Panel 10.4.4 X86_64 as it does on CentOS 6

Pleaseeee tell me i dont need to have all 16 servers pulled and looked at PLEASEEEEEE

Cheers
 

Attachments

  • pleskissue.png
    pleskissue.png
    191.7 KB · Views: 4
Im asuming your server is provided by 1and1, based on the structure of the partitions.

Starting from that sumption.

do df -h

that should give you the volumes, size, and where it is mapped.

after doing that do

lvs

this command will show you how much space is assigned to each LV volume.

then do

pvs

to see how much free space you have available to assign to your LV!

next you need to do is assign that free space to your LV

we do this by using the lvextend tool, lvextend stands for "Logical Volume Extend"

as a recommendation, i would tell you to have /usr with at least 10 GB

so do

lvextend -L +6GB /dev/mapper/vg00-usr

this will "ADD" 6 GB to the LV(Logical Volume) /usr

then do again pvs

to check how much free space it has now.

and add the remaining space to /var

lvextend -L +RESTGB /dev/mapper/vg00-var

then now do lvs to confirm the changes.

lvs

when thats done, we have to force the growth of the LVs, to do that, we use xfs_growfs (if you use xfs partitions) or resize2fs (if you use ext4 partitions)

if you use xfs:

xfs_growfs /var
wait until its done, then
xfs_growfs /usr

if you use ext4:

resize2fs /dev/mapper/vg00-var
wait until its done(it takes a while if you are adding lots of space), then
resize2fs /dev/mapper/vg00-usr

then you can check your changes with

df -h

you should now have your hard drive space (in logical volumes) assigned correctly.

restart plesk, or even the servers, and plesk should report the correct ammount of space assigned to each unit.
 
Last edited:
Back
Top