Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster [SOLVED]

Questions about cabled networking
Forum rules
Before you post please read how to get help
Post Reply
Halbarad
Level 1
Level 1
Posts: 28
Joined: Tue Feb 05, 2019 2:30 pm

Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster [SOLVED]

Post by Halbarad »

EDIT after solving. The problem didn't have to do with the network but with the fact that, during installation, I asked Debian to use the swapfile partition already used by Mint. Debian changed the UUID for the partition, and so Mint kept looking for the old UUID partition until timeout. The solution: to replace the UUID in Mint's /etc/fstab with the new (correct) one. Many thanks to Larry78723!

Hi, I have a multi-boot machine with Mint 19.3 (kernel 5.4.0-47), Lubuntu and a freshly installed Debian Buster. After installing Debian, Debian and Lubuntu boot in 7-8 seconds, as Mint also used to, but Mint takes some 97 seconds to boot. I enclose an excerpt from the output of dmesg:

Code: Select all

...
[    6.330278] input: HP WMI hotkeys as /devices/virtual/input/input9
[   95.714398] RTL8208 Fast Ethernet r8169-800:00: attached PHY driver [RTL8208 Fast Ethernet] (mii_bus:phy_addr=r8169-800:00, irq=IGNORE)
[   95.978739] r8169 0000:08:00.0 enp8s0: Link is Down
[   97.770444] r8169 0000:08:00.0 enp8s0: Link is Up - 100Mbps/Full - flow control rx/tx
[   97.770454] IPv6: ADDRCONF(NETDEV_CHANGE): enp8s0: link becomes ready
[   97.874998] vboxdrv: loading out-of-tree module taints kernel.
...
I tried to boot with kernel 4.15.0-117 (the same as in Lubuntu):

Code: Select all

