Manjaro Shutdown Time Sometimes Slow

So, I’ve recently installed Manjaro Linux in my laptop and after working for around 1 hour if I shutdown it, it takes around 90 seconds to shutdown. I have tried to make the following changes in my /etc/systemd/system.conf:

DumpCore=no
DefaultTimeoutStartSec=05s
DefaultTimeoutStopSec=05s
DefaultTimeoutAbortSec=05s

Still, nothing changed. Can someone help me out with this?

Hi, it’s been 18 minutes since I’ve posted it. Why hasn’t anybody replied yet?

Here is your reply: Improving performance - ArchWiki

This support here is community driven. Keep that in mind. We do this in our free time. :wink:

2 Likes

:+1: Welcome to Manjaro! :+1:

Please read this:


and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…

An inxi --admin --verbosity=7 --filter --no-host would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)

:innocent:

P.S. Always allow for 24 hours to pass before expecting an answer because we’re a global community and the expert you’re seeking might be in the Atlantis Time Zone and will respond to your request while you’re :zzz: :bed:

There you go:

System:    Kernel: 5.4.64-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.4-x86_64 root=UUID=09cae4e5-a15a-4dae-b41e-718543ca815b rw quiet apparmor=1 
           security=apparmor udev.log_priority=3 
           Desktop: GNOME 3.36.6 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.36.3 Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: Latitude 3500 v: N/A serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Dell model: 0V262X v: A00 serial: <filter> UEFI: Dell v: 1.13.1 date: 06/11/2020 
Battery:   ID-1: BAT0 charge: 38.7 Wh condition: 42.0/42.0 Wh (100%) volts: 12.7/11.4 model: SWD-ATL3.618 DELL WJPC407 
           type: Li-ion serial: <filter> status: Discharging 
Memory:    RAM: total: 3.73 GiB used: 1.24 GiB (33.2%) 
           RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:       Topology: Dual Core model: Intel Core i3-8145U bits: 64 type: MT MCP arch: Kaby Lake family: 6 model-id: 8E (142) 
           stepping: C (12) microcode: D6 L2 cache: 4096 KiB bogomips: 18406 
           Speed: 1757 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 1796 2: 1778 3: 1740 4: 1774 
           Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 
           bts clflush clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms 
           est f16c flexpriority flush_l1d fma fpu fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs 
           ibrs_enhanced ida intel_pt invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr 
           nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts rdrand rdseed 
           rdtscp rep_good sdbg sep smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc 
           tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           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: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: srbds mitigation: TSX disabled 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 
           Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus ID: 1-6:2 chip ID: 0bda:5675 serial: <filter> 
           Display: x11 server: X.Org 1.20.8 compositor: gnome-shell driver: intel unloaded: modesetting alternate: fbdev,vesa 
           display ID: :1 screens: 1 
           Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") s-diag: 414mm (16.3") 
           Monitor-1: eDP1 res: 1366x768 hz: 60 dpi: 102 size: 340x190mm (13.4x7.5") diag: 389mm (15.3") 
           OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.7 direct render: Yes 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel 
           alternate: snd_soc_skl,snd_sof_pci bus ID: 00:1f.3 chip ID: 8086:9dc8 
           Sound Server: ALSA v: k5.4.64-1-MANJARO 
