Manjaro not starting XFCE when windows drive is connected via SATA

[exaveal]

Hello,

I had some troubles after installing a new M.2 SSD, moving all linux partitions from the old SSD to the new M.S SSD and using the old SSD for a windows dual boot installation.

The problem is crazy - and it looks like this:
When I dissconnect the SSD with windows installed, everything works fine. Grub is booted, I can select Manjaro, it’s asking for the passphrase. After successfull mount XFCE is starting.
When I connect the SSD with windows installed, it’s different. Grub is booted, I can select Manjaro, it’s asking for the poassphrase. After entering the password the boot seems to stop, no XFCE is shown. No console or commands on the screen. Just nothing. I can trigger to shutdown with Alt+Ctrl+Del.

/dev/sda is unused ext4 filesystem
/dev/sdb is a luks crypted ext4 filesystem mounted in home when Manjaro started
/dev/nvme0n1 is the new M.2 SSD with Grub and Manjaro
The windows drive is currently not connected - so it is not listed.

sudo fdisk -l
Festplatte /dev/sda: 223,58 GiB, 240065183744 Bytes, 468877312 Sektoren
Festplattenmodell: SanDisk SSD PLUS
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: F8AE0CC8-3B64-4000-960E-308B4EC28A7E

Gerät      Anfang      Ende  Sektoren  Größe Typ
/dev/sda1    2048 468875263 468873216 223,6G Linux-Dateisystem


Festplatte /dev/sdb: 7,28 TiB, 8001563222016 Bytes, 15628053168 Sektoren
Festplattenmodell: WDC WD80EFAX-68K
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes


Festplatte /dev/nvme0n1: 1,82 TiB, 2000398934016 Bytes, 3907029168 Sektoren
Festplattenmodell: Samsung SSD 990 EVO 2TB                 
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x0006406a

Gerät          Boot   Anfang       Ende   Sektoren Größe Kn Typ
/dev/nvme0n1p1 *        2048    2099199    2097152    1G  b W95 FAT32
/dev/nvme0n1p2       2099200   12584959   10485760    5G 83 Linux
/dev/nvme0n1p3      12584960 3907028991 3894444032  1,8T  5 Erweiterte
/dev/nvme0n1p5      12587008 3907028991 3894441984  1,8T 83 Linux


Festplatte /dev/mapper/lvm_desktop1: 1,81 TiB, 1993952198656 Bytes, 3894437888 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes


Festplatte /dev/mapper/lvm_desktop1-root: 200 GiB, 214748364800 Bytes, 419430400 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes


Festplatte /dev/mapper/lvm_desktop1-home: 1,62 TiB, 1779202785280 Bytes, 3475005440 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes


Festplatte /dev/mapper/hd_data01: 7,28 TiB, 8001561124864 Bytes, 15628049072 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes

When I later connect the windows SSD via the cable (while Manjaro system is running), it looks like this:

Festplatte /dev/sdc: 465,76 GiB, 500107862016 Bytes, 976773168 Sektoren
Festplattenmodell: Samsung SSD 850 
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: F8AE0CC8-3B64-4000-960E-308B4EC28A7E

Gerät       Anfang      Ende  Sektoren  Größe Typ
/dev/sdc1     2048   1023999   1021952   499M Windows-Wiederherstellungsumgebung
/dev/sdc2  1024000   1228799    204800   100M EFI-System
/dev/sdc3  1228800   1261567     32768    16M Microsoft reserviert
/dev/sdc4  1261568 976771071 975509504 465,2G Microsoft Basisdaten

What I read is, the “Festplattenbezeichner” of the windows drive does be exact the same like the

I tried to read the log messages, but I find nothing:

