Archive for the ‘VMWare Server’ Category

Increasing the Drive Space of an SME Server – a crash course in LVM

Thursday, November 11th, 2010

My adventurous rebuild of my home server continues.

I made a mistake when rebuilding my VMWare Server virtual machine, I used the default 8GB partition size, which is too small, even though it only holds work files for a couple of users.

I had most things back up and running, so it was time to fix my disk space error.  This turned into a crash course in Logical Volume Manager (LVM).

DISCLAIMER: I take no responsibility for any actions that you take on your own systems.  As I mentioned, this is all new to me, and it is very possible that I have made mistakes. Follow at your own risk. I’m not even sure that I have all the terminology correct.

The following are somewhat edited  notes that I took as I went along.

First, some terminology, mostly from:

  • LVM abstracts disk space as seen by the operating system from physical disks.
  • A Volume Group is the highest level abstraction used within the LVM. It gathers together a collection of Logical Volumes and Physical Volumes into one administrative unit.
  • A physical volume is typically a hard disk, though it may well just be a device that ‘looks’ like a hard disk (eg. a software raid device).
  • Equivalent of a disk partition in a non-LVM system. The LV is visible as a standard block device; as such the LV can contain a file system (eg. /home).

General overview:  Create disk space in VMWare (or add physical disk space in a non virtualized environment).  Create a new partition. Join that partition to a Logical Volume to make the Logical Volume larger. Expand the Linux partition to fill it’s now bigger Logical Volume.

The steps that I took:

  • Expand the VMWare virtual disk with the VMWare tool (Google for it).  The non-VM equivalent would be to clone an old, smaller drive onto a new, larger drive.
  • create a new disk partition on the VMWare “physical” disk.
    • /sbin/fdisk /dev/sda
    • n [new]
    • p [primary – I wonder if E would have been a better long term choice]
    • 3 [I think there are two already]
    • defaults for size
    • w [write]
    • /sbin/shutdown -r now
  • create the physical partition (LVM)
    • /sbin/pvcreate /dev/sda3
  • that worked:
— Physical volume —
PV Name               /dev/md2
VG Name               main
PV Size               7.90 GB / not usable 23.31 MB
Allocatable           yes (but full)
PE Size (KByte)       32768
Total PE              252
Free PE               0
Allocated PE          252
PV UUID               n2Qp6p-Afuc-CE2F-rtdi-7ypO-wnLw-rXtb0J
“/dev/sda3” is a new physical volume of “12.00 GB”
— NEW Physical volume —
PV Name               /dev/sda3
VG Name
PV Size               12.00 GB
Allocatable           NO
PE Size (KByte)       0
Total PE              0
Free PE               0
Allocated PE          0
PV UUID               nc37cI-D4hZ-sR8K-XB7r-Cxh4-N8vn-SecZIf
  • Now,  I add the physical volume to the Volume Group (this was helpful: I have a volume group “main” already. I have to add the physical partition to it.
# /usr/sbin/vgextend main /dev/sda3
Volume group “main” successfully extended
  • Now, add I have to extend the Logical Volume to use up all the new space in the Volume Group (see:
    • # /usr/sbin/lvresize -l +100%FREE main/root
Extending logical volume root to 19.34 GB
Logical volume root successfully resized
  • Ugh.  I still have to resize the EXT3 partition. 
    • #/usr/sbin/ext2online -d -v /dev/main/root
  • Phew. It looks like I have a 20G root volume that works.
# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/main-root20G  6.3G   12G  35% /
/dev/md1               99M   16M   78M  18% /bootnone                  125M     0  125M   0% /dev/shm
Wow, LVM sure adds a lot of extra steps.  But, in the end, it’s pretty powerful.  It probably cost me time for my simple home network, but someday, I’m sure that I’ll run into LVM again.

Fixing the Time in an SME Server Running in VMWare Server 2

Monday, November 8th, 2010

First, a PSA: Please do a backup of all your data, if you haven’t done one in the last week!

A good daily backup over the network  saved my behind this week, after a hard drive crash on our home “server”.  My data was safe, though, I do have some rebuilding of the operating systems to do (Yes, systems, the server is a virtual machine).

I had the craziest time trying to get the time in the VM to stay in sync with the universe.   There are many posts on the web about a dozen different tricks and settings for making the time in a Linux VM work properly.  In my case, I think it turned out to be a simple problem, I didn’t have VMWare Tools automatically starting at boot time.

This page gave me the hints I needed:

The gist:
At the SME console:
/etc/rc.d/init.d/vmware-tools start
Make tools start on reboot:
# Redhat-based distros
chkconfig vmware-tools on
# SME 7
ln -s /etc/rc.d/init.d/vmware-tools /etc/rc7.d/S19vmware-tools


I had to do a song and dance to restore my DAR2 backup, but, generally I’m happy.  I still can’t access SME Server’s “/server-manager” web based GUI… that may be the next post on the PSI blog.

Background: My home server runs SME Server, formerly known as E-smith, from  I’ve been running this Linux based, server bundle for years, maybe even a decade.  However, a couple years ago, I migrated it into a virtual machine to reduce the number of computers that are running 24×7 at home.

Epilog: It might be time to do RAID at home.  Backups are good, but reconfiguration of a highly customized computer still takes a while.