You can re-enable them after the upgrade with the ‘software-properties’ tool or your package manager. 1 installed package is no longer supported by Canonical.
In case of the following or similar message it could be necessary to use the Solaris failsafe boot: Rebooting with command: boot Boot device: disk:a File and args: Sun OS Release 5.10 Version Generic_141414-07 64-bit Copyright 1983-2009 Sun Microsystems, Inc. To accomplish this, on a GRUB-based platform, reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe".
Now the issue is that the failsafe boot is not mounting the SVM root mirror and manual intervention is necessary to update the boot archive on all devices within the SVM root mirror.
This procedure does NOT require to unmirror the SVM root mirror to update the boot archive.
Hi when trying apt-get update it fails with Hit:1 xenial In Release Hit:2 xenial-updates In Release Hit:3 xenial-security In Release ** (appstreamcli:13571): CRITICAL **: Error while moving old database out of the way. Done [email protected]:/mnt/c/Users/Dave/Desktop$ sudo apt-get upgrade sudo: unable to resolve host DESKTOP-3RQO5S5 Reading package lists...
Done [email protected]:/mnt/c/Users/Dave/Desktop$ sudo apt-get update sudo: unable to resolve host DESKTOP-3RQO5S5 Hit:1 mirror://mirrors.ubuntu.com/xenial In Release Hit:2 mirror://mirrors.ubuntu.com/xenial-updates In Release Hit:3 mirror://mirrors.ubuntu.com/xenial-backports In Release Hit:4 mirror://mirrors.ubuntu.com/xenial-security In Release Reading package lists...
If anything goes wrong with the running ssh you can still connect to the additional one.
Updating repository information WARNING: Failed to read mirror file Third party sources disabled Some third party entries in your were disabled.
Since Solaris 10 10/08 update6 the boot archive feature was implemented into Solaris 10 for sparc.
When the system is configured with Solaris Volume Manager (SVM) root mirror then attention is necessary if using the failsafe boot (boot -F failsafe) on the 'ok prompt' environment. Hardware watchdog enabled Hostname: scnode1 WARNING: The following files in / differ from the boot archive: changed /kernel/drv/The recommended action is to reboot into the failsafe archive to correct the above inconsistency.
Changing major releases on linux is always a risk, but Debian / Ubuntu dist-upgrades really worked fine the last years.