Public bug reported:
My system configuration looks as follows:
ISP Router <--> Own TP Link Wifi Router <--> 1 Gbps Switch <---> Desktop
and switched off laptop / backup-server
My desktop can run upto 50 VBox VMs, but normally only Xubuntu 20.04 is
loaded for my communication stuff (email, kde-connect etc).
The cable between ISP Router and TP Link Router did go defect.
The system did not boot/login any-more and stayed in a loop probably
trying to get a connection with the DNS server 1.1.1.1 or 192.168.0.1
(the ISP Router). I tried to switch off stuff, disconnect cable and I
think it continued the boot after I disconnected the Ethernet cable of
the desktop.
I will include the corresponding boot log.
Most VMs did have the same issue, they did not boot/login any-more.
Exception were the Windows VMs (XP, 10 and 7) and Fedora 33 (Linux 5.9).
They booted normally and allowed me to use the non-internet functions. I
had the impression that Ubuntu based 20.04 VMs did not boot any-more,
however the development editions of 21.04 booted as expected.
I updated from 5.4.0.56 to 5.4.0.58 after I repaired the cable.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bind9 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 13 21:51:37 2020
InstallationDate: Installed on 2019-11-30 (379 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bind9 focal
** Attachment added: "bootlog.txt"
https://bugs.launchpad.net/bugs/1908012/+attachment/5443315/+files/bootlog.txt
** Description changed:
My system configuration looks as follows:
ISP Router <--> Own TP Link Wifi Router <--> 1 Gbps Switch <---> Desktop
and switched off laptop / backup-server
My desktop can run upto 50 VBox VMs, but normally only Xubuntu 20.04 is
loaded for my communication stuff (email, kde-connect etc).
The cable between ISP Router and TP Link Router did go defect.
The system did not boot/login any-more and stayed in a loop probably
trying to get a connection with the DNS server 1.1.1.1 or 192.168.0.1
(the ISP Router). I tried to switch off stuff, disconnect cable and I
think it continued the boot after I disconnected the Ethernet cable of
the desktop.
I will include the corresponding boot log.
Most VMs did have the same issue, they did not boot/login any-more.
- Exception were the Windows VMs (XP, 10 and 7) and Fedora 33 (Linux 5.7).
+ Exception were the Windows VMs (XP, 10 and 7) and Fedora 33 (Linux 5.9).
They booted normally and allowed me to use the non-internet functions. I
had the impression that Ubuntu based 20.04 VMs did not boot any-more,
however the development editions of 21.04 booted as expected.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bind9 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 13 21:51:37 2020
InstallationDate: Installed on 2019-11-30 (379 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
My system configuration looks as follows:
ISP Router <--> Own TP Link Wifi Router <--> 1 Gbps Switch <---> Desktop
and switched off laptop / backup-server
My desktop can run upto 50 VBox VMs, but normally only Xubuntu 20.04 is
loaded for my communication stuff (email, kde-connect etc).
The cable between ISP Router and TP Link Router did go defect.
The system did not boot/login any-more and stayed in a loop probably
trying to get a connection with the DNS server 1.1.1.1 or 192.168.0.1
(the ISP Router). I tried to switch off stuff, disconnect cable and I
think it continued the boot after I disconnected the Ethernet cable of
the desktop.
I will include the corresponding boot log.
Most VMs did have the same issue, they did not boot/login any-more.
Exception were the Windows VMs (XP, 10 and 7) and Fedora 33 (Linux 5.9).
They booted normally and allowed me to use the non-internet functions. I
had the impression that Ubuntu based 20.04 VMs did not boot any-more,
however the development editions of 21.04 booted as expected.
+ I updated from 5.4.0.56 to 5.4.0.58 after I repaired the cable.
+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bind9 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 13 21:51:37 2020
InstallationDate: Installed on 2019-11-30 (379 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908012
Title:
System did not boot anymore after broken cable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1908012/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
