Cannot boot after fresh install of Manjaro KDE with encrypted disk

I just installed Manjaro KDE full last night and encrypted the disk using LUKS. After install, I was able to reboot once, but since then everytime I try to boot the system it hangs on the screen that appears after inputting my encryption password (it is a screen with 3 blinking dots and “Manjaro” at the bottom of the screen).

Here is my system information (as I cannot access Manjaro presently, the information was obtained by using inxi on the same laptop running PuppyLinux):

  Kernel: 5.4.53 x86_64 bits: 64 compiler: gcc v: 9.3.0 
  parameters: BOOT_IMAGE=/vmlinuz pmedia=usbflash 
  pdrv=8d5b71b5-b7b9-4164-a482-7b662ecdf4a0 pfix=fsck,fsckp 
  Desktop: JWM 2.4.0 dm: xinit Distro: Puppy 9.5 
  Type: Laptop System: LENOVO product: 20AWS1BB00 v: ThinkPad T440p 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: LENOVO model: 20AWS1BB00 v: 0B98401 WIN serial: <filter> 
  UEFI [Legacy]: LENOVO v: GLET74WW (2.28 ) date: 10/21/2014 
  ID-1: BAT0 charge: 28.1 Wh condition: 53.2/56.2 Wh (95%) volts: 10.9/10.8 
  model: LGC 45N1147 type: Li-ion serial: <filter> status: Discharging 
  Topology: Dual Core model: Intel Core i5-4300M bits: 64 type: MT MCP 
  arch: Haswell family: 6 model-id: 3C (60) stepping: 3 microcode: 1C 
  L1 cache: 64 KiB L2 cache: 3072 KiB L3 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 20752 
  Speed: 3183 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 2595 2: 2595 
  3: 2596 4: 2595 
  Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
  Type: l1tf mitigation: PTE Inversion 
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; 
  SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass status: Vulnerable 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 
  mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Vulnerable: No microcode 
  Type: tsx_async_abort status: Not affected 
  Device-1: Intel 4th Gen Core Processor Integrated Graphics 
  vendor: Lenovo ThinkPad T440p driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:0416 
  Display: server: X.Org 1.20.8 driver: modesetting compositor: picom 
  resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) 
  v: 4.5 Mesa 20.0.8 compat-v: 3.0 direct render: Yes 
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
  vendor: Lenovo ThinkPad T440p driver: snd_hda_intel v: kernel 
  bus ID: 00:03.0 chip ID: 8086:0c0c 
  Device-2: Intel 8 Series/C220 Series High Definition Audio 
  vendor: Lenovo ThinkPad T440p driver: snd_hda_intel v: kernel 
  bus ID: 00:1b.0 chip ID: 8086:8c20 
  Sound Server: ALSA v: k5.4.53 
  Device-1: Intel Ethernet I217-LM vendor: Lenovo ThinkPad T440p 
  driver: e1000e v: 3.2.6-k port: 3080 bus ID: 00:19.0 chip ID: 8086:153a 
  IF: eth0 state: down mac: <filter> 
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: efa0 
  bus ID: 03:00.0 chip ID: 8086:08b2 
  IF: wlan0 state: up mac: <filter> 
  Local Storage: total: 148.08 GiB used: 20.77 GiB (14.0%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda vendor: Samsung model: MZ7LN128HCHP-000L1 size: 119.24 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 4L0Q scheme: MBR 
  ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 2.0 
  size: 28.84 GiB block size: physical: 512 B logical: 512 B 
  serial: <filter> rev: PMAP scheme: MBR 
  System Temperatures: cpu: 53.0 C mobo: 0.0 C 
  Fan Speeds (RPM): cpu: 0 
  Processes: 189 Uptime: 1h 06m Memory: 7.48 GiB used: 2.19 GiB (29.3%) 
  Init: SysVinit v: N/A runlevel: 35 Compilers: gcc: 9.3.0 alt: 9 
  Shell: bash v: 5.0.17 running in: terminator inxi: 3.0.38

And here is the last log entry from /var/log from my last attempt to boot:

e%G/dev/mapper/luks-1f6d2a8a-2637-4e1c-ae19-a3a5b7e59ea7: clean, 344639/7241728 files, 3632101/28950838 blocks
[e[0;32m  OK  e[0m] Finished e[0;1;39mTell Plymouth To Write Out Runtime Datae[0m.
[e[0;32m  OK  e[0m] Mounted e[0;1;39mArbitrary Executable File Formats File Systeme[0m.
[e[0;32m  OK  e[0m] Finished e[0;1;39mSet Up Additional Binary Formatse[0m.
[e[0;32m  OK  e[0m] Finished e[0;1;39mCreate Volatile Files and Directoriese[0m.
         Starting e[0;1;39mRecord System Boot/Shutdown in UTMPe[0m...
[e[0;32m  OK  e[0m] Finished e[0;1;39mRecord System Boot/Shutdown in UTMPe[0m.
[e[0;32m  OK  e[0m] Reached target e[0;1;39mSystem Initializatione[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mCUPS Schedulere[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mRefresh existing P…f archlinux-keyring regularlye[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mDaily rotation of log filese[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mDaily man-db regeneratione[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mMonthly clean packages cachee[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mGenerate mirrorlist weeklye[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mpkgfile database update timere[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mDaily verification of password and group filese[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mDaily Cleanup of Temporary Directoriese[0m.
[e[0;32m  OK  e[0m] Reached target e[0;1;39mPath Unitse[0m.
[e[0;32m  OK  e[0m] Reached target e[0;1;39mTimer Unitse[0m.
[e[0;32m  OK  e[0m] Listening on e[0;1;39mCUPS Schedulere[0m.
[e[0;32m  OK  e[0m] Listening on e[0;1;39mD-Bus System Message Bus Sockete[0m.
[e[0;32m  OK  e[0m] Reached target e[0;1;39mSocket Unitse[0m.
[e[0;32m  OK  e[0m] Reached target e[0;1;39mBasic Systeme[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mPeriodic Command Schedulere[0m.
         Starting e[0;1;39mD-Bus System Message Buse[0m...
         Starting e[0;1;39mAuthorization Managere[0m...
         Starting e[0;1;39mUser Login Managemente[0m...
[e[0;32m  OK  e[0m] Started e[0;1;39mD-Bus System Message Buse[0m.
         Starting e[0;1;39mNetwork Managere[0m...
[e[0;32m  OK  e[0m] Listening on e[0;1;39mLoad/Save RF …itch Status /dev/rfkill Watche[0m.
[e[0;32m  OK  e[0m] Started e[0;1;39mAuthorization Managere[0m.
         Starting e[0;1;39mModem Managere[0m...
[e[0;32m  OK  e[0m] Started e[0;1;39mNetwork Managere[0m.
[e[0;32m  OK  e[0m] Reached target e[0;1;39mNetworke[0m.
         Starting e[0;1;39mCUPS Schedulere[0m...
         Starting e[0;1;39mPermit User Sessionse[0m...
[e[0;32m  OK  e[0m] Finished e[0;1;39mPermit User Sessionse[0m.
         Starting e[0;1;39mHold until boot process finishes upe[0m...
         Starting e[0;1;39mTerminate Plymouth Boot Screene[0m...

Any help in identifying what the problem is when trying to boot would be deeply appreciated. Especially since I’d love to avoid going through an entirely fresh install and configuring everything again. :wink:

If your system boots after a fresh encrypted install (this is full disk encryption incl. boot) and subseqently refuse to boot - then logically something happened in-between …

The question is what

It is possible to hit Esc during boot to hide the loader - perhaps this will hint as to what is going on.

EDIT: just tested the minmal Plasma ISO from

Full disk encryption - boots like a cheetah - so I am inclined to believe that previous slow decryption when using GRUB boot loader is now in the past.

At least for my test system

 $ systemd-analyze
Startup finished in 3.993s (firmware) + 1min 14.876s (loader) + 8.835s (kernel) + 4.298s (userspace) = 1min 32.004s reached after 4.297s in userspace.
 $ inxi -SGCmD
  Host: cheetah Kernel: 6.2.2-1-MANJARO arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.27.2 Distro: Manjaro Linux
  RAM: total: 15.5 GiB used: 1.82 GiB (11.8%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
  Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 1837 min/max: 400/4000 cores: 1: 2000 2: 2000 3: 2000
    4: 2000 5: 702 6: 2000 7: 2000 8: 2000
  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
  Device-2: Chicony USB2.0 Camera type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 21.1.7 driver: X: loaded: modesetting
    dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 620 (KBL
  Local Storage: total: 465.76 GiB used: 9.12 GiB (2.0%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB

I have rebooted the system several times now and there is no problems.

Do you any specific reason for 5.4 kernel? - just noted the Puppy 9.5 must be some live system

6.1 is the new LTS.

Could you please boot from the Manjaro Live USB you used to install from?

I would like to see the output from

sudo fdisk -l

I cannot know for sure - I have a suspicion - the output would help clarify

Thank you again linux-aarhus.

Below is the output from sudo fdisk -l (for reference, sda is my internal ssd and the one that Manjaro KDE is installed on):

Disk /dev/sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: SAMSUNG MZ7LN128
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x714ed7dd

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048 231612851 231610804 110.4G 83 Linux
/dev/sda2       231612852 250067789  18454938   8.8G 83 Linux

Disk /dev/sdb: 28.84 GiB, 30966546432 bytes, 60481536 sectors
Disk model: DataTraveler 2.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdb1  *         64 8013115 8013052  3.8G  0 Empty
/dev/sdb2       8013116 8021307    8192    4M ef EFI (FAT-12/16/32)

Disk /dev/loop0: 30 MiB, 31453184 bytes, 61432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 867.5 MiB, 909635584 bytes, 1776632 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 1.89 GiB, 2030391296 bytes, 3965608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop3: 1003.02 MiB, 1051746304 bytes, 2054192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

I Will look at it tomorrow. At a glance I note it is a BIOS MBR installation.

I cannot deduct if this should be an issue as partitions correlate with the installation.

Your boot loader should be installed to the MBR on sad - do you remember doing so?

I do not recall doing so; I used the full disk option when I first installed. But your comment there led me to go back and try reinstalling Manjaro using the manual partition option in the installer. Took some research as I’m not super adept with Linux, but I did manage to manually partition my hard drive so that I now have a mbr and a swap partition, as well as encrypted root and home folders. Since doing so I’ve been able to boot without any issues.

Thank you so much for your help!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.