Systemd mount fails at shutdown if drive has been accessed (I think) - samba server was responsible

Support
1

After using my system and shutting it down (or rebooting) I see a failed unmount quickly passing by. If I do not access the drive, it does NOT fail.

$ sudo journalctl -xe -b-2 -p3  
--------------
 Subject: A stop job for unit media-fil\x2dfitt.mount has finished
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A stop job for unit media-fil\x2dfitt.mount has finished.
░░ 
░░ The job identifier is 4857 and the job result is failed.
--------------

But if I check the units log there is not much more info, and a different job number:

$ sudo journalctl -x -u media-fil\\x2dfitt.mount
Nov 02 00:48:34 bednaManjaro systemd[1]: Unmounting File drive (fil-fitt)...
░░ Subject: A stop job for unit media-fil\x2dfitt.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A stop job for unit media-fil\x2dfitt.mount has begun execution.
░░ 
░░ The job identifier is 2245.
Nov 02 00:48:34 bednaManjaro systemd[1]: media-fil\x2dfitt.mount: Deactivated successfully.
░░ Subject: Unit succeeded
Nov 02 00:48:34 bednaManjaro systemd[1]: Unmounting File drive (fil-fitt)...
░░ Subject: A stop job for unit media-fil\x2dfitt.mount has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A stop job for unit media-fil\x2dfitt.mount has begun execution.
░░ 
░░ The job identifier is 2245.
Nov 02 00:48:34 bednaManjaro systemd[1]: media-fil\x2dfitt.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit media-fil\x2dfitt.mount has successfully entered the 'dead' state.
Nov 02 00:48:34 bednaManjaro systemd[1]: Unmounted File drive (fil-fitt).
░░ Subject: A stop job for unit media-fil\x2dfitt.mount has finished
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A stop job for unit media-fil\x2dfitt.mount has finished.
░░ 
░░ The job identifier is 2245 and the job result is done.

What does that job intentifier even mean?
How can I access logs that tells me WHAT goes wrong.
The disk is old AF (wd red) and I abuse the crap out of it, so it might just be failing, but smart tells me no failures.

Please advice.

2

That does indeed appear to be the case here.

Internal housekeeping by systemd. A job identifier is usually a PID, and it is commonly only communicated when starting a process in the background.

3

So there is no way of seeing the logs of those jobs?

I feel smart would give me some kind of info of faulures. :frowning:

4

It should be in the journal, normally.

Yes, one would expect so. Have you run a full SMART test on it?

5

Excuse my noob question, internet fails me. :frowning:
How do I access those logs.

I did check smartctl and found nothing.
Not at home right now, will run it again when I’m back.

6 
man journalctl

:stuck_out_tongue:

7

You could have given me the command, but I guess I can run man too, even thoug i tried with internet.

https://www.man7.org/linux/man-pages/man1/journalctl.1.html

Is it -t?
I find no reference to job number. :frowning:

8

Yes, but then I too would have had to look it up in the man page. So I gave you the shortcut answer instead, so that you could find it yourself. :stuck_out_tongue:

Yes, in combination with -p.

Forget about that job number. It was probably just the umount process. What you need to check is whether the drive is throwing errors.

Also dmesg might give you more information.

9

Came home over lunch and ran a few commands, but using -p and -t shows nothing, but just straight up sudo journalctl -u media-fil\\x2dfitt.mount I found:

Nov 01 17:36:02 bednaManjaro systemd[1]: Mounting File drive (fil-fitt)...
Nov 01 17:36:04 bednaManjaro systemd[1]: Mounted File drive (fil-fitt).
Nov 02 00:27:22 bednaManjaro systemd[1]: Unmounting File drive (fil-fitt)...
Nov 02 00:27:22 bednaManjaro umount[39579]: umount: /media/fil-fitt: target is busy.
Nov 02 00:27:22 bednaManjaro systemd[1]: media-fil\x2dfitt.mount: Mount process exited, code=exited, status=32/n/a
Nov 02 00:27:22 bednaManjaro systemd[1]: Failed unmounting File drive (fil-fitt).

How do I find out WHAT is using it so it’s “busy”?

I cant find any reference in dmesg to this drive. :frowning:

I am no expert in using smartctl but here is the output:

sudo smartctl -a /dev/sdb3                                                                                                                                                                           ✔ 
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.0-2-MANJARO] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-WMC4N1849844
LU WWN Device Id: 5 0014ee 0ae676016
Firmware Version: 80.00A80
User Capacity:    3 000 592 982 016 bytes [3,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Nov  2 12:33:47 2023 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (41280) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 414) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x703d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   161   161   021    Pre-fail  Always       -       6916
  4 Start_Stop_Count        0x0032   083   083   000    Old_age   Always       -       17934
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   001   001   000    Old_age   Always       -       78560
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1129
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       137
193 Load_Cycle_Count        0x0032   176   176   000    Old_age   Always       -       72060
194 Temperature_Celsius     0x0022   123   106   000    Old_age   Always       -       27
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     11232         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The above only provides legacy SMART information - try 'smartctl -x' for more

But I just realized that there is an -x tag, because I’m an idiot, so:

sudo smartctl -x /dev/sdb3                                                                                                                                                                           ✔ 
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.0-2-MANJARO] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red
Device Model:     WDC WD30EFRX-68EUZN0
Serial Number:    WD-WMC4N1849844
LU WWN Device Id: 5 0014ee 0ae676016
Firmware Version: 80.00A80
User Capacity:    3 000 592 982 016 bytes [3,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Nov  2 12:34:27 2023 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (41280) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 414) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x703d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   161   161   021    -    6916
  4 Start_Stop_Count        -O--CK   083   083   000    -    17934
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   001   001   000    -    78560
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   100   000    -    0
 12 Power_Cycle_Count       -O--CK   099   099   000    -    1129
192 Power-Off_Retract_Count -O--CK   200   200   000    -    137
193 Load_Cycle_Count        -O--CK   176   176   000    -    72060
194 Temperature_Celsius     -O---K   123   106   000    -    27
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    0
198 Offline_Uncorrectable   ----CK   100   253   000    -    0
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   100   253   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb7  GPL,SL  VS       1  Device vendor specific log
0xbd       GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     11232         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       258 (0x0102)
Device State:                        Active (0)
Current Temperature:                    27 Celsius
Power Cycle Min/Max Temperature:     20/27 Celsius
Lifetime    Min/Max Temperature:      2/44 Celsius
Under/Over Temperature Limit Count:   0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (223)

Index    Estimated Time   Temperature Celsius
 224    2023-11-02 04:37    32  *************
 ...    ..( 96 skipped).    ..  *************
 321    2023-11-02 06:14    32  *************
 322    2023-11-02 06:15    33  **************
 ...    ..( 34 skipped).    ..  **************
 357    2023-11-02 06:50    33  **************
 358    2023-11-02 06:51    32  *************
 ...    ..( 17 skipped).    ..  *************
 376    2023-11-02 07:09    32  *************
 377    2023-11-02 07:10    33  **************
 ...    ..(  5 skipped).    ..  **************
 383    2023-11-02 07:16    33  **************
 384    2023-11-02 07:17    32  *************
 385    2023-11-02 07:18    33  **************
 ...    ..(  7 skipped).    ..  **************
 393    2023-11-02 07:26    33  **************
 394    2023-11-02 07:27     ?  -
 395    2023-11-02 07:28    19  -
 396    2023-11-02 07:29    20  *
 397    2023-11-02 07:30    21  **
 ...    ..(  2 skipped).    ..  **
 400    2023-11-02 07:33    21  **
 401    2023-11-02 07:34    22  ***
 402    2023-11-02 07:35    22  ***
 403    2023-11-02 07:36    23  ****
 ...    ..(  3 skipped).    ..  ****
 407    2023-11-02 07:40    23  ****
 408    2023-11-02 07:41    24  *****
 ...    ..(  6 skipped).    ..  *****
 415    2023-11-02 07:48    24  *****
 416    2023-11-02 07:49    25  ******
 ...    ..(  2 skipped).    ..  ******
 419    2023-11-02 07:52    25  ******
 420    2023-11-02 07:53    26  *******
 421    2023-11-02 07:54    26  *******
 422    2023-11-02 07:55    27  ********
 ...    ..( 12 skipped).    ..  ********
 435    2023-11-02 08:08    27  ********
 436    2023-11-02 08:09     ?  -
 437    2023-11-02 08:10    20  *
 438    2023-11-02 08:11    21  **
 ...    ..(  2 skipped).    ..  **
 441    2023-11-02 08:14    21  **
 442    2023-11-02 08:15    22  ***
 443    2023-11-02 08:16    22  ***
 444    2023-11-02 08:17    23  ****
 ...    ..(  2 skipped).    ..  ****
 447    2023-11-02 08:20    23  ****
 448    2023-11-02 08:21    24  *****
 ...    ..(  7 skipped).    ..  *****
 456    2023-11-02 08:29    24  *****
 457    2023-11-02 08:30    25  ******
 ...    ..(  3 skipped).    ..  ******
 461    2023-11-02 08:34    25  ******
 462    2023-11-02 08:35    26  *******
 ...    ..(  4 skipped).    ..  *******
 467    2023-11-02 08:40    26  *******
 468    2023-11-02 08:41    27  ********
 ...    ..(  8 skipped).    ..  ********
 477    2023-11-02 08:50    27  ********
   0    2023-11-02 08:51    31  ************
 ...    ..( 39 skipped).    ..  ************
  40    2023-11-02 09:31    31  ************
  41    2023-11-02 09:32    32  *************
 ...    ..(181 skipped).    ..  *************
 223    2023-11-02 12:34    32  *************

