Dual Boot – GRUB2 does not show Windows 10 as the third operating system on my PC after installing Ubuntu 19.10, under Windows 10 and Ubuntu 18.04

I had a perfectly functioning dual boot, but last week I connected a 250 GB SSD to install Ubuntu 19.10 under (under the existing installations of Windows 10 (128 GB SSD) and Ubuntu 18.04 (800 GB)). Unfortunately, it was not as easy as expected. The problem is as follows.

When I start my system, I can only choose between Ubuntu 18.04 and my new Ubuntu 19.10, but the GRUB2 boot loader does not find a window. To solve the problem, I ran the boot repair tool on my new system, which gave me the following dump:

https://paste.ubuntu.com/p/8r4rpB5SVv/

If I concentrate on the repair suggested by the boot repair, I would have to create an unformatted file system with> 1 MB and the flag bios_grub. However, this also gives me two problems. Assuming that it is desirable that I created this partition on my new drive, I cannot customize the partitions on this active operating system (obviously … I suppose). The second problem is that I cannot label a raw file system. The program does not allow me to manage these flags.

If information is missing, please let me know and I will update my post.

I hope someone can help me with this problem.

Thanks a lot!

The Ubuntu 19.10 zunt pool is not automatically provided after the restart

Foreword – I looked for previous solutions without success and tried them out.

I have created a zfs raidz1 pool naszfs with 3 external Sata drives. The drives are connected via USB via the following housing: https://www.amazon.co.uk/gp/product/B07449Q74W

The pool works fine and I can use it. Every time I restart, I have to import the zfs pool again sudo zpool import -a

I am relatively new to Linux. I may have accidentally done something to cause this. The only changes I remember were to change the mount point a couple of times sudo zfs set mountpoint=/my/new/mountpoints naszfs, I then returned to the original mount point from /naszfs,

I tried to edit them /etc/default/zfs File unsuccessful. Or is it because I'm using external drives?

Partitioning – Mount a previous MDADM RAID1 partition to back up data – Ubuntu 19.10

Tomorrow, team!

After a crash, mdadm lost RAID 1 and has to save the sdc3 partition on another hard drive. What should be the right steps to make it pain free? RAID 1 is no longer used on this new Ubuntu 19.10 as shown below (mdadm is of course installed):

User @: ~ $ cat / proc / mdstat
Personalities: (linear) (multipath) (raid0) (raid1) (raid6) (raid5) (raid4) (raid10)
md127: inactive sdc30
937567232 blocks Super 1.2

User @: ~ $ sudo mdadm –assemble –scan
mdadm: No arrays found in the configuration file or automatically

User @: ~ $ sudo mdadm –examine / dev / sdc
/ dev / sdc:
MBR Magic: aa55
Partition (0): 62500000 sectors at 2048 (type 83)
Partition (1): 15624192 sectors at 1937899520 (type fd)
Partition (2): 1875396608 sectors at 62502912 (type fd)

User @: ~ $ sudo fdisk -l / dev / sdc
Disco / dev / sdc: 931.53 GiB, 1000204886016 bytes, 1953525168 Setores
Hard drive model: SAMSUNG HD103SJ
Unidades: setor de 1 * 512 = 512 bytes
Tamanho de Setzer (lógico / físico): 512 bytes / 512 bytes
Tamanho E / S (Mínimo / Otimo): 512 bytes / 512 bytes
Disco tip: dos
Disco identifier: 0x0004af66

Dispositivo Inicializar Início Fim Setores Tamanho Id Tipo
/ dev / sdc1 2048 62502047 62500000 29.8G 83 Linux
/ dev / sdc2 1937899520 1953523711 15624192 7.5G fd Linux RAID a
/ dev / sdc3 62502912 1937899519 1875396608 894.3G fd Linux RAID a

Partições lógicas fora da ordem do disco

Tried to mount, but partition is busy:

User @: ~ $ sudo mdadm –assemble / dev / md127 –update = uuid / dev / sdc3
mdadm: / dev / sdc3 is busy – skips

Any help is appreciated! Thank you in advance!

The recommended nvidia-driver-390 cannot be installed in 19.10

I'm having trouble logging into 19.10 and following some suggestions (e.g. Ubuntu 18-04 login loop with missing xauthority file). ubuntu-drivers devices Displays nvidia-driver-390 as the recommended driver

If I sudo apt install_nvidia-driver-390 it fails
Enter image description here

And try it sudo apt --fix-broken_install fails Enter image description here

How can I have it sorted? Thank you very much.

Sound – Kubuntu 19.10 The settings for multi-monitor and audio hardware (profiles) do not seem to be permanent

Hardware Info:
Kubuntu 19.10+ supports PPA as an all-in-one PC
inxi edition
https://pastebin.com/VR7qKU2w

I found two very annoying problems.

Problem # 1

Audio profiles are not saved
I switched the profile in the Audio Hardware-> Additional tab to digital stereo output (HDMI x) and saved it so that all the sound came from the TV.

After I have switched off my PC and then restarted, the profile is changed to Analog Stereo Output (the built-in audio system of my PC).

Why does that happen? How can I avoid this?

Problem # 2

I have a problem with setting up multiple monitors. My projector is connected to my PC via a VGA connection.

What happens:

1) I start my PC
2) Turn on my projector
3) Kubuntu is loading.
4) For example, when I click on Dolphin or System Preferences, they all open on the second screen, not the main screen.

I need to move my mouse over my main desktop and drag everything to the main display.

Display settings:

Display 0 (the main one) –

  • activated
  • Set as the head
  • The synchronization is deactivated

Display 1 (projector)

-aktiviert
-sync disabled
– Not the main

In the image above display settings, two displays touch. I tried to break them apart but it caused another problem. If they are separated and I open Dolphin or whatever, it will be partially visible on both displays.

I have found a temporary solution to this.

I used xrandr sh script and added it to autostart …

What I don't understand is why I'm forced to use this workaround … It should work right away.

Is there any way to do this through Kubuntu settings?

Sincerely yours.

Windows subsystem for Linux – upgrade from 19.04 to 19.10 fails under WSL

I have a 19.04 installation under Windows Subsystem for Linux. When I try to upgrade to 19.10, the following happens:

$ sudo do-release-upgrade
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife

Get:1 Upgrade tool signature (1554 B)
Get:2 Upgrade tool (1329 kB)
Fetched 1331 kB in 0s (0 B/s)
authenticate 'eoan.tar.gz' against 'eoan.tar.gz.gpg'
extracting 'eoan.tar.gz'

