HELP -Power outatge in the middle of Upgrade to 76.2

I cannot get into HA now, not sure if it’s actually upgrading, or dead. The Home assistant log basically has a bunch of nuls now. Has not changed at all.
I’ve restarted,
I renamed my db.old, figured it would just make a fresh one, which it does not seem to have done.
Any recommendation, it just seems dead, where to start??

this is my log, has not changed for 20 min. I even tried renaming it hoping that would cause it to create a new log

I’m totally stuck. Running HA on ubuntu 16.04, Python VENV.

I’ve deleted (renamed the home-assistan.log and the v2.db files (three total) they are not being recreated, so I have no logs to look at to help troubleshoot. Is there a non nuclear option?? force 76.2 update to run again?? I have no idea what to do from here,

Sorry for the comments, but when I get this now

“sudo systemctl status home-assistant.service” it answers : " Unit home-assistant.service could not be found"

I got a little further, but forcing the reinstall of 76.2. It’s running but I cannot get in via UI anymore

2018-08-21 18:01:29 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 378, in start
    resp = await self._request_handler(request)
  File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_app.py", line 341, in _handle
    resp = await handler(request)
  File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 88, in impl
    return await handler(request)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 66, in staticresource_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 34, in real_ip_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 67, in ban_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 66, in auth_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/view.py", line 113, in handle
    result = await result
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/data_validator.py", line 47, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 77, in handle_req
    resp = await func(view, request, *args, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/auth/login_flow.py", line 160, in post
    return self.json(_prepare_result_json(result))
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/auth/login_flow.py", line 116, in _prepare_result_json
    data['data_schema'] = voluptuous_serialize.convert(schema)
AttributeError: module 'voluptuous_serialize' has no attribute 'convert'

It might be just as easy to delete the existing venv and re-create it.

I had to do it once and I was surprised how easy I remember it being.

I think the basic procedure is to delete the directory that contains your homeassistant venv (in my case it was /srv/homeassistant), remake that same directory, change ownership to the homeassistant user and homeassistant group, switch to the homeassistant user, then create a new venv in the above directory.

After that just activate the venv, and install Home Assistant inside the venv.

After it’s fully installed (may take a little while) start the homeassistant service.

Obviously you’ll want to verify all of that but I’m pretty certain that was all that was necessary.