Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Upgrading to vRealize Log Insight 8.x hangs on "A start job is running for dev-sda4.device" (79015)

Last Updated: 5/11/2022Categories: InformationalTotal Views: 5029Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When upgrading vRealize Log Insight to 8.0-8.2, you see this message displayed in a vSphere Web Client Console to the Log Insight appliance

A start job is running for dev-sda4.device

The job runs indefinitely and never finishes

Cause

This occurs because the upgrade to Photon OS renames sda partitions to another name, such as sdc, sdd, or sde, but the VM tries to boot to the originally configured sda4 partition.

Resolution

This issue is resolved in Log Insight 8.3, and should require no manual intervention.  If you find this is not the case, please file a support request with VMware Technical Support.

Workaround

To work around this issue:

1. Reboot the VM from vCenter and open a console immediately
2. When available Operating Systems are listed, select Photon with your arrow keys and enter rd.break=pre-mount at the end of Boot Options. Press enter.
3. When you reach the pre-mount:/# prompt, type ls /dev
4. Observe the list and find the disk which has all 4 partitions, like sdc1, sdc2, sdc3, sdc4 (it will be anything other than sda, since you are observing this issue). This means sda partition has been renamed to sdc (or sdd, sde).
5. Run the following commands in sequence:

mkdir temp-dir
mount /dev/sdc1 temp-dir
sed -i "s/sda4/sdc4/" temp-dir/boot/grub/menu.lst
umount /dev/sdc1
mount /dev/sdc4 temp-dir
sed -i "s/sda/sdc/" temp-dir/etc/fstab

Note: In the above commands, replace sdc with the disk which you identified in step 4 to have all 4 partitions (if different than sdc).

11. From vCenter, reboot the VM and from a console, be sure to select Photon from the boot options

Notes: In a single node cluster, this will resolve the issue. In a multi-node cluster, if the issue occurred on the primary node or a middle worker node (not the last mode in the upgrade list) the upgrade will not continue for the remaining worker nodes. In that instance, upgrade the node(s) manually using this article:How to Manually Upgrade vRealize Log Insight via Command Line (83225)

If you encounter the original issue on other nodes in the cluster, perform steps 1-11 on them as well.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vRealize Operations のバックアップ ジョブの失敗を示すアラートをキャンセルできない (78926)

KB
•
ESXi 升级后未安装 ESXi 7.0 NSX 内核模块时要恢复的步骤 (78679)

KB
•
管理者または root アカウントのパスワードが原因で vRealize Operations Manager 8.0 へのアップグレードが失敗する (75195)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-5 of 5

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 8.x

Take Our Survey

Support Assistant