The Stack Overflow podcast is back! Listen to an interview with our new CEO.

Hot answers tagged

6

Persistent live drive with a partition for persistence Yes, there are some web sites describing new tools and new features in [new versions of] old tools that can create a persistent live drive from an iso file with Ubuntu 19.10 and the corresponding Ubuntu family flavours. A new feature or fixed bug ('feature request' or 'bug fix' according to this link) ...


3

It is simply sending the error message "/blah/blah/: Is directory" to stderr instead of stdout: Bash command that prints a message on stderr The messages for stdout and stderr will still appear on your screen. Some applications will treat stderr messages differently though and perform special processing. Most people don't bother redirecting echo error ...


3

The program isohybrid from the package syslinux-utils converts an iso file that can be burned to a bootable CD/DVD to a hybrid iso file, that can be burned to a bootable CD/DVD and cloned to a bootable mass storage device: USB pendrive, USB SSD, memory card, internal HDD, internal SSD ... It is possible to use the robust cloning method to create a boot ...


3

Conversion of Dynamic disk to Basic disk is the first step, as recommended by Microsoft (who no longer recommend Dynamic Disks): https://docs.microsoft.com/en-us/windows/win32/fileio/basic-and-dynamic-disks However, first make a backup of your data, then verify it matches the source files. Then, make a second backup to a different destination (drive or ...


2

You will need to install Ubuntu to the NVMe drive, but install grub to the boot sector of the SATA drive. Then you should boot from the SATA drive with the NVMe as the main storage medium while running Ubuntu. You likely will also need to have the /boot partition with the kernel and initrd on the SATA drive, in case grub also cannot not see the NVMe as ...


2

I don't know if you have tried this Open a terminal, type sudo nano /etc/default/grub change the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" and run update-grub


1

This sounds like a graphics problem. To confirm, please follow these steps: Power on your machine with the Ubuntu boot-able installation USB connected. You might need to hold the left Shift at boot to see this screen: Press F6 to bring up the Other Options menu. Select nomodeset and press Enter so it becomes selected with an x in front of it like in the ...


1

Apparently this is a bug in Grub 2.04, which is shipped by Ubuntu 19.10. See: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317 https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289 You might consider either downgrading the version of Grub on your system or waiting for a fixed version.


1

The instructions on boot-repair report tell you to boot into Windows (as you do now by changing boot order) and then: 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 Do this from Windows and then if it doesn't work revise your question with current status ...


1

I can answer my question myself :-) It was indeed disabling SWAP - the old swap partition (which was deleted) was still entered in /etc/fstab. So if any of you encounter a long boot time, here are my steps: Press ESC while boot to see the boot log or look at the boot log /var/logs/boot.log. Look for "A start job..." this usually points to some uuid (hard ...


1

A few services can be disabled to reduce the boot-up time with no effect on the desktop environment functionality in most cases: Firstly: POSTFIX appears in your post. If your machine is not a mail server and you do not use POSTFIX you can disable the postfix.service by running the following command in the terminal: sudo systemctl disable postfix.service ...


1

Kali linux probably formatted the swap partition, and your Ubuntu is looking (and waiting) for the old swap UUID to appear, before eventually timeout occurs & it gives up (thus slower boot). You need to change the UUID's for your old swap partition to match your new UUID. As windows doesn't use a "linux" swap partition, it's boot-up speed will be ...


1

On another thread here, someone suggested using an alternate installation, and it worked! I have Ubuntu working on my Wyse 3040 thin client! The installation image that I got from the main download page was named: Ubuntu-18.04.3-live-server-amd64.iso This installation kit failed to find any block devices to install onto on two different systems (the Wyse and ...


1

Check your /etc/fstab file with this command: findmnt --verify This will check your fstab for errors and ensure that the mount devices are accessible. Specifically, Systemd-fstab-generator[44]: Mount point 0 is not a valid path,ignoring might mean that there is an extra line break or some extra white space in a line in your fstab. Replacing all of the ...


1

I had similar problem with me and none of the above suggestion worked for me. To save someone else from complete reinstall better do this... this is what I did: Press Ctrl+Alt+F2 Login to your username Remove your Display Manager (e.g. GNOME) and reinstall other Display Manager e.g. (MATE) After that my above problem was resolved!


Only top voted, non community-wiki answers of a minimum length are eligible