vCenter 7.0.0d Recovery 2nd stage errors

This could happen if the Source VCSA parameters are not same as the newly deployed VM.

For example, your storage/seat might be at 10GB and you have increased it to 20GB. The new VM might be deployed with 10GB only so the parameters does not match in this case.

Error: Unknown system resource type core

Error: Unknown system resource type seat

Error: Unknown system resource type vtsdblog

Error: Unknown system resource type vtsdb

Assuming these are /storage/core/, /storage/seat, /storage/db, /storage/dblog

Do you remember changing anything on VCSA after its deployed

thanks,

MS

Hi,

Thank you for your support. Yes, it seems that after I compared the old disk layout with the new appliance I indeed made some changes.

I will try to extend disks to this same size and restart recovery. After that, I will provide the result.

Cool. hoping to hear that may solve the issue

Well,

one problem was solved by your suggestion, but another appears.

After 97% of restore, I get this error, when services where starting

However, after I logged into the admin console and push setup recovered console I get another error

In both cases, there is no way to get logs.

ssh to vcsa and run vc-support to get log bundle or execute that url in browser to see if that downloads

thanks,

MS

There are no logs to download, One link is dead, 2nd the one is just a white page.

But I was able to to find something

root@vcenter [ ~ ]# service-control --start --all

Operation not cancellable. Please wait for it to finish...

Performing start operation on service lwsmd...

Successfully started service lwsmd

Performing start operation on service vmafdd...

2020-10-13T21:31:44.758Z RC = 1

Stdout =

Stderr = Job for vmafdd.service failed because the control process exited with e rror code.

See "systemctl status vmafdd.service" and "journalctl -xe" for details.

2020-10-13T21:31:44.760Z {

"detail": [

{

"id": "install.ciscommon.command.errinvoke",

"translatable": "An error occurred while invoking external command : '%(0)s'",

"args": [

"Stderr: Job for vmafdd.service failed because the control proce ss exited with error code.\nSee \"systemctl status vmafdd.service\" and \"journa lctl -xe\" for details.\n"

],

"localized": "An error occurred while invoking external command : 'S tderr: Job for vmafdd.service failed because the control process exited with err or code.\nSee \"systemctl status vmafdd.service\" and \"journalctl -xe\" for det ails.\n'"

}

],

"componentKey": null,

"problemId": null,

"resolution": null

}

Error executing start on service vmafdd. Details {

"detail": [

{

"id": "install.ciscommon.service.failstart",

"translatable": "An error occurred while starting service '%(0)s'",

"args": [

"vmafdd"

],

"localized": "An error occurred while starting service 'vmafdd'"

}

],

"componentKey": null,

"problemId": null,

"resolution": null

}

Service-control failed. Error: {

"detail": [

{

"id": "install.ciscommon.service.failstart",

"translatable": "An error occurred while starting service '%(0)s'",

"args": [

"vmafdd"

],

"localized": "An error occurred while starting service 'vmafdd'"

}

],

"componentKey": null,

"problemId": null,

"resolution": null

}

And from journal

-- The unit vmafdd.service completed and consumed the indicated resources.

Oct 13 21:32:07 vcenter..local vmafdd[10836]: t@140714126075648: Reached maximum retry. Affinitized DC vcenter..local is down.

Oct 13 21:32:17 vcenter..local vmafdd[10836]: t@140714126075648: Reached maximum retry. Affinitized DC vcenter..local is down.

lines 1184-1247/1247 (END)

Oct 13 21:32:00 vcenter..local systemd[1]: /lib/systemd/system/systemd-udevd.service:32: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'

Oct 13 21:32:00 vcenter..local systemd[1]: /lib/systemd/system/systemd-timesyncd.service:39: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'

Oct 13 21:32:00 vcenter..local systemd[1]: /lib/systemd/system/systemd-networkd.service:37: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'

Oct 13 21:32:00 vcenter..local systemd[1]: Configuration file /lib/systemd/system/vmware-pod.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.

Oct 13 21:32:00 vcenter..local systemd[1]: Configuration file /lib/systemd/system/observability.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anywa>

Oct 13 21:32:00 vcenter..local systemd[1]: Reloading.

Oct 13 21:32:01 vcenter..local systemd[1]: /lib/systemd/system/systemd-udevd.service:32: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'

