Systemd | Services | Seeing additional Services between Thinkpads (x230 and T430s) with simlar hardware configurations, wonder why both laptops don't have the same services

kagetora13 · 15 September 2020 00:34

I’ve been comparing my two Manjaro Gnome installed Services and have been seeing some differences in the Installed services in Systemd. I’ve been combing through the Systemd Wiki and Bugs to try to figure why both laptops do not have these services, so this is where I need a second opinion from the community.

Service Only on the Thinkpad x230 but not on the Thinkpad T430s:

initrd-cleanup.service
initrd-parse-etc.service
initrd-switch-root.service
initrd-udevadm-cleanup-db.service
linux-module-cleanup.service
sysroot.mount
systemd-fsck-root.service

The laptops are similar in:

From same Intel generation i5 Thinkpad x230 and T430s).
Updated to the same Manjaro Patch Level and Firmware.
No Swap file or Partition.

The difference between the laptops:

Installs image/ISO was from 2 years ago for the x230.
Install image/ISO was from 3.5 years ago for the T430s
The harddrives are partitioned differently (see below)

x230 Partition Layout

fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 860
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6fa4558c

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048   2459647   2457600   1.2G  7 HPFS/NTFS/exFAT
/dev/sda2         2459648 667525119 665065472 317.1G  7 HPFS/NTFS/exFAT
/dev/sda4       667525120 976773119 309248000 147.5G 83 Linux


Disk /dev/loop0: 61.2 MiB, 64172032 bytes, 125336 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 55.32 MiB, 58007552 bytes, 113296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 61.26 MiB, 64233472 bytes, 125456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 62.09 MiB, 65105920 bytes, 127160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 29.89 MiB, 31342592 bytes, 61216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 161.41 MiB, 169254912 bytes, 330576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

T430 Partition Layout:

sudo fdisk -l
[sudo] password for root:
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 860
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6fa4558c

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048   2459647   2457600   1.2G  7 HPFS/NTFS/exFAT
/dev/sda2  *      2459648   3583999   1124352   549M  7 HPFS/NTFS/exFAT
/dev/sda3         3584000 689942527 686358528 327.3G  7 HPFS/NTFS/exFAT
/dev/sda4       689942528 976773119 286830592 136.8G  5 Extended
/dev/sda5       689944576 976773119 286828544 136.8G 83 Linux


Disk /dev/loop0: 161.41 MiB, 169254912 bytes, 330576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 62.09 MiB, 65105920 bytes, 127160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 29.89 MiB, 31342592 bytes, 61216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 55.32 MiB, 58007552 bytes, 113296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 61.2 MiB, 64172032 bytes, 125336 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 61.26 MiB, 64233472 bytes, 125456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

x230 System Configuration:

inxi -Fza
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=85ccbb8b-086b-4c3b-a6c8-a45951356c8e rw apparmor=1 security=apparmor
	       usbcore.autosuspend=-1
	       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: LENOVO product:  v: ThinkPad X230 serial: <filter>
	       Chassis: type: 10 serial: <filter>
	       Mobo: LENOVO model:  serial: <filter> UEFI [Legacy]: LENOVO
	       
Battery:   ID-1: BAT0 charge: 34.9 Wh condition: 34.9/57.7 Wh (60%) volts: 12.5/11.1
	       model: LGC 45N1025 type: Li-ion serial: <filter> status: Full