...
[   38.467901] audit: type=1400 audit(1600251732.091:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=742 comm="apparmor_parser"
[  127.933240] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
[  128.148091] r8169 0000:08:00.0 enp8s0: link down
[  128.148092] r8169 0000:08:00.0 enp8s0: link down
[  128.148194] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
[  128.152513] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready
[  128.152574] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[  128.152804] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37
[  128.283367] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready
[  128.349239] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready
[  129.447649] wlp9s0f0: authenticate with cc:ce:1e:e7:0d:49
[  129.449338] wlp9s0f0: send auth to cc:ce:1e:e7:0d:49 (try 1/3)
[  129.451663] wlp9s0f0: authenticated
[  129.451959] wlp9s0f0: associate with cc:ce:1e:e7:0d:49 (try 1/3)
[  129.459929] wlp9s0f0: RX AssocResp from cc:ce:1e:e7:0d:49 (capab=0x431 status=0 aid=1)
[  129.460023] wlp9s0f0: associated
[  129.534490] IPv6: ADDRCONF(NETDEV_CHANGE): wlp9s0f0: link becomes ready
[  129.759600] r8169 0000:08:00.0 enp8s0: link up
[  129.759607] IPv6: ADDRCONF(NETDEV_CHANGE): enp8s0: link becomes ready
[  129.855829] PKCS#7 signature not signed with a trusted key
[  129.855839] vboxdrv: loading out-of-tree module taints kernel.
...
There is another 30 seconds delay a bit before, but it has to do with mounting the filesystem -- no such delay is there with the newer kernel 5.4.0-47.
I find it puzzling that Lubuntu should boot very fast with the same kernel and I wonder if there is a way for speeding up Mint's kernel and making it attach the PHY driver r8169 without waiting some 60 seconds before doing so. Maybe some flag in grub?? I'd also very much like to know the reasons of the delay etc. I hope someone that knows about networking and booting can shed some light on this. Thanks
Last edited by Halbarad on Fri Sep 18, 2020 4:56 pm, edited 4 times in total.
User avatar
Larry78723
Level 8
Level 8
Posts: 2108
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Boot gets stuck on attached PHY driver after installing Debian Buster

Post by Larry78723 »

Please reboot and run the following command so we can see exactly where the holdup is:

Code: Select all

systemd-analyze critical-chain

Post the results here.
Image
Halbarad
Level 1
Level 1
Posts: 28
Joined: Tue Feb 05, 2019 2:30 pm

Re: Boot gets stuck on attached PHY driver after installing Debian Buster

Post by Halbarad »

Thank you for replying. Here it is:

Code: Select all

$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @2min 1.023s
└─multi-user.target @2min 1.023s
  └─virtualbox.service @2min 830ms +191ms
    └─network-online.target @2min 822ms
      └─network.target @1min 30.780s
        └─NetworkManager.service @1min 30.559s +219ms
          └─dbus.service @1min 30.539s
            └─basic.target @1min 30.488s
              └─sockets.target @1min 30.488s
                └─cups.socket @1min 30.488s
                  └─sysinit.target @1min 30.483s
                    └─apparmor.service @1.825s +81ms
                      └─local-fs.target @1.823s
                        └─media-alberto-Old_System_Disk.mount @1min 35.620s
                          └─clean-mount-point@media-alberto-Old_System_Disk.serv
                            └─system-clean\x2dmount\x2dpoint.slice @1min 35.652s
                              └─system.slice @263ms
                                └─-.slice @260ms

I also post an excerpt of the results of dmesg in Debian Buster, which more or less corresponds to the one for Mint:

Code: Select all

[    5.497914] input: HP WMI hotkeys as /devices/virtual/input/input15
[    5.717636] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
[    5.718632] r8169 0000:08:00.0: firmware: direct-loading firmware rtl_nic/rtl8106e-1.fw
[    5.719072] Generic PHY r8169-800:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-800:00, irq=IGNORE)
[    5.982394] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
[    5.990569] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready
[    5.990651] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[    5.990832] rt2800pci 0000:09:00.0: firmware: direct-loading firmware rt3290.bin
[    5.990839] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37
[    6.097466] broken atomic modeset userspace detected, disabling atomic
[    6.116019] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready
[    6.243998] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready
[    6.344134] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready
[   11.191293] IPv6: ADDRCONF(NETDEV_UP): wlp9s0f0: link is not ready
[   11.998562] r8169 0000:08:00.0 enp8s0: Link is Up - 100Mbps/Full - flow control rx/tx
[   11.998575] IPv6: ADDRCONF(NETDEV_CHANGE): enp8s0: link becomes ready
[   12.302358] wlp9s0f0: authenticate with cc:ce:1e:e7:0d:49
[   12.304076] wlp9s0f0: send auth to cc:ce:1e:e7:0d:49 (try 1/3)
[   12.317486] wlp9s0f0: authenticated
[   12.318225] wlp9s0f0: associate with cc:ce:1e:e7:0d:49 (try 1/3)
[   12.330836] wlp9s0f0: RX AssocResp from cc:ce:1e:e7:0d:49 (capab=0x431 status=0 aid=1)
[   12.330899] wlp9s0f0: associated
[   12.367260] IPv6: ADDRCONF(NETDEV_CHANGE): wlp9s0f0: link becomes ready
The crucial line seems to me

Code: Select all

[    5.718632] r8169 0000:08:00.0: firmware: direct-loading firmware rtl_nic/rtl8106e-1.fw
This is missing in the Mint startup sequence--but I'm just guessing.
User avatar
Larry78723
Level 8
Level 8
Posts: 2108
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster

Post by Larry78723 »

Try disabling IPV6 in both wired and wifi network connections then reboot. That looks like where the problem is.
Image
Halbarad
Level 1
Level 1
Posts: 28
Joined: Tue Feb 05, 2019 2:30 pm

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster

Post by Halbarad »

I tried, but the problem is still there. I added the required lines to /etc/sysctl.conf

Code: Select all

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
I also changed /etc/default/grub adding "ipv6.disable=1" to GRUB_CMDLINE_LINUX_DEFAULT.
Reboot took the usual 90-something secs; then I first checked that ipv6 was disabled (it was). I enclose the relevant section from the output of dmesg:

Code: Select all

[    6.350615] input: HP WMI hotkeys as /devices/virtual/input/input9
[   96.109504] RTL8208 Fast Ethernet r8169-800:00: attached PHY driver [RTL8208 Fast Ethernet] (mii_bus:phy_addr=r8169-800:00, irq=IGNORE)
[   96.362922] r8169 0000:08:00.0 enp8s0: Link is Down
[   96.366960] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[   96.367308] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37
This is the output of systemd-analyze:

