System did not boot anymore after broken cable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
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)
ProcVersionSign
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
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: | updated |
Thank you for taking the time to file a bug report.
Checking the attached logs the only thing I can see is your 'sh.desktop' failing many times and some errors from the gnome-shell. I do not think they are related to the problem you have. Moreover, what you described does not help a developer to reproduce the problem and try to confirm/investigate the issue, so please try to describe how one could reproduce your issue. Due to that this bug is not actionable.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://