Boot error: Failed to start D-Bus System Message Bus

Support
42

It is just data…

43

that answer is not good enough!
You’ll need to be more thorough … we can’t see what you see, so: you need to show us to put us in a similar position with not too much of a disadvantage …

look again at my previous post - the last three lines.

is one of them your encrypted /boot ?
that is data which is on there …

44 
sudo cryptsetup open /dev/nvme0n1p3 what_is_it                                                                           
Enter passphrase for /dev/nvme0n1p3: 
mount /dev/mapper/what_is_it /mnt                                                                                  sudo mount /dev/mapper/what_is_it /mnt 
ls -al /mnt                                                                                                                
total 24
drwxr-xr-x 4 manjaro manjaro  4096 Jun  7 15:43 .
drwxr-xr-x 1 root    root      160 Nov 24 17:50 ..
drwx------ 2 manjaro manjaro 16384 Dec 22  2022 lost+found
drwxr-xr-x 3 manjaro manjaro  4096 Jun  7 15:43 VM
sudo umount /mnt 
sudo cryptsetup close what_is_it                                                                                                

sudo cryptsetup open /dev/nvme0n1p4 what_is_it                                                                            
Enter passphrase for /dev/nvme0n1p4: 
sudo mount /dev/mapper/what_is_it /mnt  
ls -al /mnt                                                                                                               
total 28
drwxr-xr-x  5 manjaro manjaro  4096 Apr  6  2024 .
drwxr-xr-x  1 root    root      160 Nov 24 17:50 ..
drwxr-xr-x 11 manjaro manjaro  4096 Apr  6  2024 Foto
drwx------  2 manjaro manjaro 16384 Apr 26  2023 lost+found
drwx------  4 manjaro manjaro  4096 Apr 26  2023 .Trash-1000
sudo umount /mnt   
sudo cryptsetup close what_is_it
46

I am still here, because I encounter boot problems…

Some history:

  1. In the first place, my system wouldn’t boot with the D-Bus System Message Bus issue in the heading
  2. I tried to fix this, but found installation issues with existing files
  3. I then learned about pacnews and managed them
  4. I reinstalled everything and rebooted
  5. Now, my system wouldn’t boot due to device not being found
47

@soundofthunder, no KDE, I end up here:

ERROR: device 'UUID=luks-794e...'  not found. Skipping fsck

mount: /new_root: can't find UUID=794e....
ERROR: Failed to mount UUID=794e... 
You are no being dropped to emergency shell.
...
48

OK.
It’s likely best to start a new thread from this point.
Call it something like “Failed to find luks partition” and include this information:

ERROR: device 'UUID=luks-794e...'  not found. Skipping fsck

mount: /new_root: can't find UUID=794e....
ERROR: Failed to mount UUID=794e... 
You are no being dropped to emergency shell.

as you did in your last post.

Place a link to the new thread here also, so that others can easily find it if following on from here.

Also include any other information you can think of specific to the new problem, such as the content of /etc/fstab.

As I mentioned much earlier, I generally can’t help with encrypted scenarios.

Let’s try to attract some attention to the current issue.

Good luck.

49

Thanks!

We now have established that the other two partitions are non-essential with regard to chroot

There is just personal data on them -
VM’s on one (/dev/nvme0n1p3) and Fotos on the other (/dev/nvme0n1p4).
Not needed at all for chroot.
There is no separate encrypted /boot - I can’t say how I arrived at the conclusion that there was …

To achieve chroot, you’d only have to open and mount /dev/nvme0n1p2 - which is your / (root)
and then you’d have to mount /dev/nvme0n1p1 to /boot/efi

I guess.

AFAIK this is not what a standard install via Calamares would have done.

what I’d do, based upon the info I have understood:

  • boot usb
  • cryptsetup open /dev/nvme0n1p2 my_system_root
  • mount /dev/mapper/my_system_root /mnt
  • mount /dev/nvme0n1p1 /mnt/boot/efi
  • manjaro-chroot /mnt /bin/bash

I hope you can follow my logic - mount the system root, mount the EFI partition to it at the appropriate place, then chroot

50

I don’t know, sorry. But I doubt that I tweaked something manually.

I’ll follow @soundofthunder advice to open a new thread…

Thanks!

51

good idea!
but perhaps see and try what I said in my last post

52

Edit:- As the meandering nature of posts makes it unclear whether a solution was actually found (or not) for the original issue, and the OP has now created a new thread for a subsequent issue, perhaps this thread can go quietly into the night.