# Cannot connect to the balenaEngine daemon at unix:///var/run/balena-engine.sock. Is the balenaEngine daemon running? **URL:** \ **Category:** Product support\ **Tags:** raspberrypi4, balenacloud\ **Created:** [May 31, 2023, 6:48am UTC](https://forums.balena.io/t/cannot-connect-to-the-balenaengine-daemon-at-unix-var-run-balena-engine-sock-is-the-balenaengine-daemon-running/368050 "2023-05-31T06:48:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![alexcorvis84](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/alexcorvis84/32/8534_2.png) [@alexcorvis84](https://forums.balena.io/u/alexcorvis84)\ **Post date:** [May 31, 2023, 6:48am UTC](https://forums.balena.io/t/cannot-connect-to-the-balenaengine-daemon-at-unix-var-run-balena-engine-sock-is-the-balenaengine-daemon-running/368050/1 "2023-05-31T06:48:18Z")
I have a device that was working and now it only shows the message **Online (VPN only)** so I can’t access servcices exposed. I tied to disconnect and plug it in again but still same behaviour. Any feedback appreciated. Thanks in advance! Attached Diagnostics [89e0ed4adedc5b2d4b85115ae8d58c6a\_diagnostics\_2023.05.31\_06.33.22+0000.txt](https://forums.balena.io/uploads/short-url/tss3EX56dpQF1dM4hBhH05eVMCv.txt) (1.2 MB) ![image](https://global.discourse-cdn.com/balena/original/2X/9/965b55e7ad0422b20608d4ad56149ee0860cf781.png) ---
**Author:** ![alexgg](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@alexgg](https://forums.balena.io/u/alexgg)\ **Post date:** [June 7, 2023, 5:54pm UTC](https://forums.balena.io/t/cannot-connect-to-the-balenaengine-daemon-at-unix-var-run-balena-engine-sock-is-the-balenaengine-daemon-running/368050/2 "2023-06-07T17:54:40Z")
Hey, according to the logs the containerd service is not able to start, so the engine is not starting and so are the supervisor and other containers. If there is no user data that you need to keep, I would stop engine and supervisor and manually purge the engine storage see if it solves the issue. If that does not work, you can try to reset the data partition by removing `/mnt/data/remove_me_to_reset` and reboot. That will remove all of the storage engine, including containers and user volumes, so on the next boot the engine should start the supervisor and the applications will be re-downloaded. ---
**Author:** ![alexcorvis84](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/alexcorvis84/32/8534_2.png) [@alexcorvis84](https://forums.balena.io/u/alexcorvis84)\ **Post date:** [June 10, 2023, 10:15am UTC](https://forums.balena.io/t/cannot-connect-to-the-balenaengine-daemon-at-unix-var-run-balena-engine-sock-is-the-balenaengine-daemon-running/368050/4 "2023-06-10T10:15:24Z")
Thanks for your reply. Finally I checked that the problem was caused by the sd corruption data. I solved it running **e2fsck** on the partition. > [Wed May 31 05:37:01 2023] EXT4-fs error (device mmcblk0p6): \_\_ext4\_find\_entry:1623: inode #12: comm balena-engine-c: checksumming directory block 0 > [Wed May 31 05:37:01 2023] EXT4-fs warning (device mmcblk0p6): ext4\_dirblock\_csum\_verify:376: inode #12: comm balena-engine-c: No space for directory leaf checksum. Please run e2fsck -D. > [Wed May 31 05:37:01 2023] EXT4-fs error (device mmcblk0p6): \_\_ext4\_find\_entry:1623: inode #12: comm balena-engine-c: checksumming directory block 0 > [Wed May 31 05:37:01 2023] EXT4-fs warning (device mmcblk0p6): ext4\_dirblock\_csum\_verify:376: inode #12: comm balena-engine-c: No space for directory leaf checksum. Please run e2fsck -D. > [Wed May 31 05:37:01 2023] EXT4-fs error (device mmcblk0p6): \_\_ext4\_find\_entry:1623: inode #12: comm balena-engine-c: checksumming directory block 0 > [Wed May 31 05:37:33 2023] EXT4-fs warning (device mmcblk0p6): ext4\_dirblock\_csum\_verify:376: inode #12: comm balena-engine-c: No space for directory leaf checksum. Please run e2fsck -D. > [Wed May 31 05:37:33 2023] EXT4-fs error (device mmcblk0p6): \_\_ext4\_find\_entry:1623: inode #12: comm balena-engine-c: checksumming directory block 0 > [Wed May 31 05:37:33 2023] EXT4-fs warning (device mmcblk0p6): ext4\_dirblock\_csum\_verify:376: inode #12: comm balena-engine-c: No space for directory leaf checksum. Please run e2fsck -D. > [Wed May 31 05:37:33 2023] EXT4-fs error (device mmcblk0p6): \_\_ext4\_find\_entry:1623: inode #12: comm balena-engine-c: checksumming directory block 0 > [Wed May 31 05:37:33 2023] EXT4-fs warning (device mmcblk0p6): ext4\_dirblock\_csum\_verify:376: inode #12: comm balena-engine-c: No space for directory leaf checksum. Please run e2fsck -D. > [Wed May 31 05:37:33 2023] EXT4-fs error (device mmcblk0p6): \_\_ext4\_find\_entry:1623: inode #12: comm balena-engine-c: checksumming directory block 0 > [Wed May 31 05:37:33 2023] EXT4-fs warning (device mmcblk0p6): ext4\_dirblock\_csum\_verify:376: inode #12: comm balena-engine-c: No space for directory leaf checksum. Please run e2fsck -D. > [Wed May 31 05:37:33 2023] EXT4-fs error (device mmcblk0p6): \_\_ext4\_find\_entry:1623: inode #12: comm balena-engine-c: checksumming directory block 0