wolf@wolf-desktop:~$ journalctl -b -p3
Nov 18 10:02:36 wolf-desktop systemd-modules-load[441]: Failed to find module 'v4l2loopback-dc'
Nov 18 10:02:36 wolf-desktop systemd-modules-load[441]: Failed to find module 'vboxdrv'
Nov 18 10:02:36 wolf-desktop systemd-modules-load[441]: Failed to find module 'vboxnetadp'
Nov 18 10:02:36 wolf-desktop systemd-modules-load[441]: Failed to find module 'vboxnetflt'
Nov 18 10:43:59 wolf-desktop lightdm[1399]: gkr-pam: couldn't unlock the login keyring.
Nov 18 10:44:00 wolf-desktop pulseaudio[1510]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': activation request failed: unknown unit
wolf@wolf-desktop:~$ journalctl -b-1 -p3
Nov 18 09:46:45 wolf-desktop systemd-modules-load[442]: Failed to find module 'v4l2loopback-dc'
Nov 18 09:46:45 wolf-desktop systemd-modules-load[442]: Failed to find module 'vboxdrv'
Nov 18 09:46:45 wolf-desktop systemd-modules-load[442]: Failed to find module 'vboxnetadp'
Nov 18 09:46:45 wolf-desktop systemd-modules-load[442]: Failed to find module 'vboxnetflt'
Nov 18 10:02:01 wolf-desktop kernel: watchdog: watchdog0: watchdog did not stop!
wolf@wolf-desktop:~$ journalctl -b-2 -p3
Nov 18 09:35:18 wolf-desktop systemd-modules-load[435]: Failed to find module 'v4l2loopback-dc'
Nov 18 09:35:18 wolf-desktop systemd-modules-load[435]: Failed to find module 'vboxdrv'
Nov 18 09:35:18 wolf-desktop systemd-modules-load[435]: Failed to find module 'vboxnetadp'
Nov 18 09:35:18 wolf-desktop systemd-modules-load[435]: Failed to find module 'vboxnetflt'
Nov 18 10:34:26 wolf-desktop lightdm[1405]: gkr-pam: couldn't unlock the login keyring.
Nov 18 10:34:27 wolf-desktop pulseaudio[1516]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': activation request failed: unknown unit
Nov 18 10:43:54 wolf-desktop dbus-broker-launch[1240]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Nov 18 10:43:56 wolf-desktop systemd[1]: Failed unmounting /home/wolf/hd_data01.
Nov 18 10:43:56 wolf-desktop systemd[1]: Failed unmounting /home.
Nov 18 10:43:57 wolf-desktop systemd-cryptsetup[6263]: Device hd_data01 is still in use.
Nov 18 10:43:57 wolf-desktop systemd-cryptsetup[6263]: Failed to deactivate 'hd_data01': Device or resource busy

Is there perhaps another place where I can find logs, why XFCE did not start? I can also not reach the machine via ssh, so I think it really does not boot up.

[Mirdarthos]

Without reading anything other than the title, I think it’s because your dual-boot isn’t set up correctly. See here:

[root tip] [How To] Dual boot Manjaro and Windows

Difficulty: ★★☆☆☆ Dual boot - Step by Step Target systems Firmware Checklist Windows preparation Manjaro installation Revisions Target systems UEFI Computers with preinstalled Windows (Windows 10) is computers using UEFI firmware. This guide is a generic guide targeted at UEFI installations. However some of the guide does apply even if you are using a BIOS/MBR setup. If you are using a BIOS/MBR (DOS) partition schema watch out for this Skip if using BIOS/MBR To ensure a …

[soundofthunder]

As mentioned in your other thread on the same topic:

• Manjaro with Luks + LVM and XFCE takes one hour to boot

@exaveal

Okay, ESP is the /boot/efi partition, right?

No and Yes.

The /boot/efi is not a partition; in fact, it’s only the mount point that points to the $ESP location. However, the fat32 EFI System Partition (ESP) that it points to should indeed be the $ESP.

@exaveal

Why would I need a second ESP?

In most cases, you don’t (it’s generally not recommended); however, some like to create an extra partition to overcome some perceived difficulties.

@exaveal

I don’t have the understanding needed of how this all works.

That I can’t help you with, but I can point out a few things I’ve noticed, which may be of interest to others wishing to help:

/dev/nvme0n1p3 appears to be an extended partition type. This might indicate that the disk partitions were created atop an MSDOS/MBR partition table. For the purposes of UEFI booting, the $ESP and all patitions need to be created on a GUID Partition Table (GPT).

