ECS Community 3.7 does not restart

Hi gents!

Recently deployed an ECS Community 2.9.1 / v3.7 using the ISO file. It worked fine until my ESXi server crashed. After reboot, the ECS isn't useable anymore. I can access the GUI login screen, but then get a TimeOut error message when trying to login.

From CLI, if I run a ecsdeploy check, I get the following error message:

TASK [common_baseline_check : fail] ******************************************************************************************************************************************************************************
failed: [192.168.1.56] (item={'_ansible_parsed': True, u'stat': {u'isuid': False, u'uid': 0, u'exists': True, u'attr_flags': u'', u'woth': False, u'isreg': False, u'device_type': 2065, u'mtime': 1657281013.193, u'block_size': 4096, u'inode': 10214, u'isgid': False, u'size': 0, u'executable': False, u'roth': False, u'charset': u'binary', u'readable': True, u'version': None, u'pw_name': u'root', u'gid': 6, u'ischr': False, u'wusr': True, u'writeable': True, u'isdir': False, u'blocks': 0, u'xoth': False, u'rusr': True, u'nlink': 1, u'issock': False, u'rgrp': True, u'gr_name': u'disk', u'path': u'/dev/sdb1', u'xusr': False, u'atime': 1657281013.193, u'mimetype': u'inode/blockdevice', u'ctime': 1657281013.193, u'isblk': True, u'xgrp': False, u'dev': 5, u'wgrp': True, u'isfifo': False, u'mode': u'0660', u'islnk': False, u'attributes': []}, u'changed': False, '_ansible_no_log': False, 'item': u'/dev/sdb', '_ansible_item_result': True, 'failed': False, u'invocation': {u'module_args': {u'checksum_algorithm': u'sha1', u'get_checksum': True, u'follow': False, u'path': u'/dev/sdb1', u'get_md5': True, u'get_mime': True, u'get_attributes': True}}, '_ansible_ignore_errors': None}) => {"changed": false, "failed": true, "item": {"changed": false, "failed": false, "invocation": {"module_args": {"checksum_algorithm": "sha1", "follow": false, "get_attributes": true, "get_checksum": true, "get_md5": true, "get_mime": true, "path": "/dev/sdb1"}}, "item": "/dev/sdb", "stat": {"atime": 1657281013.193, "attr_flags": "", "attributes": [], "block_size": 4096, "blocks": 0, "charset": "binary", "ctime": 1657281013.193, "dev": 5, "device_type": 2065, "executable": false, "exists": true, "gid": 6, "gr_name": "disk", "inode": 10214, "isblk": true, "ischr": false, "isdir": false, "isfifo": false, "isgid": false, "islnk": false, "isreg": false, "issock": false, "isuid": false, "mimetype": "inode/blockdevice", "mode": "0660", "mtime": 1657281013.193, "nlink": 1, "path": "/dev/sdb1", "pw_name": "root", "readable": true, "rgrp": true, "roth": false, "rusr": true, "size": 0, "uid": 0, "version": null, "wgrp": true, "woth": false, "writeable": true, "wusr": true, "xgrp": false, "xoth": false, "xusr": false}}, "msg": "A block device configured in deploy.yml for data nodes is already partitioned."}

...Seems like it tries to reconfigure / reformat the drives again... any idea how to restart the services?

Thanks!