Network:   Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel port: 4000 bus ID: 00:14.3 
           chip ID: 8086:9df0 
           IF: wlp0s20f3 state: up mac: <filter> 
           IP v4: <filter> type: dynamic noprefixroute scope: global broadcast: <filter> 
           IP v6: <filter> type: noprefixroute scope: link 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 
           bus ID: 01:00.0 chip ID: 10ec:8168 
           IF: enp1s0 state: down mac: <filter> 
           WAN IP: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 21.79 GiB (2.3%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/sda vendor: Toshiba model: MQ04ABF100 size: 931.51 GiB block size: physical: 4096 B logical: 512 B 
           speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 01 scheme: GPT 
           Message: No Optical or Floppy data was found. 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / raw size: 926.51 GiB size: 910.97 GiB (98.32%) used: 21.79 GiB (2.4%) fs: ext4 dev: /dev/sda2 label: root 
           uuid: 09cae4e5-a15a-4dae-b41e-718543ca815b 
           ID-2: /boot/efi raw size: 1024.0 MiB size: 1022.0 MiB (99.80%) used: 280 KiB (0.0%) fs: vfat dev: /dev/sda1 
           label: BOOT uuid: 7563-72B2 
Swap:      Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 label: swap 
           uuid: ca1534f8-a22d-4e88-95ff-b570da5136fb 
Unmounted: Message: No unmounted partitions found. 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 12 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002 
           Device-1: 1-6:2 info: Realtek Integrated_Webcam_HD type: Video driver: uvcvideo interfaces: 2 rev: 2.0 
           speed: 480 Mb/s chip ID: 0bda:5675 serial: <filter> 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.1 speed: 10 Gb/s chip ID: 1d6b:0003 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 195 Uptime: 5m Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 1290 lib: 396 flatpak: 0 
           Shell: Bash v: 5.0.18 running in: terminator inxi: 3.1.05 

I didn’t mean to be rude in the comment up there, I was just not understanding why people were replying to the posts posted after this but not to mine.

OK, but I’m sure I’m not the only one here thinking like that, but posting this kind of message is really a bad way to get attention, in my rule book I usually ignore on purpose users who complain nobody replies fast enough to them (on any ‘free’ place on the internet, I mean you’re not a customer, not paying anyone so what would you expect, especially after 18 MINUTES lol)

3 Likes

But if a new user sees nobody replying to his post but to posts that have been posted after his one, won’t he/she get confused? I thought there was probably something wrong with my post or its format, so I was just making sure that there’s nothing wrong and hence the question. If it appeared otherwise, then my apologies.

1 Like

Linux, Manjaro, IT… It’s huge and nobody can know everything on everything. If the people who have knowledge about your issue are not connected, are busy answering other topics, the other forum users, who know other things and answer other topics, will not answer yours.
And again, it’s not a paid after sales service forum, with 5 minutes top to get an answer.

1 Like

This is why it takes a long time:

So basically you only have <4G of RAM and have a 5400RPM HDD as storage and no amount of tinkering is going to change the laws of physics make your computer have a faster drive nor increase your memory so I’m sorry to say:

Be patient while your computer shuts down writing all that swapped memory to your slow hard disk…

Don’t worry: be happy!
You didn’t know, now you know, most of the die-hard hackers here have forgotten what it was to be a N00b, I haven’t although I’m an old fart…

:grin:

1 Like

Yeah, the 5400 rpm drive is the big issue there. I had one, and shutdown times were pretty slow (still faster than windows). I upgraded my laptop to a cheap SSD the other day, and shutdown is almost instantaneous.

1 Like

Here is my Solus system’s output which takes 2-3 secs on average and at most 5 seconds to shutdown:

System:
  Kernel: 5.6.19-158.current x86_64 bits: 64 compiler: gcc v: 9.3.0 
  parameters: BOOT_IMAGE=/boot/com.solus-project.current.5.6.19-158 
  root=UUID=086ff6c4-32a2-4481-992d-7423c144a204 quiet loglevel=3 splash 
  systemd.show_status=false rw radeon.si_support=0 radeon.cik_support=0 
  amdgpu.si_support=1 amdgpu.cik_support=1 
  systemd.unified_cgroup_hierarchy=0 
  resume=UUID=871af452-46b7-4f97-aa4f-1e788f8bc97f 
  Desktop: Budgie 10.5.1 info: budgie-panel wm: budgie-wm dm: LightDM 1.30.0 
  Distro: Solus 4.1 
Machine:
  Type: Desktop Mobo: Gigabyte model: H81M-S v: x.x serial: <filter> 
  BIOS: American Megatrends v: F2 date: 08/19/2015 
Memory:
  RAM: total: 3.75 GiB used: 970.2 MiB (25.3%) 
  RAM Report: 
  permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Topology: Dual Core model: Intel Pentium G3240 bits: 64 type: MCP 
  arch: Haswell family: 6 model-id: 3C (60) stepping: 3 microcode: 27 
  L2 cache: 3072 KiB bogomips: 12372 
  Speed: 898 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 865 2: 815 
  Flags: abm acpi aperfmperf apic arat arch_perfmon bts clflush cmov 
  constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts ept 
  ept_ad erms est flexpriority flush_l1d fpu fsgsbase fxsr ht ibpb ibrs 
  invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe msr 
  mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge 
  pln pni popcnt pse pse36 pti pts rdrand rdtscp rep_good sdbg sep ss ssbd 
  sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc 
  tsc_adjust tsc_deadline_timer vme vmx vnmi vpid xsave xsaveopt xtopology 
  xtpr 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
  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 status: Vulnerable: No microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0402 
  Display: x11 server: X.Org 1.20.9 compositor: budgie-wm 
  driver: modesetting unloaded: fbdev,vesa display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 359x203mm (14.1x8.0") 
  s-diag: 412mm (16.2") 
  Monitor-1: VGA-1 res: 1360x768 hz: 60 dpi: 84 size: 410x256mm (16.1x10.1") 
  diag: 483mm (19") 
  OpenGL: renderer: Mesa DRI Intel HD Graphics (HSW GT1) v: 4.5 Mesa 20.1.4 
  compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
  driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c 
  Device-2: Intel 8 Series/C220 Series High Definition Audio 
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:8c20 
  Sound Server: ALSA v: k5.6.19-158.current 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: e000 bus ID: 02:00.0 
  chip ID: 10ec:8168 
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: noprefixroute scope: link 
  WAN IP: No WAN IP found. Connected to web? SSL issues? Try --no-dig 
Drives:
  Local Storage: total: 465.76 GiB used: 30.45 GiB (6.5%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda vendor: Seagate model: ST500DM002-9YN14C size: 465.76 GiB 
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  rotation: 5400 rpm serial: <filter> rev: CC4C scheme: MBR 
  Optical-1: /dev/sr0 vendor: TSSTcorp model: CDDVDW SH-224DB rev: ID00 
  dev-links: cdrom 
  Features: speed: 48 multisession: yes audio: yes dvd: yes 
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
RAID:
  Message: No RAID data was found. 
Partition:
  ID-1: / raw size: 30.00 GiB size: 29.40 GiB (98.01%) 
  used: 19.99 GiB (68.0%) fs: ext4 dev: /dev/sda7 label: N/A 
  uuid: 086ff6c4-32a2-4481-992d-7423c144a204 
  ID-2: /home raw size: 17.99 GiB size: 17.59 GiB (97.74%) 
  used: 10.46 GiB (59.5%) fs: ext4 dev: /dev/sda8 label: N/A 
  uuid: 306fa085-e910-4e81-b6d1-474dbe42f4e6 
Swap:
  Kernel: swappiness: 10 (default 60) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 2.00 GiB used: 0 KiB (0.0%) 
  priority: -2 dev: /dev/sda9 label: N/A 
  uuid: 871af452-46b7-4f97-aa4f-1e788f8bc97f 
Unmounted:
  ID-1: /dev/sda1 size: 100.0 MiB fs: ntfs label: System Reserved 
  uuid: 7E7024EF7024AFB7 
  ID-2: /dev/sda2 size: 97.56 GiB fs: ntfs label: N/A uuid: 80AC2947AC293954 
  ID-3: /dev/sda3 size: 122.07 GiB fs: ntfs label: New Volume 
  uuid: A2CEAD1BCEACE92D 
  ID-4: /dev/sda4 size: 1 KiB fs: <superuser/root required> label: N/A 
  uuid: N/A 
  ID-5: /dev/sda5 size: 72.07 GiB fs: ntfs label: New Volume 
  uuid: DA8C73B68C738BAF 
  ID-6: /dev/sda6 size: 123.96 GiB fs: ntfs label: New Volume 
  uuid: CC38277738276026 
USB:
  Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
  speed: 480 Mb/s chip ID: 1d6b:0002 
  Hub: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 4 rev: 2.0 
  speed: 480 Mb/s chip ID: 8087:8008 
  Hub: 2-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 
  speed: 480 Mb/s chip ID: 1d6b:0002 
  Device-1: 2-2:2 info: USB OPTICAL MOUSE type: Mouse 
  driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s 
  chip ID: 0101:0007 
  Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 
  speed: 480 Mb/s chip ID: 1d6b:0002 
  Hub: 3-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip ID: 8087:8000 
  Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 speed: 5 Gb/s 
  chip ID: 1d6b:0003 
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 175 Uptime: 2m Init: systemd v: 246 runlevel: 5 Compilers: 
  gcc: 9.3.0 clang: 9.0.1 Shell: bash v: 5.0.11 running in: gnome-terminal 
  inxi: 3.1.03 

grep’ing the relevant parts out:
Memory: RAM: total: 3.75 GiB

rotation: 5400 rpm

How do you explain this taking 2-3 secs then?

This thing aside, can y’all tell me a way to figure out what’s making the shutdown slow? For example, systemd-analyze blame tells me what service is taking up how much time during boot. Is there something equivalent for the shutdown, just like the boot?

Because, really: what I find peculiar is that it takes exactly 1 minute and 30 seconds to shut down which is the default timeout span during shutdown or something like that. It looks like it’s a forced delay/timeout which can be adjusted. Again, it’s just me speculating. You all are the experts here, so I would like to hear what you guys think.

If it is exactly 90 seconds, do you have a terminal message telling you it is waiting for a stop job to finish with a 90s timer?

90 seconds is the default for stopjob (and other) timeout in systemd.

This can happen if you have a user logged in another TTY, or if some service refuses to close, at shutdown.

1 Like

What @omano said, and an inxi output will not help us help you. Please give us a shutdown log from both OSes.

Please also note this kind of critical info in your first question: compared to Solus, Manjaro takes 90 seconds more to shut down. Here are both shutdown logs.

:man_shrugging:

No, there’s no terminal message. I’ve recorded it in my stopwatch and it turns out to be around 90 seconds with 1-2 seconds here and there, maybe. Considering human reaction errors.

There’s only one user in my laptop. No multiple user accounts.

I’d love to give more information. But can you tell me how do I generate a shutdown log?

journalctl --boot=-1 | tail --lines=50

would be a good start as that gives the last (the tail) 50 lines of the previous boot (-1)

:innocent:

1 Like

Okay, so I’m supposed to shut it down after using it for 1-2 hrs, and then boot it up back and then execute this command, right? If that makes any sense.

No, just execute above command right now and post its output…

:innocent:

Alright, there you go:

Sep 19 17:02:33 dell-latitude systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000039a01c023a7-part3.
Sep 19 17:02:33 dell-latitude systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d1\x2dpart3.swap: Succeeded.
Sep 19 17:02:33 dell-latitude systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:17.0-ata-1-part3.
Sep 19 17:02:33 dell-latitude systemd[1]: dev-disk-by\x2dlabel-swap.swap: Succeeded.
Sep 19 17:02:33 dell-latitude systemd[1]: Deactivated swap /dev/disk/by-label/swap.
Sep 19 17:02:33 dell-latitude systemd[1]: dev-disk-by\x2did-ata\x2dTOSHIBA_MQ04ABF100_50APT5A2T\x2dpart3.swap: Succeeded.
Sep 19 17:02:33 dell-latitude systemd[1]: Deactivated swap /dev/disk/by-id/ata-TOSHIBA_MQ04ABF100_50APT5A2T-part3.
Sep 19 17:02:33 dell-latitude systemd[1]: dev-sda3.swap: Succeeded.
Sep 19 17:02:33 dell-latitude systemd[1]: Deactivated swap /dev/sda3.
Sep 19 17:02:33 dell-latitude systemd[1]: dev-disk-by\x2duuid-ca1534f8\x2da22d\x2d4e88\x2d95ff\x2db570da5136fb.swap: Succeeded.
Sep 19 17:02:33 dell-latitude systemd[1]: Deactivated swap /dev/disk/by-uuid/ca1534f8-a22d-4e88-95ff-b570da5136fb.
Sep 19 17:02:34 dell-latitude mkinitcpio[2166]: ==> Build complete.
Sep 19 17:02:34 dell-latitude systemd[1]: mkinitcpio-generate-shutdown-ramfs.service: Succeeded.
Sep 19 17:02:34 dell-latitude systemd[1]: Finished Generate shutdown-ramfs.
Sep 19 17:02:34 dell-latitude audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:34 dell-latitude audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=mkinitcpio-generate-shutdown-ramfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude systemd[1]: boot-efi.mount: Succeeded.
Sep 19 17:02:36 dell-latitude systemd[1]: Unmounted /boot/efi.
Sep 19 17:02:36 dell-latitude systemd[1]: Reached target Unmount All Filesystems.
Sep 19 17:02:36 dell-latitude systemd[1]: systemd-fsck@dev-disk-by\x2duuid-7563\x2d72B2.service: Succeeded.
Sep 19 17:02:36 dell-latitude systemd[1]: Stopped File System Check on /dev/disk/by-uuid/7563-72B2.
Sep 19 17:02:36 dell-latitude audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-fsck@dev-disk-by\x2duuid-7563\x2d72B2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude kernel: kauditd_printk_skb: 19 callbacks suppressed
Sep 19 17:02:36 dell-latitude kernel: audit: type=1131 audit(1600515156.055:132): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-fsck@dev-disk-by\x2duuid-7563\x2d72B2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Sep 19 17:02:36 dell-latitude systemd[1]: Stopped target Local File Systems (Pre).
Sep 19 17:02:36 dell-latitude systemd[1]: systemd-remount-fs.service: Succeeded.
Sep 19 17:02:36 dell-latitude systemd[1]: Stopped Remount Root and Kernel File Systems.
Sep 19 17:02:36 dell-latitude audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Sep 19 17:02:36 dell-latitude systemd[1]: Stopped Create Static Device Nodes in /dev.
Sep 19 17:02:36 dell-latitude audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude systemd[1]: Reached target Shutdown.
Sep 19 17:02:36 dell-latitude systemd[1]: Reached target Final Step.
Sep 19 17:02:36 dell-latitude systemd[1]: systemd-reboot.service: Succeeded.
Sep 19 17:02:36 dell-latitude audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude systemd[1]: Finished Reboot.
Sep 19 17:02:36 dell-latitude systemd[1]: Reached target Reboot.
Sep 19 17:02:36 dell-latitude systemd[1]: Shutting down.
Sep 19 17:02:36 dell-latitude kernel: audit: type=1131 audit(1600515156.059:133): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude kernel: audit: type=1131 audit(1600515156.059:134): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude kernel: audit: type=1130 audit(1600515156.059:135): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude kernel: audit: type=1131 audit(1600515156.059:136): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 17:02:36 dell-latitude systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Sep 19 17:02:36 dell-latitude systemd[1]: Set hardware watchdog to 10min.
Sep 19 17:02:36 dell-latitude kernel: watchdog: watchdog0: watchdog did not stop!
Sep 19 17:02:36 dell-latitude systemd-shutdown[1]: Syncing filesystems and block devices.
Sep 19 17:02:36 dell-latitude systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Sep 19 17:02:36 dell-latitude systemd-journald[222]: Journal stopped

There are only 3 sec? Seems it is not the full log. This will create a shutdown/reboot log from the last boot:

journalctl -b -1 | grep -A999 "System is rebooting.\|System is powering down."
1 Like