Because of this, the (ESP) partition would be invalid; just a plain fat32 formatted partition, instead of a fully qualified #ESP.

@exaveal

ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 EVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 0B2QKXJ7 temp: 37.9 C
    scheme: MBR

To further support this, I note that /dev/nvme0n1 clearly shows a DOS/MBR partitioning scheme.

With an LVM2 configuration also thrown into the mix, I don’t know of an easy way to recover from this situation, without a full reinstallation using recommended settings.

---

Perhaps someone might be kind enough to point you in the right direction; to install Manjaro purely as UEFI; and how to make the correct choices before and during installation.

Manjaro Install media must alo boot in UEFI mode.

I’m afraid I might not have the time, or patience.

Good luck.

---

Please see:

Manjaro with Luks + LVM and XFCE takes one hour to boot

The OP seems to have no understanding of the problem. While this isn’t uncommon for inexperienced computer users, they might legitimately think that the new thread relates to another issue entirely. This is not the case. The problem is that the OP is trying to boot both BIOS/MBR and UEFI. This is obvious simply by looking at their provided system information. @exaveal You can not boot a MBR booting OS and a UEFI booting OS at the same time. This is why, if you disconnect one disk, the other …

[exaveal]

The system works, when the windows-drive is not connected.
So if it is not set up correctly, why does it work perfectly?

If there is a DOS/MBR partitoning scheme, than perhaps from “earlier days”.

Setting up the system fresh needs a lot of time I do not have.

[Teo]

It says it right there in the fdisk output. Partition type - dos (mbr). And extended partitions exist only on mbr drives.

So you have one system as efi, the other as mbr. That cannot work together at the same time. Your bios is set to compatibility mode (csm) so that it recognizes the mbr disk at all, but in the moment an efi disk is present it gives priority to it.

