You are not logged in.
i reinstalled arch linux and as soon as i boot the system up its froze like this
https://cdn.discordapp.com/attachments/ … 0049d100c&
so i researched a bit a found out that the systemd is the reason with the version 257
but im not sure if it really the readon why or not
so how do i fix it ?
Last edited by ZelzalGD (2025-05-04 09:16:11)
Offline
Hello.
Were you installing per https://wiki.archlinux.org/title/Installation_guide ?
If you can post the image at a dedicated image host ( https://postimages.org/ for example) so that I/we can view it, that could give us something to work with. Otherwise it's like flying without senses..
Last edited by espresso (2025-05-05 18:51:25)
Offline
hello espresso,
before my system auto boot to arch linux i entered the kernel parmeters of grub and just deleted the quiet parameter so that i can see more details about the problem
here is an image of what it shows
https://postimg.cc/87RWHPyj
for your question in the first paragraph , i used the archinstall command , even tho before it was working normally but now after i installed and booted with the new system it will give me the same error
Offline
Perhaps there is a known issue or configuration problem, but I'm unfamiliar with archinstall and am left looking at https://wiki.archlinux.org/title/Genera … leshooting ..
Last edited by espresso (2025-05-08 04:10:11)
Offline
Idk whats the source of the problem
even the general boot problems page doesnt have what error i have specifically
should i send journatctl of it or somrthing else
Offline
Using the installation media, check journal of installed system to see what went wrong -- https://wiki.archlinux.org/title/System … al_to_view -- and possibly post if you want more eyes to interpret it.
Last edited by espresso (2025-05-08 04:44:42)
Offline
here is journalctl : https://0x0.st/8JEj.txt
if anything feels off let me know
Offline
Unless I miss something, that looks like the journal of the archiso; instead, you probably want to see a different one (the journal the installed system that failed to boot) as described in linked topic.
I'm unfamiliar with archinstall, and it can prevent understanding what happens in Installation, so I generally don't get too involved there, but maybe something will jump out to someone.
Last edited by espresso (2025-05-09 01:06:07)
Offline
the problem is that i cant get the journal of my actual system cuz as soon as i boot in no button will repond before the error message comes in
Offline
The link I gave is about how to do that.
Last edited by espresso (2025-05-10 15:18:48)
Offline
Apr 30 06:08:45 zelzaZelzal systemd[1]: mkinitcpio-generate-shutdown-ramfs.service: Deactivated successfully.
Apr 30 06:08:45 zelzaZelzal systemd[1]: Finished Generate shutdown-ramfs.
Apr 30 06:08:45 zelzaZelzal systemd[1]: Reached target System Shutdown.
Apr 30 06:08:45 zelzaZelzal systemd[1]: Reached target Late Shutdown Services.
Apr 30 06:08:45 zelzaZelzal systemd[1]: systemd-poweroff.service: Deactivated successfully.
Apr 30 06:08:45 zelzaZelzal systemd[1]: Finished System Power Off.
Apr 30 06:08:45 zelzaZelzal systemd[1]: Reached target System Power Off.
Apr 30 06:08:45 zelzaZelzal systemd[1]: Shutting down.
Apr 30 06:08:46 zelzaZelzal systemd-journald[22]: Journal stopped
-- Boot e14128418b984f0e948a6536d4a8f035 --
May 08 23:35:54 archiso kernel: Linux version 6.14.4-arch1-2 (linux@archlinux) (gcc (GCC) 15.1.1 20250425, GNU ld (GNU Binutils) 2.44.0) #1 SMP PREEMPT_DYNAMIC Tue, 29 Apr 2025 09:23:13 +0000
May 08 23:35:54 archiso kernel: Command line: initrd=\arch\boot\x86_64\initramfs-linux.img archisobasedir=arch archisosearchuuid=2025-05-01-10-09-37-00
May 08 23:35:54 archiso kernel: BIOS-provided physical RAM map:
May 08 23:35:54 archiso kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
May 08 23:35:54 archiso kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
May 08 23:35:54 archiso kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000de09ffff] usable
May 08 23:35:54 archiso kernel: BIOS-e820: [mem 0x00000000de0a0000-0x00000000de135fff] reserved
May 08 23:35:54 archiso kernel: BIOS-e820: [mem 0x00000000de136000-0x00000000de146fff] ACPI data
May 08 23:35:54 archiso kernel: BIOS-e820: [mem 0x00000000de147000-0x00000000deb20fff] ACPI NVS
Why do you have the journal of the previous system and the current archiso in the same file?
Did you try to "install" arch by copying the install iso onto the disk or otherwise turn the iso into an installed system?
even the general boot problems page doesnt have what error i have specifically
https://github.com/systemd/systemd/issues/29191 - don't comment there, that bug is closed.
This looks way more like a botched attempt at creating a live system.
But let's first see the relevant journal.
Offline
ok i just looked at the github you had sent and tried to do the same commandline in the linux kernel
here is the output of what showed
https://postimg.cc/3yrjRSjJ
Offline
https://github.com/systemd/systemd/issues/25543 - except you're not using netplan
Why do you have the journal of the previous system and the current archiso in the same file?
Did you try to "install" arch by copying the install iso onto the disk or otherwise turn the iso into an installed system?
Offline
You can load journalctl log from different places:
journalctl -h
...
-m --merge Show entries from all available journals
-D --directory=PATH Show journal files from directory
-i --file=PATH Show journal file
--root=PATH Operate on an alternate filesystem root
--image=PATH Operate on disk image as filesystem root
--image-policy=POLICY Specify disk image dissection policy
--namespace=NAMESPACE Show journal data from specified journal namespace
...
You probably used option -m merge instead -D directory or -i file. You can boot into arch iso, mount your root instalation partition and use journalctl with option -D or -i and -S since_date or/and -U until_date or try with -b-n number of boot ago.
Offline