'Enable Network' in recovery mode not working properly.

I did some progress...

I was able to make a few 'enabled|static' services to start such as :
dbus.socket
networking.service
system-resolved.service

NetworkManger doesn't seems to start well.

By making the following changes :

# /lib/recovery-mode/options/network
--------------------------------------
if [ -d /run/systemd/system ]; then
- for i in dbus.socket systemd-resolved.service networking.service systemd-networkd.service NetworkManager.service; do
+ for i in dbus.socket networking.service systemd-networkd.service systemd-resolved.service NetworkManager.service; do
- systemctl is-enabled -q $i && systemctl start $i
+ systemctl is-enabled -q $i && systemctl --job-mode=ignore-dependencies --no-ask-password start $i
    done
    /lib/systemd/systemd-networkd-wait-online && exit 0
fi
--------------------------------------

* Changed the order to start systemd-resolved.service as mentioned in:

# /lib/systemd/system/systemd-resolved.service
After=systemd-networkd.service network.target

to be after systemd-networkd.service

* Add "--no-ask-password" to avoid systemd-tty-ask-password-agent to block
* Add "--job-mode=ignore-dependencies" has most of the service are not running and waiting.

By reading more about systemd, I start to think the blocker here to start the desired services is "Type=oneshot" instruction in friendly-recovery.service.

"
Behavior of oneshot is similar to simple; however, it is expected that the process has to exit before systemd starts follow-up units.
"

Need to explore more that route.

So all the remaining jobs are basically waiting for friendly-recovery to exit to start due to the "oneshot" instruction, which make xnox patch (revno 152) not working.

Some waiting jobs are units in which the desired network services in revno 152 depends on.
I totally understand why "oneshot" is set, but in this case it is the blocker.

If we remove "oneshot" then everything will start and make the recovery mode useless.
So I think "oneshot" need to stay there.

The only thing then I can think of atm is to add --job-mode=ignore-dependencies --no-ask-password and possibly extra stuff in frienly-recovery.service to make the necessary network services to start in recovery mode when requesting 'Enable Network'.

or possibly add After=network.target or something around those line.

Status changed to 'Confirmed' because the bug affects multiple users.

https://www.freedesktop.org/software/systemd/man/systemctl.html

If "ignore-dependencies" is specified, then all unit dependencies are ignored for this new job and the operation is executed immediately. If passed, no required units of the unit passed will be pulled in, and no ordering dependencies will be honored. This is mostly a debugging and rescue tool for the administrator and should not be used by applications

based on the above description, --job-mode may apply in friendly-recovery as it fit in a debugging purpose IMHO.

The only problem missing is the dbus aspect.

dbus.service is necessary for NetworkManager but cannot be started manually[1], preventing NetworkManager to start succefully.

[1] dbus.service
# we don't properly stop D-Bus (see ExecStop=), thus disallow restart
RefuseManualStart=yes