The proper solution in 2024 is to go full efi. Convert the nvme to gpt, make an esp partition on it (you can reuse the space of that 1 gb partition there, reinstall grub.
That is if it has to go without data loss.
If it is a fresh install and no data yet on the disk, just wipe it and start a new, gpt.
Me personally always manually partition with gparted from live usb, and then start the manjaro installer and point it to the partitions.

[exaveal]

understood, will try to make everything gpt table.
But to be honest I don’t understand why this should be the problem with Manjaro not boot while windows drive is connected.

[Kobold]

@exaveal

Setting up the system fresh needs a lot of time I do not have.

Valid point, but then there will be no solution besides letting your Windows drive unplugged.

Because you have to decide between EFI or MBR Boot.

Which system you prefer to use, its up to you.

[soundofthunder]

@Kobold

Because you have to decide between EFI or MBR Boot.
Which system you prefer to use, its up to you.

The Windows disk seems to be already UEFI booting:

Gerät       Anfang      Ende  Sektoren Größe Typ
/dev/sda1     2048   1023999   1021952  499M Windows-Wiederherstellungsumgebung
/dev/sda2  1024000   1228799    204800  100M EFI-System
/dev/sda3  1228800   1261567     32768   16M Microsoft reserviert
/dev/sda4  1261568 468875263 467613696  223G Microsoft Basisdaten

It already has a fully qualified ESP.

The Manjaro disk is booting in Legacy/MBR mode:

Gerät          Boot   Anfang       Ende   Sektoren Größe Kn Typ
/dev/nvme0n1p1 *        2048    2099199    2097152    1G  b W95 FAT32
/dev/nvme0n1p2       2099200   12584959   10485760    5G 83 Linux
/dev/nvme0n1p3      12584960 3907028991 3894444032  1,8T  5 Erweiterte
/dev/nvme0n1p5      12587008 3907028991 3894441984  1,8T 83 Linux

Notice in the ‘boot’ column, the asterix indicates a Master Boot Record. /dev/nvme0n1p1 is a plain FAT32 formatted partition.

Reinstalling Manjaro from scratch from a UEFI-booting Installer USB seems the easiest approach to solving this. It would then be best to disable CSM in BIOS beforehand.

I understand this may take some time; especially if you have already set up Manjaro just the way you like it, but this might be the best remedy if you wish to use both OS in a multiboot scenario.

Does Windows still boot when the Manjaro disk is disconnected?
This is something you might wish to check.

Looking at your existing (Manjaro) partition layout, it might be possible to convert the installation to UEFI booting, but that would likely be a very involved manual process, and not guaranteed to be successful.

Reinstalling Manjaro would be the fastest, assuming BIOS and Manjaro Installer USB are properly configured for UEFI booting.

Ultimately, the choice is yours. Let us know what you decide.

[nikgnomic]

@exaveal

Festplatte /dev/sda: 465,76 GiB, 500107862016 Bytes, 976773168 Sektoren
Festplattenmodell: Samsung SSD 850 

Festplattenbezeichnungstyp: gpt


Festplatte /dev/sdb: 223,58 GiB, 240065183744 Bytes, 468877312 Sektoren
Festplattenmodell: SanDisk SSD PLUS

Festplattenbezeichnungstyp: gpt


Festplatte /dev/nvme0n1: 1,82 TiB, 2000398934016 Bytes, 3907029168 Sektoren
Festplattenmodell: Samsung SSD 990 EVO 2TB                 

Festplattenbezeichnungstyp: dos

Some basics of MBR v/s GPT and BIOS v/s UEFI - Manjaro Wiki

Converting from MBR to GPT - Manjaro Wiki

[Wollie]

@exaveal

But to be honest I don’t understand why this should be the problem with Manjaro not boot while windows drive is connected.

… because with the Windoze disk plugged in the system is booting in UEFI mode making it impossible to boot your Manjaro being installed in BIOS mode.

[exaveal]

Okay.
I don’t really get why my Manjaro is not UEFI. I always thought it’s UEFI. I mean i have an /boot/efi partition and so on … but okay.
Is there something like a command to check if the current (linux) system is running in UEFI mode?

I will start to copy my lvm container (2TB) and then reinstall.

[Wollie]

@exaveal

Is there something like a command to check if the current (linux) system is running in UEFI mode?

Yes:

test -d /sys/firmware/efi && echo efi || echo bios

[Mirdarthos]

@exaveal

Is there something like a command to check if the current (linux) system is running in UEFI mode?

Run the following in a terminal:

test -d /sys/firmware/efi && echo efi || echo bios

If the output is:

• efi, your computer uses (u)EFI.
• bios, your computer uses BIOS.

For more information, visit:

• Unified Extensible Firmware Interface, on the ArchWiki
• BIOS and UEFI, on the Manjaro Wiki

[nikgnomic]

Why can’t graphical installer create boot partition if I choose GPT over MBR?

Calamares installer shows Live ISO boot environment (BIOS or EFI)

and disk partition table (MBR or GPT)

[Teo]

The live usb was created as mbr from the whatever program created it.

[nikgnomic]

[SOLVED] Converting MBR to GPT / Installation / Arch Linux Forums

GPT fdisk - Convert between MBR and GPT - ArchWiki

How do i convert my linux disk from MBR to GPT with UEFI - Server Fault

Change a Master Boot Record (MBR) into a GUID partition table (GPT) disk | Microsoft Learn

[soundofthunder]

@exaveal

I will start to copy my lvm container (2TB) and then reinstall.

This looks to be potentially troublesome, if your first thought is to restore that container later, as it contains msdos partitions.

Festplatte /dev/mapper/lvm_desktop1: 1,81 TiB, 1993952198656 Bytes, 3894437888 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes

Festplatte /dev/mapper/lvm_desktop1-root: 200 GiB, 214748364800 Bytes, 419430400 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes

Festplatte /dev/mapper/lvm_desktop1-home: 1,62 TiB, 1779202785280 Bytes, 3475005440 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes

[exaveal]

So I did now a complete reinstall of Manjaro XFCE with GPT and UEFI. With Luks, but no LVM anymore.
Everything works as expected. Then I booted windows first time and shutdown again to start Manjaro again: After entering the passphrase, system boots until message “Jobs is running” After 60 seconds waiting the systems makes a cold restart.