Is the new Ubuntu Mate install ok? (issues during install, though finally seems ok)

Support & Help Requests
#1

I was installing Ubuntu Mate 22.04.2 in dual boot with WIndows 10 on 16GB RAM+AMD 3 4 core.

I made a bootable USB stick on another Ubuntu Mate 20.04 with

sudo dd bs=4M if=/Downloads/ubuntu-mate-22.04.2-desktop-amd64.iso of=/dev/sdb status=progress && sync

Then per Freecodecamp [1] dual boot tutorial, I clicked in Windows Power < Restart + Shift to boot from USB. Before that I inserted the bootable USB in active Windows and it showed errors on USB. I closed all error windows and booted from USB to install Ubuntu.
It proceeded until I needed to define Ubuntu username and password, than the installation was interrupted with error messages related to ~faulty hard drives. But what's unusual, is that
prior to this the Ubuntu installer didn't provide an option to choose the partition to install Ubuntu. I could choose the partition only by choosing "Something else", but during "Normal install" ("Install Ubuntu alongside Windows boot manager) the installer seemed to choose the right partition by itself.

So I checked this USB stick on another laptop with Ubuntu Mate 20.04, and fdisk -l showed 2 "WIndows data" partitions on it. So Windows basically corrupted my bootable USB.
I tried to check the USB stick via badblocks -n or -w, but in every case it reported that it can't be done, because the media is in use by the system. I used this USB stick only to install Ubuntu Mate previously and didn't write on it frequently. It should be ok, so I didn't check it further and repeated the USB bootable creation with the command above, only without bs=4M so it was slower, but may be more reliable.

So I booted in BIOS Boot menu, inserted the newly created bootable USB with Ubuntu, chose "Boot from USB". There was a very brief error looking message on black screen before installation started, so I couldn't read it. The installation proceeded as before, and instead "Install Ubuntu alongside Windows" option there was "Erase Ubuntu and reinstall it" (as there were some Ubuntu files left from previous attempt). And the installer again didn't provide the option to choose the partition to install on. But it chose the right one. So in the end I installed Ubuntu Mate 22.04 successfully (there was some brief message again on the black screen).

I navigated in the home directory, made some theme customizations etc, checked some Office, media apps. The new install seems ok. It boots in dual boot menu to choose Ubuntu or WIndows. But I'm still worried whether it is correct, given the abovementioned issues during the installation. I could have written the USB bootable Ubuntu installer on a newer USB stick with larger capacity.

How can I check that the new Ubuntu Mate installation is ok?

(hash sum of the installer .iso file is ok)

In both cases of this installation there was no disk encryption option from Ubuntu installer. Is this ok? Should I reinstall Ubuntu Mate 22.04?

[1] How to Dual Boot Windows 10 and Ubuntu – Linux Dual Booting Tutorial

#2

I examined the installation syslog a bit and searched for "error" messages (pasted below).
Ubuntu Mate was supposed to be installed on the partition #5 of /dev/nvme0n1

Mar 14 19:39:48 ubuntu-mate systemd[1]: Started ACPI Events Check.
Mar 14 19:39:48 ubuntu-mate kernel: [ 0.240968] rcu: Hierarchical SRCU implementation.
Mar 14 19:39:48 ubuntu-mate kernel: [ 0.240969] rcu: Max phase no-delay instances is 1000.
Mar 14 19:39:48 ubuntu-mate systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (file watch) being skipped.

Mar 14 19:39:48 ubuntu-mate systemd[1]: Started Trigger anacron every hour.
Mar 14 19:39:48 ubuntu-mate kernel: [ 0.248355] smpboot: Total of 4 processors activated (21558.20 BogoMIPS)
Mar 14 19:39:48 ubuntu-mate kernel: [ 0.249572] devtmpfs: initialized
Mar 14 19:39:48 ubuntu-mate systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (timer based) being skipped.

Mar 14 19:39:56 ubuntu-mate tlp[2247]: Error: tlp.service is not enabled, power saving will not apply on boot.
Mar 14 19:39:56 ubuntu-mate tlp[2247]: >>> Invoke 'systemctl enable tlp.service' to correct this!

