Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Startup errors display after increasing the LEM disk size

Startup errors display after increasing the LEM disk size

Updated March 2, 2018

Overview

After you increase the LEM allocated disk size in your virtual machine settings and power on the virtual machine, several error messages display during startup. 

For example: 

Error: Partition /dev/sda5 is being used. You must umount it before you modify it with Parted.

Error: Can't have overlapping partitions.

 

lem_disk_increase_error.PNG

 

OR

 

Your primary disk size has not changed.

Found secondary disk.

Checking for partitions:

The primary disk has already been cloned to the secondary disk.

 

lem_disk_size_has_not_changed.png

 

Environment

  • All LEM versions

Cause 

  • The virtual machine did not shut down completely when you resized the disk. 
  • The datastore did not have sufficient free space. 

Resolution

Partition /dev/sda5 is being used 

  1. Boot the LEM and wait for the Blue Screen of Life to display.
  2. Click Advanced Configuration > Appliance > Shutdown to power down the LEM.
  3. Ensure that the datastore has sufficient disk space to accommodate your new disk allocation size.
  4. Boot the LEM again and allow the scripts to run.
    If errors display during the startup process, contact SolarWinds Support.

 

Your primary disk size has not changed

  1. Press a key to power off the appliance.
  2. Right-click on your VM and select Edit Settings.
  3. Locate the two attached virtual hard disks and select the first one.
  4. Press the Inspect button to verify the disk size. Repeat this step for the other VHD.
  5. After you have located the VHD with the smaller disk size (likely the default 250 GB), take note of the .vhd location and click on the Remove button on the bottom.
  6. Save settings and start the LEM. It should boot normally and reflect your increased disk size.
 

 

Last modified

Tags

Classifications

Public