[Dorset] Laptop running fsck at every start

2020-08-20 Thread zircon 

Hi Guys

I have a new install of Xubuntu 20:04 on my Lenovo laptop. Xubuntu is 
installed on a brand new Kingston SSD. The SSD is shown as SDA and has 
three partition 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.


There is an sdb1 which is an external USB 1TB drive (2.5 spinney type) 
which mounts via fstab on /media/backup


Now the problem, when the laptop starts up it comes up with a black 
screen with the word xubuntu & the logo on the page with a progress bar 
underneath wording, it starts before the word Xubuntu and ends beyond 
the Xubuntu logo (so it looks like it has fully completed. At the bottom 
of the screen it say Press Ctrl+C to cancel all files ystem checks in 
progress. With in 2 or 3 seconds of the screen appearing the screen goes 
blank and then display a message about sda1 being clean.


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.


To date I have checked Smartd on the ssd which has come back with out an 
issue, the disk and partitions were written several times (along with 
installation) when I set the laptop up as I had a seperate issue which 
turned out to be an issue with the external USB drive. I have booted 
from a live USB stick and run fsck and e2fsck on the sda1 and sda2 with 
no errors found. I have checked the journaled log and nothing is showing 
in there.


The shutdown of the laptop seem to be normal, it does not hang or 
dispaly any errors.
So anybody got any suggestions, is there anything I can setup to run 
which will monitor the shutdown process for reviewing at the next 
reboot.



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

Re: [Dorset] Slow computer

2020-08-20 Thread PeterMerchant 

On 20/08/2020 09:36, Ralph Corderoy wrote:

Hi Peter,


$ systemd-analyze blame

Please provide the output of

 systemd-analyze time
 systemd-analyze critical-chain


peterm@peterm-MBB-34204H:~$ systemd-analyze time

Startup finished in 3.412s (kernel) + 54.628s (userspace) = 58.041s
graphical.target reached after 54.613s in userspace

peterm@peterm-MBB-34204H:~$  systemd-analyze critical-chain

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @54.613s
└─multi-user.target @54.613s
  └─mpd.service @32.239s +22.372s
    └─network.target @32.109s
  └─NetworkManager.service @21.848s +10.260s
    └─dbus.service @21.845s
  └─basic.target @21.751s
    └─sockets.target @21.751s
  └─snapd.socket @21.750s +1ms
    └─sysinit.target @21.523s
  └─cryptsetup.target @21.516s
    └─systemd-ask-password-wall.path @3.329s
  └─-.mount @3.314s
    └─system.slice @3.314s
  └─-.slice @3.314s
peterm@peterm-MBB-34204H:~$



--
 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

Re: [Dorset] Slow computer

2020-08-20 Thread Ralph Corderoy 
Hi Peter,

> $ systemd-analyze blame

Please provide the output of

systemd-analyze time
systemd-analyze critical-chain

-- 
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