# Home assistant update failing

**URL:** https://dietpi.com/forum/t/home-assistant-update-failing/17843
**Category:** Troubleshooting
**Created:** [8 September 2023 18:39 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843 "2023-09-08T18:39:13Z")
**Posts on this page:** 11
**Page:** 2

<div class="post-metadata">

### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [14 September 2023 15:19 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/21 "2023-09-14T15:19:10Z")

</div>

Anyway plus run it again and share the whole output

---

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [14 September 2023 15:20 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/22 "2023-09-14T15:20:20Z")

</div>

Jep, not trivial to get this working with BerryBoot. It is horribly outdated (kernel-wise) in the meantime and the concept itself has major limitation, as we have no access to the boot config and kernel itself, i.e. it cannot be upgraded outside of the BerryBoot UI (if even possible there).

The kernel 4.14 is so old that it will have some issues with Bookworm, notably with WiFi at least, and of course has a large number of unresolved vulnerabilities, so that I wouldn’t recommend using it on any production server that is attached to the Internet.

HA however currently can only be installed on Bookworm. It might be possible on Bullseye again soon, but there are some quirks currently preventing this, which I do not fully understand yet, probably only some bug/mistake when dealing with Git: [Unable to install package ha-av - #47 by MichaIng - Configuration - Home Assistant Community](https://community.home-assistant.io/t/unable-to-install-package-ha-av/466286/47)

---

<div class="post-metadata">

### Author: ![niel](https://dietpi.com/forum/user_avatar/dietpi.com/niel/32/3246_2.png) [@niel](https://dietpi.com/forum/u/niel)
#### Post date: [14 September 2023 16:17 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/23 "2023-09-14T16:17:55Z")

</div>

Still same error.  
[out.txt](https://dietpi.com/forum/uploads/short-url/x22Q2Y9rRAFXjZ9ZgQa4yHsKXSe.txt) (44.9 KB)

I guess I will have to live with this version for sometime until I find a clear path for alternative. Thanks guys, you can close the topic.

---

<div class="post-metadata">

### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [14 September 2023 16:39 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/24 "2023-09-14T16:39:19Z")

</div>

> [@niel](#):
>
> until I find a clear path for alternative

Use 2 different SD cards 🙂

* * *

one of the issues inside the error log

> `The pkg-config command could not be found.`

Try following and run HA install again. Once failed, share the log again.

```sh
apt install pkg-config

```

---

<div class="post-metadata">

### Author: ![niel](https://dietpi.com/forum/user_avatar/dietpi.com/niel/32/3246_2.png) [@niel](https://dietpi.com/forum/u/niel)
#### Post date: [14 September 2023 16:44 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/25 "2023-09-14T16:44:38Z")

</div>

Sure I will try. Meanwhile after berryboot upgrade, I am getting “Reboot required” message after reboot as well. I will post the logs after installing pkg-config. Should I do that inside HA python environment or before?

```auto
 DietPi v8.21.1 : Reboot required
 ─────────────────────────────────────────────────────
 - Device model : RPi 3 Model B (aarch64)
 - CPU temp : 59 °C / 138 °F : Running warm, but safe
 - LAN IP : 10.0.0.122 (eth0)
 - MOTD : Check out the DietPi v8.21 release notes:
          https://dietpi.com/docs/releases/v8_21/
 ─────────────────────────────────────────────────────

 DietPi Team : https://github.com/MichaIng/DietPi#the-dietpi-project-team
 Patreon Legends : Camry2731, Chris Gelatt
 Website : https://dietpi.com/ | https://twitter.com/DietPi_
 Contribute : https://dietpi.com/contribute.html
 Web Hosting by : https://myvirtualserver.com

 reboot : A reboot is required to finalise a recent kernel upgrade

When I run diet-software, I was presented with following warning message

 Kernel modules for the loaded kernel at /lib/modules/5.10.43v64 are missing. This is most likely the case as of a │
│ recently applied kernel upgrade where a reboot is required to load the new kernel.                                                                                                                                                       
│ To assure that DietPi-Software can run successfully, especially when performing installs, it is required that you │
│ perform a reboot so that kernel modules can be loaded ondemand. 
│ There may be rare cases where no dedicated kernel modules are used but all require modules are builtin. If this is the case, please create the mentioned directory manually to proceed.  
│ Do you want to reboot now?

```

---

<div class="post-metadata">

### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [14 September 2023 17:08 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/26 "2023-09-14T17:08:46Z")

</div>

what is the version of the loaded kernel?

```auto
uname -a

```

I guess issue might be related to 32bit vs 64bit.

Now it is 64bit

> [@niel](#):
>
> `- Device model : RPi 3 Model B (aarch64)`

> [@niel](#):
>
> `/lib/modules/5.10.43v64 are missing`

but was 32bit before

> [@niel](#):
>
> 4.14.58v7-aufs #1 SMP Sat Jul 28 20:40:59 CEST 2018 armv7l

Did you switched to 64bit by purpose? Because your entire system/userland is 32bit still. You just force a 64bit kernel mode. Which usually is a bad idea as it could cause other issues.

---

<div class="post-metadata">

### Author: ![niel](https://dietpi.com/forum/user_avatar/dietpi.com/niel/32/3246_2.png) [@niel](https://dietpi.com/forum/u/niel)
#### Post date: [14 September 2023 17:36 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/27 "2023-09-14T17:36:10Z")

</div>

I didn’t switch on purpose. This message started showing up after berryboot upgrade. Berryboot has only one download for upgrade. I used that.

> <https://raspberrypi.stackexchange.com/questions/75348/upgrading-berryboot-version>

> **[berryboot - Browse Files at SourceForge.net](https://sourceforge.net/projects/berryboot/files/)**
>
> Berryboot -- Boot menu / OS installer for ARM devices

Should I rollback to older berryboot?

---

<div class="post-metadata">

### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [14 September 2023 17:51 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/28 "2023-09-14T17:51:07Z")

</div>

Which file you downloaded?

---

<div class="post-metadata">

### Author: ![niel](https://dietpi.com/forum/user_avatar/dietpi.com/niel/32/3246_2.png) [@niel](https://dietpi.com/forum/u/niel)
#### Post date: [14 September 2023 17:53 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/29 "2023-09-14T17:53:59Z")

</div>

[berryboot-20210701-pi4.zip](https://sourceforge.net/projects/berryboot/files/berryboot-20210701-pi4.zip/download)

---

<div class="post-metadata">

### Author: ![niel](https://dietpi.com/forum/user_avatar/dietpi.com/niel/32/3246_2.png) [@niel](https://dietpi.com/forum/u/niel)
#### Post date: [14 September 2023 18:06 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/30 "2023-09-14T18:06:19Z")

</div>

Guys, I found this thread which has similar issues reported. You have spent enough time and energy on this issue and decided not to pursue it further. Let me know if you still wish to continue troubleshooting this issue. Thanks again for such a amazing work!

> <https://github.com/MichaIng/DietPi/issues/3929>
>
> Hi! :)
> First: Great Development and it really makes fun to work with DietPi! :)…
> 
> Now to my Problem:
> Emby will not install from the Software Menu.
> 
> \[INFO \] DietPi-Software | APT install for: ./41.deb, please wait...
> E: Unable to correct problems, you have held broken packages.
> \[FAILED\] DietPi-Software | APT install for: ./41.deb
> - Command: apt-get -qq --allow-change-held-packages install ./41.deb
> \[INFO \] DietPi-Bugreport | Packing upload archive, please wait...
> 
> \#### Details:
> \- Date | Mon Nov 23 10:29:15 CET 2020
> \- Bug report | 428e5997-d223-499f-b385-11a5838b681c
> \- DietPi version | v6.33.3 (MichaIng/master)
> \- Image creator | DietPi Core Team
> \- Pre-image | Raspberry Pi OS (32-bit) Lite
> \- Hardware | RPi 3 Model B+ (aarch64) (ID=3)
> \- Kernel version | Linux BerryBootDietPi 5.4.73v64 #2 SMP PREEMPT Tue Nov 3 16:11:05 CET 2020 aarch64 GNU/Linux
> \- Distro | buster (ID=5,RASPBIAN=1)
> \- Command | apt-get -qq --allow-change-held-packages install ./41.deb
> \- Exit code | 100
> \- Software title | DietPi-Software
> \#### Steps to reproduce:
> 
> 1. Just try to install emby from dietpi-software
> 
> \#### Expected behaviour:
> 
> \- Emby server should be installed
> \#### Actual behaviour:
> 
> \- \[INFO \] DietPi-Software | APT install for: ./41.deb, please wait...
> E: Unable to correct problems, you have held broken packages.
> \[FAILED\] DietPi-Software | APT install for: ./41.deb
> - Command: apt-get -qq --allow-change-held-packages install ./41.deb
> \[INFO \] DietPi-Bugreport | Packing upload archive, please wait...
> 
> \#### Extra details:
> 
> \- I tried to install the 41.deb by hand with:
> sudo apt-get install /tmp/DietPi-Software/41.deb
> in the "Open subshell" and get this error:
> Note, selecting 'emby-server:arm64' instead of '/tmp/DietPi-Software/41.deb'
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
> emby-server:arm64 : Depends: zlib1g:arm64 (\>= 1:1.1.4) but it is not installable
> E: Unable to correct problems, you have held broken packages.
> 
> \#### Additional logs:
> \`\`\`
> E: Unable to correct problems, you have held broken packages.
> \`\`\`
> 
> Have it something to do with 64bit needed?
> I have an other Problem too with DietPi and Docker but this is not primary on my list and I will try Docker again in some days.
> But I stumbled about 64bit and Docker too...

---

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [14 September 2023 19:37 UTC](https://dietpi.com/forum/t/home-assistant-update-failing/17843/31 "2023-09-14T19:37:21Z")

</div>

Yes, the underlying problems with BerryBoot are always the same. In your case, the kernel image itself was updated, but not the kernel modules located below `/lib/modules/`. This StackExchange answer is very minimal and incomplete. Are there no official kernel upgrade docs for/from BerryBoot?  
However, copying the content of `/lib/modules/` from the image you downloaded over to the DietPi image should work.

[Previous page](https://dietpi.com/forum/t/home-assistant-update-failing/17843.md?page=1)
