Ubuntu wont finish booting up in fresh install

Seeing how today the new version of Ubuntu comes out I wanted to install it in my laptop. I installed the ISO image in a USB with Rufus, booted up the USB in my laptop without issues, and installed Ubuntu while changing the partitions I previously had (Deleted a Windows I never used, with the booting partition that Windows creates for itself, plus my / and /home partitions).

Made the new partitions (ext4 /boot at the start, swap, ext4 /home and ext4 / plus an NTFS partition that I use to store files and info, I left this partition as is) and installed without issues.

So, right when I reboot, it boots into Ubuntu fine but it hangs at the initial services startup, I’m not sure if a service is hanging or what but I always end up with a screen looking like this (see image) boot picture showing the starting services

That “Hold until boot process finishes up” never seems to finish, or there must be a service that never starts (or finishes), so it never ends.

If I push the power button the laptop powers off, so there must be something holding this stage of the boot up.

My laptop is an MSI CX61 2PC, and never had a problem like this before.

I’m gonna have to go back to 18.04 :/

Booting 19.04 from LUKS system drive

I’m trying to install Kubuntu 19.04 on an encrypted system drive with LUKS. The installation finishes, but GRUB doesn’t ask for a password and the system won’t boot.

I’ve found a few other questions about this, but they result in dead links or tell me to set CRYPTFS=y and run update-initramfs. I think this is already the default in Ubuntu 19.04, but I tried it anyway and it doesn’t work.

How can I make GRUB ask for a password on boot?

Summary

  1. Disks:
    • /dev/sda1: /boot/efi, unencrypted
    • /dev/sda2: /boot, unencrypted
    • /dev/sda3, /dev/mapper/cryptroot: /, encrypted
  2. Installed Kubuntu using the mount points above
  3. Added cryptdevice=UUID=6d5b5f47-58e8-4a9c-89c8-4f503f35ff3f:cryptroot root=/dev/mapper/cryptroot to /etc/default/grub and ran update-grub in chroot
  4. I see GRUB, I see the Kubuntu splash screen and then just a blinking underscore

Details

  1. Boot from live CD
  2. Partition disk using sudo fdisk /dev/sda

    • /dev/sda1: EFI System
    • /dev/sda2: Linux filesystem
    • /dev/sda3: Linux filesystem
    Welcome to fdisk (util-linux 2.33.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command.  Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x087d3a28.  Command (m for help): g Created a new GPT disklabel (GUID: 73F157B8-7425-7844-AE8E-3A46EF2ED5A4).  Command (m for help): n Partition number (1-128, default 1):  First sector (2048-20971486, default 2048):  Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-20971486, default        20971486): +128M  Created a new partition 1 of type 'Linux filesystem' and of size 128 MiB.  Command (m for help): t Selected partition 1 Partition type (type L to list all types): 1 Changed type of partition 'Linux filesystem' to 'EFI System'.  Command (m for help): n Partition number (2-128, default 2):  First sector (264192-20971486, default 264192):  Last sector, +/-sectors or +/-size{K,M,G,T,P} (264192-20971486, default        20971486): +512M  Created a new partition 2 of type 'Linux filesystem' and of size 512 MiB.  Command (m for help): n Partition number (3-128, default 3):  First sector (1312768-20971486, default 1312768):  Last sector, +/-sectors or +/-size{K,M,G,T,P} (1312768-20971486, default        20971486):   Created a new partition 3 of type 'Linux filesystem' and of size 9.4 GiB.  Command (m for help): w  The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. 
  3. Encrypt root partition using sudo cryptsetup -y -v luksFormat --type luks2 /dev/sda3

  4. Mount the encrypted drive using sudo cryptsetup open /dev/sda3 cryptroot
  5. Format the partitions:
    1. EFI partition: sudo mkfs.vfat /dev/sda1
    2. Boot partition: sudo mkfs.ext4 /dev/sda2
    3. Root partition: sudo mkfs.ext4 /dev/mapper/cryptroot
  6. Install Kubuntu using these devices (/dev/sda1, /dev/sda2 and /dev/mapper/cryptroot)
  7. Chroot into the installed Kubuntu:

    1. Mount required devices:

      sudo mount /dev/mapper/cryptroot /mnt sudo mount --bind /dev /mnt/dev sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount /dev/sda2 /mnt/boot 
    2. Adjust kernel parameters (/etc/default/grub):

      GRUB_CMDLINE_LINUX="cryptdevice=UUID=6d5b5f47-58e8-4a9c-89c8-4f503f35ff3f:cryptroot root=/dev/mapper/cryptroot" 

      I’ve also tried:

      GRUB_CMDLINE_LINUX="rd.luks.name=6d5b5f47-58e8-4a9c-89c8-4f503f35ff3f=cryptroot root=/dev/mapper/cryptroot" 
    3. Run update-grub

  8. Reboot, when I boot without quiet I see the following output:

    [some other output]  Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device.  Common problems:  - Boot args (cat /proc/cmdline)    - Check rootdelay= (did the system wait long enough?)  - Missing modules (cat /proc/modules; ls /dev) ALERT!  /dev/mapper/cryptroot does not exist.  Dropping to a shell!  [BusyBox shell] 