Oct 13 21:32:01 vcenter..local systemd[1]: /lib/systemd/system/systemd-timesyncd.service:39: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'

Oct 13 21:32:01 vcenter..local systemd[1]: /lib/systemd/system/systemd-networkd.service:37: Unknown lvalue 'RestrictSUIDSGID' in section 'Service'

Oct 13 21:32:01 vcenter..local systemd[1]: Configuration file /lib/systemd/system/vmware-pod.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.

Oct 13 21:32:01 vcenter..local systemd[1]: Configuration file /lib/systemd/system/observability.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anywa>

Oct 13 21:32:01 vcenter..local systemd[1]: vmafdd.service: Found left-over process 26210 (lwsm) in control group while starting unit. Ignoring.

Oct 13 21:32:01 vcenter..local systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.

Oct 13 21:32:01 vcenter..local systemd[1]: Starting LSB: Start and Stop vmafd...

-- Subject: Unit vmafdd.service has begun start-up

-- Defined-By: systemd

-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel

--

-- Unit vmafdd.service has begun starting up.

Oct 13 21:32:01 vcenter..local CROND[28624]: (root) CMD (. /etc/profile.d/VMware-visl-integration.sh; /usr/lib/applmgmt/backup_restore/scripts/SchedulerCron.py >>/var/log/vmware/applmgmt/backupSchedulerCron.log 2>&1)

Oct 13 21:32:01 vcenter..local CROND[28625]: (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)

Oct 13 21:32:01 vcenter..local lwsmd[28358]: Starting service: vmafd

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 183, ../../../server/vmafd/vecsserviceapi.c:191]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: VecsSrvCreateCertStore: Failed to create Cert Store

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 183, ../../../server/vmafd/authservice.c:36]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 183, ../../../server/vmafd/vecsserviceapi.c:191]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: VecsSrvCreateCertStore: Failed to create Cert Store

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 183, ../../../server/vmafd/authservice.c:36]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 183, ../../../server/vmafd/vecsserviceapi.c:191]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: VecsSrvCreateCertStore: Failed to create Cert Store

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 183, ../../../server/vmafd/authservice.c:36]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 382312451, ../../../server/vmafd/rpc.c:572]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 382312451, ../../../server/vmafd/service.c:202]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: VmAfdBindServer failed. Error(382312451)

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 382312451, ../../../server/vmafd/service.c:144]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 382312451, ../../../server/vmafd/service.c:46]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: VmAfdRpcServerInit failed (382312451)

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: RPC service status (not yet listening)

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 382312451, ../../../server/vmafd/init.c:133]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: ERROR: VmAfdInit failed (382312451)

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 382312451, ../../../server/vmafd/main.c:95]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: vmafdd: stop

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 382312719, ../../../server/vmafd/rpc.c:464]

Oct 13 21:32:01 vcenter..local vmafdd[28648]: t@140718289165760: [Error - 382312719, ../../../server/vmafd/service.c:99]

Oct 13 21:32:01 vcenter..local lwsmd[28358]: Service died: vmafd (restarted 2 times in 17 seconds)

Oct 13 21:32:01 vcenter..local vmafdd[28618]: Starting VMware afd Servicefailed

Oct 13 21:32:01 vcenter..local systemd[1]: vmafdd.service: Control process exited, code=exited status=1

Oct 13 21:32:01 vcenter..local systemd[1]: vmafdd.service: Failed with result 'exit-code'.

Oct 13 21:32:01 vcenter..local systemd[1]: Failed to start LSB: Start and Stop vmafd.

Perhaps it is something with certificates, but I use default VMware, nothing external.

I think that the best solution will be to deploy a new vcenter, as these backups are just theory

They have worked for us and good. I am unsure if there was an issue during backup or corruption. Cheers

thanks,

MS

Thank you for this thread.

We were restoring a 6.7 U3 backup and ran into the error:

Error: Unknown system resource type /dev/sda3

From this discussion, it lead us to check the size of disk1 on the vCenter Appliance, and the default Large size is 12 GB, but our failed server had been increased to 25 GB.

Increasing the new restored VCSA to 25 GB for Disk 1 and then running this on the appliance:

/usr/lib/applmgmt/support/scripts/autogrow.sh

allowed it to grow the disk size to match the failed VCSA and then the restore process was able to progress.

All

vCenter 7.0.0d Recovery 2nd stage errors