filesystem check on every system start

[gnomek]

After upgrade from 14.04 to 16.04 I have filesystem check on every system start.

Upgrade was ok, only there was a message about plymouth error.

What log can I provide for you to help me identify the source of the problem?

[GreyGeek]

kernel log

[gnomek]

Please see attachment.

sudo tune2fs -c 60 -i 30 /dev/sda1
tune2fs 1.42.13 (17-May-2015)
setting max mount number  60
Ustawianie odstępu pomiędzy sprawdzeniami na 2592000 sekund

sudo tune2fs -l /dev/sda1 |grep -e count -e interval
Inode count:              932064
Block count:              3706742
Reserved block count:     185336
Mount count:              6
Maximum mount count:      60
Check interval:           2592000 (1 month)

[GreyGeek]

Your kernel log shows 2 HD devices, split into several partitions. The raid6 xor check is normal, even though you didn't install a RAID6 configuration.

Show the output of "fdisk -l" and the contents of /etc/fstab
.

[claydoh]

Is it doing a full fsck, or just the quick looksie it is supposed to do every boot?
Remember, 14.04 to 16.04 involves the move to systemd, so messaging will be different.

What does sudo tune2fs -l /dev/sda1 | grep "Last checked:" show?

[gnomek]

Maybe I had a disk attached, I don't remember but now it is sigle disk with three partitions and two snap loop devices.

sudo fdisk -l
[sudo] hasło użytkownika user1: 
Disk /dev/loop0: 86,9 MiB, 91115520 bytes, 177960 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: 139,8 MiB, 146591744 bytes, 286312 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/sda: 55,9 GiB, 60021399040 bytes, 117229295 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
Disklabel type: dos
Disk identifier: 0x0001b6eb

Urządzenie Rozruch    Start    End  Sektory  Size Id Typ
/dev/sda1  *           2048  29655989 29653942 14,1G 83 Linux
/dev/sda3          29655990  52741394 23085405   11G 83 Linux
/dev/sda4          52742144 117227519 64485376 30,8G  f W95 Rozsz. (LBA)
/dev/sda5          52744192 117227519 64483328 30,8G 83 Linux

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=2b383205-d6e5-4711-adc8-85d841b090c7 /               ext4    noatime,commit=120,errors=remount-ro 0       1
# /home was on /dev/sda5 during installation
UUID=64ade4ae-e2a5-4c19-a463-b9fd8de9f44e /home           ext4    noatime,commit=120,defaults        0       2
#Entry for /dev/sda6 :
UUID=cad64966-275d-4dd2-8b04-e9164061aa27       /media/data ext4    noatime,commit=120,defaults        0       2
#cdwriter
/dev/cdrom /media/cdrom udf,iso9660 rw,noauto,user,exec,utf8 0 0
#inne
none /tmp tmpfs defaults,noatime,mode=1777 0 0
none /var/tmp tmpfs defaults,noatime 0 0
none /var/log tmpfs defaults,noatime 0 0
none /var/spool tmpfs defaults,noatime 0 0

sudo tune2fs -l /dev/sda1 | grep "Last checked:"
Last checked:             Thu Jun 21 14:47:26 2018

Last checked shows time right after install.

[GreyGeek]

Jun 21 19:33:35 user1-945P-DS3 kernel: [ 3.596821] BTRFS: device fsid 7d5636f8-863a-4153-a8ca-e43e0f207efb devid 1 transid 508 /dev/sda5
Jun 21 19:33:35 user1-945P-DS3 kernel: [ 3.597031] BTRFS: device fsid 30561dcc-7888-437e-b4b2-4d4172a9d754 devid 1 transid 4048 /dev/sda1
Jun 21 19:33:35 user1-945P-DS3 kernel: [ 3.638831] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
...
Jun 21 19:35:48 user1-945P-DS3 kernel: [ 226.342695] BTRFS info (device sda5): disk space caching is enabled
...
Jun 21 19:39:10 user1-945P-DS3 kernel: [ 429.099259] BTRFS info (device sda1): disk space caching is enabled
Jun 21 19:39:10 user1-945P-DS3 kernel: [ 429.099266] BTRFS: has skinny extents
Jun 21 19:39:10 user1-945P-DS3 kernel: [ 429.188229] BTRFS: checking UUID tree

