Cannot boot this morning, network looks down

Hi,

First big issue after months with EOS : cannot boot system anymore this morning.
Boot fails when mount some NFS share, then after timeout I am moved to emergency mode. If I look at network at that time (ip addr), networks appears down. Don’t know what to do more at that step.

Fortunately, desktop has dual boot with Debian, and Debian boots fine (network, etc…).
Looking at system logs, here is some output :

$ grep fail eos-log.txt
avril 13 10:02:57 pascal-eos kernel: asus_wmi: failed to register LPS0 sleep handler in asus-wmi
avril 13 10:02:57 pascal-eos kernel: faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
avril 13 10:02:57 pascal-eos kernel: cfg80211: failed to load regulatory.db
avril 13 10:04:26 pascal-eos systemd[1]: Dependency failed for /External-Backup.
avril 13 10:04:26 pascal-eos systemd[1]: Dependency failed for Local File Systems.
avril 13 10:04:26 pascal-eos systemd[1]: local-fs.target: Job local-fs.target/start failed with result ‘dependency’.
avril 13 10:04:26 pascal-eos systemd[1]: External\x2dBackup.mount: Job External\x2dBackup.mount/start failed with result ‘dependency’.
avril 13 10:04:26 pascal-eos systemd[1]: dev-disk-by\x2duuid-4435edb2\x2dcc7c\x2d44fd\x2db343\x2d537c4d2ac117.device: Job dev-disk-by\x2duuid-4435edb2\x2dcc7c\x2d44fd\x2db343\x2d537c4d2ac117.device/start failed with result ‘timeout’.

Tried other boot options from GRUB (LTS kernel, legacy) with no luck. Still timeout on NFS mount.

Any idea what I should check or take action when I am in Emergency mode ?
Thanks !

Normally a non-reachable NFS mount should not result in emergency mode - at least it does not with my installation.
How do you mount your NFS shares? If you do it via fstab, mind to share it?

Sorry, I was wrong, this was a USB external disk that was faultly (/External-Backup).
Issue is now solved, not really sure how it works now, but here is what I did :

From emergency mode, I set up ethernet manually :

ip a add 192.168.1.20/24 dev enp9s0
ip link set enp9s0 up

Interface was now UP with the right address.
I also check mount manually and realize that it was the USB disk in fault, which I commented out from /etc/fstab.
Then I press Ctrl-D and Gnome session started successfully (previously with network down, system was hanging at that step).
So I Iogin Gnome, disconnect/reconnect USB disk manually, and it comes back (!) (ok, old disk, may be good to take some preventive action about it).
But internet was not working (probably wrong DNS setting). So I launched a reboot … and all was back to normal.

So it seems the USB disk in error generated the mount error, and the emergency mode after. A bit strange to me though… Is that expected ?

Thank you for helping !