Mar 14 19:41:15 ubuntu-mate ubiquity: mount: /tmp/tmp.o5zXrhGCro: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.
Mar 14 19:41:16 ubuntu-mate systemd[1]: tmp-tmp.o5zXrhGCro.mount: Deactivated successfully.
Mar 14 19:41:16 ubuntu-mate systemd[1]: tmp-tmp.o5zXrhGCro.mount: Deactivated successfully.
Mar 14 19:41:16 ubuntu-mate ubiquity: mount: /tmp/tmp.o5zXrhGCro: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
Mar 14 19:41:17 ubuntu-mate ubiquity: mount: /tmp/tmp.S8x6o802Xe: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.
Mar 14 19:41:17 ubuntu-mate systemd[1]: tmp-tmp.S8x6o802Xe.mount: Deactivated successfully.
Mar 14 19:41:17 ubuntu-mate ubiquity: mount: /tmp/tmp.S8x6o802Xe: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
Mar 14 19:41:17 ubuntu-mate ubiquity: mount: /tmp/tmp.c2AC4oqGOz: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.
Mar 14 19:41:18 ubuntu-mate systemd[1]: tmp-tmp.S8x6o802Xe.mount: Deactivated successfully.
Mar 14 19:41:18 ubuntu-mate systemd[1]: tmp-tmp.c2AC4oqGOz.mount: Deactivated successfully.
Mar 14 19:41:18 ubuntu-mate ubiquity: mount: /tmp/tmp.c2AC4oqGOz: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
Mar 14 19:41:18 ubuntu-mate ubiquity: mount: /tmp/tmp.kKYxd6gzhn: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.
Mar 14 19:41:19 ubuntu-mate systemd[1]: tmp-tmp.c2AC4oqGOz.mount: Deactivated successfully.
Mar 14 19:41:19 ubuntu-mate ubiquity: mount: /tmp/tmp.kKYxd6gzhn: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
Mar 14 19:41:19 ubuntu-mate systemd[1]: tmp-tmp.kKYxd6gzhn.mount: Deactivated successfully.
Mar 14 19:41:19 ubuntu-mate kernel: [ 105.162687] nvme0n1: p1 p2 p3 p4 p5
Mar 14 19:41:19 ubuntu-mate ubiquity: mount: /tmp/tmp.NSf8U3xaH8: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.
Mar 14 19:41:19 ubuntu-mate systemd-udevd[5247]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
Mar 14 19:41:19 ubuntu-mate systemd-udevd[5158]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1.
Mar 14 19:41:19 ubuntu-mate systemd-udevd[6309]: nvme0n1p5: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p5' failed with exit code 1.
Mar 14 19:41:19 ubuntu-mate systemd-udevd[5245]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
Mar 14 19:41:19 ubuntu-mate systemd-udevd[5249]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
Mar 14 19:41:20 ubuntu-mate systemd[1]: tmp-tmp.NSf8U3xaH8.mount: Deactivated successfully.
Mar 14 19:41:20 ubuntu-mate ubiquity: mount: /tmp/tmp.NSf8U3xaH8: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
Mar 14 19:41:20 ubuntu-mate systemd[1]: tmp-tmp.NSf8U3xaH8.mount: Deactivated successfully.
Mar 14 19:41:20 ubuntu-mate ubiquity: mount: /tmp/tmp.Doe5RCFKX5: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.
Mar 14 19:41:21 ubuntu-mate systemd[1]: tmp-tmp.Doe5RCFKX5.mount: Deactivated successfully.
Mar 14 19:41:21 ubuntu-mate ubiquity: mount: /tmp/tmp.Doe5RCFKX5: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
Mar 14 19:41:21 ubuntu-mate systemd[1]: tmp-tmp.Doe5RCFKX5.mount: Deactivated successfully

Mar 14 19:52:13 ubuntu-mate ubiquity: py_compile.py: error: the following arguments are required: filenames
Mar 14 19:52:13 ubuntu-mate plugininstall.py: log-output -t ubiquity chroot /target python3.10 /usr/lib/python3.10/py_compile.py
Mar 14 19:52:13 ubuntu-mate ubiquity: usage: py_compile.py [-h] [-q] filenames [filenames ...]
Mar 14 19:52:13 ubuntu-mate ubiquity: py_compile.py: error: the following arguments are required: filenames
Mar 14 19:52:13 ubuntu-mate plugininstall.py: log-output -t ubiquity chroot /target python3.10 /usr/lib/python3.10/py_compile.py

Mar 14 19:52:14 ubuntu-mate ubiquity: /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
Mar 14 19:52:14 ubuntu-mate ubiquity: raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \

Mar 14 19:53:13 ubuntu-mate grub-installer: Installation finished. No error reported.
Mar 14 19:53:13 ubuntu-mate grub-installer: info: grub-install ran successfully

Mar 14 19:53:40 ubuntu-mate ubiquity: update-initramfs: Generating /boot/initrd.img-5.19.0-32-generic#015
Mar 14 19:53:47 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu#015
Mar 14 19:53:47 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu#015
Mar 14 19:53:47 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu#015
Mar 14 19:53:47 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu#015
Mar 14 19:53:47 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_imu.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_rlc.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mec.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_me.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_pfp.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_1.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes1.bin for module amdgpu#015
Mar 14 19:53:48 ubuntu-mate ubiquity: W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes.bin for module amdgpu#015