How to check that Ubuntu 18.04 is correctly installed.

Do you have enough info to respond or I asking the impossible?

Look forward to hearing from you,  Peter Ratcliffe

On 17/06/2019 16:57, peter ratcliffe wrote:
> New question #681445 on Ubuntu:
> https://answers.launchpad.net/ubuntu/+question/681445
>
> Moved to a new computer not long ago. Somehow it does not feel right. It should have a small SSD for boot and a much larger HDD for data but I can't see the the HDD disc. Most of the data was transfers were done using USB sticks. The computer came with ubuntu 18.04 loaded. Is there any software which will run the rule over my new machine to make sure all is OK. Some files show up twice, but with different start dates.
>
> Many thanks, Peter Ratcliffe
>

What exactly do you think might be wrong?

Is the system booting correctly?
Is the network connection working as expected?
Do package updates correctly run?
Do you see warnings or error messages somewhere?

For some basic diagnostic checks, what is the output of the commands

uname -a
lsb_release -crid
sudo apt update
sudo dpkg --audit
sudo fdisk -l

My computer is not sensing the HDD disc, although the intention was to boot from the ssd to be as fast as possible. Boot woks OK but is not as fast as I hoped.
Network connection as i would expect, with hard connection. Wi-Fi is not connected.
Updates work as far as I can see.
No error messages except for an occasional "can't find this file" or "don't recognize this format.

Outputs are,

Got this far then stopped. Terminal is on and recognizes the command w hen copied from your list but then does nothing with it. running the cursor across your command Shows white rather than red I have seen before.
Any tips? Peter Ratcliffe

What do you want to say with "... does nothing with it …".

Have you tried pressing the right mouse button in the terminal window, and in the small pop-up that you get selecting paste or copy (whatever might be appropriate in that moment)?

When I moved the cursor across a command from you, i e " uname-a " I expected to press the return key and be presented with the command detail. In the event nothing happened. I tried again this morning with this result.

I have no idea what happened yesterday, but hope this is enough info for you to make sense of it.

You guys are brilliant, be lost without you. But do wonder sometimes, when my understanding lets me down, if the community has a facility for one to one verbal help?

Many thanks Manfred from Peter Ratcliffe

petercarey@querky:~$ uname -a
Linux querky 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
petercarey@querky:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
petercarey@querky:~$ sudo apt update
[sudo] password for petercarey:
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:2 http://gb.archive.ubuntu.com/ubuntu bionic InRelease
Get:3 http://gb.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Ign:4 http://ppa.launchpad.net/webupd8team/gnome3/ubuntu bionic InRelease
Err:5 http://ppa.launchpad.net/webupd8team/gnome3/ubuntu bionic Release
  404 Not Found [IP: 91.189.95.83 80]
Get:6 http://gb.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:7 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [17.9 kB]
Get:8 http://security.ubuntu.com/ubuntu bionic-security/main DEP-11 64x64 Icons [25.6 kB]
Get:9 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [36.2 kB]
Get:10 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [16.4 kB]
Get:11 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [104 kB]
Get:12 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2,460 B]
Get:13 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB]
Get:14 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66.7 kB]
Get:15 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [127 kB]
Get:16 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [245 kB]
Get:17 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [197 kB]
Get:18 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [410 kB]
Get:19 http://gb.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2,464 B]
Get:20 http://gb.archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7,224 B]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/webupd8team/gnome3/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
petercarey@querky:~$ sudo dpkg --audit
petercarey@querky:~$ sudo fdisk -l
Disk /dev/loop0: 143.5 MiB, 150470656 bytes, 293888 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: 53.7 MiB, 56315904 bytes, 109992 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/loop2: 13 MiB, 13619200 bytes, 26600 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/loop3: 14.8 MiB, 15458304 bytes, 30192 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/loop4: 3.7 MiB, 3821568 bytes, 7464 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/loop5: 151 MiB, 158363648 bytes, 309304 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/loop6: 1008 KiB, 1032192 bytes, 2016 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/loop7: 89.3 MiB, 93581312 bytes, 182776 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: 223.6 GiB, 240057409536 bytes, 468862128 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: gpt
Disk identifier: 9C55A9FC-5B89-4308-B1A3-EC06CFD186B3

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 468860927 467810304 223.1G Linux filesystem

Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/loop8: 86.9 MiB, 91099136 bytes, 177928 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/loop9: 34.7 MiB, 36323328 bytes, 70944 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/loop10: 4 MiB, 4218880 bytes, 8240 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/loop11: 140.9 MiB, 147722240 bytes, 288520 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/loop12: 35.3 MiB, 37027840 bytes, 72320 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/loop13: 3.7 MiB, 3887104 bytes, 7592 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/loop14: 88.4 MiB, 92733440 bytes, 181120 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/loop15: 14.8 MiB, 15458304 bytes, 30192 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/loop16: 2.3 MiB, 2433024 bytes, 4752 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/loop17: 140.7 MiB, 147496960 bytes, 288080 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/loop18: 53.7 MiB, 56328192 bytes, 110016 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/loop19: 140.7 MiB, 147501056 bytes, 288088 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/loop20: 4 MiB, 4214784 bytes, 8232 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/loop21: 211 MiB, 221298688 bytes, 432224 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/loop22: 209.3 MiB, 219475968 bytes, 428664 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/loop23: 14.5 MiB, 15196160 bytes, 29680 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/loop24: 3.7 MiB, 3846144 bytes, 7512 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/loop25: 1008 KiB, 1032192 bytes, 2016 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
petercarey@querky:~$

