You are not logged in.

Pages: 1 2 3 … 6

#1 2022-12-02 04:41:16

Morta
Member
Registered: 2019-07-07
Posts: 660

[Solved]systemd kills boot up till version 252.1-2-arch

I have a emergency shell where I have to login with root password and all services doesn't show up till systemd version 252.1-2

Here my journalctl -b is ~150 MB big... I don't know why.

https://www104.zippyshare.com/v/FrOu842P/file.html

Last edited by Morta (2023-01-06 16:49:07)

Offline

#2 2022-12-02 04:53:20

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,167

Re: [Solved]systemd kills boot up till version 252.1-2-arch

I get a 403 error but you won't have anything in the journal if you're dumped into an emergency shell. What messages are shown?

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#3 2022-12-02 05:00:04

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

waiting for initrd-root-fs.target

and waiting for /dev/vg_main/swap and root, data but when I log in emergency shell shows full filesystem

Offline

#4 2022-12-02 08:44:24

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

Please link a photo of what you actually see when being dropped into the emergency shell - the system would tell you "why" that happens.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2022-12-02 13:53:14

pitastrudl
Member
Registered: 2022-05-10
Posts: 8

Re: [Solved]systemd kills boot up till version 252.1-2-arch

Have you tried fully upgrading your arch install? seems the systemd version you are using is outdated, https://archlinux.org/packages/core/x86_64/systemd/

Offline

#7 2022-12-02 14:46:07

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

pitastrudl wrote:

Have you tried fully upgrading your arch install? seems the systemd version you are using is outdated, https://archlinux.org/packages/core/x86_64/systemd/

Yes have kernel 6.0.10

The problemen starts with the systemd update to 252.2–1 and every change of systemd has a new generation of initramfs within

Offline

#8 2022-12-02 16:53:54

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

initrd-switch-root fails, please post the output of 

lsblk -f

Possibly same as https://bbs.archlinux.org/viewtopic.php … 7#p2071377

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2022-12-02 17:25:23

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

With which systemd version?

Offline

#10 2022-12-02 17:51:03

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

The lsblk output is not supposed to vary w/ the system version.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2022-12-03 12:33:44

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

[morta@5erver ~]$ lsblk -f
NAME                 FSTYPE            FSVER    LABEL     UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                             
└─sda1               linux_raid_member 1.2      archiso:1 724aeba6-a520-7a87-51d6-36b158706ed2                  
  └─md1              crypto_LUKS       2                  d5793f0d-9a62-4eac-8fb2-d08b04e61bf7                  
    └─cryptdata      LVM2_member       LVM2 001           G0J7Va-xhrb-Fr2q-rb1g-xbeq-Sc3L-8dh0SC                
      └─vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      7.1G    95% /home/data
sdb                                                                                                             
└─sdb1               linux_raid_member 1.2      archiso:1 724aeba6-a520-7a87-51d6-36b158706ed2                  
  └─md1              crypto_LUKS       2                  d5793f0d-9a62-4eac-8fb2-d08b04e61bf7                  
    └─cryptdata      LVM2_member       LVM2 001           G0J7Va-xhrb-Fr2q-rb1g-xbeq-Sc3L-8dh0SC                
      └─vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      7.1G    95% /home/data
sdc                                                                                                             
└─sdc1               linux_raid_member 1.2      archiso:1 724aeba6-a520-7a87-51d6-36b158706ed2                  
  └─md1              crypto_LUKS       2                  d5793f0d-9a62-4eac-8fb2-d08b04e61bf7                  
    └─cryptdata      LVM2_member       LVM2 001           G0J7Va-xhrb-Fr2q-rb1g-xbeq-Sc3L-8dh0SC                
      └─vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      7.1G    95% /home/data
sdd                                                                                                             
└─sdd1               linux_raid_member 1.2      archiso:1 724aeba6-a520-7a87-51d6-36b158706ed2                  
  └─md1              crypto_LUKS       2                  d5793f0d-9a62-4eac-8fb2-d08b04e61bf7                  
    └─cryptdata      LVM2_member       LVM2 001           G0J7Va-xhrb-Fr2q-rb1g-xbeq-Sc3L-8dh0SC                
      └─vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      7.1G    95% /home/data