As a debug exercise, I have commented (#RefuseManualStart=yes) start dbus.service by hand and then pick the 'Enable Networking' option and it works.

Need to find a way to make dbus.service to start with friendly-recovery or when 'Enable Network' is chosen.

So the --job-mode=ignore-dependencies approach cover the scenario when using systemd-networkd, but NetworkManager still fails for the reason above ^ (dbus.service) not starting.

Hello

My ubuntu version is 18.04.1

cat /etc/lsb*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

It works very well. But thinking that someday, this could not be the case, I decided to check if the recovery mode works

function "fsck" works
function "dpg" works
but function "enable network support" hangs.
dmesg | grep vmlinuz
[ 0.000000] Command line: \\boot\vmlinuz-4.15.0-32-generic recovery root=UUID=cb50473a-5d9c-441a-9502-690c1c8684d6 ro initrd=\boot\initrd.img-4.15.0-32-generic
[ 0.000000] Kernel command line: \\boot\vmlinuz-4.15.0-32-generic recovery root=UUID=cb50473a-

it is necessary to press the ctrl c keys to unlock the situation.

(checked with two different computers.

Attachment: contents of the start trace

Another computer

We made some progress last week about this bug. We should be able to push the changes into bzr soon, and then start testing. Once the testing feedback are positive, we will then start SRU'ing the fix.

- Eric

Test packages[1] are available for Xenial/16.04 & Bionic/18.04 on my PPA[2]. I did some preliminary test which seems to work as expected.

Please anyone affected test the packages, and keep me posted.

[1] - Test package
Xenial - friendly-recovery - 0.2.31ubuntu1+testpkgb2
Bionic - friendly-recovery - 0.2.38ubuntu1+testpkgb1

[2] PPA
sudo add-apt-repository ppa:slashd/test
sudo apt-get update
sudo apt-get install friendly-recovery

Regards,
Eric

Hello Eric, I just tested your "friendly-recovery" PPA package on Bionic/18.04, and it works perfectly ! Network access is finally restored when I use friendly-recovery menu. (NetworkManager is no longer stopped from being start by dbus dependency.)
Well done !

I still don't understand why this bug's importance is "Low". When you are stucked in recovery mode without network and you can't (re)install/upgrade critical packages (like graphics drivers package) ... Good luck !

Thanks Saroumane,

I changed the priority to medium. I'm waiting for another test feedback, and I'll upload the new packages in the upload queue very soon.

- Eric

debdiff for Xenial

debdiff for bionic

debdiff for cosmic

I've been told that the "resume" doesn't resume boot.

Can someone validate ?

This is good. After accepting please double-check if the resume functionality really didn't regress. Thanks!

Hello Eric, or anyone else affected,

Accepted friendly-recovery into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/friendly-recovery/0.2.38ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Uploaded to Xenial as well. It is now waiting for SRU approval to start building in xenial-proposed for the testing phase.

[Verification Done Bionic]

I have tested "0.2.38ubuntu1" in Bionic/18.04.1 LTS. Recovery mode now properly enable 'network' and 'dns' (/etc/resolv.conf) as expected with systemd without hitting dependencies unit issues nor asking for tty-ask-password or anything else which was previously blocking the process networking process when systemd-networkd or NetworkManager was involved.

The other friendly-recovery options still works and seems to behave as it was prior this SRU.

- Eric

The verification of the Stable Release Update for friendly-recovery has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package friendly-recovery - 0.2.38ubuntu1

---------------
friendly-recovery (0.2.38ubuntu1) bionic; urgency=medium

  [ Dimitri John Ledkov ]
  * Actually use a friendly-recovery.target which systemd boots to
    using a generator for default.target symlink. This ensures that
    one is not in the middle of a boot transaction during recovery
    and can start/stop/change systemd units without interference.
  * Cleanup lintian warnings. (LP: #1766872)

 -- Eric Desrochers <email address hidden> Mon, 15 Oct 2018 09:02:45 -0400

Hello Eric, or anyone else affected,

Accepted friendly-recovery into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/friendly-recovery/0.2.31ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

I tested friendly-recovery 0.2.31ubuntu2 in Xenial/16.04.3 LTS.

Selecting network Enable networking" from the Recovery Menu now enables the network and DNS successfully. I can "cat /etc/resolv.conf" vs before I couldn't. I don't see any issues with dependencies or asking for tty-ask-password or anything that was reported previously.

Selecting "resume Resume normal boot" works good as well to return to the normal OS.

This bug was fixed in the package friendly-recovery - 0.2.31ubuntu2

---------------
friendly-recovery (0.2.31ubuntu2) xenial; urgency=medium

  [ Dimitri John Ledkov ]
  * Actually use a friendly-recovery.target which systemd boots to
    using a generator for default.target symlink. This ensures that
    one is not in the middle of a boot transaction during recovery
    and can start/stop/change systemd units without interference.
  * Cleanup lintian warnings. (LP: #1766872)

 -- Eric Desrochers <email address hidden> Tue, 02 Oct 2018 14:43:12 -0400

With friendly-recovery version 0.2.38ubuntu1, selecting the check filesystems option results in an error message like:

/etc/default/rcS: file or directory not found

This file does not exist on my system. I don't know if the problem I'm reporting is related to this issue, but it does seem to be the same as another bug that was marked as a duplicate of this one (1767685).

Cory, problem is not related, but I agree that this must be fix eventually in Ubuntu.
I have to check if it was fix upstream.

Can you please report a new bug about it ?