You are not logged in.
https://0x0.st/K9IL.txt
This is installed onto a USB drive, and stops here while booting, never getting to a login prompt.
Offline
Nov 10 17:48:40 archlinux dbus-broker-launch[367]: ERROR launcher_open_journal @ ../dbus-broker-37/src/launch/launcher.c +179: Permission denied
Nov 10 17:48:40 archlinux dbus-broker-launch[367]: launcher_run_child @ ../dbus-broker-37/src/launch/launcher.c +314
Nov 10 17:48:40 archlinux dbus-broker-launch[366]: ERROR service_add @ ../dbus-broker-37/src/launch/service.c +1011: Transport endpoint is not connected
Nov 10 17:48:40 archlinux dbus-broker-launch[366]: launcher_add_services @ ../dbus-broker-37/src/launch/launcher.c +823
Nov 10 17:48:40 archlinux dbus-broker-launch[366]: launcher_run @ ../dbus-broker-37/src/launch/launcher.c +1439
Nov 10 17:48:40 archlinux dbus-broker-launch[366]: run @ ../dbus-broker-37/src/launch/main.c +152
Nov 10 17:48:40 archlinux dbus-broker-launch[366]: main @ ../dbus-broker-37/src/launch/main.c +178
Nov 10 17:48:40 archlinux dbus-broker-launch[366]: Exiting due to fatal error: -107There's no sdc in that journal, you're booting from
Nov 10 17:48:33 archlinux kernel: scsi 6:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
Nov 10 17:48:33 archlinux kernel: sd 6:0:0:0: [sdb] 60125184 512-byte logical blocks: (30.8 GB/28.7 GiB)
Nov 10 17:48:33 archlinux kernel: sd 6:0:0:0: [sdb] Write Protect is off
Nov 10 17:48:33 archlinux kernel: sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
Nov 10 17:48:33 archlinux kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Nov 10 17:48:33 archlinux kernel: sdb: sdb1 sdb2
Nov 10 17:48:33 archlinux kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
Nov 10 17:48:33 archlinux systemd[1]: Found device Cruzer_Blade Arch.
Nov 10 17:48:33 archlinux systemd[1]: Reached target Initrd Root Device.
Nov 10 17:48:33 archlinux systemd[1]: Starting File System Check on /dev/disk/by-uuid/5c50ecf4-44f7-4e5e-8a5b-7e2361af1487...
Nov 10 17:48:33 archlinux systemd-fsck[173]: Arch: recovering journal
Nov 10 17:48:33 archlinux systemd-fsck[173]: Arch: clean, 44179/1818624 files, 648367/7271168 blocks
Nov 10 17:48:33 archlinux systemd[1]: Finished File System Check on /dev/disk/by-uuid/5c50ecf4-44f7-4e5e-8a5b-7e2361af1487.
Nov 10 17:48:33 archlinux systemd[1]: Mounting /sysroot...
Nov 10 17:48:33 archlinux kernel: EXT4-fs (sdb2): mounted filesystem 5c50ecf4-44f7-4e5e-8a5b-7e2361af1487 r/w with ordered data mode. Quota mode: none.
Nov 10 17:48:33 archlinux systemd[1]: Mounted /sysroot.PSA: USB keys are NOT cheap SSDs, there's no wear leveling and overwriting the same sectors again and again will kill them in no time.
https://wiki.archlinux.org/title/Instal … ble_medium
https://wiki.archlinux.org/title/Instal … isk_access
Boot the install iso, mount the root partition of the broken system into /mnt and run
LC_ALL=C pacman --root /mnt -Qkk |& grep -v ', 0 altered files' | grep -v backup | tee /tmp/howbadisit.txt
cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.stOffline
warning: filesystem: /mnt/dev (Permissions mismatch)
warning: filesystem: /mnt/run (Permissions mismatch)
filesystem: 127 total files, 2 altered files
libcap: 120 total files, 0 altered filewarning: shadow: /mnt/usr/bin/groupmems (GID mismatch)
warning: shadow: /mnt/usr/bin/groupmems (Permissions mismatch)
warning: systemd: /mnt/var/log/journal (GID mismatch)
s
shadow: 576 total files, 1 altered file
systemd: 1670 total files, 1 altered fileOffline
stat /mnt/dev /mnt/runYou're supposed to mount devfs and runfs there, but still those should be root:root/755
Edit: to be clear: you *are* mounting devfs and runfs there and there're currently not files in /mnt/dev or /mnt/run ?
Last edited by seth (2025-11-10 09:34:29)
Offline
Doesn't arch-chroot and the regular boot process mount them there?
Anyway, once I ran chmod 755 on them those first 3 lines are no longer there, and the output is
libcap: 120 total files, 0 altered filewarning: shadow: /mnt/usr/bin/groupmems (GID mismatch)
warning: shadow: /mnt/usr/bin/groupmems (Permissions mismatch)
warning: systemd: /mnt/var/log/journal (GID mismatch)
s
shadow: 576 total files, 1 altered file
systemd: 1670 total files, 1 altered file/mnt/dev and /mnt/run are not currently mounted.
Offline
Doesn't arch-chroot and the regular boot process mount them there?
Ideally - does the system now boot after fixing the permissions?
Can you boot the multi-user.target or rescue.target (2nd link below)?
Do devfs and esp. runfs now mount or does dbus-broker still complain?
Offline
https://0x0.st/K9dR.txt
Still does not boot after fixing perms.
I am able to boot to rescue.target, and in the shell I can see devfs and runfs are mounted. I am not able to reach multi-user.target, with the same errors.
Offline
https://github.com/bus1/dbus-broker/blo … her.c#L179
stat /run/systemd/journal/socketEdit: also better
stat /run/systemd/journal
stat /run/systemd
stat /runEdit #2: and
findmnt -T /run/systemd/journal/socketLast edited by seth (2025-11-10 21:41:20)
Offline
This is in arch-chroot.
# stat /run/systemd/journal/socket
File: /run/systemd/journal/socket
Size: 0 Blocks: 0 IO Block: 4096 socket
Device: 0,26 Inode: 613 Links: 1
Access: (0666/srw-rw-rw-) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-11-10 12:18:57.531510568 +1100
Modify: 2025-11-06 12:03:24.326912647 +1100
Change: 2025-11-06 12:03:24.326912647 +1100
Birth: 2025-11-06 12:03:24.326912647 +1100
# stat /run/systemd/journal
File: /run/systemd/journal
Size: 200 Blocks: 0 IO Block: 4096 directory
Device: 0,26 Inode: 608 Links: 3
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-11-10 14:29:20.888857979 +1100
Modify: 2025-11-06 12:03:24.455912655 +1100
Change: 2025-11-06 12:03:24.455912655 +1100
Birth: 2025-11-06 12:03:24.325912647 +1100
# stat /run/systemd
File: /run/systemd
Size: 560 Blocks: 0 IO Block: 4096 directory
Device: 0,26 Inode: 560 Links: 24
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-11-10 14:29:17.933896963 +1100
Modify: 2025-11-09 20:29:41.304496481 +1100
Change: 2025-11-09 20:29:41.304496481 +1100
Birth: 2025-11-06 12:03:24.086912633 +1100
# stat /run
File: /run
Size: 1520 Blocks: 0 IO Block: 4096 directory
Device: 0,26 Inode: 1 Links: 50
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-11-11 08:44:06.817500129 +1100
Modify: 2025-11-11 06:35:37.499081490 +1100
Change: 2025-11-11 06:35:37.499081490 +1100
Birth: 2025-11-06 12:03:20.202000033 +1100
# findmnt -T /run/systemd/journal/socket
TARGET SOURCE FSTYPE OPTIONS
/run tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=3278008k,mode=755,inode64
# Offline
Not chroot, rescue.target - the chroot is pointless, you're getting the runfs from the install iso or a systemd fabricated one from the working system.
Edit: you can in doubt post a photo of the output.
Last edited by seth (2025-11-10 21:55:56)
Offline
Output from rescue.target shell:
File: /run/systemd/journal/socket
Size: 0 Blocks: 0 IO Block: 4096 socket
Device: 0,26 Inode: 39 Links: 1
Access: (0666/srw-rw-rw-) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-11-11 08:57:21.759677481 +1100
Modify: 2025-11-11 08:57:11.718466041 +1100
Change: 2025-11-11 08:57:11.718466041 +1100
Birth: 2025-11-11 08:57:11.718279247 +1100
File: /run/systemd/journal
Size: 200 Blocks: 0 IO Block: 4096 directory
Device: 0,26 Inode: 37 Links: 3
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-11-11 08:57:48.314676356 +1100
Modify: 2025-11-11 08:57:16.464677706 +1100
Change: 2025-11-11 08:57:16.464677706 +1100
Birth: 2025-11-11 08:57:11.716677907 +1100
File: /run/systemd
Size: 480 Blocks: 0 IO Block: 4096 directory
Device: 0,26 Inode: 2 Links: 18
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-11-11 08:57:46.922676415 +1100
Modify: 2025-11-11 08:57:20.736677525 +1100
Change: 2025-11-11 08:57:20.736677525 +1100
Birth: 2025-11-11 08:57:11.674677909 +1100
File: /run
Size: 360 Blocks: 0 IO Block: 4096 directory
Device: 0,26 Inode: 1 Links: 16
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2025-11-11 08:57:56.261676019 +1100
Modify: 2025-11-11 08:57:20.739680056 +1100
Change: 2025-11-11 08:57:20.739680056 +1100
Birth: 2025-11-11 08:57:11.672677909 +1100
TARGET SOURCE FSTYPE OPTIONS
/run tmpfs tmpfs rw,nosuid,nodev,size=1564208k,nr_inodes=819200,mode=755,inode64Offline
None of that looks concerning …
stat / # does the root note have too strict permissions?Edit: you want that to be root:root/755
Edit #2: -107 is "ENOTCONN 107 Transport endpoint is not connected"…
journald is restarted w/ the root switch
Nov 10 18:21:52 archlinux systemd[1]: Listening on Journal Socket (/dev/log).
Nov 10 18:21:52 archlinux systemd[1]: Listening on Journal Sockets.
Nov 10 18:21:52 archlinux systemd[1]: Starting Journal Service...
Nov 10 18:21:52 archlinux systemd-journald[117]: Collecting audit messages is disabled.
Nov 10 18:21:52 archlinux systemd-journald[117]: Journal started
Nov 10 18:21:52 archlinux systemd-journald[117]: Runtime Journal (/run/log/journal/a158c8e41e184b1b80e7afbd551ffb6b) is 8M, max 152.7M, 144.7M free.
Nov 10 18:21:52 archlinux systemd[1]: Started Journal Service.
Nov 10 18:21:54 archlinux systemd-journald[117]: Journal stopped
Nov 10 18:21:56 archlinux systemd-journald[117]: Received SIGTERM from PID 1 (systemd).
Nov 10 18:21:56 archlinux systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
Nov 10 18:21:56 archlinux systemd[1]: Starting Journal Service...
Nov 10 18:21:56 archlinux systemd-journald[226]: Collecting audit messages is disabled.
Nov 10 18:21:56 archlinux systemd-journald[226]: Journal started
Nov 10 18:21:56 archlinux systemd-journald[226]: Runtime Journal (/run/log/journal/45f5cfc3dd174c9ea6d4b2eacbb413c7) is 8M, max 152.7M, 144.7M free.
Nov 10 18:21:56 archlinux systemd[1]: systemd-journald.service: Deactivated successfully.
Nov 10 18:21:56 archlinux systemd[1]: Started Journal Service.
Nov 10 18:21:56 archlinux systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 10 18:21:56 archlinux systemd-journald[226]: Time spent on flushing to /var/log/journal/45f5cfc3dd174c9ea6d4b2eacbb413c7 is 10.986ms for 907 entries.
Nov 10 18:21:56 archlinux systemd-journald[226]: System Journal (/var/log/journal/45f5cfc3dd174c9ea6d4b2eacbb413c7) is 16M, max 2.7G, 2.6G free.
Nov 10 18:21:57 archlinux systemd-journald[226]: Received client request to flush runtime journal.
Nov 10 18:21:57 archlinux systemd-journald[226]: File /var/log/journal/45f5cfc3dd174c9ea6d4b2eacbb413c7/system.journal corrupted or uncleanly shut down, renaming and replacing.
Nov 10 18:21:57 archlinux systemd[1]: Finished Flush Journal to Persistent Storage.
Nov 10 18:22:00 archlinux systemd[1]: Starting Rebuild Journal Catalog...
Nov 10 18:22:00 archlinux systemd[1]: Finished Rebuild Journal Catalog.
Nov 10 18:22:02 archlinux dbus-broker-launch[365]: ERROR launcher_open_journal @ ../dbus-broker-37/src/launch/launcher.c +179: Permission denied
Nov 10 18:23:32 archlinux dbus-broker-launch[380]: ERROR launcher_open_journal @ ../dbus-broker-37/src/launch/launcher.c +179: Permission denied
Nov 10 18:25:03 archlinux dbus-broker-launch[385]: ERROR launcher_open_journal @ ../dbus-broker-37/src/launch/launcher.c +179: Permission deniedAnything fancy about your initramfs configuration?
Last edited by seth (2025-11-10 22:12:04)
Offline
root was 700, I ran chmod 755 on it and now it boots!
Thanks for your help.
Offline
I think this may have been caused by doing the install on a system that was not the arch install disk, and having mount point be inside the home dir instead of /mnt.
Offline
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
I don't think I can, since I am not the OP.
Offline
Yeah, sorry - forgot that you had hijacked the thread ![]()
Offline