Dual/Multi boot from persistant USB

https://askubuntu.com/questions/1563749/dual-multi-boot-from-persistant-usb

I recently followed a guide on here that allowed me to install Ubuntu 24.04 lts on USB that was compatible with BIOS and UEFI. I have tested in on all of my computers and they all work great so far, except for my ARM based one, which of course won't work with this version of Ubuntu. I think it would be cool to also put windows 7 or 10 or something on a partition, but this may be beyond the scope of this project for me.

My question is, without ruining my partitions, how can I add other OS's to my USB stick that wont ruin my so far ultra compatible Ubuntu USB installation. I attached a link to the forum post on here that walked me through the first installation, as well as another post from the same user who detailed an older method for multiboot installation (see bottom of that post), but I think it may be out of date.

Current single boot method

Older multiboot method

Edit:

Thank you to karel for responding, basically I had to to set up my paritions in a very specific way according to those post to allow for booting with BIOS and UEFI. I am aware of tools to create multiboot usb drives, but if I use that tool will it ruin the way I had to set up my USB to be compatible with BIOS and UEFI? Should I resize my ext4 to unformated space and then use the multi boot tool on that space? Sorry, I am relatively new to live usbs and this project may be a bit advanced for me.

Ubuntu's "Kernel release schedule" suggests that Ubuntu 24.04.3 has no supported kernel

https://askubuntu.com/questions/1563748/ubuntus-kernel-release-schedule-suggests-that-ubuntu-24-04-3-has-no-supported

The page https://ubuntu.com/kernel/lifecycle mentions only kernel version 6.14 near Ubuntu version 24.04.3 and it says that the standard security maintenance for kernel 6.14 ended in January 2026. For kernel version 6.8, the standard security maintenance is still active. However, according to the aforementioned page, kernel version 6.8 only corresponds to Ubuntu versions 24.04.[0 or 1] and 22.04.5:

This might be interpreted in the way that Ubuntu version 24.04.3 is not supported anymore at all (which would be very surprising according to this answer).

So does it mean that the kernel version 6.8 is still supported for any installation of Ubuntu version 24.04 (and the "24.04.[0 or 1]" just means that 6.8 was released when there was no 24.04.2 yet)?

And kernel version 6.17 is not supported for any installation of Ubuntu 24.04, but only starting from 25.10?

WSL /dev/console, /dev/ttyN, /dev/vcsN and /dev/hvc0

https://askubuntu.com/questions/1563747/wsl-dev-console-dev-ttyn-dev-vcsn-and-dev-hvc0

In WSL, writing to /dev/console goes nowhere apparent. What happens to things written there? This question is generally to clarify the role of virtual consoles in WSL and hvc0.

A 2010 post with no responses asks

I would like to get some information regrading the hvc0 terminal. A search on the web hasn't came with useful stuff.

And it is thinly discussed in any StackExchange questions; one of the only is https://unix.stackexchange.com/questions/10857/what-is-hvc0-appearing-in-who-list

In Ubuntu running on Virtualbox,

virtualbox$ cat /proc/consoles
tty0                 -WU (EC  p  )    4:3
virtualbox$ echo hello | sudo dd of=/dev/console status=none
hello                                                                                                                                           virtualbox$ echo hello | sudo dd of=/dev/tty0 status=none
hello
virtualbox$ tty
/dev/tty3
virtualbox$ fgconsole
3
virtualbox$ cat /sys/class/tty/tty0/active
tty3                                                                                                                                               virtualbox$ echo hello | dd of=/dev/tty3 status=none
hello
virtualbox$ sudo cat /dev/vcs3 > out

The above session typescript is made with the last command in it.

In WSL, writing to /dev/console goes nowhere apparent. If the answer is to run strace, like

echo hello | sudo strace dd of=/dev/console

where is the "interesting" part of the output, which is a bunch of UTF stuff, mmap, fstat, open and close.

There is no /dev/tty0 or /dev/vcs0, but instead /dev/hvc0.

wsl$ cat /proc/consoles
hvc0                 -W- (EC p  )  229:0

In WSL, despite not being able to access virtual consoles like in usual Linux, we can write and read to them:

wsl$ echo hello | sudo dd of=/dev/tty1 status=none
wsl$ sudo cat /dev/vcs1

Ubuntu 24.04.3 LTS laptop tty1                                                                                                                                  laptop login: hello

The following seems to mean that tty1 is "populated" with a login screen (by systemd getty?), that is we can see the login by reading /dev/vcs1 but we see nothing reading /dev/vcs2.

wsl$ cat /sys/class/tty/tty0/active
tty1
wsl$ fgconsole
Couldn't get a file descriptor referring to the console.

However we can indeed write to /dev/tty2 and then read from /dev/vcs2:

wsl$ echo hello | sudo dd of=/dev/tty2 status=none
wsl$ sudo cat /dev/vcs2
hello

Electron + Node.js: how to open the Windows 10 virtual keyboard (not the touch keyboard)? [closed]

https://askubuntu.com/questions/1563746/electron-node-js-how-to-open-the-windows-10-virtual-keyboard-not-the-touch-k

I’m developing a desktop application for Windows 10 using Electron and Node.js. How can I programmatically open the Windows 10 on-screen (virtual) keyboard?
Currently, I’m opening the touch keyboard, but it looks ugly and is not what I want.

When i close my laptop(entering supended mode) my wi-fi enters "hardware Airplane mode"

https://askubuntu.com/questions/1563745/when-i-close-my-laptopentering-supended-mode-my-wi-fi-enters-hardware-airplan

this started right after i completely installed Ubuntu 24 and now everytime i put my laptop in sleep, standby, supended mode my wifi driver goes into hardware airplane mode, and the terminal said "softstop: no hardstop: yes"

Ubuntu 26.04 update issue [closed]

https://askubuntu.com/questions/1563743/ubuntu-26-04-update-issue

I am currently using 26.04 dev version and today morning 8th Feb 2026 I did a system update and after that my browser and any flatpak packages is not working accept zen browser but it's Firefox type browser chromium type browser like brave is not opening any new tab but old tabs are working and in the new tab google.com is opening but not other sites like YouTube etc nothing.

Do something please

uninstall nautilus, and reinstall

https://askubuntu.com/questions/1563705/uninstall-nautilus-and-reinstall

Using TERMINAL in Ubuntu 24.04.3lts Wayland - Linux 6.8.0-85-generic, how do I SUCCESSFULLY uninstall nautilus completely, and aferwhich, how do I reinstall it SUCCESSFULLY - dependencies and all...?

