Stopped file system check when boot

English Install/Boot/Login
#1

Hi,

I have openSuse Leap for about 1 month now.

So, I looked through /var/log/boot.log for some reason and found that the random file system check for my root partition when booting is stopped.

cat boot.log | grep "Stopped"

gives

  OK  ] Stopped Switch Root.
  OK  ] Stopped target Switch Root.
  OK  ] Stopped target Initrd File Systems.
  OK  ] Stopped File System Check on /dev/disk/by-uuid/598d0acc-3340-43bf-b8d3-9d51da0b4128.
  OK  ] Stopped target Initrd Root File System.
  OK  ] Stopped Trigger Flushing of Journal to Persistent Storage.
  OK  ] Stopped Journal Service.
  OK  ] Stopped Entropy Daemon based on the HAVEGE algorithm.

That /dev/disk/… 128 should be my root parition.

Is that bad? I always thought it’s not a good idea to stop a file system check.
I also have a file system check for my /home partition afterwards, which is not stopped.

I am basically just a bit worried.

Best
Marc

#2

Because of the grep we see all “Stoped” messages together that may in fact be spread all over the file. I think it is more usefull to have a few lines before and after the line you worry about. That will show what happens at about the same time.

#3

sure

sed -n '1,27p' /var/log/boot.log
  OK  ] Started Show Plymouth Boot Screen.
  OK  ] Reached target Paths.
  OK  ] Reached target Basic System.
  OK  ] Found device Samsung_SSD_850 2.
  OK  ] Started dracut initqueue hook.
  OK  ] Reached target Remote File Systems (Pre).
  OK  ] Reached target Remote File Systems.
         Starting dracut pre-mount hook...                                                    
  OK  ] Started dracut pre-mount hook.                                                       
         Starting File System Check on /dev/disk/by-uuid/598d0acc-3340-43bf-b8d3-9d51da0b4128...
  OK  ] Started File System Check on /dev/disk/by-uuid/598d0acc-3340-43bf-b8d3-9d51da0b4128. 
         Mounting /sysroot...                                                                 
  OK  ] Mounted /sysroot.                                                                    
  OK  ] Reached target Initrd Root File System.                                              
         Starting Reload Configuration from the Real Root...                                  
  OK  ] Started Reload Configuration from the Real Root.                                     
  OK  ] Reached target Initrd File Systems.                                                  
  OK  ] Reached target Initrd Default Target.                                                
                                                                                              
Welcome to openSUSE Leap 42.1 (x86_64)!                                                       
                                                                                              
  OK  ] Stopped Switch Root.                                                                 
  OK  ] Stopped target Switch Root.                                                          
  OK  ] Stopped target Initrd File Systems.                                                  
         Stopping File System Check on /dev/disk/by-uuid/598d0acc-3340-43bf-b8d3-9d51da0b4128...
  OK  ] Stopped File System Check on /dev/disk/by-uuid/598d0acc-3340-43bf-b8d3-9d51da0b4128. 
  OK  ] Stopped target Initrd Root File System.
#4

IMHO systemd simply tells that it is ready with that action. It is stopped because it is finished. Like several others there.

#5

One possibility is that you have a failing disk, causing some of these to take too long. Maybe do some disk checking with “smartctl”. And this might be a good time for a backup.

#6

Will do.

It’s a very new ssd. However, I’ve heard mass storages fail either very early, or after about 6-8 years.