Btrfs:
sda1
sda5

Ext4:
sdb1

The tune2fs utility displays and modifies filesystem parameters on ext2,ext3,and ext4 filesystems.
You are attempting to use it on a partition that is formatted using Btrfs:

sudo tune2fs -c 60 -i 30 /dev/sda1

I have no clue what that will do but I suspect that it won't be pleasant for your Btrfs system, IF it runs at all against Btrfs.


Also, your fstab file shows that while your kernel thinks that sda1 & sda5 are Btrfs subvolumes, you apparently have modified fstab to convert them to EXT4 partitions.

# / was on /dev/sda1 during installation
UUID=2b383205-d6e5-4711-adc8-85d841b090c7 / ext4 noatime,commit=120,errors=remount-ro 0 1
# /home was on /dev/sda5 during installation
UUID=64ade4ae-e2a5-4c19-a463-b9fd8de9f44e /home ext4 noatime,commit=120,defaults 0 2
#Entry for /dev/sda6 :
UUID=cad64966-275d-4dd2-8b04-e9164061aa27 /media/data ext4 noatime,commit=120,defaults 0

If your intent was to create a Btrfs @ and @home (/ and /home) then you misunderstand the process.

Also, there is no need to create loop devices in order to install Btrfs.

I suggest that you save your data to a removable HD or USB stick and then do a reinstall. This time, forget the EXT4 partition stuff. Delete all partitions on sda and from the raw space create one partiton, sda1. Select Btrfs as the filesystem and "/" as the label. Bionic will do the rest. and you will have one Btrfs <ROOT_FS> pool holding @ and @home. Let the installer save grub where it will.

[gnomek]

Perhaps I had temporarily attached another disk but my system disk with 16.04 has no brtfs.

df -Th
System plików  Typ      rozm. użyte dost. %uż. zamont. na
udev           devtmpfs  1,5G     0  1,5G   0% /dev
tmpfs          tmpfs     301M  5,3M  296M   2% /run
[B]/dev/sda1      ext4       14G   11G  2,3G  83% /[/B]
tmpfs          tmpfs     1,5G  6,6M  1,5G   1% /dev/shm
tmpfs          tmpfs     5,0M  4,0K  5,0M   1% /run/lock
tmpfs          tmpfs     1,5G     0  1,5G   0% /sys/fs/cgroup
none           tmpfs     1,5G     0  1,5G   0% /var/spool
none           tmpfs     1,5G  332K  1,5G   1% /var/log
none           tmpfs     1,5G   36K  1,5G   1% /tmp
none           tmpfs     1,5G   11M  1,5G   1% /var/tmp
/dev/loop0     squashfs   87M   87M     0 100% /snap/core/4830
/dev/loop1     squashfs  140M  140M     0 100% /snap/chromium/353
[B]/dev/sda5      ext4       31G   27G  1,8G  95% /media/data[/B]
[B]/dev/sda3      ext4       11G  9,3G  919M  92% /home[/B]
cgmfs          tmpfs     100K     0  100K   0% /run/cgmanager/fs
tmpfs          tmpfs     301M   16K  301M   1% /run/user/1001

On this disk I never had btrfs and I did only a standard upgrade.

In this new kernel.log I can see only one message about btrfs

Btrfs loaded
Jun 21 21:44:43 user1-945P-DS3 kernel: [    2.827338] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

On screen it looks like this
https://imgur.com/a/xBLtUjX

It is not even a proper fsck message that should have options to skip checking.

update:
I changed fsck option in fstab from 2 to 0 and now I this info
that is on screenshot doesn't appear but system start is terribly slow in comparison to 14.04. Plymouth first flashes blue dots and blank screen and than orange dots. Does the colour has any meaning?

[gnomek]

Up.

Update 2:
@GreyGeek
Can you please have another look at bootlog. It looks like system is looking for an encrypted disk that I labelled green. But it is not mounted and doesn't have fstab entry.