Code: Select all

systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @2min 1.074s
└─multi-user.target @2min 1.074s
  └─virtualbox.service @2min 982ms +91ms
    └─network-online.target @2min 976ms
      └─network.target @1min 30.923s
        └─NetworkManager.service @1min 30.492s +428ms
          └─dbus.service @1min 30.467s
            └─basic.target @1min 30.459s
              └─sockets.target @1min 30.459s
                └─acpid.socket @1min 30.459s
                  └─sysinit.target @1min 30.453s
                    └─apparmor.service @1.207s +107ms
                      └─local-fs.target @1.196s
                        └─run-user-1000-gvfs.mount @1min 34.214s
                          └─run-user-1000.mount @1min 32.054s
                            └─local-fs-pre.target @446ms
                              └─keyboard-setup.service @280ms +165ms
                                └─systemd-journald.socket @270ms
                                  └─system.slice @268ms
                                    └─-.slice @265ms
I actually expected that the problem didn't have to do with ipv6 because (i) boot and startup were fine before installing Debian; (ii) both Debian and Lubuntu boot in a few seconds, even with the same hardware and with the same kernel (for Lubuntu).
Before installing Debian I actually had three OSs installed: Lubuntu and two Mint 19.3--I kept a Mint for "experiments". Both my Mints now behave the same way on boot & startup. I should perhaps reinstall one of them and see.
t42
Level 4
Level 4
Posts: 232
Joined: Mon Jan 20, 2014 6:48 pm

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster

Post by t42 »

Halbarad wrote:
Fri Sep 18, 2020 5:43 am
I actually expected that the problem didn't have to do with ipv6
Just to confirm that please try to pass kernel parameters to disable IPv6 at the boot time.
Edit /etc/default/grub

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"
GRUB_CMDLINE_LINUX="ipv6.disable=1"
Just add ipv6.disable=1 to what you have there.
Save the file and run the update-grub:

Code: Select all

sudo update-grub
-=t42=-
Halbarad
Level 1
Level 1
Posts: 28
Joined: Tue Feb 05, 2019 2:30 pm

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster

Post by Halbarad »

@t42: this is precisely what I did, as I think I mentioned in my previous post. Ipv6 is not the culprit, not this time.
t42
Level 4
Level 4
Posts: 232
Joined: Mon Jan 20, 2014 6:48 pm

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster

Post by t42 »

Halbarad wrote:
Fri Sep 18, 2020 6:30 am
this is precisely what I did
...sorry...

Nothing fancy in /etc/network/interfaces and /etc/network/interfaces.d/setup ?
You can compare with your Debian files and even substitute with them if there is a significant difference.
In my Debian bullseye /etc/network/interfaces.d/setup for eth0 is (and it worked OK for my strange Linux MInt 20 original setup)

Code: Select all

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp
-=t42=-
Halbarad
Level 1
Level 1
Posts: 28
Joined: Tue Feb 05, 2019 2:30 pm

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster

Post by Halbarad »

Thank you, I had a look at /etc/network/interfaces, which are quite the same in the two systems. In both of them, /etc/network/interfaces.d/setup contains no subdirectories.
To me, the truly puzzling thing is that Mint's booting behavior changed after installing Debian, therefore I have to look for some possible interference. This cannot be in the partition(s) reserved for my Mint(s) and I can't see how any settings in the efi boot partition could alter the way in which the Mint's kernel would load the firmware rtl_nic/rtl8106e-1.fw, which both Debian and Mint have in /usr/lib/firmware. Is it possible that some switch in the network hardware has been set by Debian and it survives rebooting etc.? But why both Debian's and Ubuntu's kernels flawlessly load the correct fw while Mint's kernel has to wait some 60 seconds before deciding to do so? ---even when the kernel is just the same as in Lubuntu? This defeats me and I'd be really grateful if someone could help me to understand. Why, I'm grateful even if the trials are unsuccessful... ;-) I am simply unable to regard the kernel as a mysterious black box...
User avatar
Larry78723
Level 8
Level 8
Posts: 2108
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster

Post by Larry78723 »