sr0                                                                                                             
nvme0n1                                                                                                         
├─nvme0n1p1          vfat              FAT32              9F86-D68C                               781.5M    24% /boot
└─nvme0n1p2          linux_raid_member 1.2      archiso:0 ead24ea6-751c-0557-330c-a00a75779cf5                  
  └─md0              crypto_LUKS       2                  4a13d219-3d56-4375-9889-de0fe1385d8e                  
    └─cryptroot      LVM2_member       LVM2 001           qflUBC-vi8m-Mn3c-F9ZC-d4il-xB3W-sTjyqf                
      ├─vg_main-root ext4              1.0      root      32500ebd-e5ad-4485-b281-edf0a3556420     23.5G    65% /
      ├─vg_main-swap swap              1                  1a9626b3-30bb-4426-9457-67fe7a4266c4                  [SWAP]
      └─vg_main-home ext4              1.0      home      34f99504-9ffc-45fd-bd8d-9e7c815e93da    192.4G    34% /home
nvme1n1                                                                                                         
├─nvme1n1p1                                                                                                     
└─nvme1n1p2          linux_raid_member 1.2      archiso:0 ead24ea6-751c-0557-330c-a00a75779cf5                  
  └─md0              crypto_LUKS       2                  4a13d219-3d56-4375-9889-de0fe1385d8e                  
    └─cryptroot      LVM2_member       LVM2 001           qflUBC-vi8m-Mn3c-F9ZC-d4il-xB3W-sTjyqf                
      ├─vg_main-root ext4              1.0      root      32500ebd-e5ad-4485-b281-edf0a3556420     23.5G    65% /
      ├─vg_main-swap swap              1                  1a9626b3-30bb-4426-9457-67fe7a4266c4                  [SWAP]
      └─vg_main-home ext4              1.0      home      34f99504-9ffc-45fd-bd8d-9e7c815e93da    192.4G    34% /home

Offline

#12 2022-12-03 14:43:48

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

It's waiting for 

vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      7.1G    95% /home/data

Post your fstab and try to make that partition "noauto,x-systemd.automount" to delay the mount.

Then post a complete system journal after trying to mount the partition.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2022-12-03 14:47:30

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

old

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/vg_main-root LABEL=root
UUID=32500ebd-e5ad-4485-b281-edf0a3556420	/         	ext4      	rw,relatime,stripe=256	0 1

# /dev/mapper/vg_main-home LABEL=home
UUID=34f99504-9ffc-45fd-bd8d-9e7c815e93da	/home     	ext4      	rw,relatime,stripe=256	0 2

# /dev/mapper/vg_main-data LABEL=data
UUID=7cc8bc6c-2063-445d-925b-3df0131eaad5	/home/data	ext4      	rw,relatime,stripe=512	0 2

# /dev/nvme0n1p1
UUID=9F86-D68C      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/mapper/vg_main-swap
UUID=1a9626b3-30bb-4426-9457-67fe7a4266c4	none      	swap      	defaults  	0 0

#Ramdisk tmps
tmpfs			/tmp		tmpfs		defaults,noatime,mode=1777	

#Mount nfs /home/backup
192.168.1.118:/data	/home/backup	nfs4	defaults,timeo=900,retrans=5,_netdev,noauto	0 0
[/quote]

new

[quote]
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/vg_main-root LABEL=root
UUID=32500ebd-e5ad-4485-b281-edf0a3556420	/         	ext4      	rw,relatime,stripe=256	0 1

# /dev/mapper/vg_main-home LABEL=home
UUID=34f99504-9ffc-45fd-bd8d-9e7c815e93da	/home     	ext4      	rw,relatime,stripe=256	0 2

# /dev/mapper/vg_main-data LABEL=data
UUID=7cc8bc6c-2063-445d-925b-3df0131eaad5	/home/data	ext4      	rw,relatime,noauto,x-systemd.automount,stripe=512	0 2

# /dev/nvme0n1p1
UUID=9F86-D68C      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/mapper/vg_main-swap
UUID=1a9626b3-30bb-4426-9457-67fe7a4266c4	none      	swap      	defaults  	0 0

