Ubuntu VM stuck in boot loop.

Question

Ubuntu VM stuck in boot loop.

Anonymous

I increased the OS disk size in the portal and afterwards it would not come up and is stuck in a boot loop. The console shows the error below. I have tried recovering from backups but still get the same behavior. Any help would be appreciated.

[FAILED] Failed to start System Security Services Daemon.

See 'systemctl status sssd.service' for details.

[DEPEND] Dependency failed for SSSD Sudo Service responder socket.

[DEPEND] Dependency failed for SSSD PAM Service responder socket.

[DEPEND] Dependency failed for SSSD…vice responder private socket.

[DEPEND] Dependency failed for SSSD NSS Service responder socket.

[DEPEND] Dependency failed for SSSD PAC Service responder socket.

[DEPEND] Dependency failed for SSSD…toFS Service responder socket.

[DEPEND] Dependency failed for SSSD SSH Service responder socket.

[ OK ] Stopped System Security Services Daemon.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Anonymous

2025-02-18T18:03:41.02+00:00

Hi LAFLEUR, ALAN,
Could you please let me know which series are you using?
Anonymous

2025-02-19T14:41:33.6666667+00:00

E2ads v5
Anonymous

2025-02-19T22:29:08.8633333+00:00

Hi LAFLEUR, ALAN
I noticed that the default OS disk size options available are 32GB and 64GB, and the 30GB size is not listed. Could you please review the attached screenshot for reference and confirm how the 30GB size was enabled?

Additionally, could you provide details of the available disks and the current disk size for the specific VM? If possible, please share an image showing the available disk sizes?. This will help us understand the previous correct size so we can determine the appropriate steps to increase the size if needed

1 answer

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Anonymous

2025-02-18T18:03:41.02+00:00

Hi LAFLEUR, ALAN,
Could you please let me know which series are you using?
Anonymous

2025-02-19T22:29:08.8633333+00:00

Hi LAFLEUR, ALAN
I noticed that the default OS disk size options available are 32GB and 64GB, and the 30GB size is not listed. Could you please review the attached screenshot for reference and confirm how the 30GB size was enabled?

Additionally, could you provide details of the available disks and the current disk size for the specific VM? If possible, please share an image showing the available disk sizes?. This will help us understand the previous correct size so we can determine the appropriate steps to increase the size if needed

Answer 1

Anonymous

Hi LAFLEUR, ALAN,
Thank you for reaching out to the Microsoft Q&A Platform!
I’m happy to assist you with your query.

To help resolve the issue, I recommend reviewing the documentation linked below.
Failed to start system security services daemon (SSSD) Error
If you are having trouble accessing it locally or cli, you can try using the Azure Serial Console to troubleshoot the issue as outlined in the guide.
Prerequisites to access the Azure Serial Console
Access Serial Console for Virtual Machines via Azure portal

If you're facing the same issue again, redeploying the Linux VM to a new node.
Redeploy Linux virtual machine to new Azure node

Before making any changes, I highly advise you to back up your configurations and any important data to prevent potential issues during the troubleshooting process.

Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

If you have any further questions or run into any difficulties, please don’t hesitate to let me know. I'm available to assist you anytime. Just tag me if you need further help

If you found this information helpful, give an upvote

Anonymous

2025-02-16T16:10:02.3966667+00:00

Hi @Anonymous . Thanks for the info. I tried all the steps you provided but they did not fix the problem. Following the first suggestion, I was able to break the boot sequence via the serial console, but it seemed it always nterrupted it so early in the process that the first command of systemctl was not even recognized. The redeploy did not seem to do anything, perhaps because it is in a boot loop? Redeploy does not work when the VM is deallocated, I did also try to reapply but that also did not seem to do anything. Would you be available to help me troubleshoot in real time perhaps?

Alan LaFleur
Anonymous

2025-02-17T19:16:57.57+00:00
Hi LAFLEUR, ALAN,
Thank you for getting back to us and sharing what you've tried so far.
I have conducted a similar test in my lab, successfully increasing the OS disk size, and was able to log in afterward. you can see the image for your reference
Old disk configuration

New disk configuration resize on existing VM

After increasing the OS disk Login interface

To assist you further and ensure we're on the same page, could you please provide the following details:

The operating system image you are using (e.g., RedHat, Ubuntu)

The version of the operating system

The size of the old OS disk

The new size of the OS disk after the increase

The region where your deployment is located

Once I have this information, I will be able to assist you more effectively.

Thank you for your cooperation and understanding
Anonymous

2025-02-17T22:59:23.4133333+00:00
Hi, thanks for the assistance. Here is the info you requested.

The operating system image you are using (e.g., RedHat, Ubuntu)

Ubuntu

The version of the operating system

22.04

The size of the old OS disk

30GB

The new size of the OS disk after the increase

64GB

The region where your deployment is located

USEAST2
Anonymous

2025-02-17T23:14:22.7033333+00:00

Hi LAFLEUR, ALAN,
Can you please mention which series name you are using?
Just pasting here image for your reference how the series names look like for VM OS disk
Anonymous

2025-02-20T17:52:21.4633333+00:00

I ended up opening a case and it is resolved now. Turned out to be a corrupt SSSD install on the OS.
Anonymous

2025-02-20T20:51:36.7933333+00:00

Hi LAFLEUR, ALAN,
Thank you for the update.
what is causing the issue and now it resolved now glad to hear
Please let me know if you have any further queries

Share via

Ubuntu VM stuck in boot loop.

1 answer

Your answer