Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Increasing the size of the root partition on a vRealize Log Insight 4.x node (76304)

Last Updated: 2/27/2024Categories: How toTotal Views: 15376Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Purpose

This article provides steps to increase the size of root partition on vRealize Log Insight 4.x nodes.

Note: This article should not be applied to vRealize Log Insight 8.x environments.

Resolution

To increase the size of the root partition:

Log into the VMware vSphere Web Client as an administrative user.

Right-click the appropriate vRealize Log Insight virtual machine and click Power > Guest Shut Down Guest OS.

Right-click the appropriate vRealize Log Insight virtual machine and click Edit Settings.

Increase the Hard Disk 1 size.

Note: You cannot increase the size of any disk if there is a snapshot in place.  To increase disk size, remove any snapshots on the VM before continuing.

Click OK.

Right-click the appropriate vRealize Log Insight virtual machine and click Snapshots > Take Snapshot.

Click OK.

Open a console to the appropriate vRealize Log Insight virtual machine.

Click Power On.

When the GRUB boot menu is displayed, press the arrow key to select the line that begins with SUSE Linux Enterprise Server.

Note: If you cannot reach the boot menu before it disappears, enable Force BIOS setup in tn the Virtual Machine's Settings > VM Options > Boot Options and reboot.

Add init=/bin/sh to the end of the line. Ensure that there is a space between the end of the current line and the additional parameter.

Press Enter to boot the virtual machine into single user mode.

After # prompt is presented, type fdisk /dev/sda to begin manipulating the partition table.

Note: The prompt will change to Command (m for help):

Type d to start the process of deleting the partition table information for the root partition.

Type 3 to specify the root partition.

Type n to rebuild the partition table information for the root partition.

Type p to specify a primary partition.

Press Enter to accept the default partition number (3).

Press Enter to accept the default first sector.

Press Enter to accept the default last sector.

Type a to start the process of marking the root partition as bootable.

Type 3 to specify the root partition.

Type w to write the updated partition table.

Note: You see this warning message, which can be safely ignored:
WARNING: Re-reading the partition table failed with error 16: Device or resource busy.The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8)

Run this command to reboot the virtual machine:

shutdown -r -n -f now

Note: Let the virtual machine boot normally.

Log in to the appropriate vRealize Log Insight virtual machine as root via SSH or Console.

Run this command to extend the root file system:

resize2fs /dev/sda3

Run this command to verify that the / partition is larger:

df -h /

Repeat steps 2-27 for any other vRealize Log Insight nodes as required.

Once everything is confirmed to be working, the snapshots taken in step 6 can be deleted.

Related Information

The vRealize Log Insight root partition is full (82170)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
适用于 vRA 8.0.0 HA 环境的修补程序解决了阻止某些服务在数据库故障切换事件后恢复的问题 (76222)

KB
•
データベースのフェイルオーバー イベント後に一部のサービスを復旧できない問題を解決するための vRA 8.0.0 HA 環境用のパッチ (76222)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Log Insight

Related Versions:

VMware vRealize Log Insight 4.8.x

VMware vRealize Log Insight 4.7.x

Take Our Survey

Support Assistant