#Ramdisk tmps
tmpfs			/tmp		tmpfs		defaults,noatime,mode=1777	

#Mount nfs /home/backup
192.168.1.118:/data	/home/backup	nfs4	defaults,timeo=900,retrans=5,_netdev,noauto	0 0

Has no effect

Last edited by Morta (2022-12-03 17:36:51)

Offline

#14 2022-12-03 15:06:09

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

lsblk -f with systemd 252.1-2

morta@5erver ~]$ lsblk -f
NAME                 FSTYPE            FSVER    LABEL     UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                             
└─sda1               linux_raid_member 1.2      archiso:1 724aeba6-a520-7a87-51d6-36b158706ed2                  
  └─md1              crypto_LUKS       2                  d5793f0d-9a62-4eac-8fb2-d08b04e61bf7                  
    └─cryptdata      LVM2_member       LVM2 001           G0J7Va-xhrb-Fr2q-rb1g-xbeq-Sc3L-8dh0SC                
      └─vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      6.8G    95% /home/data
sdb                                                                                                             
└─sdb1               linux_raid_member 1.2      archiso:1 724aeba6-a520-7a87-51d6-36b158706ed2                  
  └─md1              crypto_LUKS       2                  d5793f0d-9a62-4eac-8fb2-d08b04e61bf7                  
    └─cryptdata      LVM2_member       LVM2 001           G0J7Va-xhrb-Fr2q-rb1g-xbeq-Sc3L-8dh0SC                
      └─vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      6.8G    95% /home/data
sdc                                                                                                             
└─sdc1               linux_raid_member 1.2      archiso:1 724aeba6-a520-7a87-51d6-36b158706ed2                  
  └─md1              crypto_LUKS       2                  d5793f0d-9a62-4eac-8fb2-d08b04e61bf7                  
    └─cryptdata      LVM2_member       LVM2 001           G0J7Va-xhrb-Fr2q-rb1g-xbeq-Sc3L-8dh0SC                
      └─vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      6.8G    95% /home/data
sdd                                                                                                             
└─sdd1               linux_raid_member 1.2      archiso:1 724aeba6-a520-7a87-51d6-36b158706ed2                  
  └─md1              crypto_LUKS       2                  d5793f0d-9a62-4eac-8fb2-d08b04e61bf7                  
    └─cryptdata      LVM2_member       LVM2 001           G0J7Va-xhrb-Fr2q-rb1g-xbeq-Sc3L-8dh0SC                
      └─vg_main-data ext4              1.0      data      7cc8bc6c-2063-445d-925b-3df0131eaad5      6.8G    95% /home/data
sr0                                                                                                             
nvme0n1                                                                                                         
├─nvme0n1p1          vfat              FAT32              9F86-D68C                               781.7M    24% /boot
└─nvme0n1p2          linux_raid_member 1.2      archiso:0 ead24ea6-751c-0557-330c-a00a75779cf5                  
  └─md0              crypto_LUKS       2                  4a13d219-3d56-4375-9889-de0fe1385d8e                  
    └─cryptroot      LVM2_member       LVM2 001           qflUBC-vi8m-Mn3c-F9ZC-d4il-xB3W-sTjyqf                
      ├─vg_main-root ext4              1.0      root      32500ebd-e5ad-4485-b281-edf0a3556420     23.4G    65% /
      ├─vg_main-swap swap              1                  1a9626b3-30bb-4426-9457-67fe7a4266c4                  [SWAP]
      └─vg_main-home ext4              1.0      home      34f99504-9ffc-45fd-bd8d-9e7c815e93da    192.4G    34% /home