Currently, I can copy, edit, move, etc. files using terminal so drive itself and permissions seem no problem, edit using nano, etc., but nautilus seems to just want to crash (like it's corrupt) so want to reinstall, not repair, it.

from terminal:

Desktop$ nautilus
** Message: 19:33:27.602: Connecting to org.freedesktop.Tracker3.Miner.Files
Gsk-Message: 19:33:30.917: Failed to realize renderer of type 'GskNglRenderer' for surface 'GdkWaylandToplevel': OpenGL ES 3.0 is not supported by this renderer.

Gsk-Message: 19:34:24.833: Failed to realize renderer of type 'GskNglRenderer' for surface    'GdkWaylandPopup': OpenGL ES 3.0 is not supported by this renderer.

Gsk-Message: 19:34:46.395: Failed to realize renderer of type 'GskNglRenderer' for surface 'GdkWaylandPopup': OpenGL ES 3.0 is not supported by this renderer.

Shouldn't that be Gsk.NglRenderer, not GskNglRenderer?

OK, Daniel T, I ran dpkg -V, but no /bin lines at all:

/Desktop$ dpkg -V
?????????   /boot/vmlinuz-6.8.0-94-generic
missing     /etc/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /etc/polkit-1/localauthority/20-org.d (Permission denied)
missing     /etc/polkit-1/localauthority/30-site.d (Permission denied)
missing     /etc/polkit-1/localauthority/50-local.d (Permission denied)
missing     /etc/polkit-1/localauthority/90-mandatory.d (Permission denied)
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/20-org.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/30-site.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/50-local.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/90-mandatory.d (Permission denied)
?????????   /boot/vmlinuz-6.8.0-85-generic
missing     /lib/modules/6.8.0-35-generic
?????????   /boot/kernel.efi-6.8.0-79-generic
??5?????? c /etc/apt/apt.conf.d/10periodic
??5?????? c /etc/UPower/UPower.conf
??5?????? c /etc/conky/conky.conf
??5?????? c /etc/mono/config
??5?????? c /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
?????????   /usr/libexec/sssd/proxy_child
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/org.blueman.pkla (Permission denied)
?????????   /boot/vmlinuz-6.8.0-53-generic
?????????   /lib/netplan/00-network-manager-all.yaml
?????????   /boot/System.map-6.8.0-53-generic
??5?????? c /etc/fuse.conf
?????????   /boot/System.map-6.8.0-84-generic
missing   c /etc/grub.d/10_linux
?????????   /usr/libexec/sssd/selinux_child
??5?????? c /etc/tlp.conf
?????????   /usr/libexec/sssd/krb5_child
?????????   /usr/libexec/sssd/ldap_child
missing     /var/cache/cups/rss (Permission denied)
missing     /var/spool/cups/tmp (Permission denied)
??5?????? c /etc/update-manager/release-upgrades
?????????   /boot/System.map-6.8.0-85-generic
????????? c /etc/sudoers
????????? c /etc/sudoers.d/README
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.Flatpak.pkla (Permission denied)
?????????   /boot/vmlinuz-6.8.0-84-generic
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/gnome-initial-setup.pkla (Permission denied)
??5?????? c /etc/gdm3/custom.conf
??5?????? c /etc/sysctl.conf
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.packagekit.pkla (Permission denied)
?????????   /boot/vmlinuz-6.8.0-79-generic
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla (Permission denied)
????????? c /etc/default/cacerts
?????????   /boot/System.map-6.8.0-79-generic
????????? c /etc/fwupd/fwupd.conf
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/fwupd.pkla (Permission denied)
?????????   /boot/System.map-6.8.0-50-generic
?????????   /boot/System.map-6.8.0-94-generic

In lieu of using termnal on the desktop, would using the RECOVERY tool from grub and dropping into root be better way to uninstall, then reboot and again to the tool to root, to reinstall nautilus?

I can run Firefox, browse away, play things, etc., and all is fine until I try to attach a file to an email which tries to bring up a nautilus type window, or try to download/save a file which also tries to bring up a nautilus type window, then it'll try but ends up crashing Firefox during the attempt. I assume a piece of nautilus is what the browser uses - same with using something like LibreOffice - try to open a file which tries to bring up the window and that does similarly...

connection failed

https://askubuntu.com/questions/1538326/connection-failed

in Ubuntu 22.04 internet worked regularly, but after the upgrade to Ubuntu 24.10 when I use internet, I repeatedly get the very annoying message system now - connection failed - network connection activation failed at irregular intervals, and despite this the internet works fine. If I give the command nmcli radio from the terminal WWAN-HW missing.

Grub dual boot results in Windows error code 0x000428

https://askubuntu.com/questions/1486599/grub-dual-boot-results-in-windows-error-code-0x000428

I am on Ubuntu 23.04. For some reason I am getting an error when trying to boot into Windows Boot Manager. The error code is 0x000428 Windows cannot verify digital signature. I know it is not an issue with the Windows bootloader because if it boots straight to the windows bootloader I don't get any errors and it boots right up. This only happens when I boot into grub and then select the Windows Boot Manager selection, so I can only assume this is an issue with grub. I don't know if maybe grub caches these values somewhere or if there is some kind of issue in a grub config somewhere. It was working fine and then it just wasn't. I'm not sure when it broke because I don't boot into Windows that often.

I first thought it was a Windows issue so I reinstalled Windows, but that didn't matter. I have tried using Boot-Repair to reinstall grub, but I had no luck. Does anyone know what the issue could be? If I can't figure it out my next move will be to just nuke everything and reinstall both Ubuntu and Windows, or I might try to upgrade to the upcoming 23.10.

SD card partitioning got messed up while installing Ubuntu [duplicate]

https://askubuntu.com/questions/1324396/sd-card-partitioning-got-messed-up-while-installing-ubuntu

I recently switched from Windows to Ubuntu. I've got a problem of SD card partitioning. I ran the sudo fdisk /dev/sdc1 command and tried to manage it. I want only a single partition of 32 GB so that my SD card works normally on any PC. Here are the details of current state of my SD card.

Device     Boot    Start      End  Sectors  Size Id Type
/dev/sdc1        5619583  5619583        1  512B  5 Extended

Please help me by telling the commands so that I can achieve the desired result.

It currently has 1 sector of type extended and my SD card is not detected on either Windows or Linux.

Cloning Ubuntu from a USB key to a partition of an internal SSD

https://askubuntu.com/questions/1319985/cloning-ubuntu-from-a-usb-key-to-a-partition-of-an-internal-ssd

I have Ubuntu installed on a usb drive for a while now. I could not installed it along side Windows because my SSD was in RAID mode and not AHCI, so Ubuntu was not able to detect it. But recently I got a new laptop and switch to AHCI mode with no risk of loosing data because the PC was brand new.

Now Ubuntu can detect my internal SSD, and I want to clone it from my USB drive to a partition of my SSD, alongside Windows 10. I chose to do it with the dd command (I've already used it with success for cloning Ubuntu from one USB key to another), but this time it did not work properly.

I ran a live session of Ubuntu 18.04, plugged the USB key with my Ubuntu on it, and launched GParted in order to create a partition for the cloning operation. I unmount /dev/sdb (my Ubuntu USB key), as well as /dev/nvme01 (the SSD), and launched the command :

sudo dd status=progress if=/dev/sdb of=/dev/nvme01p4

The process worked quite well, but in GParted the partition nvme01p4 (which is supposed to contain the clone of my Ubuntu) is not correctly detected.

GParted screenshot after running the dd command:

It appears there is a new Ubuntu option in the boot menu, but it leads to a grub console where I don't know what to do.

What did I do wrong?

Multiboot: Windows + Ubuntu 18.04 + 20.04

https://askubuntu.com/questions/1271050/multiboot-windows-ubuntu-18-04-20-04

I had already installation of a Windows 10 / Kubuntu 18.04 dual boot. It was 2 years ago, so I don't exactly remember how was it, but probably first was Windows and then Ubuntu created grub bootloader, (used EFI?) I use also LVM partitions in Linux.

Now I would like to add new installation of Ubuntu 20.04 and here I am stuck. Kubuntu Installer asking for bootloader device and I am not sure what is correct next steps to avoid break my previous boot setup. With new install destination device for new 20.04 I already created PV and VG01, that is not the problem, issue is the bootloader. Do you have any idea? I would like to have all 3 installations: Windows, 18.04 and 20.04

Another question is how to save my current bootloader / grub conf.

Here is screenshot from installation option:

And here is my correct boot setup.

And here are my devices>

Device Start End Sectors SizeType
/dev/nvme0n1p1 2048 1023999 1021952 499M Windows recovery environment
/dev/nvme0n1p2 1024000 1228799 204800 100M EFI System
/dev/nvme0n1p3 1228800 1261567 32768 16M Microsoft reserved
/dev/nvme0n1p4 1261568 817877051 816615484 389,4G Microsoft basic data
/dev/nvme0n1p5 817879040 819199999 1320960 645M Windows recovery environment
/dev/nvme0n1p6 819202048 903088127 83886080 40G Linux filesystem
/dev/nvme0n1p7 903088128 919865343 16777216 8G Linux swap
/dev/nvme0n1p8 919865344 1338396671 418531328 199,6G Microsoft basic data
/dev/nvme0n1p9 1338396672 1645596671 307200000 146,5G Linux filesystem
/dev/nvme0n1p10 1645596672 2669596671 1024000000 488,3G Linux filesystem
/dev/nvme0n1p11 2669596672 2874396671 204800000 97,7G Linux filesystem
/dev/nvme0n1p12 2874396672 3079196671 204800000 97,7G Linux filesystem
/dev/nvme0n1p13 3079196672 3283996671 204800000 97,7G Linux LVM
/dev/nvme0n1p14 3283996672 3509276671 225280000 107,4G Linux LVM

I also found that grub cfg configuration for my old setup is in /boot/grub/grub.cfg, but in the head is below notice

"It is automatically generated by grub-mkconfig using templates from /etc/grub.d and settings from /etc/default/grub"

When I look in /etc/grub.d/ there are some templates, but it looks like it's not reflected my current setup, so I don't know how this auto-gen grub works. (e.g. I don't have any Xen in my current boot menu, but here it is.)

ls /etc/grub.d/
00_header 10_linux 20_memtest86+ 30_uefi-firmware 41_custom
05_debian_theme 20_linux_xen 30_os-prober 40_custom README

How resolve WARN when run ansible: [WARNING]: Skipping plugin as it seems to be invalid?

https://askubuntu.com/questions/1261347/how-resolve-warn-when-run-ansible-warning-skipping-plugin-as-it-seems-to-be

When I run ansible command, like this:

ansible -i host all -m ping

I got this warnings:

[WARNING]: Skipping plugin (/usr/lib/python2.7/dist-packages/ansible/plugins/callback/foreman.py) as it seems to be invalid: from_buffer() cannot return the address of the raw string
within a str or unicode or bytearray object
[WARNING]: Skipping plugin (/usr/lib/python2.7/dist-packages/ansible/plugins/callback/grafana_annotations.py) as it seems to be invalid: from_buffer() cannot return the address of the
raw string within a str or unicode or bytearray object
[WARNING]: Skipping plugin (/usr/lib/python2.7/dist-packages/ansible/plugins/callback/hipchat.py) as it seems to be invalid: from_buffer() cannot return the address of the raw string
within a str or unicode or bytearray object
[WARNING]: Skipping plugin (/usr/lib/python2.7/dist-packages/ansible/plugins/callback/nrdp.py) as it seems to be invalid: from_buffer() cannot return the address of the raw string
within a str or unicode or bytearray object
[WARNING]: Skipping plugin (/usr/lib/python2.7/dist-packages/ansible/plugins/callback/slack.py) as it seems to be invalid: from_buffer() cannot return the address of the raw string
within a str or unicode or bytearray object
[WARNING]: Skipping plugin (/usr/lib/python2.7/dist-packages/ansible/plugins/callback/splunk.py) as it seems to be invalid: from_buffer() cannot return the address of the raw string
within a str or unicode or bytearray object
[WARNING]: Skipping plugin (/usr/lib/python2.7/dist-packages/ansible/plugins/callback/sumologic.py) as it seems to be invalid: from_buffer() cannot return the address of the raw string
within a str or unicode or bytearray object

Why this happen, and how can I remove this warning?

Server params:
ansible version - 2.9
OS version - Ubuntu 16.04

Help with installing boot grub in Windows 10

https://askubuntu.com/questions/1224848/help-with-installing-boot-grub-in-windows-10

I'm having a hard time trying to install on my Windows 10 the Grub bootloader. I downloaded the Ubuntu 18.04.4-desktop-amd64 ISO then ran the Ubuntu live session, then I ran this command sudo fdisk -l

SSD:

According to some internet articles I need to shrink my current SSD at least by 400 MB in order to format a boot partition as EFI FAT32 with a proper flag, and with that I will be able to install GRUB there. I have never used a Linux distro before.

Would someone here give me guidance me with proper commands in order to shrink my current drive which has 223 size, but only has a free space of 33 GIB? I only need a 400 MB boot partition.

Once I have installed Grub, finally I would be able to ran the grub configuration to finally fix the HPET of my motherboard firmware among other things.

With GRUB booting Windows, I can access to the configuration of the motherboard firmware allowed in Asrock, and with that force High Event Precision Timing to Disable Cause in a regular way my motherboard firmware is causing issues with HPET forced enable even if I disabled it, so with the GRUB there is a configuration to force HPET to disable, and force the Windows timer to 3.580 MHz.

I still get "Dummy output" for audio after installing alsa-base and pulseaudio

https://askubuntu.com/questions/1169798/i-still-get-dummy-output-for-audio-after-installing-alsa-base-and-pulseaudio

I tried using my audio recently and I noticed that I couldn't any more, I've tried a few of the options I've seen but they do not seem to work:

Dummy Output in Audio; nothing is working (ALSA broken?) This doesn't work, after i run sudo alsa force-reload I get:

Unloading ALSA sound driver modules: (none loaded).
Loading ALSA sound driver modules: (none to reload).

https://askubuntu.com/a/800280/990366 and this too, when i run:

sudo apt-get install --reinstall linux-image-`uname -r`

I get errors that a config is bad:

sudo apt-get install --reinstall linux-image-`uname -r`
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/8,360 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 182773 files and directories currently installed.)
Preparing to unpack .../linux-image-5.0.0-25-generic_5.0.0-25.26_amd64.deb ...
/etc/kernel/preinst.d/intel-microcode:
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
Unpacking linux-image-5.0.0-25-generic (5.0.0-25.26) over (5.0.0-25.26) ...
Setting up linux-image-5.0.0-25-generic (5.0.0-25.26) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.0.0-25-generic
I: /initrd.img.old is now a symlink to boot/initrd.img-5.0.0-25-generic
Processing triggers for linux-image-5.0.0-25-generic (5.0.0-25.26) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.0.0-25-generic
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
I: The initramfs will attempt to resume from /dev/sda8
I: (UUID=b69c28bb-170e-48a4-a279-f4449d689741)
I: Set the RESUME variable to override this.
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.0.0-25-generic
Found initrd image: /boot/initrd.img-5.0.0-25-generic
Found linux image: /boot/vmlinuz-5.0.0-13-generic
Found initrd image: /boot/initrd.img-5.0.0-13-generic
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done

and sudo modprobe snd-hda-intel gave me:

libkmod: ERROR ../libkmod/libkmod-config.c:656 kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 44: ignoring bad line starting with 'snd-hda-intel'
modprobe: FATAL: Module snd-hda-intel not found in directory /lib/modules/5.0.0-25-generic

I do not really know what these commands do, It's just been trial and error. This is happening on Ubuntu 19.04.

cat /etc/modprobe.d/alsa-base.conf gave me:

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet --use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
snd-hda-intel probe_mask=1

pacmd list-cards gives me: 0 card(s) available.

Unable to connect to SQL server after update

https://askubuntu.com/questions/1164334/unable-to-connect-to-sql-server-after-update

I updated my server today with all pending update and after reboot I was unable to connect to SQL server. Prior to reboot I've also enabled the firewall but now it's disabled again and server is after another reboot. When I try to connect locally using

sqlcmd -S localhost

I get error:

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x2749.
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

Server itself is up and running:

hyperqbe@slaro:/etc$ sudo systemctl status mssql-server
[sudo] hasło użytkownika hyperqbe:
● mssql-server.service - Microsoft SQL Server Database Engine
   Loaded: loaded (/lib/systemd/system/mssql-server.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-08-08 15:06:28 CEST; 19min ago
     Docs: https://docs.microsoft.com/en-us/sql/linux
 Main PID: 7259 (sqlservr)
    Tasks: 158
   CGroup: /system.slice/mssql-server.service
           ├─7259 /opt/mssql/bin/sqlservr
           └─7288 /opt/mssql/bin/sqlservr

sie 08 15:06:38 slaro sqlservr[7259]: [95B blob data]
sie 08 15:06:38 slaro sqlservr[7259]: [91B blob data]
sie 08 15:06:38 slaro sqlservr[7259]: [145B blob data]
sie 08 15:06:38 slaro sqlservr[7259]: [61B blob data]
sie 08 15:06:39 slaro sqlservr[7259]: [96B blob data]
sie 08 15:06:39 slaro sqlservr[7259]: [66B blob data]
sie 08 15:06:40 slaro sqlservr[7259]: [96B blob data]
sie 08 15:06:40 slaro sqlservr[7259]: [100B blob data]
sie 08 15:06:40 slaro sqlservr[7259]: [71B blob data]
sie 08 15:06:40 slaro sqlservr[7259]: [124B blob data]

I'm unable to connect remotely from other machine as well:

TITLE: Connect to Server
------------------------------
Cannot connect to 192.168.1.141.
------------------------------
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - Istniejące połączenie zostało gwałtownie zamknięte przez zdalnego hosta.) (Microsoft SQL Server, Error: 10054)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10054&LinkId=20476

As far as I know there were no errors during update process.

Here are the last entries from errorlog:

2019-08-08 15:06:34.89 Server      Microsoft SQL Server 2019 (CTP3.2) - 15.0.1800.32 (X64)
        Jul 17 2019 21:29:33
        Copyright (C) 2019 Microsoft Corporation
        Express Edition (64-bit) on Linux (Ubuntu 18.04.3 LTS) <X64>
2019-08-08 15:06:34.89 Server      UTC adjustment: 2:00
2019-08-08 15:06:34.89 Server      (c) Microsoft Corporation.
2019-08-08 15:06:34.89 Server      All rights reserved.
2019-08-08 15:06:34.89 Server      Server process ID is 32.
2019-08-08 15:06:34.89 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2019-08-08 15:06:34.89 Server      Registry startup parameters:
         -d /var/opt/mssql/data/master.mdf
         -l /var/opt/mssql/data/mastlog.ldf
         -e /var/opt/mssql/log/errorlog
2019-08-08 15:06:34.90 Server      SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-08-08 15:06:34.90 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-08-08 15:06:34.90 Server      Detected 12800 MB of RAM. This is an informational message; no user action is required.
2019-08-08 15:06:34.90 Server      Using conventional memory in the memory manager.
2019-08-08 15:06:34.90 Server      Page exclusion bitmap is enabled.
2019-08-08 15:06:35.01 Server      Buffer pool extension is not supported on Linux platform.
2019-08-08 15:06:35.02 Server      Buffer Pool: Allocating 2097152 bytes for 1963331 hashPages.
2019-08-08 15:06:35.16 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2019-08-08 15:06:35.69 Server      Buffer pool extension is already disabled. No action is necessary.
2019-08-08 15:06:35.99 Server      Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2019-08-08 15:06:36.01 Server      Query Store settings initialized with enabled = 1,
2019-08-08 15:06:36.07 Server      The maximum number of dedicated administrator connections for this instance is '1'
2019-08-08 15:06:36.07 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-08-08 15:06:36.11 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2019-08-08 15:06:36.17 Server      In-Memory OLTP initialized on lowend machine.
2019-08-08 15:06:36.37 Server      CLR version v4.0.30319 loaded.
2019-08-08 15:06:36.57 Server      [INFO] Created Extended Events session 'hkenginexesession'

2019-08-08 15:06:36.58 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2019-08-08 15:06:36.59 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.
2019-08-08 15:06:36.72 Server      clflushopt is selected for pmem flush operation.
2019-08-08 15:06:36.72 Server      Software Usage Metrics is disabled.
2019-08-08 15:06:36.97 spid11s     [1]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-08-08 15:06:36.98 spid11s     Starting up database 'master'.
2019-08-08 15:06:37.58 Server      Common language runtime (CLR) functionality initialized.
2019-08-08 15:06:37.77 spid11s     SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-08-08 15:06:37.78 spid11s     SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-08-08 15:06:38.05 Server      Failed to verify the Authenticode signature of 'C:\binn\secforwarder.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2019-08-08 15:06:38.11 spid11s     SQL Trace ID 1 was started by login "sa".
2019-08-08 15:06:38.27 spid11s     Server name is 'slaro'. This is an informational message only. No user action is required.
2019-08-08 15:06:38.29 spid29s     Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-08-08 15:06:38.29 spid29s     Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2019-08-08 15:06:38.30 spid11s     [4]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-08-08 15:06:38.30 spid11s     Starting up database 'msdb'.
2019-08-08 15:06:38.32 spid12s     [32767]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-08-08 15:06:38.32 spid12s     Starting up database 'mssqlsystemresource'.
2019-08-08 15:06:38.33 spid12s     The resource database build version is 15.00.1800. This is an informational message only. No user action is required.
2019-08-08 15:06:38.36 spid12s     [3]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-08-08 15:06:38.36 spid12s     Starting up database 'model'.
2019-08-08 15:06:38.40 Server      Failed to verify the Authenticode signature of 'C:\binn\msoledbsql.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2019-08-08 15:06:38.48 spid28s     A self-generated certificate was successfully loaded for encryption.
2019-08-08 15:06:38.51 Server      Error: 37308, Severity: 16, State: 1.
2019-08-08 15:06:38.51 Server      Loaded None enclave for always encrypted.
2019-08-08 15:06:38.51 spid28s     Server is listening on [ 192.168.1.141 <ipv4> 1433].
2019-08-08 15:06:38.54 spid28s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-08-08 15:06:38.54 spid28s     Error: 39002, Severity: 16, State: 1.
2019-08-08 15:06:38.54 spid28s     SQL failed to boot extensibility for error code 0x80070005.
2019-08-08 15:06:38.55 spid28s     InitializeXdbPkgLauncher failed. ErrorCode: 0x80004005.
2019-08-08 15:06:38.55 spid28s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-08-08 15:06:38.85 spid12s     Clearing tempdb database.
2019-08-08 15:06:39.88 spid12s     [2]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-08-08 15:06:39.89 spid12s     Starting up database 'tempdb'.
2019-08-08 15:06:40.26 spid29s     The Service Broker endpoint is in disabled or stopped state.
2019-08-08 15:06:40.26 spid29s     The Database Mirroring endpoint is in disabled or stopped state.
2019-08-08 15:06:40.27 spid29s     Service Broker manager has started.
2019-08-08 15:06:40.27 spid11s     Recovery is complete. This is an informational message only. No user action is required.
2019-08-08 15:27:16.30 spid55      [5]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-08-08 15:27:16.30 spid55      Starting up database 'ProgramMagazynowy'.
2019-08-08 15:27:16.53 spid55      Parallel redo is started for database 'ProgramMagazynowy' with worker pool size [2].
2019-08-08 15:27:16.73 spid55      Parallel redo is shutdown for database 'ProgramMagazynowy' with worker pool size [2].

It may have something to do with ODBC driver. I was able to enable logging and found this:

[ODBC][29210][1565333226.007247][SQLDriverConnectW.c][290]
                Entry:
                        Connection = 0x8c90e0
                        Window Hdl = (nil)
                        Str In = [DRIVER={ODBC Driver 17 for SQL Server};SERVER={192.168.1.141};Trusted_Connection={YES};WSID={slaro};APP={SQLCMD};][length = 113 (SQL_NTS)]
                        Str Out = (nil)
                        Str Out Max = 0
                        Str Out Ptr = (nil)
                        Completion = 0
                UNICODE Using encoding ASCII 'ANSI_X3.4-1968' and UNICODE 'UTF-16LE'

According to Documentation

If the ASCII character encoding is not UTF-8, there is more than one Driver Manager installed and your application is using the wrong one, or the Driver Manager was not built correctly.

In my case it's 'ANSI_X3.4-1968' so there has to be something wrong. I will further review the articles suggested in documentation but right now I don't know how to confirm that I indeed have two drivers installed and how to remove one.

EDIT:

odbcinst lists only one driver:

hyperqbe@slaro:/etc$ odbcinst -q -d
[ODBC Driver 17 for SQL Server]

This part seems to be fine. I'm not sure if I have my odbc.ini and odbcinst.ini defined correctly.

hyperqbe@slaro:/etc$ cat odbc.ini
[slaro]
Driver='ODBC Driver 17 for SQL Server'
Servername=192.168.1.141

hyperqbe@slaro:/etc$ cat odbcinst.ini
[ODBC Driver 17 for SQL Server]
Description=Microsoft ODBC Driver 17 for SQL Server
Driver=/opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.4.so.1.1
UsageCount=1
Trace=Yes
TraceFile=/home/hyperqbe/odbc.log

=======================================

EDIT ((ufw details per request)):

hyperqbe@slaro:~$ sudo ufw status
[sudo] hasło użytkownika hyperqbe:
Stan: aktywny

Do                         Działanie   Z
--                         ---------   -
27                         ALLOW       Anywhere
1433                       ALLOW       Anywhere
1434                       ALLOW       Anywhere
8686                       ALLOW       Anywhere
27 (v6)                    ALLOW       Anywhere (v6)
1433 (v6)                  ALLOW       Anywhere (v6)
1434 (v6)                  ALLOW       Anywhere (v6)
8686 (v6)                  ALLOW       Anywhere (v6)

22/tcp                     REJECT OUT  Anywhere
22/tcp (v6)                REJECT OUT  Anywhere (v6)

hyperqbe@slaro:~$ sudo iptables --list
Chain INPUT (policy DROP)
target     prot opt source               destination
ufw-before-logging-input  all  --  anywhere             anywhere
ufw-before-input  all  --  anywhere             anywhere
ufw-after-input  all  --  anywhere             anywhere
ufw-after-logging-input  all  --  anywhere             anywhere
ufw-reject-input  all  --  anywhere             anywhere
ufw-track-input  all  --  anywhere             anywhere

Chain FORWARD (policy DROP)
target     prot opt source               destination
ufw-before-logging-forward  all  --  anywhere             anywhere
ufw-before-forward  all  --  anywhere             anywhere
ufw-after-forward  all  --  anywhere             anywhere
ufw-after-logging-forward  all  --  anywhere             anywhere
ufw-reject-forward  all  --  anywhere             anywhere
ufw-track-forward  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
ufw-before-logging-output  all  --  anywhere             anywhere
ufw-before-output  all  --  anywhere             anywhere
ufw-after-output  all  --  anywhere             anywhere
ufw-after-logging-output  all  --  anywhere             anywhere
ufw-reject-output  all  --  anywhere             anywhere
ufw-track-output  all  --  anywhere             anywhere

Chain ufw-after-forward (1 references)
target     prot opt source               destination

Chain ufw-after-input (1 references)
target     prot opt source               destination
ufw-skip-to-policy-input  udp  --  anywhere             anywhere             udp dpt:netbios-ns
ufw-skip-to-policy-input  udp  --  anywhere             anywhere             udp dpt:netbios-dgm
ufw-skip-to-policy-input  tcp  --  anywhere             anywhere             tcp dpt:netbios-ssn
ufw-skip-to-policy-input  tcp  --  anywhere             anywhere             tcp dpt:microsoft-ds
ufw-skip-to-policy-input  udp  --  anywhere             anywhere             udp dpt:bootps
ufw-skip-to-policy-input  udp  --  anywhere             anywhere             udp dpt:bootpc
ufw-skip-to-policy-input  all  --  anywhere             anywhere             ADDRTYPE match dst-type BROADCAST

Chain ufw-after-logging-forward (1 references)
target     prot opt source               destination
LOG        all  --  anywhere             anywhere             limit: avg 3/min burst 10 LOG level warning prefix "[UFW BLOCK] "

Chain ufw-after-logging-input (1 references)
target     prot opt source               destination
LOG        all  --  anywhere             anywhere             limit: avg 3/min burst 10 LOG level warning prefix "[UFW BLOCK] "

Chain ufw-after-logging-output (1 references)
target     prot opt source               destination

Chain ufw-after-output (1 references)
target     prot opt source               destination

Chain ufw-before-forward (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ACCEPT     icmp --  anywhere             anywhere             icmp destination-unreachable
ACCEPT     icmp --  anywhere             anywhere             icmp time-exceeded
ACCEPT     icmp --  anywhere             anywhere             icmp parameter-problem
ACCEPT     icmp --  anywhere             anywhere             icmp echo-request
ufw-user-forward  all  --  anywhere             anywhere

Chain ufw-before-input (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ufw-logging-deny  all  --  anywhere             anywhere             ctstate INVALID
DROP       all  --  anywhere             anywhere             ctstate INVALID
ACCEPT     icmp --  anywhere             anywhere             icmp destination-unreachable
ACCEPT     icmp --  anywhere             anywhere             icmp time-exceeded
ACCEPT     icmp --  anywhere             anywhere             icmp parameter-problem
ACCEPT     icmp --  anywhere             anywhere             icmp echo-request
ACCEPT     udp  --  anywhere             anywhere             udp spt:bootps dpt:bootpc
ufw-not-local  all  --  anywhere             anywhere
ACCEPT     udp  --  anywhere             224.0.0.251          udp dpt:mdns
ACCEPT     udp  --  anywhere             239.255.255.250      udp dpt:1900
ufw-user-input  all  --  anywhere             anywhere

Chain ufw-before-logging-forward (1 references)
target     prot opt source               destination

Chain ufw-before-logging-input (1 references)
target     prot opt source               destination

Chain ufw-before-logging-output (1 references)
target     prot opt source               destination

Chain ufw-before-output (1 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
ufw-user-output  all  --  anywhere             anywhere

Chain ufw-logging-allow (0 references)
target     prot opt source               destination
LOG        all  --  anywhere             anywhere             limit: avg 3/min burst 10 LOG level warning prefix "[UFW ALLOW] "

Chain ufw-logging-deny (2 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere             ctstate INVALID limit: avg 3/min burst 10
LOG        all  --  anywhere             anywhere             limit: avg 3/min burst 10 LOG level warning prefix "[UFW BLOCK] "

Chain ufw-not-local (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere             ADDRTYPE match dst-type LOCAL
RETURN     all  --  anywhere             anywhere             ADDRTYPE match dst-type MULTICAST
RETURN     all  --  anywhere             anywhere             ADDRTYPE match dst-type BROADCAST
ufw-logging-deny  all  --  anywhere             anywhere             limit: avg 3/min burst 10
DROP       all  --  anywhere             anywhere

Chain ufw-reject-forward (1 references)
target     prot opt source               destination

Chain ufw-reject-input (1 references)
target     prot opt source               destination

Chain ufw-reject-output (1 references)
target     prot opt source               destination

Chain ufw-skip-to-policy-forward (0 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere

Chain ufw-skip-to-policy-input (7 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere

Chain ufw-skip-to-policy-output (0 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere

Chain ufw-track-forward (1 references)
target     prot opt source               destination

Chain ufw-track-input (1 references)
target     prot opt source               destination

Chain ufw-track-output (1 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere             ctstate NEW
ACCEPT     udp  --  anywhere             anywhere             ctstate NEW

Chain ufw-user-forward (1 references)
target     prot opt source               destination

Chain ufw-user-input (1 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:27
ACCEPT     udp  --  anywhere             anywhere             udp dpt:27
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:ms-sql-s
ACCEPT     udp  --  anywhere             anywhere             udp dpt:ms-sql-s
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:ms-sql-m
ACCEPT     udp  --  anywhere             anywhere             udp dpt:ms-sql-m
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:8686
ACCEPT     udp  --  anywhere             anywhere             udp dpt:8686

Chain ufw-user-limit (0 references)
target     prot opt source               destination
LOG        all  --  anywhere             anywhere             limit: avg 3/min burst 5 LOG level warning prefix "[UFW LIMIT BLOCK] "
REJECT     all  --  anywhere             anywhere             reject-with icmp-port-unreachable

Chain ufw-user-limit-accept (0 references)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere

Chain ufw-user-logging-forward (0 references)
target     prot opt source               destination

Chain ufw-user-logging-input (0 references)
target     prot opt source               destination

Chain ufw-user-logging-output (0 references)
target     prot opt source               destination

Chain ufw-user-output (1 references)
target     prot opt source               destination
REJECT     tcp  --  anywhere             anywhere             tcp dpt:ssh reject-with tcp-reset

I've found post suggesting that problem might be caused by python.

After upgrade from 16.04 LTS to 18.04 LTS, display manager fails apparently because of freedesktop

https://askubuntu.com/questions/1070572/after-upgrade-from-16-04-lts-to-18-04-lts-display-manager-fails-apparently-beca

I recently took the hint and upgraded from 16.04 LTS to 18.04 LTS, but had a nasty surprise when no login screen appeared, and even ctrl-alt F2 and friends didn't work. Fortunately, I was able to ssh in from elsewhere.

Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-33-generic x86_64)

Looking at syslog, I saw that gdm3/wayland tried repeatedly to start org.freedesktop.systemd1 and it would immediately fail (exit 1). A message like this would be repeated over and over in syslog.

Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=127 pid=1442 comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: Unable to register display with display manager
Aug 30 09:13:38 pabst gdm3: Child process -1442 was already dead.
Aug 30 09:13:38 pabst gdm3: Child process 1439 was already dead.
Aug 30 09:13:38 pabst gdm3: Unable to kill session worker process

Seeing advice elsewhere, I tried using "ubuntu-drivers autoinstall" which installed the recommended nvidia-driver-390. That didn't help.

I also tried disabling Wayland in a configuration file, but also no good.

I purged the Nvidia driver and tried with nouveau. Still no dice.

Then I installed nvidia-340 which at least sets the screen resolution correctly (as seen using "xinit" which brings up an xterm without a display manager).

Then I installed xdm, and made "xdm" the default greeter (it was part of the configuration when xdm was installed).

Now a login screen appears (and ctrl-alt F2 and friends work) but if I try to log on, it waits a bit after the login and then bumps back to the login screen.

.xsession-errors shows no serious problems.

But syslog shows that gnome-session-binary is trying to start org.freedesktop.systemd1 which (of course) fails again, which makes the required Gnome Shell.desktop die which causes the whole shebang fail (after lots of futile tries).

The sad ending to the story:

Aug 30 11:40:12 pabst dbus-daemon[3966]: [session uid=820 pid=3964] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-DFQHOZ
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: SSH_AUTH_SOCK=/home/john/.cache/keyring-DFQHOZ/ssh
Aug 30 11:40:12 pabst org.gnome.Shell.desktop[4057]: Window manager warning: Unsupported session type
Aug 30 11:40:12 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:12 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst org.gnome.Shell.desktop[4060]: Window manager warning: Unsupported session type
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 30 11:40:13 pabst gnome-session-binary[3926]: Unrecoverable failure in required component org.gnome.Shell.desktop
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....

So: (1) Can org.freedesktop.systemd1 be fixed? Is there any way to see why it's failing? or if it's unfixable (2) Is there a way to have gnome use something other than org.freedesktop.systemd1 ? or (3) Is there a display manager I can use on Ubuntu bionic that doesn't use any gnome stuff?

Ubuntu 18.04 and Windows 10 not booting after dual boot installation

https://askubuntu.com/questions/1028754/ubuntu-18-04-and-windows-10-not-booting-after-dual-boot-installation

I tried to install Ubuntu 18.04 as a second OS, but now neither of them is booting anymore. While boot "System BootOrder not found. Initializing defaults. Boot System." is displayed.

System BootOrder not found. Initializing defaults. 
Boot System.

I followed this guide and created two (/ and /home) partitions like in the screenshot below:

Screenshot: Partitions

Because it did not work and displayed this:

grub-efi-amd64-signed failed installation /target/

I found this solution to create a third FAT32 boot/esp partition to successfully install grub and Ubuntu, but now I can't boot either of them.

Some more screenshots:

Screenshot: Boot menu
^{Boot menu}

Screenshot: UEFI boot settings
^{UEFI boot settings}

Did I mess with the bootloader/MBR, and why did I need to create the esp/boot partition to install grub?

Additional information:

Secure boot configuration:

Remove read-only partition from a USB flash drive

https://askubuntu.com/questions/910585/remove-read-only-partition-from-a-usb-flash-drive

I have a USB that I'd like to use for a live disk. The problem is that it has a read-only partition on it. I've tried everything I can find to remove this read-only partition, but nothing worked. Below are the things I've tried:

sudo fdisk /dev/sdc
sudo mkfs -t vfat /dev/sdc1
sudo mount -o remount,rw /dev/sdc1 /test
sudo fsck.vfat -f -p /dev/sdc1
dosfsck -a /dev/sdc

Everything I try always returns a failure that the disk is read-only. Do you have any thoughts?

Can't access Windows 10 after installing Ubuntu 16.04

https://askubuntu.com/questions/809016/cant-access-windows-10-after-installing-ubuntu-16-04

I installed Ubuntu 16.04 alongside Windows 10. Now I'm unable to boot into Windows 10. How can I get the dual boot working, and get Windows 10 back?

When I turn on the system I get the following options:

Ubuntu
Advanced options for Ubuntu
Windows UEFI bootmgfw.efi
Window Boot UEFI loader
EFI/Ubuntu/fwupx64.efi
efi/ubuntumokmanager.efi
efi/toshiba/boot/bootmgfw.efi
Windows Boot Manager (on /dev/sda2)
System setup

Selecting any Windows option gives an error. Given below is the error that I got when I selected the Window Boot UEFI loader option

/EndEntire file path: /ACPI(a0341do,0) /PCI(2,1f)/Sata(0,0,0)/HD(2,200800,820000,60466f299ba3e211,2,2)/File(\EFI\Boot)/File(bk.pbootx64.efi)/EndEntire
error:  cannot load image 
Press any key to continue....

Boot info from Boot-Repair:

Partial Boot Info Summary:

============================= Boot Info Summary: ===============================

 => No boot loader is installed in the MBR of /dev/sda.
 => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdb.

sda1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /boot/bcd

sda2: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  Windows 8/2012: FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /EFI/Boot/bkpbootx64.efi /EFI/Boot/bootx64.efi 
                       /EFI/ubuntu/MokManager.efi /EFI/ubuntu/fwupx64.efi 
                       /EFI/ubuntu/grubx64.efi /EFI/ubuntu/shimx64.efi 
                       /EFI/Microsoft/Boot/bootmgfw.efi 
                       /EFI/Microsoft/Boot/bootmgr.efi 
                       /EFI/Microsoft/Boot/memtest.efi 
                       /EFI/toshiba/Boot/bootmgfw.efi 
                       /EFI/toshiba/Boot/bootmgr.efi 
                       /EFI/toshiba/Boot/memtest.efi

sda3: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sda4: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /bootmgr /Windows/System32/winload.exe

sda5: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sda6: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sda7: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows 8/2012: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

sda8: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Ubuntu 16.04.1 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab

sda9: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info: 

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  SYSLINUX 6.03
    Boot sector info:  Syslinux looks at sector 30362 of /dev/sdb1 for its 
                       second stage. The integrity check of Syslinux failed. 
                       No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /boot/grub/grub.cfg /syslinux.cfg /casper/vmlinuz.efi 
                       /EFI/BOOT/grubx64.efi /ldlinux.sys

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________
Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 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
Disklabel type: gpt

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1                   1 1,465,149,167 1,465,149,167  ee GPT


GUID Partition Table detected.

Partition  Attrs   Start Sector    End Sector  # of Sectors System
/dev/sda1      R          2,048     2,099,199     2,097,152 Windows Recovery Environment (Windows)
/dev/sda2             2,099,200     2,631,679       532,480 EFI System partition
/dev/sda3             2,631,680     2,893,823       262,144 Microsoft Reserved Partition (Windows)
/dev/sda4             2,893,824   532,007,078   529,113,255 Data partition (Windows/Linux)
/dev/sda5      R    727,412,736   729,171,967     1,759,232 Windows Recovery Environment (Windows)
/dev/sda6           729,171,968 1,442,658,303   713,486,336 Data partition (Windows/Linux)
/dev/sda7      R  1,442,660,352 1,465,147,391    22,487,040 Windows Recovery Environment (Windows)
/dev/sda8           532,008,960   715,077,631   183,068,672 Data partition (Linux)
/dev/sda9           715,077,632   727,412,735    12,335,104 Swap partition (Linux)

    =================== Recommended repair
    The default repair of the Boot-Repair utility will reinstall the grub-efi-amd64-signed of sda8, using the following options:        sda2/boot/efi,
    Additional repair will be performed: unhide-bootmenu-10s   fix-windows-boot use-standard-efi-file


    /boot/efi added in sda8/fstab
    Quantity of real Windows: 1
    Mount sda2 on /mnt/boot-sav/sda8/boot/efi
    ls sda2/efi: /toshiba/Boot/zh-TW /toshiba/Boot/zh-HK /toshiba/Boot/zh-CN /toshiba/Boot/uk-UA /toshiba/Boot/tr-TR /toshiba/Boot/sv-SE /toshiba/Boot/sr-Latn-CS /toshiba/Boot/sl-SI /toshiba/Boot/sk-SK /toshiba/Boot/ru-RU /toshiba/Boot/ro-RO /toshiba/Boot/Resources /toshiba/Boot/qps-ploc /toshiba/Boot/pt-PT /toshiba/Boot/pt-BR /toshiba/Boot/pl-PL /toshiba/Boot/nl-NL /toshiba/Boot/nb-NO /toshiba/Boot/memtest.efi /toshiba/Boot/lv-LV /toshiba/Boot/lt-LT /toshiba/Boot/ko-KR /toshiba/Boot/ja-JP /toshiba/Boot/it-IT /toshiba/Boot/hu-HU /toshiba/Boot/hr-HR /toshiba/Boot/fr-FR /toshiba/Boot/Fonts /toshiba/Boot/fi-FI /toshiba/Boot/et-EE /toshiba/Boot/es-ES /toshiba/Boot/en-US /toshiba/Boot/en-GB /toshiba/Boot/el-GR /toshiba/Boot/de-DE /toshiba/Boot/da-DK /toshiba/Boot/cs-CZ /toshiba/Boot/boot.stl /toshiba/Boot/BOOTSTAT.DAT /toshiba/Boot/bootmgr.efi /toshiba/Boot/bootmgfw.efi /toshiba/Boot/bg-BG /toshiba/Boot/bcd.LOG /toshiba/Boot/bcd /Microsoft/Recovery/BCD.LOG2 /Microsoft/Recovery/BCD.LOG1 /Microsoft/Recovery/BCD.LOG /Microsoft/Recovery/BCD /Microsoft/Boot/zh-TW /Microsoft/Boot/zh-HK /Microsoft/Boot/zh-CN /Microsoft/Boot/uk-UA /Microsoft/Boot/tr-TR /Microsoft/Boot/sv-SE /Microsoft/Boot/sr-Latn-RS /Microsoft/Boot/sr-Latn-CS /Microsoft/Boot/sl-SI /Microsoft/Boot/sk-SK /Microsoft/Boot/ru-RU /Microsoft/Boot/ro-RO /Microsoft/Boot/Resources /Microsoft/Boot/qps-ploc /Microsoft/Boot/pt-PT /Microsoft/Boot/pt-BR /Microsoft/Boot/pl-PL /Microsoft/Boot/nl-NL /Microsoft/Boot/nb-NO /Microsoft/Boot/memtest.efi /Microsoft/Boot/lv-LV /Microsoft/Boot/lt-LT /Microsoft/Boot/ko-KR /Microsoft/Boot/kdstub.dll /Microsoft/Boot/kd_0C_8086.dll /Microsoft/Boot/kd_07_1415.dll /Microsoft/Boot/kd_02_8086.dll /Microsoft/Boot/kd_02_19a2.dll /Microsoft/Boot/kd_02_1969.dll /Microsoft/Boot/kd_02_15b3.dll /Microsoft/Boot/kd_02_14e4.dll /Microsoft/Boot/kd_02_1137.dll /Microsoft/Boot/kd_02_10ec.dll /Microsoft/Boot/kd_02_10df.dll /Microsoft/Boot/ja-JP /Microsoft/Boot/it-IT /Microsoft/Boot/hu-HU /Microsoft/Boot/hr-HR /Microsoft/Boot/fr-FR /Microsoft/Boot/fr-CA /Microsoft/Boot/Fonts /Microsoft/Boot/fi-FI /Microsoft/Boot/et-EE /Microsoft/Boot/es-MX /Microsoft/Boot/es-ES /Microsoft/Boot/en-US /Microsoft/Boot/en-GB /Microsoft/Boot/el-GR /Microsoft/Boot/de-DE /Microsoft/Boot/da-DK /Microsoft/Boot/cs-CZ /Microsoft/Boot/boot.stl /Microsoft/Boot/BOOTSTAT.DAT /Microsoft/Boot/bootmgr.efi /Microsoft/Boot/bootmgfw.efi /Microsoft/Boot/bg-BG /Microsoft/Boot/BCD.LOG2 /Microsoft/Boot/BCD.LOG1 /Microsoft/Boot/BCD.LOG /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TMContainer00000000000000000002.regtrans-ms /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TMContainer00000000000000000001.regtrans-ms /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TM.blf /Microsoft/Boot/BCD /ubuntu/shimx64.efi /ubuntu/MokManager.efi /ubuntu/grubx64.efi /ubuntu/grub.cfg /ubuntu/fwupx64.efi /ubuntu/fw /toshiba/Boot /Microsoft/Recovery /Microsoft/Boot /Boot/bootx64.efi
    ls sda2: boot-sav
    BOOTSECT.BAK
    EFI  . Please report this message to boot.repair@gmail.com

    *******lspci -nnk | grep -iA3 vga
    00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09)
    Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fa20]
    Kernel driver in use: i915
    Kernel modules: i915
    *******

    grub-install --version
    grub-install (GRUB) 2.02~beta2-36ubuntu3.2,grub-install (GRUB) 2.

    chroot /mnt/boot-sav/sda8 efibootmgr -v
    BootCurrent: 0000
    Timeout: 2 seconds
    BootOrder: 2001,0004,0003,0005,2003,2002
    Boot0000* EFI USB Device (USB DISK 3.0) PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(2,0)/HD(1,MBR,0x93,0x800,0x75ff800)RC
    Boot0001* EFI Network 0 for IPv6 (00-8C-FA-4B-D0-64)    PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(008cfa4bd064,0)/IPv6([::]:<->[::]:,0,0)RC
    Boot0002* EFI Network 0 for IPv4 (00-8C-FA-4B-D0-64)    PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(008cfa4bd064,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
    Boot0003* Windows Boot Manager  HD(2,GPT,296f4660-a39b-11e2-a1a5-d6452f6c7727,0x200800,0x82000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...s................
    Boot0004* ubuntu    HD(2,GPT,296f4660-a39b-11e2-a1a5-d6452f6c7727,0x200800,0x82000)/File(EFIubuntushimx64.efi)
    Boot0005* Ubuntu    HD(2,GPT,296f4660-a39b-11e2-a1a5-d6452f6c7727,0x200800,0x82000)/File(EFIubuntugrubx64.efi)RC
    Boot0006* EFI Network 0 for IPv6 (00-8C-FA-4B-D0-64)    PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(008cfa4bd064,0)/IPv6([::]:<->[::]:,0,0)RC
    Boot0007* EFI Network 0 for IPv4 (00-8C-FA-4B-D0-64)    PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(008cfa4bd064,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
    Boot2001* EFI USB Device    RC
    Boot2002* EFI DVD/CDROM RC
    Boot2003* EFI Network   RC

    chroot /mnt/boot-sav/sda8 uname -r
    Kernel: 4.4.0-31-generic

    Reinstall the grub-efi-amd64-signed of sda8
    Installing for x86_64-efi platform.
    Installation finished. No error reported.
    grub-install --efi-directory=/boot/efi --target=x86_64-efi --uefi-secure-boot : exit code of grub-install :0
    ls sda2/efi: /toshiba/Boot/zh-TW /toshiba/Boot/zh-HK /toshiba/Boot/zh-CN /toshiba/Boot/uk-UA /toshiba/Boot/tr-TR /toshiba/Boot/sv-SE /toshiba/Boot/sr-Latn-CS /toshiba/Boot/sl-SI /toshiba/Boot/sk-SK /toshiba/Boot/ru-RU /toshiba/Boot/ro-RO /toshiba/Boot/Resources /toshiba/Boot/qps-ploc /toshiba/Boot/pt-PT /toshiba/Boot/pt-BR /toshiba/Boot/pl-PL /toshiba/Boot/nl-NL /toshiba/Boot/nb-NO /toshiba/Boot/memtest.efi /toshiba/Boot/lv-LV /toshiba/Boot/lt-LT /toshiba/Boot/ko-KR /toshiba/Boot/ja-JP /toshiba/Boot/it-IT /toshiba/Boot/hu-HU /toshiba/Boot/hr-HR /toshiba/Boot/fr-FR /toshiba/Boot/Fonts /toshiba/Boot/fi-FI /toshiba/Boot/et-EE /toshiba/Boot/es-ES /toshiba/Boot/en-US /toshiba/Boot/en-GB /toshiba/Boot/el-GR /toshiba/Boot/de-DE /toshiba/Boot/da-DK /toshiba/Boot/cs-CZ /toshiba/Boot/boot.stl /toshiba/Boot/BOOTSTAT.DAT /toshiba/Boot/bootmgr.efi /toshiba/Boot/bootmgfw.efi /toshiba/Boot/bg-BG /toshiba/Boot/bcd.LOG /toshiba/Boot/bcd /Microsoft/Recovery/BCD.LOG2 /Microsoft/Recovery/BCD.LOG1 /Microsoft/Recovery/BCD.LOG /Microsoft/Recovery/BCD /Microsoft/Boot/zh-TW /Microsoft/Boot/zh-HK /Microsoft/Boot/zh-CN /Microsoft/Boot/uk-UA /Microsoft/Boot/tr-TR /Microsoft/Boot/sv-SE /Microsoft/Boot/sr-Latn-RS /Microsoft/Boot/sr-Latn-CS /Microsoft/Boot/sl-SI /Microsoft/Boot/sk-SK /Microsoft/Boot/ru-RU /Microsoft/Boot/ro-RO /Microsoft/Boot/Resources /Microsoft/Boot/qps-ploc /Microsoft/Boot/pt-PT /Microsoft/Boot/pt-BR /Microsoft/Boot/pl-PL /Microsoft/Boot/nl-NL /Microsoft/Boot/nb-NO /Microsoft/Boot/memtest.efi /Microsoft/Boot/lv-LV /Microsoft/Boot/lt-LT /Microsoft/Boot/ko-KR /Microsoft/Boot/kdstub.dll /Microsoft/Boot/kd_0C_8086.dll /Microsoft/Boot/kd_07_1415.dll /Microsoft/Boot/kd_02_8086.dll /Microsoft/Boot/kd_02_19a2.dll /Microsoft/Boot/kd_02_1969.dll /Microsoft/Boot/kd_02_15b3.dll /Microsoft/Boot/kd_02_14e4.dll /Microsoft/Boot/kd_02_1137.dll /Microsoft/Boot/kd_02_10ec.dll /Microsoft/Boot/kd_02_10df.dll /Microsoft/Boot/ja-JP /Microsoft/Boot/it-IT /Microsoft/Boot/hu-HU /Microsoft/Boot/hr-HR /Microsoft/Boot/fr-FR /Microsoft/Boot/fr-CA /Microsoft/Boot/Fonts /Microsoft/Boot/fi-FI /Microsoft/Boot/et-EE /Microsoft/Boot/es-MX /Microsoft/Boot/es-ES /Microsoft/Boot/en-US /Microsoft/Boot/en-GB /Microsoft/Boot/el-GR /Microsoft/Boot/de-DE /Microsoft/Boot/da-DK /Microsoft/Boot/cs-CZ /Microsoft/Boot/boot.stl /Microsoft/Boot/BOOTSTAT.DAT /Microsoft/Boot/bootmgr.efi /Microsoft/Boot/bootmgfw.efi /Microsoft/Boot/bg-BG /Microsoft/Boot/BCD.LOG2 /Microsoft/Boot/BCD.LOG1 /Microsoft/Boot/BCD.LOG /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TMContainer00000000000000000002.regtrans-ms /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TMContainer00000000000000000001.regtrans-ms /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TM.blf /Microsoft/Boot/BCD /ubuntu/shimx64.efi /ubuntu/MokManager.efi /ubuntu/grubx64.efi /ubuntu/grub.cfg /ubuntu/fwupx64.efi /ubuntu/fw /toshiba/Boot /Microsoft/Recovery /Microsoft/Boot /Boot/bootx64.efi
    ls sda2: boot-sav
    BOOTSECT.BAK
    EFI  . Please report this message to boot.repair@gmail.com
    df /dev/sda2
    Save and rename /mnt/boot-sav/sda8/boot/efi/EFI/Boot/bootx64.efi (/mnt/boot-sav/sda8/boot/efi/EFI/Boot/bkpbootx64.efi)
    cp /mnt/boot-sav/sda8/boot/efi/EFI/ubuntu/shimx64.efi /mnt/boot-sav/sda8/boot/efi/EFI/Boot/bootx64.efi
    ls sda2/efi: /toshiba/Boot/zh-TW /toshiba/Boot/zh-HK /toshiba/Boot/zh-CN /toshiba/Boot/uk-UA /toshiba/Boot/tr-TR /toshiba/Boot/sv-SE /toshiba/Boot/sr-Latn-CS /toshiba/Boot/sl-SI /toshiba/Boot/sk-SK /toshiba/Boot/ru-RU /toshiba/Boot/ro-RO /toshiba/Boot/Resources /toshiba/Boot/qps-ploc /toshiba/Boot/pt-PT /toshiba/Boot/pt-BR /toshiba/Boot/pl-PL /toshiba/Boot/nl-NL /toshiba/Boot/nb-NO /toshiba/Boot/memtest.efi /toshiba/Boot/lv-LV /toshiba/Boot/lt-LT /toshiba/Boot/ko-KR /toshiba/Boot/ja-JP /toshiba/Boot/it-IT /toshiba/Boot/hu-HU /toshiba/Boot/hr-HR /toshiba/Boot/fr-FR /toshiba/Boot/Fonts /toshiba/Boot/fi-FI /toshiba/Boot/et-EE /toshiba/Boot/es-ES /toshiba/Boot/en-US /toshiba/Boot/en-GB /toshiba/Boot/el-GR /toshiba/Boot/de-DE /toshiba/Boot/da-DK /toshiba/Boot/cs-CZ /toshiba/Boot/boot.stl /toshiba/Boot/BOOTSTAT.DAT /toshiba/Boot/bootmgr.efi /toshiba/Boot/bootmgfw.efi /toshiba/Boot/bg-BG /toshiba/Boot/bcd.LOG /toshiba/Boot/bcd /Microsoft/Recovery/BCD.LOG2 /Microsoft/Recovery/BCD.LOG1 /Microsoft/Recovery/BCD.LOG /Microsoft/Recovery/BCD /Microsoft/Boot/zh-TW /Microsoft/Boot/zh-HK /Microsoft/Boot/zh-CN /Microsoft/Boot/uk-UA /Microsoft/Boot/tr-TR /Microsoft/Boot/sv-SE /Microsoft/Boot/sr-Latn-RS /Microsoft/Boot/sr-Latn-CS /Microsoft/Boot/sl-SI /Microsoft/Boot/sk-SK /Microsoft/Boot/ru-RU /Microsoft/Boot/ro-RO /Microsoft/Boot/Resources /Microsoft/Boot/qps-ploc /Microsoft/Boot/pt-PT /Microsoft/Boot/pt-BR /Microsoft/Boot/pl-PL /Microsoft/Boot/nl-NL /Microsoft/Boot/nb-NO /Microsoft/Boot/memtest.efi /Microsoft/Boot/lv-LV /Microsoft/Boot/lt-LT /Microsoft/Boot/ko-KR /Microsoft/Boot/kdstub.dll /Microsoft/Boot/kd_0C_8086.dll /Microsoft/Boot/kd_07_1415.dll /Microsoft/Boot/kd_02_8086.dll /Microsoft/Boot/kd_02_19a2.dll /Microsoft/Boot/kd_02_1969.dll /Microsoft/Boot/kd_02_15b3.dll /Microsoft/Boot/kd_02_14e4.dll /Microsoft/Boot/kd_02_1137.dll /Microsoft/Boot/kd_02_10ec.dll /Microsoft/Boot/kd_02_10df.dll /Microsoft/Boot/ja-JP /Microsoft/Boot/it-IT /Microsoft/Boot/hu-HU /Microsoft/Boot/hr-HR /Microsoft/Boot/fr-FR /Microsoft/Boot/fr-CA /Microsoft/Boot/Fonts /Microsoft/Boot/fi-FI /Microsoft/Boot/et-EE /Microsoft/Boot/es-MX /Microsoft/Boot/es-ES /Microsoft/Boot/en-US /Microsoft/Boot/en-GB /Microsoft/Boot/el-GR /Microsoft/Boot/de-DE /Microsoft/Boot/da-DK /Microsoft/Boot/cs-CZ /Microsoft/Boot/boot.stl /Microsoft/Boot/BOOTSTAT.DAT /Microsoft/Boot/bootmgr.efi /Microsoft/Boot/bootmgfw.efi /Microsoft/Boot/bg-BG /Microsoft/Boot/BCD.LOG2 /Microsoft/Boot/BCD.LOG1 /Microsoft/Boot/BCD.LOG /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TMContainer00000000000000000002.regtrans-ms /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TMContainer00000000000000000001.regtrans-ms /Microsoft/Boot/BCD{3f8eb3f6-3f05-11e3-beb1-008cfa4bd064}.TM.blf /Microsoft/Boot/BCD /ubuntu/shimx64.efi /ubuntu/MokManager.efi /ubuntu/grubx64.efi /ubuntu/grub.cfg /ubuntu/fwupx64.efi /ubuntu/fw /toshiba/Boot /Microsoft/Recovery /Microsoft/Boot /Boot/bootx64.efi /Boot/bkpbootx64.efi
    ls sda2: boot-sav
    BOOTSECT.BAK
    EFI  . Please report this message to boot.repair@gmail.com
    Add /mnt/boot-sav/sda8/boot/efi efi entries in /mnt/boot-sav/sda8/etc/grub.d/25_custom
    Adding custom /mnt/boot-sav/sda8/boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
    Adding custom /mnt/boot-sav/sda8/boot/efi/EFI/Boot/bkpbootx64.efi
    sda2/bkpbootx64.efi already added
    Adding custom /mnt/boot-sav/sda8/boot/efi/EFI/ubuntu/fwupx64.efi
    Adding custom /mnt/boot-sav/sda8/boot/efi/EFI/ubuntu/MokManager.efi
    sda2/bootmgfw.efi already added
    Adding custom /mnt/boot-sav/sda8/boot/efi/EFI/toshiba/Boot/bootmgfw.efi
    Installing for x86_64-efi platform.
    Installation finished. No error reported.
    grub-install --efi-directory=/boot/efi --target=x86_64-efi --uefi-secure-boot : exit code of grub-install :0

    chroot /mnt/boot-sav/sda8 efibootmgr -v
    BootCurrent: 0000
    Timeout: 2 seconds
    BootOrder: 0004,2001,0003,2003,2002
    Boot0000* EFI USB Device (USB DISK 3.0) PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(2,0)/HD(1,MBR,0x93,0x800,0x75ff800)RC
    Boot0001* EFI Network 0 for IPv6 (00-8C-FA-4B-D0-64)    PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(008cfa4bd064,0)/IPv6([::]:<->[::]:,0,0)RC
    Boot0002* EFI Network 0 for IPv4 (00-8C-FA-4B-D0-64)    PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(008cfa4bd064,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
    Boot0003* Windows Boot Manager  HD(2,GPT,296f4660-a39b-11e2-a1a5-d6452f6c7727,0x200800,0x82000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...s................
    Boot0004* ubuntu    HD(2,GPT,296f4660-a39b-11e2-a1a5-d6452f6c7727,0x200800,0x82000)/File(EFIubuntushimx64.efi)
    Boot0006* EFI Network 0 for IPv6 (00-8C-FA-4B-D0-64)    PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(008cfa4bd064,0)/IPv6([::]:<->[::]:,0,0)RC
    Boot0007* EFI Network 0 for IPv4 (00-8C-FA-4B-D0-64)    PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(008cfa4bd064,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
    Boot2001* EFI USB Device    RC
    Boot2002* EFI DVD/CDROM RC
    Boot2003* EFI Network   RC

    chroot /mnt/boot-sav/sda8 update-grub
    Generating grub configuration file ...
    Found linux image: /boot/vmlinuz-4.4.0-31-generic
    Found initrd image: /boot/initrd.img-4.4.0-31-generic
    Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
    Adding boot menu entry for EFI firmware configuration
    Unhide GRUB boot menu in sda8/boot/grub/grub.cfg

    Boot successfully repaired.

    You can now reboot your computer.

    If your computer reboots directly into Windows, try to change the boot order in your BIOS.
    If your BIOS does not allow to change the boot order, change the default boot entry of the Windows bootloader.
    For example you can boot into Windows, then type the following command in an admin command prompt:
    bcdedit /set {bootmgr} path \EFI\ubuntu\shimx64.efi

Initramfs after Kubuntu 16.04 installation - possibly partitioning error

https://askubuntu.com/questions/794752/initramfs-after-kubuntu-16-04-installation-possibly-partitioning-error

I installed Kubuntu 16.04 on my desktop, which had Windows 8.1 installed. The dual boot options appear, but when I try to boot into Kubuntu, I get stuck at an (initramfs) _ prompt in the terminal. Booting with a live USB, sudo fdisk -lu returns this:

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
Disklabel type: dos
Disk identifier: 0x730c4ee9

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdb1  *          2048     206847     204800   100M  7 HPFS/NTFS        /exFAT
/dev/sdb2           206848 1502089214 1501882367 716.2G  7 HPFS/NTFS        /exFAT
/dev/sdb3       1952602112 1953521663     919552   449M 27 Hidden NTFS     WinRE
/dev/sdb4       1502089215 1952602111  450512897 214.8G  5 Extended
/dev/sdb5       1502089216 1919082495  416993280 198.9G 83 Linux
/dev/sdb6       1919084544 1952602111   33517568    16G 82 Linux swap /     Solaris

Partition 4 does not start on physical sector boundary.
Partition table entries are not in disk order.

How can I make GRUB boot by default instead of Windows Boot Manager?

https://askubuntu.com/questions/788941/how-can-i-make-grub-boot-by-default-instead-of-windows-boot-manager

I'm dual booting with Windows 10, and it sets WBM ("OS Boot Manager" in the menu.) above grub. I want to have it boot grub.

HP Sleekbook Pavilion.

I have UEFI mode on both OSs.

Column select in Mousepad?

https://askubuntu.com/questions/647854/column-select-in-mousepad

Mousepad is the default text editor of Xubuntu. Is there a column select mode in Mousepad? How can I enable it?

Flashing cursor on system boot

https://askubuntu.com/questions/592715/flashing-cursor-on-system-boot

I'm trying to install the latest version of Ubuntu using a USB stick. I had Windows 7 running normally when I installed Ubuntu. I created a primary-swap and logical-ext4 ( / ) partitions for Ubuntu. When I start the machine, all I see is a flashing cursor instead of the grub boot menu.

configfile FILE                         device DRIVE DEVICE
displayapm                              displaymem
find FILENAME                           geometry DRIVE [CYLINDER HEAD SECTOR [
halt [--no-apm]                         help [--all] [PATTERN ...]
hide PARTITION                          initrd FILE [ARG ...]
kernel [--no-mem-option] [--type=TYPE]  makeactive
map TO_DRIVE FROM_DRIVE                 md5crypt
module FILE [ARG ...]                   modulenounzip FILE [ARG ...]
pager [FLAG]                            partnew PART TYPE START LEN
parttype PART TYPE                      quit
quietboot                               reboot
root [DEVICE [HDBIAS]]                  rootnoverify [DEVICE [HDBIAS]]
serial [--unit=UNIT] [--port=PORT]      [-- setkey [TO_KEY FROM_KEY]
setup [--prefix=DIR] [--stage2=STAGE2_  terminal [--dumb] [--no-echo] [--no-ed
terminfo [--name=NAME --cursor-address  testvbe MODE
unhide PARTITION                        uppermem KBYTES
vbeprobe [MODE]

grub> quit
quit

ubuntu@ubuntu:~$ sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
NAME   FSTYPE   SIZE MOUNTPOINT LABEL
sda           298.1G
├─sda1 ntfs     100M            System Reserved
├─sda2 ntfs     93.1G
├─sda3 swap      7.6G [SWAP]
├─sda4             1K
└─sda5 ext4     84.8G
sdb             15G
└─sdb1 vfat       15G /cdrom     UUI
sr0            1024M
loop0  squashfs  953M /rofs
ubuntu@ubuntu:~$ sudo grub
Probing devices to guess BIOS drives. This may take a long time.

[ Minimal BASH-like line editing is supported.   For
  the   first   word,  TAB  lists  possible  command
  completions.  Anywhere else TAB lists the possible
  completions of a device/filename. ]

grub> root hd(0,0)
root hd(0,0)

Error 11: Unrecognized device string
grub> root (hd0,0)
root (hd0,0)
grub> setup (hd0)
setup (hd0)

Error 17: Cannot mount selected partition
grub>

DM-Crypt does not accept passphrase

https://askubuntu.com/questions/576848/dm-crypt-does-not-accept-passphrase

The partition table is:

sda1 - /boot

sda2 - dmcrypt with LVM, containing root, home and swap volumes

Cryptsetup does not accept passphrase, that have been used for a long time and can not have any mistakes. I tried to mount it using PXE Live Ubuntu:

root@ubuntu:~# cryptsetup luksOpen /dev/sda2 vgroot
Enter passphrase for /dev/sda2: 
No key available with this passphrase.

On the live image US keyboard layot is only one by default. Copying and pasting of passphrase does not help too.

A month ago I have successfully mounted the dm-crypt on the same live image to chroot.

I have Ubuntu 14.04 installed and 13.10 live image on PXE boot.

curl to tar to zip not working properly

https://askubuntu.com/questions/523736/curl-to-tar-to-zip-not-working-properly

I am wanting to download an tar.gz archive, extract it and compress it into a zip file in one command. Reason for this is to be independent from temporary files.

The command I use:

curl -L "someURL" | tar xOzf - | zip -qr > /home/username/filename.zip

gives me a zip File that contains a file named -.

Removing the - from the tar command leaves me with an zip file only containing a small portion of the downloaded file, while beeing a very large archive.

Maybe I am missing something out here...

Ubuntu is not booting from USB, No Continue option in the installer when choosing to install alongside Windows

https://askubuntu.com/questions/519457/ubuntu-is-not-booting-from-usb-no-continue-option-in-the-installer-when-choosin

I have Windows 8.1 installed on my laptop. I want to install Ubuntu alongside Windows 8.1 as a dual boot. I have burned Ubuntu 14.04 to a USB flash drive, but when I restart my laptop and go to the boot menu Ubuntu cannot boot from USB. I have made a separate partition of 20 GB. Please help me to install from the USB. I have also tried Wubi for 12.04, but it gives an error.

Update:

I have done booting from USB helping with answers. and now on installation step, when I choice Install Ubuntu alongside Windows 8", I have no Continue option button to continue the installation.

Here is the screenshot of this step:

Dual boot Windows 7 UEFI RAID with Ubuntu 14.04 grub2 problem

https://askubuntu.com/questions/486250/dual-boot-windows-7-uefi-raid-with-ubuntu-14-04-grub2-problem

I used the Intel RAID 0 to RAID SSD #1 and #2 on RAID 0 for video editing work, and everything was good. I installed Windows 7 64-bit on an Asus x79 deluxe motherboard on these RAID 0 two SSDs using UEFI+gpt, and all went good.

I then installed 64-bit Ubuntu 14.04 on a third non-RAID SSD # 3 with manual partitioning and I got gpt and UEFI on that and everything is almost all good. I can browse and see the Windows RAID Windows partition, but grub2 does not see list Windows UEFI.

In UEFI BIOS I can select UEFI Windows Boot Manager or UEFI Ubuntu boot manager and each will boot respectively from their own boot manager, however I want to add the UEFI Windows Boot Manager to grub2 so I can select the OS from grub2 and not have to go into the BIOS to choose an OS.

How can I do this? I tried Boot-Repair, but it seems to screw things up to the point of reinstalling the OS. I wonder if there's a way to manually add the Windows bootloader to grub2 and daisy chain UEFI Windows Boot Manager?

Samba file share permissions issue

https://askubuntu.com/questions/403252/samba-file-share-permissions-issue

I have a quick question in regards to Samba share. I have recently built an Ubuntu server and moved all my previous Windows NTFS HDD into the server. My goal is to share all 4 HDD to utilize on my other Windows machines and to share through Plex media server. I have shared the HDD through Ubuntu but I can't change permissions and even when trying to manually configure through smb.conf I can't get the permissions to successfully change. I have attached what I have configured in the smb.conf. Any help would be greatly appreciated. Here is the rest of the smb.conf for reference.

[global]

   workgroup = WORKGROUP
   server string = %h server (Samba, Ubuntu)
   wins support = yes
   dns proxy = no



   log file = /var/log/samba/log.%m
   max log size = 1000

   syslog = 0
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######


  security = user
  encrypt passwords = true
  passdb backend = tdbsam
  obey pam restrictions = yes
  unix password sync = yes


  passwd program = /usr/bin/passwd %u
  passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n     *password\supdated\ssuccessfully* .

  pam password change = yes

  map to guest = bad user


#======================= Share Definitions =======================

  realm = localdomain
  server role = domain controller
  server services = +smb -s3fs
  dcerpc endpoint servers = -winreg -srvsvc
[printers]
  comment = All Printers
  browseable = no
  path = /var/spool/samba
  printable = yes
  guest ok = no
  read only = yes
  create mask = 0700


[print$]
  comment = Printer Drivers
  path = /var/lib/samba/printers
  browseable = yes
  read only = yes
  guest ok = no


# Ross's Shares
[share]
    comment = home
    path = /home/roce/Downloads
    browsable = yes
    guest ok = yes
    read only = no
    create mask = 0777

[share]
    comment = SDB - Data
    path = /home/roce/Data
    browsable = yes
    guest ok = yes
    read only = no
    create mask = 0777

[share]
    comment = SDC - Movies
    path = /home/roce/Movies
    browsable = yes
    guest ok = yes
    read only = no
    create mask = 0777

[share]
    comment = SDD - TV Shows
    path = /home/roce/TV Shows
    browsable = yes
    guest ok = yes
    read only = no
    create mask = 0777

[share]
    comment = SDE
    path = /home/roce/Data
    browsable = yes
    guest ok = yes
    read only = no
    create mask = 0777

[sysvol]
  path = /var/lib/samba/sysvol
  read only = no

[netlogon]
  path = /var/lib/samba/sysvol/localdomain/scripts
  read only = no

Ubuntu 12.04.2 Dual boot UEFI Windows 8 Preinstalled CX21903W Ultrabook [duplicate]

https://askubuntu.com/questions/327897/ubuntu-12-04-2-dual-boot-uefi-windows-8-preinstalled-cx21903w-ultrabook

I have a problem when trying to install Ubuntu. The machine is a CX Ultrabook model CX.21903W Intel I5 with 500GB hard disk, 8 GB RAM and 32 GB SSD.

From How do I install Ubuntu alongside a pre-installed Windows with UEFI?, and according to the steps guide:

We create a partition from Windows 8 (70 GB) using the Windows 8 program.
Confirm-SecureBootUEFI=True.
From Windows 8, shift + Restart and from the special menu we selected the UEFI Firmware Setting.
From BIOS Option:

Option 1) Disable Secure Boot.
Option 2) Disable UEFI (Not Available)
from Option 1: Three ways are available.
With Secure Boot enabled -> We can't even boot Ubuntu. A red window saying Soft unproper signed.

With Secure Boot disabled -> and this config in boot device order:

1 - UEFI: USB
2 - Windows Boot Manager
3 - Others

with CSM (Compatibility Support Module): enable -> GRUB appears and selecting try Ubuntu then a black window appears and nothing happens. The same result occurs if Install Ubuntu is selected.
With Secure Boot disabled -> and this config in boot device order:

1 - USB (No UEFI)
2 - Windows Boot Manager
3 - Others

with CSM (Compatibility Support Module): enable -> GRUB appears and selecting try Ubuntu, -> Ubuntu boots and we can even install it.

Rebooting and just changing the boot order as

1 - Ubuntu []
2 - Windows Boot Manager
3 - Others

then nothings happens.

Booting from live USB again and, as per instructed, making Boot-Repair (A warning window: Ubuntu is working in legacy mode.).
Saving changes and rebooting, Grub works but selecting Ubuntu, a black window appears and nothing happens. Selecting Windows 8, Windows 8 boots and works.

Up until now we are unable to install Ubuntu.