How can I make ubuntu start faster

First, let's check your file system(s).

  • boot to a Ubuntu Live DVD/USB in “Try Ubuntu” mode
  • open a terminal window by pressing Ctrl+Alt+T
  • type sudo fdisk -l
  • identify the /dev/sdXX device name for your "Linux Filesystem"
  • type sudo fsck -f /dev/sda3, replacing sdXX with the number you found earlier
  • type sudo fsck -f /dev/sda1, replacing sdXX with the number you found earlier
  • repeat the fsck command if there were errors
  • type reboot

Review

Show me cat /etc/fstab and sudo blkid and sudo fdisk -l, and screenshots of the Disks app SMART Data & Tests data window (resize this window to capture all of the data).

I've reviewed the above, but didn't get the requested SMART data screenshot.

Note: If I can get the SMART data, I may make further recommendations.

Note: There is no SSD on this system.

There are a number of things wrong. The following excerpts and comments will detail the problems.


RAM

model name  : AMD A8-5500 APU with Radeon(tm) HD Graphics
12 GB ram

AMD Processors are very fussy about RAM.

With 12G RAM, you must have 8G and 4G DIMMS, so your system cannot take speed advantage of having equal size/spec DIMMS, and memory interleaving is not being used.

Go to https://www.memtest86.com/ and download/run their free memtest to test your memory. Get at least one complete pass of all the 4/4 tests to confirm good memory. This may take a few hours to complete.


/etc/fstab

# /boot was on /dev/sda1 during installation
UUID=5dff6fb3-361f-4666-9462-45f78a65ab47 /boot           ext4    defaults        0       2

You'll notice this same UUID in the systemd-analyze command output.

This should be:

# /boot was on /dev/sda1 during installation
UUID=5dff6fb3-361f-4666-9462-45f78a65ab47 /boot           vfat    defaults        0       1

ext4 should be vfat. The fsck test should be 1, not 2.

But you can't just change this in fstab. More detail in a moment.


fdisk -l (skipping /dev/loop1 ... /dev/loop30)

Each SNAP application slows down the boot. Remove SNAP apps as possible, and change to regular .deb/repo apps to speed things up.

Disketikettstyp: dos

If you've got a UEFI computer, then dos should be GPT partition table.

Enhet      Start   Början    Slutet  Sektorer Storlek Id Typ
/dev/sda1  *         2048   1953791   1951744    953M 83 Linux

Poster i partitionstabell är inte i diskordning

Same partition that I mention earlier, and it's not in the correct partition order. This effects boot time also.

Summary

  • Backup your important data
  • Lay down a fresh GPT partition table (this WILL wipe the disk), using gparted
  • Clean install Ubuntu
  • Accept the installer's default partition plan
  • Reinstall apps and data. Better to not use SNAP apps if possible.
  • If possible, change 4G DIMM to a matching 8G DIMM

Mounting the disk is taking ridiculous time.

Check:

  • Time system clock is correct (i.e. not far in the past or the future, and your RTC battery is working)
  • Check logs (e.g. dmesg, /var/log/kern.log, /var/log/syslog) for errors in /dev/sda. Your disk may be dying, or the cable could be loose.
  • Run sudo tune2fs -l /dev/sda3 (and for all partitions) and check for 'Maximum mount count:' (run fsck every N mounts) and 'Check interval:' (run fsck after N days since last check). Your partition may be misconfigured to run fsck on every boot. You can tweak those values with tune2fs
  • Run a full fsck scan (alternate guide)

Maybe your disk could just do some service by getting a full wipe (if it's an SSD). Some SSDs get really bad after enough write cycles and TRIM maintenance isn't enough (or the TRIM itself takes too long).

But as Matthias Lenmher said, without specs it's hard to figure out more.

Update

I saw you posted HDD info. According to the internet the WD3200BEVT is a laptop regular hdd disk. Your disk could just be too fragmented and/or you have a lot of bloat. The best course of action is to just do a full format and reinstall (or replace it with an SSD...)

But to be on the safe side, post the full output of sudo smartctl -a /dev/sda. It's far too common for laptop HDDs to receive impacts and have lots of startup errors or read/write errors.