CPU:       Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP arch: Ivy Bridge
	       family: 6 model-id: 3A (58) stepping: 9 microcode: 21 L2 cache: 3072 KiB
	       flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20763
	       Speed: 3095 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 3094 2: 3230 3: 2044
	       4: 2879
	       Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
	       Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
	       Type: mds mitigation: Clear CPU buffers; SMT vulnerable
	       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: conditional, RSB filling
	       Type: srbds status: Vulnerable: No microcode
	       Type: tsx_async_abort status: Not affected
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics vendor: Lenovo driver: i915 v: kernel
	       bus ID: 00:02.0 chip ID: 8086:0166
	       Device-2: Acer ThinkPad Integrated Camera type: USB driver: uvcvideo bus ID: 1-1.6:4
	       chip ID: 5986:02d2
	       Display: x11 server: X.Org 1.20.8 compositor: gnome-shell driver: intel
	       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: LVDS1 res: 1366x768 hz: 60 dpi: 124 size: 280x160mm (11.0x6.3")
	       diag: 322mm (12.7")
	       OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.1.7
	       compat-v: 3.0 direct render: Yes
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo
	       driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20
	       Sound Server: ALSA v: k5.4.64-1-MANJARO
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k
	       port: 6080 bus ID: 00:19.0 chip ID: 8086:1502
	       IF: enp0s25 state: down mac: <filter>
	       Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel
	       port: efa0 bus ID: 03:00.0 chip ID: 8086:0085
	       IF: wlp3s0 state: up mac: <filter>
Drives:    Local Storage: total: 465.76 GiB used: 59.45 GiB (12.8%)
	       ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB block size:
	       physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR
	       SMART Message: Unknown smartctl error. Unable to get data.
Partition: ID-1: / raw size: 147.46 GiB size: 144.15 GiB (97.75%) used: 59.45 GiB (41.2%)
	       fs: ext4 block size: 4096 B dev: /dev/sda4
Swap:      Alert: No Swap data was found.
Sensors:   System Temperatures: cpu: 48.0 C mobo: 0.0 C
	       Fan Speeds (RPM): cpu: 0
Info:      Processes: 247 Uptime: 3h 46m Memory: 11.41 GiB used: 1.68 GiB (14.7%) Init: systemd
	       v: 246 Compilers: gcc: 10.2.0 Packages: 1470 pacman: 1453 lib: 411 flatpak: 11
	       snap: 6 Shell: fish v: 3.1.2 running in: alacritty inxi: 3.1.05

kagetora13 · 18 September 2020 15:07

Give this post a bump just in case anyone has input about the service differences between the two installs.

So far I can only find this documentation:

https://www.freedesktop.org/software/systemd/man/bootup.html

megavolt · 18 September 2020 16:16

Hi there

kagetora13:

Service Only on the Thinkpad x230 but not on the Thinkpad T430s:

initrd-cleanup.service
initrd-parse-etc.service
initrd-switch-root.service
initrd-udevadm-cleanup-db.service
linux-module-cleanup.service
sysroot.mount
systemd-fsck-root.service

The services are not there or just not started?

Did you compare that dir?

ls /usr/lib/systemd/system/

kagetora13 · 18 September 2020 20:02

Hi Megavolt,

Thanks for the feedback.

I was using the “systemd-analyze blame” command to see what was loading at startup and how much time it took to get the list of processes (Mr Tunes allot ).

I went ahead and re-compared based on your feedback and these are the new differences between the system.

Only on the T430s:

nvidia-persistenced.service
optimus-manager.service
tpacpi-bat.service
vboxweb.service

Only on the x230:

brltty.service
hplip-printer@.service
irexec.service
lircd.service
lircd-setup.service
lircd.socket
lircd-uinput.service
lircmd.service
ratbagd.service
systemd-swap.service

The differences on the T430s are expected (as optimus setup + has Oracle Virtual box).

So now I will go through the online documentation for the different x230 services to see if I have outstanding questions.

kagetora13 · 19 September 2020 23:22

@megavolt

Hi Megavolt,

Just wanted to let you know that I ended up comparing the following services between the two laptops. I’ve also included a table comparison table showing the status of the services after boot.

My goal at this point will be to clean up errors and then try to learn what services might not be needed. Its been challenging to try to find documentation on each service.

Services to be Checked:

systemctl status initrd-cleanup.service
systemctl status initrd-parse-etc.service
systemctl status initrd-switch-root.service
systemctl status initrd-udevadm-cleanup-db.service
systemctl status linux-module-cleanup.service
systemctl status sysroot.mount
systemctl status systemd-fsck-root.service

Service Being Researched	T430s	x230
systemctl status initrd-cleanup.service	initrd-cleanup.service - Cleaning Up and Shutting Down Daemons Loaded: loaded (/usr/lib/systemd/system/initrd-cleanup.service; static) Active: inactive (dead)	initrd-cleanup.service - Cleaning Up and Shutting Down Daemons Loaded: loaded (/usr/lib/systemd/system/initrd-cleanup.service; static) Active: inactive (dead) since Sat 2020-09-19 04:53:02 EDT; 4h 5min ago Main PID: 213 (code=exited, status=0/SUCCESS) Sep 19 04:53:02 manjaro systemd[1]: Starting Cleaning Up and Shutting Down Daemons… Sep 19 04:53:02 manjaro systemd[1]: initrd-cleanup.service: Succeeded. Sep 19 04:53:02 manjaro systemd[1]: Finished Cleaning Up and Shutting Down Daemons.
systemctl status initrd-parse-etc.service	initrd-parse-etc.service - Reload Configuration from the Real Root Loaded: loaded (/usr/lib/systemd/system/initrd-parse-etc.service; static) Active: inactive (dead)	initrd-parse-etc.service - Reload Configuration from the Real Root Loaded: loaded (/usr/lib/systemd/system/initrd-parse-etc.service; static) Active: inactive (dead) since Sat 2020-09-19 04:53:02 EDT; 4h 6min ago Main PID: 212 (code=exited, status=0/SUCCESS) Sep 19 04:53:02 manjaro systemd[1]: Starting Reload Configuration from the Real Root> Sep 19 04:53:02 manjaro systemd[1]: initrd-parse-etc.service: Succeeded. Sep 19 04:53:02 manjaro systemd[1]: Finished Reload Configuration from the Real Root. lines 1-8/8 (END)
systemctl status initrd-switch-root.service	initrd-switch-root.service - Switch Root Loaded: loaded (/usr/lib/systemd/system/initrd-switch-root.service; static) Active: inactive (dead)	initrd-switch-root.service - Switch Root Loaded: loaded (/usr/lib/systemd/system/initrd-switch-root.service; static) Active: inactive (dead) since Sat 2020-09-19 08:53:02 EDT; 6min ago Process: 216 ExecStart=/usr/bin/systemctl --no-block switch-root /sysroot (code=> Main PID: 216 (code=exited, status=0/SUCCESS) Sep 19 04:53:02 manjaro systemd[1]: Starting Switch Root…
systemctl status initrd-udevadm-cleanup-db.service	initrd-udevadm-cleanup-db.service - Cleanup udev Database Loaded: loaded (/usr/lib/systemd/system/initrd-udevadm-cleanup-db.service; static) Active: inactive (dead)	initrd-udevadm-cleanup-db.service - Cleanup udev Database Loaded: loaded (/usr/lib/systemd/system/initrd-udevadm-cleanup-db.service; stat> Active: inactive (dead) since Sat 2020-09-19 04:53:02 EDT; 4h 7min ago Main PID: 215 (code=exited, status=0/SUCCESS) Sep 19 04:53:02 manjaro systemd[1]: Starting Cleanup udev Database… Sep 19 04:53:02 manjaro systemd[1]: initrd-udevadm-cleanup-db.service: Succeeded. Sep 19 04:53:02 manjaro systemd[1]: Finished Cleanup udev Database.
systemctl status linux-module-cleanup.service	Unit linux-module-cleanup.service could not be found.	linux-module-cleanup.service - Clean up modules from old kernels Loaded: loaded (/etc/systemd/system/linux-module-cleanup.service; enabled; vend> Active: inactive (dead) since Sat 2020-09-19 08:53:05 EDT; 8min ago Process: 546 ExecStart=/usr/bin/linux-module-cleanup (code=exited, status=0/SUCC> Main PID: 546 (code=exited, status=0/SUCCESS) Sep 19 08:53:05 mani systemd[1]: Starting Clean up modules from old kernels… Sep 19 08:53:05 mani linux-module-cleanup[547]: cat: /usr/lib/modules/.old: No such > Sep 19 08:53:05 mani systemd[1]: linux-module-cleanup.service: Succeeded. Sep 19 08:53:05 mani systemd[1]: Finished Clean up modules from old kernels.
systemctl status sysroot.mount	Unit sysroot.mount could not be found.	Unit sysroot.mount could not be found.
systemctl status systemd-fsck-root.service	Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; enabled-runtime; vendor pre> Active: inactive (dead) Condition: start condition failed at Sat 2020-09-19 08:21:50 EDT; 8min ago └─ ConditionPathIsReadWrite=!/ was not met Docs: man:systemd-fsck-root.service(8)	systemd-fsck-root.service - File System Check on Root Device Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; enabled-runt> Active: active (exited) since Sat 2020-09-19 04:53:02 EDT; 4h 10min ago Docs: man:systemd-fsck-root.service(8) Main PID: 195 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 13996) Memory: 0B CGroup: /system.slice/systemd-fsck-root.service Sep 19 04:53:02 manjaro systemd[1]: Starting File System Check on /dev/disk/by-uuid/> Sep 19 04:53:02 manjaro systemd-fsck[197]: /dev/sda4: clean, 1012981/9666560 files, > Sep 19 04:53:02 manjaro systemd[1]: Finished File System Check on /dev/disk/by-uuid/> lines 1-12/12 (END)