SCT Error Recovery Control:
           Read:     70 (7,0 seconds)
          Write:     70 (7,0 seconds)

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            2  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            3  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4         2430  Vendor specific

But this could just as well be in Marsian, I do not understand what it is telling me. :frowning:

10

You probably have some process either writing to the device, or having files open (in read/write mode) that reside on the device.

Check out the following man pages… :point_down:

man lsof
man fuser
1 Like
11

I have to go back to work, if anyone feel like trying to translate the Marsian language smartclt gave me I would love it.

But I will def see if I can figure out what is doing this. I am ALWAYS closing everything down before reboot.
It might be something like dolphin tbh, because only opening dolphin to browse the files, then close dolphin and reboot throws the error, but if I do not, it doesn’t (witch means the drive is never mounted because it mounts at access with systemd)

Yes, thank you for pointing that out. I will try those after starting dolphin and see if there is anything strange going on.

12

baloo perhaps? dolphin sources much of the information it displays through baloo. :thinking:

13

Baloo is disabled (that is the file indexing thing right?)
Pretty sure I disabled the systemd service, but I have to double check when getting back home.

I was thinking watchdog, I saw cscs made a post about how to disable it, I have, in the past, seen the “watchdog failed” but that was a while ago.

14

Yes.

Um, it doesn’t use systemd. It is enabled, configured or disabled from within System Settings, although it can also be manipulated from the command line through balooctl.

Hmm, I don’t think this would be related to any watchdog timers. If it was, then the error message would say so — “Watchdog timer did not stop […]”.

As for the smartctl output, I don’t see anything out of the ordinary there. :man_shrugging:

Additional information that may or may not be related:

Over the last couple of months, I have on several occasions needed to completely wipe my home directory and restore a backup of it, which according to my analysis and tracing back on my steps leading to these “crashes”, leads me to suspect that systemd does not cleanly unmount all filesystems anymore, and that this would be a systemd regression that has crept into the latest update to the systemd package.

I have found that everything is fine when rebooting through the sddm screen, and that things go haywire when rebooting from the command line with systemctl reboot, or even dropping to runlevel 1 with systemd isolate rescue.target.

Therefore, if my theory is correct, then it’s a systemd bug — probably a timing issue, because systemd calls mount/umount. And that said, I also prefer listing my filesystems in /etc/fstab instead of relying on systemd mounts and/or auto-mounting.

:thinking:

1 Like
15

Possibly related:

16

LOL, “njae”, it’s a btrfs, and there is zero problems using it, but will def check out the bugs and see if there is any relation.

I’ll do some testing once I wined down a bit from the day.

2 Likes
17

?
I also assumed it didn’t use systemd, but I was recently reading this post Baloo and Frameworks 5.111 - Tips and Tricks - KDE Discuss, and checked my system and indeed, I have on my fully up-to-date system, kde-baloo.service running.

  • also just to mention it, I did a full re-index today and it didn’t slow down my system like it did in the past.
1 Like
18

You guys are correct, it uses balooctl but it was disabled, so it’s not that.
I have no systemd service called kde-baloo.service but maybe that is because I disabled it with balooctl suspend a long time ago (and have it disabled in the kde settings)