Is removing hiberfil.sys file the solution of my no longer booting, hibernated Windows 10?

Short said, would removing the hiberfil.sys file from my Windows 10 partition allow it to boot again after it “got broken” due to conflict with Grub + Ubuntu?

My Windows 10 partition no longer wants to boot, after -I suppose by reading a lot on same issue- it stopped with hibernation or fast startup.

It starts by “preparing auto repair…” It starts by "preparing auto repair..."

Then always fails on booting, allowing either Restart or advanced options. Then always fails on booting, allowing either Restart or advanced options.

From this answer, I see ntfs-3g tool (which I discovered is installed, and a NTFS driver) has a remove_hiberfile option that would delete this file to allow read-write mount of windows partition on Ubutun again. (which is an issue but not my main issue, being, Windows no longer accept to boot at all)

   remove_hiberfile           When the NTFS volume is hibernated, a read-write mount  is  denied  and  a  read-only           mount  is forced. One needs either to resume Windows and shutdown it properly, or use           this option which will remove the Windows hibernation file. Please note,  this  means           that  the  saved  Windows session will be completely lost. Use this option under your           own responsibility. 

Before applying this solution, and taking more risk at damaging some data, do you think it could solve my broken, no longer booting windows 10?

Here is a little more details.
I have a 1To SSD with dual boot with Grub and split as:

  1. Windows 10 (main with +/-800Gb)
  2. Ubuntu 18.04.1 (+/-70Gb)

Dual boot used to work well, until windows hibernated, then no longer accept to boot again, possibly due to an intermediate boot on Ubuntu.

