Posts by spupuz

    Hi i'm getting this error at the reboot and ftp is stopped i need to disable and enable again:



    how ca i solve it?

    i'm going to thing about and upgrade to my OMV,


    if i don't change boot and data disk but i change motherboard, memory and cpu.

    what is the best way to manage that kind of change?

    what should i do in order to make it start again properly?

    is it possible?


    thanks in advace

    Your database upgrade never happened. I would backup your install and run the following:


    sudo /usr/share/openmediavault/confdb/migrations.d/conf_5.0.0.sh

    sudo /usr/share/openmediavault/confdb/migrations.d/conf_5.0.3.sh

    sudo /usr/share/openmediavault/confdb/migrations.d/conf_5.2.0.sh

    how can we check if it has happened in other cases? i followed the same procedure and i don't have problems, but i would like to check

    is there an unofficial guide to upgrade from 4.x to 5.x? i have no plugin installed and just samba shares, ftp and docker but already using portainer (also in a docker)?

    is it safe?


    also i don't use ovm-extra neither other plugins.


    sed -i "s/stretch/buster/g" /etc/apt/sources.list

    sed -i "s/stretch/buster/g" /etc/apt/sources.list.d/*

    sed -i "s/arrakis/usul/g" /etc/apt/sources.list.d/*

    sed -i "/[Dd]ocker/d" /etc/apt/sources.list.d/omv-extras-org.list

    apt-get update

    apt-get dist-upgrade


    reboot


    is this enough or do i have to do something else?

    coretemp-isa-0000
    Adapter: ISA adapter
    Core 0: +94.0°C (high = +84.0°C, crit = +100.0°C) ALARM (CRIT)
    Core 1: +94.0°C (high = +84.0°C, crit = +100.0°C) ALARM (CRIT)
    Core 2: +91.0°C (high = +84.0°C, crit = +100.0°C) ALARM (CRIT)
    Core 3: +92.0°C (high = +84.0°C, crit = +100.0°C) ALARM (CRIT)

    root@openmediavault:~# sensors
    coretemp-isa-0000
    Adapter: ISA adapter
    Core 0: +69.0°C (high = +84.0°C, crit = +100.0°C) ALARM (CRIT)
    Core 1: +68.0°C (high = +84.0°C, crit = +100.0°C) ALARM (CRIT)
    Core 2: +65.0°C (high = +84.0°C, crit = +100.0°C) ALARM (CRIT)
    Core 3: +66.0°C (high = +84.0°C, crit = +100.0°C) ALARM (CRIT)

    again, is that CPU temperature too high?


    here are last messages before crashing and 7:29 and then restart 8:39 in /var/log/syslog:





    Files

    • syslog.txt

      (18.71 kB, downloaded 51 times, last: )

    Hi, have built this OMV last november 2018 i had no problem since last week it started to crash and i found it sever time shutted down and still it's having this behaviour, i can't understand why, can anyone help me? which logs can i provide?




    i have docker with some image running, smb, ftp, ssh and virtualbox as services


    in attach the repot

    Files


    Sorry, when you talk about 4 version or 2.14 you talk bout version of what OMV, Kernel or Virtualbox?


    sorry for the dumb question