--- edit ---
gerade gesehen dass nichtmal das update auf 1.4 erfolgreich war
--------------
ich habe heute via OVF eine loxberry VM erstellt und erstmal Updates gemacht (kein einziges Plugin instqalliert). Nach den kleinen Updates habe ich das Update von 1.4.4 auf 2.0.0 gestartet.
Zum Glück habe ich mir davor einen Snapshot gemacht, weil das Update offenbar zweimal schiefgegangen ist. In beiden Fällen ist der apache nicht gelaufen und Zugriff war nur per SSH möglich.
Das log vom letzten Reboot hat folgendes geschrieben:
================================================== ============================== <LOGSTART> 12.05.2021 19:19:22 TASK STARTED <LOGSTART> Update Reboot script /opt/loxberry/sbin/loxberryupdate/updatereboot_v1.4.0.pl started. <INFO> LoxBerry Version 2.0.0 ( is_vmware.cfg is_x64.cfg ) <INFO> Loglevel: 7 <INFO> Message : Doing system upgrade (envoked from upgrade to V1.4.0) <INFO> This script already started 5 times. <INFO> Try to reach download.loxberry.de <OK> download.loxberry.de is reachable, so network seems to be up. <INFO> Repair broken apt database from maybe broken updates Reading package lists... Building dependency tree... Reading state information... The following package was automatically installed and is no longer required: python3-debconf Use 'apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up grub-pc (2.02+dfsg1-20+deb10u4) ... debconf: unable to initialize frontend: Dialog debconf: (TERM is not set, so the dialog frontend is not usable.) debconf: falling back to frontend: Readline Configuring grub-pc ------------------- The GRUB boot loader was previously installed to a disk that is no longer present, or whose unique identifier has changed for some reason. It is important to make sure that the installed GRUB core image stays in sync with GRUB modules and grub.cfg. Please check again to make sure that GRUB is written to the appropriate boot devices. If you're unsure which drive is designated as boot drive by your BIOS, it is often a good idea to install GRUB to all of them. Note: it is possible to install GRUB to partition boot records as well, and some appropriate partitions are offered here. However, this forces GRUB to use the blocklist mechanism, which makes it less reliable, and therefore is not recommended. 1. /dev/sda (37580 MB; Virtual_disk) 3. none of the above 2. /dev/sda1 (35432 MB; Virtual_disk) (Enter the items you want to select, separated by spaces.) GRUB install devices:
Kommentar