Some historic:

  • windows did broke when it was on an Intel i7 6700K + motherboard MSI Z170A Gaming
  • I only could start on Ubuntu by those steps: [grub (automatically appears)] > [Ubuntu]. If I choosed Windows (or Windows boot manager), Windows failed booting.
  • since recent crash of either my motherboard or cpu, I changed to a i7 9700K + motherboard MSI Z390 Gaming carbon pro
  • with this new setup, I only can boot Ubuntu after those steps: [boots on windows] > fails with debugging/starting options on a blue screen > [Debug (meaning an “Other OS” menu] > [Ubuntu]. Difference is, I no longer get on Grub menu by default

I try to restore it myself, trying to understand what is wrong, read a lot on same topic, but agree not to be confortable with MBR, EFI, UEFI, boot flag, etc… Some answer are about fast restart and how to disable it, on Windows, which I can’t since my windows don’t boot.

Here is what GParted says today: enter image description here

We can see:

  • /dev/sda1: some windows required partition I think (récupération == recovery)
  • /dev/sda2: an EFI partition which has boot flag
  • /dev/sda3: a Windows reserved partition on /dev/sda3, but its filesystem is unknown, and used space (on a 16MB total) cannot be calculated. Looks like broken?
  • /dev/sda4: my main windows partition
  • /dev/sda[5-6]: Ubuntu

Chain of security by booting Linux

I am curious if there is any solution that ensures that the actual OS I start is safe. I have SecureBoot on my microserver, and that way I can ensure, that GRUB is safe. But what about the drive encryption software, the OS and the installed applications? Is there any working solution or best practice in the topic?

Ubuntu EFI boot entry created on its own, even if just booting Live-USB

On my Windows 10 laptop, (UEFI Secure boot), I can boot from Ubuntu18:04 live-USB, successfully. I don’t actually install Ubuntu ( I choose “Try Ubuntu”). Still, when I reboot (after proper Shutdown and removing USB), I get Windows boot menu with Win-10 and Ubuntu as option. It means, this EFI entry is being created on its own, even if it is just a live-cd session.

Each time, I have to manually remove the EFI boot entry. How can I avoid this situation ? Please help.

Moved home-folder to external drive – after booting up Apps sometimes won’t load

Bid on an 2018 Mac Mini on Ebay, when I realized that this impulse buy is an error (128GB internal drive) it was already too late. Solved that problem by moving my Home-Folder to an external thunderbolt drive, the OS and my Apps are still on the internal Flashdrive. Everything’s working fine, including Time Machine.

However, this solutions seems to cause infrequent problems at boot-up, when that external drive is recognized just fine (reading and writing is possible), but I cannot open most of my apps (Mail, Photos, Chrome). Furthermore, I get an error indicating that the iCloud login failed, and Photos/ iTunes report something about being unable to access their library, hence, they don’t work. A few Apps (Disk Utility and System Preferences) are never affected.

There are no other system-messages indicating that something’s wrong though. The only surefire solution I could figure out is rebooting, not only once, but at least 4 times consecutively.

  • How is it that the system reacts differently to 4 or 5 reboots than it does to one?
  • Is there a trick to solve this problem with just one reboot, or even without the necessity to reboot at all?

Dual booting encrypted ubuntu 18.04 and microsoft windows

Is there a way to dual boot ubuntu 18.04 with drive encryption AND windows 10? Reason being is that the ubuntu installer insists on installing encrypted ubuntu on the WHOLE DRIVE, which prevents me from making a separate partition for windows.

Normally, I would just use gparted to re-partition the drive after installation. However, luks/lvm seems to make the whole linux partition seem “full” from gparted’s perspective, thus making reducing the size of the partition impossible. I tried reducing the size of the lvm partition by several guides, but none of them seem to work.

Has anyone succeeded in finding a way to dual-boot windows?

Booting problem after force shutdown

My laptop model is HP ProBook 440 GL. My Ubuntu got hanged while i was editing stuffs in gravity designer. And forcefully shut the system by pressing power button for long time…. Then whenever I open my system it shows me three options to choose from. 1. Ubuntu 2. Advanced options for Ubuntu 3. System setup. Whenever i click on the above two options and any following options in them (in option 2), the screen shows the pattern without any text in it and get stuck over there…! I have important datas and more importantly some works to do…! Please help me out…!

Linux lite iso successfully flashed to usb but not booting

I have the latest linux lite 4.4 iso dowloaded from the official website. After that I flashed it to adata 16GB usb stick. I tried rufus, unetbootin and etcher(as suggested in the website). In case of rufus and unetbootin the usb is successfully booted like my experience of installing ubuntu and windows several times previously. But when from the bootloader list of my device I selected the usb stick. Nothing happens and it goes directly to bios menu. I tried several times also tried re-downloading the iso but the situation is same. I have booted several versions of ubuntu, debian and windows this way successfully. But does linux lite requires some different formats? Secondly in case of etcher my usb is not even detected. It only shows windows 10 and ubuntu 16.04 that is previously installed in my device. Also windows 10 is not able to read the data after flashing by etcher. After format it becomes 1.3GB insted of 14.4GB in normal case. What is the actual problem? Is my device not compatible or the iso or softwares I used is not working correctly? (Sorry for bad english)

Why is 18.04 LTS not booting after installation?

After several attempts at installation, I finally got 18.04 to boot on a live DVD and finally got it to install. However, after rebooting to boot from HDD, it hangs up after a long wait (like 6 hours) sitting at the Ubuntu logo. My machine is an i9 7960x with 128GB RAM, two Nvidia Titan P graphics cards, and a 6TB HDD. Is this too much machine for 18.04 LTS? BTW, I swapped out the HDD with an older 80GB HDD that had a 16.04 LTS install and the machine booted just fine. Why is 18.04 LTS struggling to install and boot?