Ask Your Question

VM Ubuntu 16.04 Unable to login

asked 2017-07-25 04:59:45 -0500

TijoV gravatar image

updated 2017-07-27 05:55:33 -0500

On our Openstack Ocata setup, The instance is getting created and it shows running status, but we are unable to login. On looking at the VM full logs, below is the suspected information. VM logs below:

Scanning for Btrfs filesystems
Warning: fsck not present, so skipping root file system
[    3.896367] EXT4-fs (vda1): INFO: recovery required on readonly filesystem
[    3.898517] EXT4-fs (vda1): write access will be enabled during recovery
[    3.929099] EXT4-fs (vda1): recovery complete
[    3.932915] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[    4.508808] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[    4.514040] systemd[1]: Detected virtualization kvm.
[    4.515633] systemd[1]: Detected architecture x86-64.

Welcome to [1mUbuntu 16.04.2 LTS[0m!
[    7.018042] EXT4-fs error (device vda1): ext4_mb_generate_buddy:758: group 3, block bitmap and bg descriptor inconsistent: 6947 vs 7049 free clusters

[[0;32m  OK  [0m] Started ifup for ens3.

Welcome to emergency mode! After logging in, type "journalctl -xGive root password for maintenance
(or press Control-D to continue): [  109.384749] EXT4-fs error (device vda1): ext4_mb_generate_buddy:758: group 0, block bitmap and bg descriptor inconsistent: 7412 vs 7401 free clusters
[  110.324261] cloud-init[962]: Cloud-init v. 0.7.9 running 'init' at Mon, 24 Jul 2017 09:55:39 +0000. Up 106.32 seconds.
[  110.326210] cloud-init[962]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++
[  110.326700] cloud-init[962]: ci-info: +--------+------+------------------------------+---------------+-------+-------------------+

The VM stays inaccessible, However if a Hardreboot is done for the VM, The VM comes fine and we are able to accesible. This issue is happening 3 out of 20 times when a VM is created.

Can someone please help on this issue.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2017-12-04 04:51:35 -0500

TijoV gravatar image

This issue was because Our SAN Storage equipment was facing some issues, Once storage issue is fixed and all Iscsi initiators were reconnected with storage the VM creation went fine. No issues so far.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-07-25 04:59:45 -0500

Seen: 492 times

Last updated: Dec 04 '17