[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (1 of 2) A start job is running for...c50.device (1min 28s / 1min 30s)
[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (1 of 2) A start job is running for...c50.device (1min 29s / 1min 30s)
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] (1 of 2) A start job is running for...c50.device (1min 29s / 1min 30s)
[K[[0;1;31m TIME [0m] Timed out waiting for device dev-di...\x2db31c\x2d86b18549cc50.device.
[[0;1;33mDEPEND[0m] Dependency failed for Cryptography Setup for green.
[[0;1;33mDEPEND[0m] Dependency failed for dev-mapper-green.device.
[[0;1;33mDEPEND[0m] Dependency failed for Encrypted Volumes.

How can I fix it?
bootlog
https://pastebin.com/fXiYA0gK
kernlog
https://pastebin.com/LNbeuTwV
syslog
https://pastebin.com/ka0ELdui
xorg
https://pastebin.com/NHymryAv
apport
https://pastebin.com/mZBpS8Q8

dmesg > /tmp/boot.txt

https://pastebin.com/2TCd6dUh

systemd-analyze blame

https://pastebin.com/jLpts8yP

systemd-analyze
Startup finished in 2.930s (kernel) + 3min 585ms (userspace) = 3min 3.515s

It is on SSD drive.

sudo systemd-analyze critical-chain
graphical.target@1min 50.207s 
└─multi-user.target @1min 50.206s
└─getty.target @1min 50.177s 
└─getty@tty1.service@1min 50.176s 
└─[B]rc-local.service@1min 40.110s +10.047s[/B]
└─network-online.target@1min 40.090s 
└─[B]NetworkManager-wait-online.service@1min 30.677s +9.412s[/B]
  └─[B]NetworkManager.service@1min 30.512s +150ms[/B]
    └─dbus.service@1min 30.454s 
      └─basic.target@1min 30.411s 
        └─sockets.target@1min 30.411s 
          └─dbus.socket@1min 30.411s 
            └─sysinit.target@1min 30.398s 
              └─[B]apparmor.service@1.092s +350ms[/B]
                └─local-fs.target@1.087s                                                               
                  └─run-user-1001.mount@1min 31.704s                                                   
                    └─local-fs-pre.target@478ms                                                        
                      └─[B]keyboard-setup.service@221ms +197ms[/B]
                        └─system.slice@196ms                                                           
                          └─-.slice@177ms

Update:
the difference between 15:53:30 and 15:54:58 = 1:28 min.

cze 23 15:53:30 user1-945P-DS3 kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:0
cze 23 15:53:30 user1-945P-DS3 nvidia-persistenced[682]: Shutdown (682)
cze 23 15:54:58 user1-945P-DS3 systemd[1]: dev-disk-by\x2duuid-fe9bc1cb\x2de3a1\x2d4a8f\x2db31c\x2d86b18549cc50.d
cze 23 15:54:58 user1-945P-DS3 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-fe9bc1cb\x2de3a1\x2d4
cze 23 15:54:58 user1-945P-DS3 systemd[1]: Dependency failed for Cryptography Setup for green.
cze 23 15:54:58 user1-945P-DS3 systemd[1]: Dependency failed for dev-mapper-green.device.
cze 23 15:54:58 user1-945P-DS3 systemd[1]: dev-mapper-green.device: Job dev-mapper-green.device/start failed with
cze 23 15:54:58 user1-945P-DS3 systemd[1]: Dependency failed for Encrypted Volumes.
cze 23 15:54:58 user1-945P-DS3 systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dep
cze 23 15:54:58 user1-945P-DS3 systemd[1]: systemd-cryptsetup@green.service: Job systemd-cryptsetup@green.service
cze 23 15:54:58 user1-945P-DS3 systemd[1]: dev-disk-by\x2duuid-fe9bc1cb\x2de3a1\x2d4a8f\x2db31c\x2d86b18549cc50.d
cze 23 15:54:58 user1-945P-DS3 systemd[1]: Reached target System Initialization.

[GreyGeek]

I don't know what you are trying to do, but what ever it is you are mixing apples and oranges, or Btrfs & EXT4. In addition to that your GPU is not properly configured, nor is your network managers.

sudo systemd-analyze critical-chain
graphical.target@[COLOR=#ff0000]1min 50.207s [/COLOR]
└─multi-user.target @[COLOR=#ff0000]1min 50.206s[/COLOR]
└─getty.target @[COLOR=#ff0000]1min 50.177s [/COLOR]
└─getty@tty1.service@[COLOR=#ff0000]1min 50.176s [/COLOR]
└─[B]rc-local.service@[COLOR=#ff0000]1min 40.110s +10.047s[/COLOR][/B]
 └─network-online.target@[COLOR=#ff0000]1min 40.090s[/COLOR] 
   └─[B]NetworkManager-wait-online.service@[COLOR=#ff0000]1min 30.677s +9.412s[/COLOR][/B]
     └─[B]NetworkManager.service@[COLOR=#ff0000]1min 30.512s +150ms[/COLOR][/B]
       └─dbus.service@[COLOR=#ff0000]1min 30.454s[/COLOR] 
         └─basic.target@[COLOR=#ff0000]1min 30.411s [/COLOR]
           └─sockets.target@[COLOR=#ff0000]1min 30.411s [/COLOR]
             └─dbus.socket@1min 30.411s 
               └─sysinit.target@1min 30.398s 
                 └─[B]apparmor.service@1.092s +350ms[/B]
                   └─local-fs.target@1.087s                                                               
                     └─run-user-1001.mount@[COLOR=#ff0000]1min 31.704s[/COLOR]

Here is my critical-chain:

graphical.target @43.696s
└─sddm.service @1min 58.799s +4ms
  └─systemd-user-sessions.service @16.575s +7ms
    └─basic.target @16.235s
      └─paths.target @16.235s
        └─acpid.path @16.235s
          └─sysinit.target @16.224s
            └─systemd-timesyncd.service @16.116s +108ms
              └─systemd-tmpfiles-setup.service @15.646s +468ms
                └─local-fs.target @15.645s
                  └─run-user-1000.mount @59.176s
                    └─local-fs-pre.target @11.437s
                      └─systemd-remount-fs.service @10.453s +982ms
                        └─systemd-journald.socket @

Notice what you are missing compared to my listing.

sudo systemd-analyze plot > bootup.svg
Then you can browse that svg file with your browser. It will show which processes start and how long they last, and if any are running simultaneously with others, which will be quite a few.

In your logs I see that you have Btrfs installed as a service BUT you have not used it. ALL three of your partitions are formatted as EXT4 (sda1, sda3, sda5).

You are doing so many jives that you've faked yourself out of your own pants.

Do it simple and stop trying to be so complicated. You don't have the Linux-fu to do that stuff yet.

Fire up your LiveBIONIC USB stick and when the installation process gets to the partition manager delete sda1, sda3 and sda5, assuming they are contiguous. Then, select the raw unformatted part of the disk and select "New" partition. In the dialog that pops up select "Btrfs" as the file system and use / as the label. Then click the apply button. Continue with the rest of the install. When you are done and have rebooted you can proceed to configure your wifi connection using the system tray icon. IF you have an NVidia GPU then use Muon to install nvidia-390 and its dozen or more associated apps. Reboot. You should have everything running well.
If so, open a Kosnsole and "sudo -i". As root,
mount /dev/disk-by-uuid/whatever /mnt
(Note that the uuid may not be what it was before.
Then create a snapshot subdirectory.
mkdir /mnt/snapshots
Then take your first snapshot of @ and @home
btrfs subvol snapshot -r /mnt/@ /mnt/snapshots/@homeYYYYMMDD
sync
btrfs subvol snapshot -r /mnt/@home /mnt/snapshots/@homeYYYYMMDD
sync
umount /mnt
exit (out of root)
exit (out of Konsole)
You are done. Nothing could be easier. Stop trying to be fancy and messing up the install. You are not ready to install Btrfs with a full working desktop on a hard drive without using a LiveUSB installer. And, quite frankly, I've been using Linux for 20 years and programming for 40 years, and I won't even attempt to do that.

[gnomek]

Ok. I will do a clean install. Thank you.

update:
I figured out what is going on.

this is very helpful command that shows errors:

journalctl -b -p 3

I use it with send to txt option because I don't know how to make Terminal show full lines. So it is:

journalctl -b -p 3 >01.txt

In my case the problem was that I used to have encrypted disk and system was looking for it in /etc/crypttab.
The temporary workaround is to # whatever is there. This file contain entry similar to those you can find in fstab.
Some people advice to add noauto to this disk entry but it didn't work for me. Now instaed of

systemd-analyze
Startup finished in 2.930s (kernel) + 3min 585ms (userspace) = 3min 3.515s

I have

systemd-analyze 
Startup finished in 1.225s (kernel) + 20.912s (userspace) = 22.137s

What a difference!