Hi Tim,
> SDA1 mounted as / and formatted to ext4 (45gb)
> sda2 > mounted as /home (79gb)and formatted to ext4
> a Swap partition (10gb)
> and around 88gb of free unpartitioned space.
>
> sdb1 which is an external USB 1TB drive (2.5 spinney type)
...
> With in 2 or 3 seconds of the screen appearing the screen goes
> blank and then display a message about sda1 being clean.
So boot is only delayed for those 2-3 seconds?
> Now I fully understand the principle of the disk check and a disk
> check will runs when a marker has been set on the superblock to
> suggest that there is an issue with the file system and when you force
> a disk check. What I can not understand is why is it happening.
I think your full understanding may be lacking things like mount counts?
:-) See tune2fs(8)'s options: -l -c -C -i -T.
Here's some example output, with interesting lines kept, but it's worth
skimming all the output.
$ sudo -i tune2fs -l /dev/sda1
tune2fs 1.45.2 (27-May-2019)
...
Filesystem state: clean
...
Mount count: 1
Maximum mount count: 1
Last checked: Sun Feb 16 10:03:21 2020
Check interval: 604800 (1 week)
Next check after: Sun Feb 23 10:03:21 2020
Perhaps examining/altering those will help explain what's happening,
e.g. is an fsck occurring and on what filesystems.
I'd also look for ‘fsck’ in the output of ‘sudo -i journalctl -b’.
--
Cheers, Ralph.
--
Next meeting: Online, Jitsi, Tuesday, 2020-09-01 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