Reading cache
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://archive.ubuntu.com/ubuntu disco InRelease
Get:1 http://archive.ubuntu.com/ubuntu disco-updates InRelease (97.5 kB)
Get:2 http://archive.ubuntu.com/ubuntu disco-backports InRelease (88.8 kB)
Get:3 http://security.ubuntu.com/ubuntu disco-security InRelease (97.5 kB)
Fetched 284 kB in 6s (45.8 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done

Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
=== Command detached from window (Wed Feb  5 12:39:40 2020) ===
=== Command terminated with exit status 1 (Wed Feb  5 12:39:50 2020) ===

Apparently the upgrade script wants to examine the PCI bus for some reason, which fails under WSL.

Touchpad does not work with Lenovo thinkbook 14 with Ubuntu 19.10

Hey, the touchpad on my Lenovo Thinkbook 14 does not work on Ubuntu 19.10 or Linux Mint. However, it works on Windows. I tried the suggested solutions here and elsewhere. It seems that the touchpad is not recognized at all.

Is there an easy way to fix this?

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=062a Product=4101 Version=0110
N: Name="MOSART Semi. 2.4G Keyboard Mouse"
P: Phys=usb-0000:00:14.0-4/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.0/0003:062A:4101.0004/input/input9
U: Uniq=
H: Handlers=sysrq kbd event8 leds 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=062a Product=4101 Version=0110
N: Name="MOSART Semi. 2.4G Keyboard Mouse"
P: Phys=usb-0000:00:14.0-4/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:062A:4101.0005/input/input10
U: Uniq=
H: Handlers=mouse1 event9 
B: PROP=0
B: EV=17
B: KEY=1f0000 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0003 Vendor=062a Product=4101 Version=0110
N: Name="MOSART Semi. 2.4G Keyboard Mouse Consumer Control"
P: Phys=usb-0000:00:14.0-4/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:062A:4101.0005/input/input11
U: Uniq=
H: Handlers=kbd event10 
B: PROP=0
B: EV=1f
B: KEY=3f000301ff 0 0 483ffff17aff32d bfd4444600000000 1 130ff38b17c000 677bfad9415fed 19ed68000004400 10000002
B: REL=1040
B: ABS=100000000
B: MSC=10

I: Bus=0003 Vendor=062a Product=4101 Version=0110
N: Name="MOSART Semi. 2.4G Keyboard Mouse System Control"
P: Phys=usb-0000:00:14.0-4/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:062A:4101.0005/input/input12
U: Uniq=
H: Handlers=kbd event11 
B: PROP=0
B: EV=13
B: KEY=c000 10000000000000 0
B: MSC=10

I: Bus=0003 Vendor=062a Product=4101 Version=0110
N: Name="MOSART Semi. 2.4G Keyboard Mouse"
P: Phys=usb-0000:00:14.0-4/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1/0003:062A:4101.0005/input/input13
U: Uniq=
H: Handlers=event12 
B: PROP=0
B: EV=9
B: ABS=10000000000

I: Bus=0003 Vendor=0e8f Product=00a8 Version=0110
N: Name="DaKai 2.4G RX"
P: Phys=usb-0000:00:14.0-7/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:0E8F:00A8.0006/input/input14
U: Uniq=
H: Handlers=sysrq kbd event13 leds 
B: PROP=0
B: EV=13
B: KEY=c000 10000000000000 0
B: MSC=10

I: Bus=0003 Vendor=0e8f Product=00a8 Version=0110
N: Name="DaKai 2.4G RX Consumer Control"
P: Phys=usb-0000:00:14.0-7/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:0E8F:00A8.0007/input/input17
U: Uniq=
H: Handlers=kbd event16 
B: PROP=0
B: EV=1f
B: KEY=300ff 0 0 483ffff17aff32d bfd4444600000000 1 130c730b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=1040
B: ABS=100000000
B: MSC=10

I: Bus=0003 Vendor=0e8f Product=00a8 Version=0110
N: Name="DaKai 2.4G RX"
P: Phys=usb-0000:00:14.0-7/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:0E8F:00A8.0007/input/input18
U: Uniq=
H: Handlers=event17 
B: PROP=0
B: EV=9
B: ABS=10000000000

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/input/input24
U: Uniq=
H: Handlers=rfkill kbd event5 
B: PROP=0
B: EV=13
B: KEY=81000800100c03 4400000000300000 0 2
B: MSC=10

I: Bus=0003 Vendor=13d3 Product=5415 Version=1906
N: Name="Integrated Camera: Integrated C"
P: Phys=usb-0000:00:14.0-6/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/input/input25
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input26
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input27
U: Uniq=
H: Handlers=event18 
B: PROP=0
B: EV=21
B: SW=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input28
U: Uniq=
H: Handlers=event19 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input29
U: Uniq=
H: Handlers=event20 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input30
U: Uniq=
H: Handlers=event21 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input31
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input31
U: Uniq=
H: Handlers=event22 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input32
U: Uniq=
H: Handlers=event23 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input33
U: Uniq=
H: Handlers=event24 
B: PROP=0
B: EV=21
B: SW=140