$ balooctl status
Baloo is currently disabled. To enable, please run balooctl enable

Did find this though: https://unix.stackexchange.com/questions/750854/systemd-failed-to-unmount-during-shutdown

There are gremlins in my system, because now, whatever I do I can not get it to fail at reboot (like it has before)

lsof and fuser does not report anything unless I have something open, but I will use the system until I go to bed now a few hours making sure I run the commands before shutdown.

If I just manage to figure out what is sometimes doing this I can most likely implement a check in the systemd service like mentioned in the link.

My research continues.

Edit
Nvm, there is a service for baloo, but it is a --user service (probably mentioned in the link, that I did not click xD)
But it is also disabled.

systemctl --user status kde-baloo.service                                                                                                                                                          1 ✘ 
○ kde-baloo.service - Baloo File Indexer Daemon
     Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: enabled)
     Active: inactive (dead) (Result: exec-condition) since Thu 2023-11-02 17:57:28 CET; 18min ago
  Condition: start condition unmet at Thu 2023-11-02 17:57:28 CET; 18min ago
    Process: 1207 ExecCondition=/usr/bin/kde-systemd-start-condition --condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited, status=1/FAILURE)
        CPU: 3ms

Nov 02 17:57:28 bednaManjaro systemd[1167]: Starting Baloo File Indexer Daemon...
Nov 02 17:57:28 bednaManjaro systemd[1167]: kde-baloo.service: Skipped due to 'exec-condition'.
Nov 02 17:57:28 bednaManjaro systemd[1167]: Condition check resulted in Baloo File Indexer Daemon being skipped.

Kinda weird that it still tries to run a check, even though the service is disabled… hmmm…

$ journalctl --user -u kde-baloo.service
--------------------
-- Boot 1f3346d451ba42b8adec986f87b9aa76 --
Nov 02 11:54:28 bednaManjaro systemd[1196]: Starting Baloo File Indexer Daemon...
Nov 02 11:54:28 bednaManjaro systemd[1196]: kde-baloo.service: Skipped due to 'exec-condition'.
Nov 02 11:54:28 bednaManjaro systemd[1196]: Condition check resulted in Baloo File Indexer Daemon being skipped.
-- Boot 86cbc6b2f8f94cb79dae510487ce29ac --
Nov 02 15:00:14 bednaManjaro systemd[1141]: Starting Baloo File Indexer Daemon...
Nov 02 15:00:14 bednaManjaro systemd[1141]: kde-baloo.service: Skipped due to 'exec-condition'.
Nov 02 15:00:14 bednaManjaro systemd[1141]: Condition check resulted in Baloo File Indexer Daemon being skipped.
-- Boot e58e981a25784684955dd8d7709faee8 --
Nov 02 17:33:43 bednaManjaro systemd[1154]: Starting Baloo File Indexer Daemon...
Nov 02 17:33:43 bednaManjaro systemd[1154]: kde-baloo.service: Skipped due to 'exec-condition'.
Nov 02 17:33:43 bednaManjaro systemd[1154]: Condition check resulted in Baloo File Indexer Daemon being skipped.
Nov 02 17:56:27 bednaManjaro systemd[1154]: Starting Baloo File Indexer Daemon...
Nov 02 17:56:27 bednaManjaro systemd[1154]: kde-baloo.service: Skipped due to 'exec-condition'.
Nov 02 17:56:27 bednaManjaro systemd[1154]: Condition check resulted in Baloo File Indexer Daemon being skipped.
-- Boot 6a36bf1b885e4673a59bc541d395f74d --
Nov 02 17:57:28 bednaManjaro systemd[1167]: Starting Baloo File Indexer Daemon...
Nov 02 17:57:28 bednaManjaro systemd[1167]: kde-baloo.service: Skipped due to 'exec-condition'.
Nov 02 17:57:28 bednaManjaro systemd[1167]: Condition check resulted in Baloo File Indexer Daemon being skipped.

Is it supposed to work like that? The service is disabled.
Should I mask it?

19

Disabled means it wont start automatically … but it can still be started, such as if called by something else.
Masking will truly block it from being started.
Though there is balooctl

balooctl suspend
balooctl disable
20

:wink:

I think it’s this, but not sure I will break something if I mask anything:
ExecCondition=/usr/bin/kde-systemd-start-condition --condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited, status=1/FAILURE)