Posts by Slavek

    Hi.

    I also have restarts on odroid HC2 device.

    Thank you chente for your time spending on my problem.

    I will do again installation (armbian only) and check for a problem.


    If error occurred after updates maybe is caused by:

    armbian-bsp-cli-odroidxu4-current armbian-config armbian-firmware

    armbian-plymouth-theme armbian-zsh base-files

    linux-dtb-current-odroidxu4 linux-image-current-odroidxu4

    linux-u-boot-odroidxu4-current ?


    Update, for information only.

    I did again full installation and after each step executed manualy command systemctl list-unit-files

    All was OK till omv-regen regenera.

    I did again full installation using older backup. And again after regenera problem is back.

    Thanks for answer.

    Option "update the system" is not set.

    3d03dd6706d248e79ef97594ae6098c9.png


    d8944c00165b7986f75ecef41787cc22.png


    omv-upgrade is not causing system reset. Is still working.


    ccc696aff864525453782795ac9b0246.png


    Strange thing is OMV not showing info about sd card, but info can be read from:


    7cf8b2694438c97d50a3b5336fef5cfe.png


    omv-regen regenera also is not able to show/read info from sdcard? Is it error or normal situation when I'am running regenera with old system disk?


    7110271a4e7b254cd421c5cd947764fb.png


    Anyway i will try to change my sd card in few days.

    Hello,

    i find that my scheduled daily omv-regen backup was done last time on May 27th. Every 'omv-regen backup' try (scheduled or manually) is leading to system restart. On May 27th. (few hours after last backup) my system was updating. Also in GUI OMV is not listed my system disk's parameters like before. Did someone can check my log for errors, please?

    The last activity before restart:

    58ac6325c585bc0c4317bcf776d27989.png


    e27f6134065a6489361f91c3857cc380.png

    OS: Armbian (24.5.1) armv7l --- Host: Hardkernel ODROID XU4 --- Kernel: 6.6.31-current-odroidxu4 --- Shell: bash 5.2.15 --- CPU: Samsung Exynos (Flattened Device Tree) (8) @ 200MHz

    Hi guys.

    After successfully upgrade to

    Version
    7.0.2-2 (Sandworm)

    Processor
    ARMv7 Processor rev 3 (v7l)

    Kernel
    Linux 6.1.79-current-odroidxu4


    I received warnings:

    Code
    W: http://apt.armbian.com/dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

    My apt-key list not showing any armbian-related file/code/?



    Code
    root@omv:~# apt update
    ........
    W: http://apt.armbian.com/dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
    N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
    N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/armhf/release-notes/ch-information.html#non-free-split

    According to this info:

    Chapter 5. Issues to be aware of for bookworm

    and:

    Code
    root@omv:~# cat /etc/apt/apt.conf.d/no-bookworm-firmware.conf
    cat: /etc/apt/apt.conf.d/no-bookworm-firmware.conf: No such file or directory


    should I only:

    Quote

    If you were pointed to this chapter by apt you can prevent it from continuously notifying you about this change by creating an apt.conf(5) file named /etc/apt/apt.conf.d/no-bookworm-firmware.conf with the following content:

    Code
    APT::Get::Update::SourceListWarnings::NonFreeFirmware "false";

    ?

    Hi.

    Changing variable from "yes" to "no" solving problem in my case (odroid 4u 32 bit).

    I find one strange (for me) thing. In GUI valid date is quite different.


    from email:

    Code
    /etc/cron.daily/openmediavault-check_ssl_cert_expiry:
    date: invalid date ‘Apr 29 07:20:24 2048’
    run-parts: /etc/cron.daily/openmediavault-check_ssl_cert_expiry exited with return code 1


    from CLI:

    root@omv:~# date -d "Apr 29 07:20:24 2048" +%s

    date: invalid date ‘Apr 29 07:20:24 2048'


    from GUI (valid to):

    Hi,

    ls List directory

    ls -l Gives more information about every file/directory

    ls -l filename.txt Gives file information

    pwd Show current working directory


    for example:

    root@OMV:~# ls /etc/mc

    edit.indent.rc mc.default.keymap mc.ext mc.menu sfs.ini

    filehighlight.ini mc.emacs.keymap mc.keymap mcedit.menu

    We did it on Oct 6th 2022. Few post ago.

    If warning is not harming my upgrade, I will try clean install and config from beginning. Probably will be faster.

    Thank You very much for your help.

    I'm surrender. Maybe in few day I will try upgrade again after restoring my OMV5 backup, just to check why is upgrde not working.

    reboot:

    still old version.

    ...

    omv-salt

    rm /etc/netplan/20-openmediavault-enx001e0632bfca.yaml

    omv-salt

    no error

    nano /etc/netplan/20-openmediavault-enx001e0632bfca.yaml - file is empty

    omv-firstaid - dhcp config

    omv-upgrade:

    omv-release-upgrade

    ...

    Always after restoring backup this file contains mac. Always after executing "omv-salt stage run deploy" error apears and mac is missing. I can add mac manually, repeat omv-salt... and mac is missing again. Continuing with point 5.2 and finishing upgrade always giving false "successfull" message and there is no change.

    I've tried this several times.

    Using putty on windows for ssh, the beginning of the output 5.1 is not visible (can't scroll, maybe too long output?). Starting post from network error (missing mac). All what I can copy from putty is here: https://1dr

    But after omv-upgrade, omv-release-upgrade and reboot I have info about successfully upgrade to omv6, but I don't have a GUI via web browser and omv is still

    root@OMV:~# dpkg-query -W -f='${Version}' openmediavault

    5.6.26-1root@OMV:~#

    and is not upgraded to bullseye.

    This is probably the last problem:

    Code
    W: --force-yes is deprecated, use one of the options starting with --allow instead.

    I can't find any file containing --force-yes

    with command:

    Where can it be located?

    Part2/2