The one thing we haven't seen is your complete journalctl right after a reboot, Please run the following:

Code: Select all

journalctl -b | grep -i "error\|warn\|fail" | tee >(gzip --stdout > journalctl_$USER.gz)
This command will write the current system log problems to the file journalctl_(yourname).gz. The file will be located in your /home/login_name directory

Attach this file to your next reply, please.
Image
Halbarad
Level 1
Level 1
Posts: 28
Joined: Tue Feb 05, 2019 2:30 pm

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster

Post by Halbarad »

@Larry78723: That was it! Thank you SO MUCH! This is the output of journalctl:

Code: Select all

Sep 18 21:59:50 alberto-HP-250-G3-Notebook-PC kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Sep 18 21:59:50 alberto-HP-250-G3-Notebook-PC kernel: RAS: Correctable Errors collector initialized.
Sep 18 21:59:50 alberto-HP-250-G3-Notebook-PC kernel: EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
Sep 18 21:59:51 alberto-HP-250-G3-Notebook-PC kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: errors=remount-ro
Sep 18 22:01:20 alberto-HP-250-G3-Notebook-PC systemd[1]: Dependency failed for /dev/disk/by-uuid/f18687b4-8f3c-443d-bab4-8a608784c983.
Sep 18 22:01:20 alberto-HP-250-G3-Notebook-PC systemd[1]: Dependency failed for Swap.
Sep 18 22:01:20 alberto-HP-250-G3-Notebook-PC systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
Sep 18 22:01:20 alberto-HP-250-G3-Notebook-PC systemd[1]: dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.swap: Job dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.swap/start failed with result 'dependency'.
Sep 18 22:01:20 alberto-HP-250-G3-Notebook-PC systemd[1]: dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.device: Job dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.device/start failed with result 'timeout'.
Sep 18 22:01:20 alberto-HP-250-G3-Notebook-PC gpu-manager[756]: Error: can't open /lib/modules/5.4.0-47-generic/updates/dkms
Sep 18 22:01:20 alberto-HP-250-G3-Notebook-PC udisksd[778]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Sep 18 22:01:21 alberto-HP-250-G3-Notebook-PC thermald[788]: sysfs write failed /sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/enabled
Sep 18 22:01:21 alberto-HP-250-G3-Notebook-PC thermald[788]: sysfs read failed constraint_0_max_power_uw
Sep 18 22:01:21 alberto-HP-250-G3-Notebook-PC udisksd[778]: Failed to load the 'mdraid' libblockdev plugin
Sep 18 22:01:21 alberto-HP-250-G3-Notebook-PC networkd-dispatcher[782]: WARNING: systemd-networkd is not running, output will be incomplete.
Sep 18 22:01:21 alberto-HP-250-G3-Notebook-PC colord[831]: failed to get session [pid 776]: No data available
Sep 18 22:01:21 alberto-HP-250-G3-Notebook-PC NetworkManager[771]: <warn>  [1600459281.3506] interfaces file /etc/network/interfaces.d/* doesn't exist
Sep 18 22:01:22 alberto-HP-250-G3-Notebook-PC wpa_supplicant[773]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Sep 18 22:01:22 alberto-HP-250-G3-Notebook-PC wpa_supplicant[773]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Sep 18 22:01:22 alberto-HP-250-G3-Notebook-PC wpa_supplicant[773]: dbus: Failed to construct signal
Sep 18 22:01:22 alberto-HP-250-G3-Notebook-PC wpa_supplicant[773]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Sep 18 22:01:22 alberto-HP-250-G3-Notebook-PC ntpd[882]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
Sep 18 22:01:23 alberto-HP-250-G3-Notebook-PC ntpd[882]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
Sep 18 22:01:23 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:01:23 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:01:23 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:01:23 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:01:23 alberto-HP-250-G3-Notebook-PC kernel: vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Sep 18 22:01:24 alberto-HP-250-G3-Notebook-PC mate-session[962]: WARNING: Unable to find provider '' of required component 'dock'
Sep 18 22:01:25 alberto-HP-250-G3-Notebook-PC pulseaudio[1675]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
Sep 18 22:02:50 alberto-HP-250-G3-Notebook-PC systemd[1]: Dependency failed for /dev/disk/by-uuid/f18687b4-8f3c-443d-bab4-8a608784c983.
Sep 18 22:02:50 alberto-HP-250-G3-Notebook-PC systemd[1]: dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.swap: Job dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.swap/start failed with result 'dependency'.
Sep 18 22:02:50 alberto-HP-250-G3-Notebook-PC systemd[1]: dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.device: Job dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.device/start failed with result 'timeout'.
Sep 18 22:11:21 alberto-HP-250-G3-Notebook-PC gvfsd-metadata[1884]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Sep 18 22:11:21 alberto-HP-250-G3-Notebook-PC gvfsd-metadata[1884]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Sep 18 22:11:21 alberto-HP-250-G3-Notebook-PC gvfsd-metadata[1884]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Sep 18 22:11:21 alberto-HP-250-G3-Notebook-PC gvfsd-metadata[1884]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Sep 18 22:11:21 alberto-HP-250-G3-Notebook-PC gvfsd-metadata[1884]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Sep 18 22:11:21 alberto-HP-250-G3-Notebook-PC gvfsd-metadata[1884]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Sep 18 22:11:21 alberto-HP-250-G3-Notebook-PC gvfsd-metadata[1884]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Sep 18 22:11:21 alberto-HP-250-G3-Notebook-PC gvfsd-metadata[1884]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Sep 18 22:11:46 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:11:46 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:11:46 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:11:46 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:11:46 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:11:46 alberto-HP-250-G3-Notebook-PC systemd-resolved[638]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 18 22:13:18 alberto-HP-250-G3-Notebook-PC systemd[1]: Dependency failed for /dev/disk/by-uuid/f18687b4-8f3c-443d-bab4-8a608784c983.
Sep 18 22:13:18 alberto-HP-250-G3-Notebook-PC systemd[1]: dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.swap: Job dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.swap/start failed with result 'dependency'.
Sep 18 22:13:18 alberto-HP-250-G3-Notebook-PC systemd[1]: dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.device: Job dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.device/start failed with result 'timeout'.
Sep 18 22:15:40 alberto-HP-250-G3-Notebook-PC systemd[1]: Dependency failed for /dev/disk/by-uuid/f18687b4-8f3c-443d-bab4-8a608784c983.
Sep 18 22:15:40 alberto-HP-250-G3-Notebook-PC systemd[1]: dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.swap: Job dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.swap/start failed with result 'dependency'.
Sep 18 22:15:40 alberto-HP-250-G3-Notebook-PC systemd[1]: dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.device: Job dev-disk-by\x2duuid-f18687b4\x2d8f3c\x2d443d\x2dbab4\x2d8a608784c983.device/start failed with result 'timeout'.
Sep 18 22:16:09 alberto-HP-250-G3-Notebook-PC xdg-desktop-por[4150]: Error getting permissions: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for inhibit
Sep 18 22:16:09 alberto-HP-250-G3-Notebook-PC xdg-desktop-por[4150]: Backend call failed: GDBus.Error:org.freedesktop.portal.Error.Failed: Inhibiting other than idle not supported
There is some stuff that might require attention, but the main issue is :

Code: Select all

Sep 18 22:01:20 alberto-HP-250-G3-Notebook-PC systemd[1]: Dependency failed for /dev/disk/by-uuid/f18687b4-8f3c-443d-bab4-8a608784c983.
This was the swap partition. And it makes sense. Debian is installed; it uses the swap partition and assigns a new UUID to it, which differs from the one in Mint's fstab. The wrong UUID is in fact in Mint's fstab, while the right one is in Debian's fstab; I've also checked with gparted. "device/start failed with result 'timeout'": indeed. And so, I just changed Mint's /etc/fstab replacing the swap UUID with the correct one and the system booted quick and smooth.
Thank you so much! If you see some more reason for taking action and making changes pls just tell me; but the system is as good as it used to be.
User avatar
Larry78723
Level 8
Level 8
Posts: 2108
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Mint 19.3 boot gets stuck on attached PHY driver after installing Debian Buster [SOLVED]

Post by Larry78723 »

Glad you were able to spot the problem. Now that you fixed the swap problem, you may want to reboot and run the command again to be sure there aren't any further problems.
Image
Post Reply

Return to “Ethernet”