What I see:

1. There is an obsolete PPA defined in the list of repository servers, causing this
"E: The repository 'http://ppa.launchpad.net/webupd8team/gnome3/ubuntu bionic Release' does not have a Release file."
error message.

I do not know why this PPA is added, but it does not make any sense on an Ubuntu bionic system and has to be removed.

2. The output shows two hard disks:
Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
with two partitions
 /dev/sda1 2048 1050623 1048576 512M EFI System
 /dev/sda2 1050624 468860927 467810304 223.1G Linux filesystem

and
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
which is unused and unpartitioned.

However long I look at your response I can't understand it. What is a PPA? If it should be removed how do I do that.

The SSP disc should be partitioned to use to boot, and the HDD set up to accept data. How many partitions will it need and how do I get there?

The real question is is this set up OK to use or are there any dangers or problems.

Thank you Manfred, from Peter Ratcliffe

PPA stands for "Personal Package Archive".
PPAs are Software package repositories where people can package additional software, or newer versions of software, such that it can be easily installed with help of the package management tools, just like the software provided in the official Ubuntu repositories.

Apparently you tried to add the webupd8team/gnome3 PPA (https://launchpad.net/~webupd8team/+archive/ubuntu/gnome3 )at a certain moment in time.
If you didn't do this, then I do not know why it is activated on your system at all.

You wrote:
"The computer came with ubuntu 18.04 loaded"
If the computer was already pre-configured, why is there an unused and unpartitioned hard disk in it?
Why is an obsolete PPA activated?
This is something which I do not understand.

Difficult for me to comment on your last post. My new computer was ordered with, and as far as I know supplied with, UBUNTU 18.04. I have added data but that is all. I did try to use the gnome tool but without success. I have no idea why or how this PPA got involved: can I delete it and if so, how. What I really want to know is is this computer safe to use as it is?

I asked "activities, disc" what is there and it lists

240 GB Disc ADATA SU650 with 2 partitions

1.0 TB Hard Disk ST1000DM010-2EP102 With no partitions. How many and how big should I have to hold all data. Tips on how to do it please.

62 GB Drive which is a memory stick to hold backup.

I should add that there was a hick up with delivery so it is possible something got missed.

Thanks again from Peter Ratcliffe

"I did try to use the gnome tool but without success."
Which gnome tool? For what purpose? Why no success, what happened?

For removing the webupd8team/gnome3 PPA please provide the output that you receive for the command
grep -i webupd8team /etc/apt/sources.list /etc/apt/sources.list.d/*.list

Without further information it is not possible to recommend a disk layout for the 1 TB hard disk.
What do you want to store on your computer? Is this computer used only by one person, or by several users? If there are more users, are all data "private" to the user who created them, or is there the need for a "shared" area with access for everybody where a lot of data are to be stored? How much data do you expect to have in total?

You have to be aware that decisions on partitioning should be done before installing Ubuntu, such that during the first installation the partitions can already be allocated as desired. Changing this afterwards is always more complicated.

I tried to use GNOME Tweak Tool to change some preferences but found the options confusing. There is a big change between Ubuntu 16 and Ubuntu 18 and I really haven't got to grips with it yet, so all is trial and error.

The output of your command is

petercarey@querky:~$ grep -i webupd8team /etc/apt/sources.list /etc/apt/sources.list.d/*.list
/etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.list:deb http://ppa.launchpad.net/webupd8team/gnome3/ubuntu bionic main
/etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.list:# deb-src http://ppa.launchpad.net/webupd8team/gnome3/ubuntu bionic main
petercarey@querky:~$

This computer will be used by myself and my wife for domestic things like letters and lists and keeping track of money. In my case what I spend and what I have left. Carey has internet banking but not me. We have separate accounts but no secrets. There will be other things to save such as photos and data we need to keep but it won't amount to much. As for initial partitions I guess they are as the dealer entered.

Thanks for your help, Peter Ratcliffe.

1. To repair the cause for the error messages when running package updates executed the command
sudo rm /etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.list

2. If you do not plan to store lots of big data files (e.g. videos) on your hard disk, then I would like to recommend leaving the disks as they are. The SSD disk has enough space available, that I doubt that you ever will fill it more than small percentage.

What is the output of the command

df -h | grep -v Loop

3. Please use correct version names/numbers. There is neither an "Ubuntu 16", nor an "Ubuntu 18". I assume you were referring to the Ubuntu Releases 16.04 and 18.04, see also https://ubuntu.com/about/release-cycle

Opps. sorry, wrong autocorrection; the command should have been

df -h | grep -v loop

2. Output of your command is

petercarey@querky:~$ df -h | grep -v loop
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 791M 1.8M 789M 1% /run
/dev/sda2 219G 11G 197G 6% /
tmpfs 3.9G 28M 3.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda1 511M 6.1M 505M 2% /boot/efi
tmpfs 791M 36K 791M 1% /run/user/1000
/dev/sdc1 58G 238M 58G 1% /media/petercarey/4FA3-845B
petercarey@querky:~$

3. You are quite right; I was being economical with typing.

1. Do you want me to activate this command or is it just for information of what has already been done.

Thanks for your patience, Peter Ratcliffe

ad 1.
To get rid of the error message "E: The repository ... does not have a Release file" you have to delete the obsolete configuration file, i.e. you have to execute the following command once:

sudo rm /etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.list

ad 2.
"Filesystem Size Used Avail Use% Mounted on
/dev/sda2 219G 11G 197G 6% /"

Your current setup is that all Ubuntu data are stored on the SSD. The data partition is 219 GiB, and currenly only 11 GiB (=6%) are occupied, leaving 197 GiB free space. I beleive that even without adding the 1 TB hard disk you will not run out of space. Taking into account the effort and risks involved with restructuring your partitioning structure, I would like to recommend leaving it as it is, with an unused and idle 1 TB hard disk.

(Remark: the used plus free numbers do not match with the total size, because Linux systems reserve about 5% for special use.)

ad 1.

Activating your command resulted in petercarey@querky:~$ sudo rm /etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.listexit
[sudo] password for petercarey:
rm: cannot remove '/etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.listexit': No such file or directory
petercarey@querky:~$

Is this the end of the road for this question. If so, thanks for your help from Peter Ratcliffe

Where does the "exit" at the end come from?

My advice was the command
sudo rm /etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.list
and not
sudo rm /etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.listexit

What messages do you now receive for the command
sudo apt update

Tried to run your command again, and got

$ sudo rm /etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.list sudo rm /etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.list
[sudo] password for petercarey:
Sorry, try again.
[sudo] password for petercarey:
rm: cannot remove 'sudo': No such file or directory
rm: cannot remove 'rm': No such file or directory
rm: cannot remove '/etc/apt/sources.list.d/webupd8team-ubuntu-gnome3-bionic.list': No such file or directory
petercarey@querky:~$

not what I expected. Had to run t twice but don't know why.
Long time ago I was advised to use the command "exit" to leave terminal, No idea where it came from here.

sudo apt update gives
$ sudo apt update
[sudo] password for petercarey:
Hit:1 http://gb.archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://gb.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://gb.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
43 packages can be upgraded. Run 'apt list --upgradable' to see them.
petercarey@querky:~$

Over to yo sir, from Peter Ratcliffe

Thanks Manfred Hampl, that solved my question.