Rpi4 Error message when updating omv update

  • L2ast login: Mon Aug 11 09:55:34 2025 from 192.168.2.19

    sudo apt update && sudo apt full-upgrade

    root@raspberrypi:~# sudo apt update && sudo apt full-upgrade

    Get:1 file:/var/cache/openmediavault/archives InRelease

    Ign:1 file:/var/cache/openmediavault/archives InRelease

    Get:2 file:/var/cache/openmediavault/archives Release

    Ign:2 file:/var/cache/openmediavault/archives Release

    Get:3 file:/var/cache/openmediavault/archives Packages

    Ign:3 file:/var/cache/openmediavault/archives Packages


    -- Serge Schneider <serge@raspberrypi.com> Mon, 11 Aug 2025 17:23:43 +0100


    Selecting previously unselected package raspi-firmware.

    (Reading database ... 60307 files and directories currently installed.)

    Preparing to unpack .../raspi-firmware_1%3a1.20250430-4~bookworm_all.deb ...

    Unpacking raspi-firmware (1:1.20250430-4~bookworm) ...

    Preparing to unpack .../archives/sense-hat_1.5_all.deb ...

    Unpacking sense-hat (1.5) over (1.4) ...

    Setting up raspi-firmware (1:1.20250430-4~bookworm) ...

    stat: cannot read file system information for '/boot/firmware': No such file or directory

    Error: missing /boot/firmware, did you forget to mount it?

    dpkg: error processing package raspi-firmware (--configure):

    installed raspi-firmware package post-installation script subprocess returned error exit status 1

    dpkg: dependency problems prevent configuration of sense-hat:

    sense-hat depends on raspi-firmware; however:

    Package raspi-firmware is not configured yet.


    dpkg: error processing package sense-hat (--configure):

    dependency problems - leaving unconfigured

    Processing triggers for initramfs-tools (0.142+rpt4+deb12u3) ...

    Errors were encountered while processing:

    raspi-firmware

    sense-hat

    E: Sub-process /usr/bin/dpkg returned an error code (1)

    root@raspberrypi:~#

  • Setting up raspi-firmware (1:1.20250430-4~bookworm) ...

    stat: cannot read file system information for '/boot/firmware': No such file or directory

    Error: missing /boot/firmware, did you forget to mount it?

    Is your boot partition mounted?

    And this is something to be asked on the raspberry forum.
    The issue has nothing to do with OMV.

  • dependency problems - leaving unconfigured

    Processing triggers for initramfs-tools (0.142+rpt4+deb12u3) ...

    Errors were encountered while processing:

    raspi-firmware

    sense-hat

    I mean these errors

    When sudo apt update

  • Birdybird

    Added the Label OMV 7.x
  • Birdybird

    Changed the title of the thread from “Rpi4 Error message when updating raspi firmware et” to “Rpi4 Error message when updating omv update”.
  • The errors are due to the failed access to the /boot/firmware

    you need to see what is wrong with it

  • But system is ok. Dont know what to do

    I get this error when omv update

    How is the system ok if you have errors while updating?


    I already told you that your /boot/firmware partition is spitting "is it mounted?" on post #3
    This has nothing to do with OMV, it's an issue from raspberry.

  • ryecoaaron
    Do you have any Pi running that has been updated from OMV6 to 7???


    According to the info above on raspberry forum, the change from Debian11 to 12 implied the move from /boot to /boot/firmware

    is it possible that the omv-release-upgrade didn't take that in consideration?

    of course, I'm assuming OP has been upgrading versions and not a fresh OMV7 install.

    Birdybird
    Post inside CODE boxes the output of:


    cat /etc/fstab


    sudo omv-showkey mntent


    df -h

    • Official Post

    Do you have any Pi running that has been updated from OMV6 to 7???

    yep


    According to the info above on raspberry forum, the change from Debian11 to 12 implied the move from /boot to /boot/firmware

    it did


    is it possible that the omv-release-upgrade didn't take that in consideration?

    omv-release-upgrade doesn't do anything RPi specific. I really don't remember if I did something manually or not. In my opinion, the RPi packages should do it but they technically don't support the debian 11 to 12 upgrade. I have seen lots of rpi omv6 to 7 upgrades on here and don't remember this being an issue though.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • In my opinion, the RPi packages should do it but they technically don't support the debian 11 to 12 upgrade.

    Yep, that's what the raspberry mods constantly advise.

    I have seen lots of rpi omv6 to 7 upgrades on here and don't remember this being an issue though.

    For me, it's also the first time I see someone complaining here on this forum about this specific issue.
    Maybe OP just got "lucky".

    It's easy to fix though.


    Since it's been too long since my last use of Pis (too many put away on the electronics box ATM) I just don't recall if the /boot partition is mentioned on the XML dB or not.

    • Official Post

    just don't recall if the /boot partition is mentioned on the XML dB or not.

    nope, it isn't. fixing the issue shouldn't require any omv changes.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Dont know how to put it in boxes


    Last login: Wed Aug 20 19:18:17 2025 from 192.168.2.19

    root@raspberrypi:~# cat /etc/fstab

    proc /proc proc defaults 0 0

    PARTUUID=1bcda4d6-01 /boot vfat defaults,flush 0 2

    PARTUUID=1bcda4d6-02 / ext4 noatime,nodiratime,defaults 0 1

    # >>> [openmediavault]

    /dev/disk/by-uuid/bdf49ae4-f7a7-4512-bce0-2c28f3d3adc6 /srv/dev-disk-by-uuid-bdf49ae4-f7a7-4512-bce0-2c28f3d3adc6 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2

    /dev/disk/by-uuid/677ec25a-9132-db01-606e-c25a9132db01 /srv/dev-disk-by-uuid-677ec25a-9132-db01-606e-c25a9132db01 ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2

    # <<< [openmediavault]

    # a swapfile is not a swap partition, no line here

    # use dphys-swapfile swap[on|off] for that

    root@raspberrypi:~#

  • @raspberrypi:~# sudo omv-showkey mntent

    <mntent>

    <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>

    <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>

    <dir>/xxx/yyy/zzz</dir>

    <type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>

    <opts></opts>

    <freq>0</freq>

    <passno>0|1|2</passno>

    <hidden>0|1</hidden>

    <usagewarnthreshold>xxx</usagewarnthreshold>

    <comment>xxx</comment>

    </mntent>

    <mntent>

    <uuid>bdcc58c5-14ff-42f5-93da-c17731619c75</uuid>

    <fsname>/dev/disk/by-uuid/bdf49ae4-f7a7-4512-bce0-2c28f3d3adc6</fsname>

    <dir>/srv/dev-disk-by-uuid-bdf49ae4-f7a7-4512-bce0-2c28f3d3adc6</dir> <type>ext4</type>

    <opts>defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>

    <freq>0</freq>

    <passno>2</passno>

    <hidden>0</hidden>

    <usagewarnthreshold>95</usagewarnthreshold>

    <comment></comment>

    </mntent>

    <mntent>

    <uuid>14d7142d-06d7-4720-b80c-1bd1927530ed</uuid>

    <fsname>/dev/disk/by-uuid/677ec25a-9132-db01-606e-c25a9132db01</fsname>

    <dir>/srv/dev-disk-by-uuid-677ec25a-9132-db01-606e-c25a9132db01</dir> <type>ext4</type>

    <opts>defaults,nofail,user_xattr,usrquota,grpquota,acl</opts>

    <freq>0</freq>

    <passno>2</passno>

    <hidden>0</hidden>

    <usagewarnthreshold>95</usagewarnthreshold>

    <comment></comment>

    </mntent>

    root@raspberrypi:~#

  • Last login: Wed Aug 20 19:34:40 2025 from 192.168.2.19

    root@raspberrypi:~# df -h

    Filesystem Size Used Avail Use% Mounted on

    /dev/root 15G 3.8G 9.8G 28% /

    devtmpfs 1.7G 0 1.7G 0% /dev

    tmpfs 1.9G 0 1.9G 0% /dev/shm

    tmpfs 759M 12M 748M 2% /run

    tmpfs 5.0M 16K 5.0M 1% /run/lock

    tmpfs 1.9G 236K 1.9G 1% /tmp

    /dev/mmcblk0p1 253M 50M 203M 20% /boot

    folder2ram 1.9G 137M 1.8G 8% /var/log

    /dev/sdb1 1.8T 1.6T 264G 86% /srv/dev-disk-by-uuid-bdf49ae4-f7a7-4512-bce0-2c28f3d3adc6

    folder2ram 1.9G 0 1.9G 0% /var/tmp

    folder2ram 1.9G 2.1M 1.9G 1% /var/lib/openmediavault/rrd

    folder2ram 1.9G 2.6M 1.9G 1% /var/spool

    folder2ram 1.9G 20M 1.9G 2% /var/lib/rrdcached

    folder2ram 1.9G 8.0K 1.9G 1% /var/lib/monit

    folder2ram 1.9G 44K 1.9G 1% /var/cache/samba

    tmpfs 380M 0 380M 0% /run/user/1000

    /dev/sda1 874G 524G 304G 64% /srv/dev-disk-by-uuid-677ec25a-9132-db01-606e-c25a9132db01

    tmpfs 380M 0 380M 0% /run/user/0

    root@raspberrypi:~#

  • Dont know how to put it in boxes



    Output of

    ls -al /boot


    ls -al /boot/firmware

  • Last login: Wed Aug 20 19:41:57 2025 from 192.168.2.19

    root@raspberrypi:~# ls -al /boot

    total 49810

    drwxr-xr-x 4 root root 4096 Jan 1 1970 .

    drwxr-xr-x 22 root root 4096 Aug 5 11:51 ..

    -rwxr-xr-x 1 root root 41 Mar 24 2022 .firmware_revision

    -rwxr-xr-x 1 root root 18693 Apr 6 2023 COPYING.linux

    -rwxr-xr-x 1 root root 1594 Apr 6 2023 LICENCE.broadcom

    drwxr-xr-x 2 root root 512 Mar 24 2022 'System Volume Information'

    -rwxr-xr-x 1 root root 28391 Mar 24 2022 bcm2708-rpi-b-plus.dtb

    -rwxr-xr-x 1 root root 27699 Mar 24 2022 bcm2708-rpi-b-rev1.dtb

    -rwxr-xr-x 1 root root 28084 Mar 24 2022 bcm2708-rpi-b.dtb

    -rwxr-xr-x 1 root root 28005 Mar 24 2022 bcm2708-rpi-cm.dtb

    -rwxr-xr-x 1 root root 29240 Mar 24 2022 bcm2708-rpi-zero-w.dtb

    -rwxr-xr-x 1 root root 27829 Mar 24 2022 bcm2708-rpi-zero.dtb

    -rwxr-xr-x 1 root root 29278 Mar 24 2022 bcm2709-rpi-2-b.dtb

    -rwxr-xr-x 1 root root 30390 Apr 6 2023 bcm2710-rpi-2-b.dtb

    -rwxr-xr-x 1 root root 32753 Apr 6 2023 bcm2710-rpi-3-b-plus.dtb

    -rwxr-xr-x 1 root root 32142 Apr 6 2023 bcm2710-rpi-3-b.dtb

    -rwxr-xr-x 1 root root 30285 Apr 6 2023 bcm2710-rpi-cm3.dtb

    -rwxr-xr-x 1 root root 31318 Apr 6 2023 bcm2710-rpi-zero-2-w.dtb

    -rwxr-xr-x 1 root root 31318 Apr 6 2023 bcm2710-rpi-zero-2.dtb

    -rwxr-xr-x 1 root root 52593 Apr 6 2023 bcm2711-rpi-4-b.dtb

    -rwxr-xr-x 1 root root 52682 Apr 6 2023 bcm2711-rpi-400.dtb

    -rwxr-xr-x 1 root root 38182 Apr 6 2023 bcm2711-rpi-cm4-io.dtb

    -rwxr-xr-x 1 root root 53202 Apr 6 2023 bcm2711-rpi-cm4.dtb

    -rwxr-xr-x 1 root root 50504 Apr 6 2023 bcm2711-rpi-cm4s.dtb

    -rwxr-xr-x 1 root root 52476 Apr 6 2023 bootcode.bin

    -rwxr-xr-x 1 root root 103 Jul 22 15:02 cmdline.txt

    -rwxr-xr-x 1 root root 2311 Oct 20 2024 config.txt

    -rwxr-xr-x 1 root root 7266 Apr 6 2023 fixup.dat

    -rwxr-xr-x 1 root root 5399 Apr 6 2023 fixup4.dat

    -rwxr-xr-x 1 root root 3173 Apr 6 2023 fixup4cd.dat

    -rwxr-xr-x 1 root root 8381 Apr 6 2023 fixup4db.dat

    -rwxr-xr-x 1 root root 8387 Apr 6 2023 fixup4x.dat

    -rwxr-xr-x 1 root root 3173 Apr 6 2023 fixup_cd.dat

    -rwxr-xr-x 1 root root 10230 Apr 6 2023 fixup_db.dat

    -rwxr-xr-x 1 root root 10228 Apr 6 2023 fixup_x.dat

    -rwxr-xr-x 1 root root 145 Jan 28 2022 issue.txt

    -rwxr-xr-x 1 root root 6242264 Mar 24 2022 kernel.img

    -rwxr-xr-x 1 root root 6596800 Mar 24 2022 kernel7.img

    -rwxr-xr-x 1 root root 7008792 Mar 24 2022 kernel7l.img

    -rwxr-xr-x 1 root root 8219600 Apr 6 2023 kernel8.img

    drwxr-xr-x 2 root root 24064 Apr 6 2023 overlays

    -rwxr-xr-x 1 root root 2975680 Apr 6 2023 start.elf

    -rwxr-xr-x 1 root root 2251392 Apr 6 2023 start4.elf

    -rwxr-xr-x 1 root root 805756 Apr 6 2023 start4cd.elf

    -rwxr-xr-x 1 root root 3747688 Apr 6 2023 start4db.elf

    -rwxr-xr-x 1 root root 2998888 Apr 6 2023 start4x.elf

    -rwxr-xr-x 1 root root 805756 Apr 6 2023 start_cd.elf

    -rwxr-xr-x 1 root root 4819624 Apr 6 2023 start_db.elf

    -rwxr-xr-x 1 root root 3722504 Apr 6 2023 start_x.elf

    root@raspberrypi:~#

  • Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64


    The programs included with the Debian GNU/Linux system are free software;

    the exact distribution terms for each program are described in the

    individual files in /usr/share/doc/*/copyright.


    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

    permitted by applicable law.

    Last login: Wed Aug 20 21:40:01 2025 from 192.168.2.19

    root@raspberrypi:~# ls -al /boot/firmware

    ls: cannot access '/boot/firmware': No such file or directory

    root@raspberrypi:~#

  • I give up...


    Is it so difficult to read the Post I pointed to you and post the outputs on a CODE box???

    [How-To] Post content in a code box - Guides - openmediavault

    Since I have no time to do more piggybacking, just go to the raspberry forum post I gave you on #8 and the solution is mentioned there.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!