nvme1n1                                                                                                         
├─nvme1n1p1                                                                                                     
└─nvme1n1p2          linux_raid_member 1.2      archiso:0 ead24ea6-751c-0557-330c-a00a75779cf5                  
  └─md0              crypto_LUKS       2                  4a13d219-3d56-4375-9889-de0fe1385d8e                  
    └─cryptroot      LVM2_member       LVM2 001           qflUBC-vi8m-Mn3c-F9ZC-d4il-xB3W-sTjyqf                
      ├─vg_main-root ext4              1.0      root      32500ebd-e5ad-4485-b281-edf0a3556420     23.4G    65% /
      ├─vg_main-swap swap              1                  1a9626b3-30bb-4426-9457-67fe7a4266c4                  [SWAP]
      └─vg_main-home ext4              1.0      home      34f99504-9ffc-45fd-bd8d-9e7c815e93da    192.4G    34% /home

lsblk with systemd 252.2-2

NAME                 FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda                                                         
└─sda1                                                      
  └─md1                                                     
    └─cryptdata                                             
      └─vg_main-data                                        
sdb                                                         
└─sdb1                                                      
  └─md1                                                     
    └─cryptdata                                             
      └─vg_main-data                                        
sdc                                                         
└─sdc1                                                      
  └─md1                                                     
    └─cryptdata                                             
      └─vg_main-data                                        
sdd                                                         
└─sdd1                                                      
  └─md1                                                     
    └─cryptdata                                             
      └─vg_main-data                                        
sr0                                                         
nvme0n1                                                     
├─nvme0n1p1                                   781.7M    24% /boot
└─nvme0n1p2                                                 
  └─md0                                                     
    └─cryptroot                                             
      ├─vg_main-root                           23.2G    65% /
      ├─vg_main-swap                                        [SWAP]
      └─vg_main-home                                        
nvme1n1                                                     
├─nvme1n1p1                                                 
└─nvme1n1p2                                                 
  └─md0                                                     
    └─cryptroot                                             
      ├─vg_main-root                           23.2G    65% /
      ├─vg_main-swap                                        [SWAP]
      └─vg_main-home

journalctl -b

https://www6.zippyshare.com/v/GcDuaSxl/file.html

Last edited by Morta (2022-12-03 17:38:11)

Offline

#15 2022-12-03 15:32:48

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

Please use "code" tags, not "quote" tags.
Does the system now boot (/home failed as well?)
Can you mount /home/data later on?
The zippyshare url is 403

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2022-12-03 15:38:10

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

journalctl -b
https://filehorst.de/d/eBGaIqsb

Whit systemd 252.1-2 works all fine after not and I fall in emergency mode and swap home data not mount

Last edited by Morta (2022-12-03 15:38:55)

Offline

#17 2022-12-03 16:11:19

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

See the 1s link below for non-annoying pastebin services.

Your journal is with

Dec 03 15:56:12 archlinux systemd[1]: systemd 252.2-2-arch running in system mode …

and has

Dec 03 14:56:28 5erver systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway.
Dec 03 14:56:28 5erver systemd[1]: Mounting /home...
Dec 03 14:56:28 5erver systemd[1]: Mounted /home.
Dec 03 14:56:28 5erver systemd[1]: home-data.automount: Directory /home/data to mount over is not empty, mounting anyway.
Dec 03 14:56:30 5erver systemd[1]: home-data.automount: Got automount request for /home/data, triggered by 971 ((php-fpm))
Dec 03 14:56:30 5erver systemd[1]: Mounting /home/data...
Dec 03 14:56:30 5erver systemd[1]: Mounted /home/data.
Dec 03 14:56:42 5erver systemd[1]: home-backup.automount: Directory /home/backup to mount over is not empty, mounting anyway.
Dec 03 14:56:42 5erver systemd[1]: home-backup.automount: Got automount request for /home/backup, triggered by 1476 (mopidy)

what does not look like any trouble but you clearly have stashed data in /home and /home/data

I suspect the issue around  this:

Dec 03 15:56:12 archlinux systemd[1]: Starting Cryptography Setup for cryptdata...
Dec 03 15:56:12 archlinux systemd[1]: Starting Cryptography Setup for cryptroot...
Dec 03 15:56:25 archlinux systemd[1]: Finished Cryptography Setup for cryptroot.
Dec 03 15:56:27 archlinux systemd[1]: Finished Cryptography Setup for cryptdata.

Because this is late

