# "Error: System service failed" after power failure **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [July 12, 2023, 3:11am UTC](https://community.umbrel.com/t/error-system-service-failed-after-power-failure/13058 "2023-07-12T03:11:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![censored](https://avatars.discourse-cdn.com/v4/letter/c/35a633/32.png) [@censored](https://community.umbrel.com/u/censored)\ **Post date:** [July 12, 2023, 3:11am UTC](https://community.umbrel.com/t/error-system-service-failed-after-power-failure/13058/1 "2023-07-12T03:11:58Z")
After a sudden power failure last night, my umbrel does not start anymore and states the above message in the browser. The start script says the following – is anyone able to help, please? # ====================================== ============= STARTING =============== ============== UMBREL ================ Setting environment variables… Starting karen… Starting status monitors… Starting memory monitor… Starting backup monitor… Starting decoy backup trigger… Starting umbreld… Starting Docker services… Traceback (most recent call last): File “/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py”, line 802, in urlopen \*\*response\_kw, File “/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py”, line 504, in \_make\_request enforce\_content\_length=enforce\_content\_length, File “/usr/local/lib/python3.7/dist-packages/urllib3/connection.py”, line 388, in request self.endheaders() File “/usr/lib/python3.7/http/client.py”, line 1259, in endheaders self.\_send\_output(message\_body, encode\_chunked=encode\_chunked) File “/usr/lib/python3.7/http/client.py”, line 1034, in \_send\_output self.send(msg) File “/usr/lib/python3.7/http/client.py”, line 974, in send self.connect() File “/usr/local/lib/python3.7/dist-packages/docker/transport/unixconn.py”, line 27, in connect sock.connect(self.unix\_socket) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/usr/local/lib/python3.7/dist-packages/requests/adapters.py”, line 497, in send chunked=chunked, File “/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py”, line 845, in urlopen method, url, error=new\_e, \_pool=self, \_stacktrace=sys.exc\_info()[2] File “/usr/local/lib/python3.7/dist-packages/urllib3/util/retry.py”, line 470, in increment raise reraise(type(error), error, \_stacktrace) File “/usr/local/lib/python3.7/dist-packages/urllib3/util/util.py”, line 38, in reraise raise value.with\_traceback(tb) File “/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py”, line 802, in urlopen \*\*response\_kw, File “/usr/local/lib/python3.7/dist-packages/urllib3/connectionpool.py”, line 504, in \_make\_request enforce\_content\_length=enforce\_content\_length, File “/usr/local/lib/python3.7/dist-packages/urllib3/connection.py”, line 388, in request self.endheaders() File “/usr/lib/python3.7/http/client.py”, line 1259, in endheaders self.\_send\_output(message\_body, encode\_chunked=encode\_chunked) File “/usr/lib/python3.7/http/client.py”, line 1034, in \_send\_output self.send(msg) File “/usr/lib/python3.7/http/client.py”, line 974, in send self.connect() File “/usr/local/lib/python3.7/dist-packages/docker/transport/unixconn.py”, line 27, in connect sock.connect(self.unix\_socket) urllib3.exceptions.ProtocolError: (‘Connection aborted.’, ConnectionRefusedError(111, ‘Connection refused’)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/usr/local/lib/python3.7/dist-packages/docker/api/client.py”, line 214, in \_retrieve\_server\_version return self.version(api\_version=False)[“ApiVersion”] File “/usr/local/lib/python3.7/dist-packages/docker/api/daemon.py”, line 181, in version return self.\_result(self.\_get(url), json=True) File “/usr/local/lib/python3.7/dist-packages/docker/utils/decorators.py”, line 46, in inner return f(self, \*args, \*\*kwargs) File “/usr/local/lib/python3.7/dist-packages/docker/api/client.py”, line 237, in \_get return self.get(url, \*\*self.\_set\_request\_timeout(kwargs)) File “/usr/local/lib/python3.7/dist-packages/requests/sessions.py”, line 602, in get return self.request(“GET”, url, \*\*kwargs) File “/usr/local/lib/python3.7/dist-packages/requests/sessions.py”, line 589, in request resp = self.send(prep, \*\*send\_kwargs) File “/usr/local/lib/python3.7/dist-packages/requests/sessions.py”, line 703, in send r = adapter.send(request, \*\*kwargs) File “/usr/local/lib/python3.7/dist-packages/requests/adapters.py”, line 501, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: (‘Connection aborted.’, ConnectionRefusedError(111, ‘Connection refused’)) During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/usr/local/bin/docker-compose”, line 8, in sys.exit(main()) File “/usr/local/lib/python3.7/dist-packages/compose/cli/main.py”, line 81, in main command\_func() File “/usr/local/lib/python3.7/dist-packages/compose/cli/main.py”, line 200, in perform\_command project = project\_from\_options(‘.’, options) File “/usr/local/lib/python3.7/dist-packages/compose/cli/command.py”, line 70, in project\_from\_options enabled\_profiles=get\_profiles\_from\_options(options, environment) File “/usr/local/lib/python3.7/dist-packages/compose/cli/command.py”, line 153, in get\_project verbose=verbose, version=api\_version, context=context, environment=environment File “/usr/local/lib/python3.7/dist-packages/compose/cli/docker\_client.py”, line 43, in get\_client environment=environment, tls\_version=get\_tls\_version(environment) File “/usr/local/lib/python3.7/dist-packages/compose/cli/docker\_client.py”, line 170, in docker\_client client = APIClient(use\_ssh\_client=not use\_paramiko\_ssh, \*\*kwargs) File “/usr/local/lib/python3.7/dist-packages/docker/api/client.py”, line 197, in **init** self.\_version = self.\_retrieve\_server\_version() File “/usr/local/lib/python3.7/dist-packages/docker/api/client.py”, line 222, in \_retrieve\_server\_version f’Error while fetching server API version: {e}’ docker.errors.DockerException: Error while fetching server API version: (‘Connection aborted.’, ConnectionRefusedError(111, ‘Connection refused’)) Failed to start containers ---
**Author:** ![censored](https://avatars.discourse-cdn.com/v4/letter/c/35a633/32.png) [@censored](https://community.umbrel.com/u/censored)\ **Post date:** [July 13, 2023, 11:29am UTC](https://community.umbrel.com/t/error-system-service-failed-after-power-failure/13058/2 "2023-07-13T11:29:14Z")
After flashing another mSD with a clean umbrel, the error persists (though now it says " **Error: Failed to start containers**"). ---
**Author:** ![smolgrrr](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/smolgrrr/32/2825_2.png) [@smolgrrr](https://community.umbrel.com/u/smolgrrr)\ **Post date:** [August 3, 2023, 12:53am UTC](https://community.umbrel.com/t/error-system-service-failed-after-power-failure/13058/3 "2023-08-03T00:53:46Z")
Handy guide here might help. Let me know how it goes! > [@Resolving “Error: System service failed”](https://community.umbrel.com/t/resolving-error-system-service-failed/12939/1): > > _As a disclaimer please always make sure you have secured your 24 word seed phrase before making any drastic system changes, primarily if you skip the step to reflash your MicroSD card (where you don’t lose any data) and instead skip to reformatting your storage drive then you would lose all your data (all data is stored on the storage drive and will result in a clean install)_ > > This error is the result of several issues usually occurring on Raspberry Pi 4 devices and related to the MicroSD card and/or a read/write issue with the installed storage drive. > > This is for when you receive this screen specifically: > > ![image](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/2X/9/9eba33384573c41cc0c8d66e6b3bab0470196e70.png) > > It can be caused by a failing MicroSD or a storage device that has not been formatted correctly in ext4, has become corrupted, or simply had any data on it prior to attempting a new installation. > > > The most reliable fix for this issue if you are on the Raspberry Pi 4 platform is to reflash your MicroSD card. If you have another one you can swap in, please try another card as well > > > SSH and run this command to safely shutdown: `sudo shutdown` > > > Unplug power and reflash your MicroSD card, then when complete, plug in your power last and wait ~5 minutes > > > For reference, reflashing will not result in any data loss because all user data is stored on your external storage drive (SSD or HDD). > > > **To reflash your MicroSD card, follow the steps on our website under [“Install on a Rasberry Pi 4.”](https://umbrel.com/#start)** > > If it is your first time setting up Umbrel, and you don’t have any data on it yet please try reformatting your storage device again and make sure all partitions are completely clear- this is also a common cause if you already had a prior installation or any data on your drive and are trying to setup like new once more. You can delete all partitions and format in any default format file type, upon a successful Umbrel installation- during the Umbrel setup it will then automatically format again in the correct ext4. > > For Windows you can use a program called AOMEI partition assistant to detect and manage ext4 disks and format them. On Mac there is a program suite from Paragon software you can also use to manage ext4 disks, to avoid the hassle of manually mounting and wiping an ext4 drive. [This process is detailed in another guide here.](https://community.umbrel.com/t/how-to-easily-reformat-an-ext4-umbrel-drive/13139) > > If after a reflash or this problem persists on a different Linux installation please reach out to us so we can track and resolve these issues for you to avoid having to delete and reinstall. You can always connect directly with our team using the chat icon 💬 located at the bottom right of [Umbrel.com](http://Umbrel.com) or make a post in our [Help & Support Telegram Channel](https://t.me/getumbrel/207765) > > When reaching out let us know when this issue began and provide us your debug logs for review so we can investigate and get you back up and running. > > Following the instructions in [_How to SSH into Umbrel on a Raspberry Pi_](https://community.umbrel.com/umbrel-troubleshooting-guide/faq/troubleshooting/how-to-ssh-into-umbrel-on-a-rasberry-pi) and [_Generating Troubleshooting Logs_](https://community.umbrel.com/umbrel-troubleshooting-guide/faq/troubleshooting/generating-troubleshooting-logs)