On 2020-08-23 11:32, Ralph Corderoy wrote:
Hi Tim,
> 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
I had a look at the above on my system and I found this
Maximum mount count: -1
For what filesystem?
So is that saying it is going to do a fsck every boot
No, it is disabling the ‘check every N mounts’.
But a check also occurs due to ‘Check interval’ above. See
tune2fs(8)'s
options: -l -c -C -i -T.
and should I adjust it to say check after 20 mounts (is there ideal
figure?)
It depends how often the filesystem is mounted. If it's mounted once a
day then seven could be a good number. Once a year, then it should be
one. That's why ‘Check interval’ was added.
The only thing I see that mentions fsck and my partitions is below but
no mention of sda1:
systemd-fsck[745]: /dev/sda2: clean, 254588/5185536 files,
7727002/20719616 blocks
systemd[1]: Finished File System Check on
/dev/disk/by-uuid/75b45da2-86b3-4574-96d8-3de84f1c4c49.
systemd[1]: Mounting /home...
kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode.
Opts: (null)
systemd[1]: Mounted /home.
systemd-fsck[682]: /dev/sdb1: clean, 609505/61054976 files,
11916348/244190208 blocks
systemd[1]: Finished File System Check on
/dev/disk/by-uuid/04d578e3-78a4-474a-bac5-d048e001f565.
Perhaps sda1 isn't being checked at all and not one of those
contributing to the few-second delay.
Does a proper shutdown always occur? Booting from other media and
inspecting the filesystems should show ‘clean’, as above.
Also, the distro's boot method will probably have some means of
ditching
the GUI logo, letting you observe logging as it happens.
--
Cheers, Ralph.
Just a quick update on this issue.
Yesterday I was having issues booting with the laptop not booting
completely. Logged on with a USB boot image, removed the external USB
disk from fstab (mounted as my backup drive sdb1). The laptop booted, I
ran a fsck on the ext USB hard disk and it was a mess, error upon error.
It was only at the start of August that I formatted the drive and ran
smart on it and it reported as alright no issues found.
Strange thing was when I booted the laptop up after removing the entry
in my fstab file it booted up without the File Check in progress
message. So why was the file check saying that sda2 was clean when
obviously it was sdb1 that had the issues, there nothing in any of the
logs to suggest there was anything untoward with sdb1. For reference
sdb1 was a 2.5" spinney disk??
Fitted a new ext USB SDD drive and everything seems to be OK
Tim H
--
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
