When Debian is starting the following are the highlighted messages and or places where booting pauses and at the very end pauses almost indefinitely (or rather when I lost the patience for waiting for new messages to come up and shut down the machine).
I am writing everything down I was able to get out of the system below. I have the following questions (i) is there any automatic system recovery tools worth trying (ii) is there a set of commands that could be executed when in rescue mode to restore the system (iii) is it worth the time to try to rescue the system (or better of giving up and reinstalling the system from scratch on the device) (iv) is there something to be learned from this series of errors so that if not repeated, this problem can be avoided in the future from occuring again? (i.e. a correct diagnosis of the reason for the problem) Can anyone help? Thanks Semih ---------- ERROR MESSAGES: (A) During boot the following pink/red messages occur: [DEPEND] Dependency failed for /dev/disk/by-uuid/.... and also for swap (B) after debian switches to rescue mode and root bash line appears, In the response to "journalctl -xf" the following problems occur (i) kernel:Bluetooth:hcio:unexpected event for opcode 0xfc2f (ii) systemd[1]:Timed out waiting for device /dev/disk/by-uuid/... (for two disks) (iii) Failed to get initial list of names:Connection timed out (iv) dbus.service: Main process exited, status=1/FAILURE Failed with result 'exit-code' (v) L1TF CPU bug present and SMT on, data leak possible see CVE-2018-3646 kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html (C) systemctl -al gives following problems Loaded failed: bluetooth.service,dbus.service Not found: tmp.mount, auditd.service,connman.service,console-screen.service,fcoe.service,firewalld.service,greylist.service,iscsi.service, iscsid.serive,kbd.service,lvm2-activation.service,postgresq;.service,snapd.failure.service,spamassasin.service,systemd-machined.service, systemd-update-done.service,systemd-vconsole-setup.service. (D) Booting pauses indefinitely (as long as I had the patience to wait for) at the line IPv6:ADDCONF(NETDV_UP): docker0, br- : link is not ready This line appears after some messages regarding vbox (virtualbox) Semih Ozlem <semihozlemlinuxu...@gmail.com>, 20 Şub 2021 Cmt, 15:23 tarihinde şunu yazdı: > In addition to my earlier message, the usb drive has three partitions FAT > partition including EFI, swap partition, btrfs partition where home folder > is located. > > sudo btrfs rescue super-recover /dev/sdc3 > gives the response > All supers are valid, no need to recover > > When starting from the usb, the boot process starts with some messages > such as not starting network manager. Indeed if I drop to root shell, > apt-get update won't do what it usually does since internet connection > can't be established. (similarly neither apt --fix-broken install) there > was also a message about a bug in kernel at boot time. > > Any ideas on what can be done so that booting of the system can be > restored? > > > Semih Ozlem <semihozlemlinuxu...@gmail.com>, 20 Şub 2021 Cmt, 09:26 > tarihinde şunu yazdı: > >> Hi everyone, >> >> I installed debian 10 on a 64 GB usb. It had been working fine. Last I >> installed apache server, virtualbox, docker. After all this it worked fine >> for a while, though at times slowly. Currently it is not working. It does >> not finish booting, and it gets stuck at a certain point. The scrolling >> lines indicate DEPEND problem and failing to start network manager and some >> other issues, that I have not been able to write down. >> When I choose to boot in recovery mode, I am able to get to a shell as >> root. However I do not know and am not sure about what steps to take to >> rescue the system. Can anyone offer help or indicate a good source to read >> through? >> I have not written down machine details, (would this be related to the >> machine, since it used to work fine). >> >> Linux kernel that the debian 10 system is using is 4.19.0.6 or 4.19.0.8 >> >> Thank you >> >