Dec 03 15:56:23 archlinux systemd-tty-ask-password-agent[328]: Password query on /dev/tty1 finished successfully.
Dec 03 15:56:23 archlinux systemd-tty-ask-password-agent[328]: Starting password query on /dev/tty1.
Dec 03 15:56:23 archlinux systemd-cryptsetup[326]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/4a13d219-3d56-4375-9889-de0fe1385d8e.
Dec 03 15:56:23 archlinux systemd-cryptsetup[325]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/d5793f0d-9a62-4eac-8fb2-d08b04e61bf7.
Dec 03 15:56:25 archlinux audit[326]: DM_CTRL module=crypt op=ctr ppid=1 pid=326 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-cryptse" exe="/usr/lib/systemd/systemd-cryptsetup" dev=254:0 error_msg='success' res=1
Dec 03 15:56:25 archlinux audit[326]: SYSCALL arch=c000003e syscall=16 success=yes exit=0 a0=4 a1=c138fd09 a2=55a839116ec0 a3=0 items=6 ppid=1 pid=326 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-cryptse" exe="/u

You might want to ealborate on how you configured https://wiki.archlinux.org/title/Dm-cry … -generator and whether you're using mkinitcpio or dracut and whether you rebuild the initramfs after updating systemd.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#18 2022-12-03 16:22:30

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

The journalctl was too big for ix.io or termbin. I know them.

I use mkinitcpio and after update systemd it’s rebuild automatically initramfs.

I can’t get the error. I made the cryptsetup on 3 various computer. On two I hasn’t problem on one yes!

What I have to do exactly? And why it's works with systemd 252.1-2 and neither with systemd 252.2-1 or 252.2-2

My /etc/crypttab is empty

Last edited by Morta (2022-12-03 17:40:56)

Offline

#19 2022-12-03 17:18:49

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

The default suggestion is https://0x0.st/ w/ a 512MB quota…

What I have to do exactly?

seth wrote:

Rebuild the initramfs explicitly nd look out for errors.
Compare the mkinitio.conf's on whether you flubbered some hook/module include.
Fix #13 & #14 to use code tags and don't full-quote previous posts - that's useless.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#20 2022-12-03 17:43:45

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

seth wrote:

The default suggestion is https://0x0.st/ w/ a 512MB quota…

What I have to do exactly?

seth wrote:

Rebuild the initramfs explicitly nd look out for errors.
Compare the mkinitio.conf's on whether you flubbered some hook/module include.
Fix #13 & #14 to use code tags and don't full-quote previous posts - that's useless.

I fixed the tags and deleted the quota.

There is no error in generation of initramfs nor an error in cryptsetup config!

This was a working setup like 3 years long!!

There is a bug in systemd 252.2-1

Offline

#21 2022-12-03 17:57:25

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

There is a bug in systemd 252.2-1

that only affects one out of three supposingly equal systems?
Ok.
But if you're sure about that, why are you posting here?
=> https://github.com/systemd/systemd/issues

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#22 2022-12-03 18:03:55

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

seth wrote:

There is a bug in systemd 252.2-1

that only affects one out of three supposingly equal systems?
Ok.
But if you're sure about that, why are you posting here?
=> https://github.com/systemd/systemd/issues

Equal like cryptsetup LVM and ArchLinux but different Hardware

I hoped to get more information and I’m not enough skilled to find them and you are :-)

If the error is localised I will do a bug report.

Is there a log of initramfs generation?

Last edited by Morta (2022-12-03 18:10:37)

Offline

#23 2022-12-03 20:34:58

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

Is there a log of initramfs generation?

It's printed into the terminal when you run mkinitcpio?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#24 2022-12-04 06:34:24

Morta
Member
Registered: 2019-07-07
Posts: 660

Re: [Solved]systemd kills boot up till version 252.1-2-arch

seth wrote:

Is there a log of initramfs generation?

It's printed into the terminal when you run mkinitcpio?

No errors!

Offline

#25 2022-12-04 07:50:43

seth
Member
Registered: 2012-09-03
Posts: 66,040

Re: [Solved]systemd kills boot up till version 252.1-2-arch

Post the journal of a "good" machine for comparism.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1 2 3 … 6

Board footer

Powered by FluxBB