My system will not reboot after I am advised to reboot following installing additional packages

daggett · 31 January 2022 14:08

For some time I have got my Manjaro Linux system to work in a stable fashion. However, when I recently rebooted as I was told to after I had installed a few additional applications, my computer failed to reboot, as has already happened to me on a number of previous occasions as described above.

I have posted the system.journal entries from when it failed to reboot to [system.journal entries when my Manjaro Linux failed to reboot - to system.journal entries when my Manjaro Linux failed to reboot - Pastebin.com

Is anyone able to see from these system.journal entries. why my Manjaro Linux computer now can’t boot up?

If this data is insufficient to show the cause of my problem, could someone advise me of how to provide the necessary additional information, presumably by causing additional data to be written to /var/log/journal/1a…91c/system.journal ?

Thank you for you attention.

anon12891489 · 31 January 2022 14:16

Can you post the output of inxi -Fazy and mhwd-kernel -li

Mirdarthos · 31 January 2022 14:19

Hi @daggett,

Can you get into a TTY or something? I ask, because the pasted output doesn’t give ME any info, so I doubt it will anyone else.

If not, you’ll have to chroot into your installation, to provide more info. If you can, you can provide more info from the TTY or chroot, whichever’s easiest for you.

Whichever you do, please provide the output for:

sudo journalctl --boot --priority=3 | tail -n 200 |  curl -F "file=@-" https://0x0.st

That, I suspect, will give much more information. It’ll upload the output, and provide a link to it. Which you can then share here.

daggett · 31 January 2022 21:59

Thank you, Mirdarthos.

I tried a copy of what you posted and was not able to get any useful information. I was fist given an error message:

[manjaro@manjaro Desktop]$ sudo su -
[manjaro ~]# chroot /mnt/sda2 journalctl --boot --priority=3 | tail -n 200 |  curl -F "file=@-" https://0x0.st
Failed to get boot id: No such file or directory
https://0x0.st/-k.txt

I tried a second time, using /tmp/diagnosis instead of https://0x0.st, and got:

[manjaro ~]# chroot /mnt/sda2 journalctl --boot --priority=3 | tail -n 200 |  curl -F "file=@-" /tmp/diagnosis
Failed to get boot id: No such file or directory
curl: (3) URL using bad/illegal format or missing URL

Removing the ‘/’ from /tmp/diagnosis got me:

[manjaro ~]# chroot /mnt/sda2 journalctl --boot --priority=3 | tail -n 200 |  curl -F "file=@-" tmp/diagnosis
Failed to get boot id: No such file or directory
curl: (6) Could not resolve host: tmp

daggett · 1 February 2022 07:03

After this, I will have to spend several hours attempting to recover /dev/sdb1 on which about 30 gigs of my /home partition was before I accidentally reformatted it as ISO recently - apparently GParted contains one recovery program, i was relieved to find out. So it could be some time before I can further respond.

I wasn’t sure whether or not I should prepend “chroot /mnt/sda2” to the start of the commands, so I ran both versions. I was not sure whether the output was too big for here, so I also pasted it to Output data to help solve my inability to boot up my Manjaro Linux System - Pastebin.com

Nonetheless, I will also post it in full below. Should that be a problem, I will remove some of the following:

Output data to help solve my inability to boot up my Manjaro Linux System

CONTENTS

Output from “chroot /mnt/sda2 mhwd-kernel -li”
Output from “mwhd-kernel -li”
Output from “chroot /mnt/sda2 inxi -Fazy” (which could be the complete comand)
Output from “inxi -Fazy” (as I was advised to do).

1. Output from "chroot /mnt/sda2 mwhd-kernel -li"

[manjaro ~]# chroot /mnt/sda2 mhwd-kernel -li
Currently running: 5.15.16-1-MANJARO (linux515)
The following kernels are installed in your system:

linux515

2. Output from "mhwd-kernel -li"

[manjaro ~]# mhwd-kernel -li
Currently running: 5.15.16-1-MANJARO (linux515)
The following kernels are installed in your system:

linux515

3. Output from “chroot /mnt/sda2 inxi -Fazy” (which could be the complete comand)

[manjaro ~]# chroot /mnt/sda2 inxi -Fazy
12System:
12Kernel 5.15.16-1-MANJARO x86_64 12bits 64 12compiler N/A 12Console N/A
12Distro Manjaro Linux 12base Arch Linux
12Machine:
12Message No machine data: try newer kernel. Is dmidecode installed? Try -M
–dmidecode.
Can’t use an undefined value as an ARRAY reference at /usr/bin/inxi line 10125.

4. Output from “inxi -Fazy” (**as I was advised to do).

[manjaro ~]# inxi -Fazy
System:
Kernel: 5.15.16-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
misobasedir=manjaro misolabel=MANJARO_XFCE_2122 quiet
systemd.show_status=1 apparmor=1 security=apparmor driver=free
nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
Console: pty pts/1 DM: LightDM 1.30.0 Distro: Manjaro Linux
base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME H310M-K R2.0 v: Rev X.0x
serial: UEFI: American Megatrends v: 0418 date: 09/13/2018
CPU:
Info: model: Intel Core i3-8100 socket: LGA1151 bits: 64 type: MCP
arch: Coffee Lake family: 6 model-id: 0x9E (158) stepping: 0xB (11)
microcode: 0xEA
Topology: cpus: 1x cores: 4 smt: cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
desc: 1x6 MiB
Speed (MHz): avg: 938 high: 1322 min/max: 800/3600 base/boost: 3600/8300
scaling: driver: intel_pstate governor: powersave volts: 1.0 V
ext-clock: 100 MHz cores: 1: 1322 2: 833 3: 800 4: 800 bogomips: 28808
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: disabled, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ASUSTeK driver: nouveau
v: kernel bus-ID: 01:00.0 chip-ID: 10de:128b class-ID: 0300
Display: server: X.org 1.21.1.3 compositor: xfwm4 driver:
loaded: modesetting alternate: fbdev,vesa tty: 80x43
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
class-ID: 0403
Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 01:00.1 chip-ID: 10de:0e0f class-ID: 0403
Sound Server-1: ALSA v: k5.15.16-1-MANJARO running: yes
Sound Server-2: JACK v: 1.9.20 running: no
Sound Server-3: PulseAudio v: 15.0 running: yes
Sound Server-4: PipeWire v: 0.3.43 running: no
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: d000
bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac:
Drives:
Local Storage: total: 2.79 TiB used: 22.52 GiB (0.8%)
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM003-1CH162
family: Barracuda 7200.14 (AF) size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 7200
serial: rev: CC47 temp: 35 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 22d 23h cycles: 777
read: 5 TiB written: 4.4 TiB Pre-Fail: attribute: Spin_Retry_Count
value: 100 worst: 100 threshold: 97
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD20EARS-00MVWB0 family: Caviar Green (AF) size: 1.82 TiB block-size:
physical: 512 B logical: 512 B sata: 2.6 speed: 3.0 Gb/s type: N/A
serial: rev: AB51 temp: 34 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 4y 139d 19h cycles: 2731
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Cruzer Blade
size: 57.33 GiB block-size: physical: 512 B logical: 512 B type: N/A
serial: rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 45.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 197 Uptime: 15h 46m wakeups: 3 Memory: 15.56 GiB
used: 3.77 GiB (24.2%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1163 lib: 319 flatpak: 0
Shell: Bash (su) v: 5.1.16 running-in: pty pts/1 inxi: 3.3.12

Mirdarthos · 1 February 2022 07:15

Hi @daggett,

That is not the way to do things VIA chroot , and that’s why I asked. chroot ing refers to entering a chroot environment of your installation, typically from a live ISO install medium.

Look at testdisk for the rescuing of your data. I have personally used it successfully once to recover more than 2 TB of data, so I know it works. But don’t skim over the instru8ctions, thinking you’ve got it. Read. Actually read. And pay attention.

daggett · 1 February 2022 09:04

chrooting refers to entering a chroot environment of your installation, typically from a live ISO install medium.

Right now I am running Manjaro Linux (as I recall) from an ISO file copied (with dd) onto a 60G USB drive.

Other ISO media I have are:

More than one Manjaro ISO installation DVD; and
A Puppy Linux CD

So, would my Manjaro Linux that I am currently running from my 60G USB drive be a suitable environment for chrooting?

… or should I instead use one of my Manjaro Installation DVDs, or even my Puppy Linux CD (assuming the Puppy CD has testdisk), before chrooting?

Thanks for the testdisk link. Whilst I expect that the GParted parted program could also recover that data, you, no doubt, have good reason for preferring TestDisk. I will read the TestDisk documentation before proceeding as you have suggested.

Mirdarthos · 1 February 2022 10:25

The Manjaro ISO is preferred, by me. Just make sure it’s a relatively recent one. (So that the kernel isn’t too old.)

Use manjaro-chroot to make chrootint a lot easier.

You can install test in the live ISO environment. It’s in the extra repository:

$ pamac search testdisk
[...]
testdisk                                                                                                                                                                                                             [Installed] 7.1-3                extra
Checks and undeletes partitions + PhotoRec, signature based recovery tool

So, install it with:

pamac install testdisk

Note: Wile installing it in thee Live environment should work, it will not survive a reboot.