Update hung up on post trans update

English Install/Boot/Login
1

Did a zypper dup today on my Tumbleweed and appeared to crash on the below line:

Running %posttrans(dracut-059+suse.665.gd2af7028-1.1.x86_64) script <3%> =======[|]

When I say crash it went to the HP logo screen with the spinning circle and the Tumbleweed logo at the bottom. That usually happens on reboot. I hit esc to see if I could see any messages and it was a blank screen. Waited a bit thinking I had an issue I fixed with unmounting drives, and got impatient and hit ctrl-alt-f3 and low and behold my desktop is still there working. So I see itā€™s there, give it a few minutes still stuck at 3%, so I hit ctrl-c to stop it. It says ā€œTrying to exit gracefullyā€¦ā€ and is sitting there.

Iā€™m a bit worried, so not sure what this means or how to fix. It did update the nvidia drivers today so it had to build them. Iā€™m going to do a hard reboot and see if my system is hosed. I can live with iGPU for a while.

QUESTION: does anyone know a way to re-run the %posttrans(dracut-059+suse.665.gd2af7028-1.1.x86_64) script after-the-fact? Is there a file somewhere? Wish me luck, Iā€™m off to reboot. I guess Iā€™m grateful for btrfs

2 Likes
2

You can force a reinstall using zypper in -f <packagename> - that will reinstall the package and rerun any scripts, assuming you donā€™t revert to an earlier snapshot.

1 Like
3

I am getting the same, i guess maybe its because of the nvidia drivers update? I did it even from the tty, same experience.
Failed to start Postfix Mail Transport Agent

4

I donā€™t know what package needs to be reinstalled. Iā€™m not sure what that %posttrans is, I assume itā€™s cleanup and changes to system config files? But I hesitate to make assumptions.

5

The message shows ā€˜dracutā€™ as the package name in the message you shared. That particular package is what builds the initrd for the system. It might be some other kernel-related package thatā€™s the root cause of the issue, though.

6

Yeah I donā€™t know enough to tell you what is going on in those messages, but I always thought that the %posttrans was a generic ā€œpost install cleanupā€ type thing that ran post-install scripts which made me think that the dracut had finished fine. I rebooted, all went well and I just checked and Iā€™m on kernel 6.11.8-1-default so I hope that is the current one.

Since all seems well Iā€™m going to roll with it. I was just wondering where that script was so I could try to rerun it. If it hung again, while Iā€™m no ā€œprogrammerā€ if itā€™s a simple bash type script I could at least attempt to determine where in the file it is hanging up.

7

Same issue here. Looking at the journald log, I donā€™t think anything crashed, exactly. I think the issue is related to the update of plymouth (the boot splash program). For some reason, the posttrans script caused plymouth to get restarted, and plymouth ā€œstoleā€ the screen away from the desktop environment (Plasma or GNOME or ā€¦).

Should probably be reported as a bug in the update script.

8

Here is the relevant journald log (most recent line first). After the top line, thereā€™s nothing abnormal in the log until I hit the power button on my laptop.

Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Starting Hold until boot process finishes up...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Started Show Plymouth Boot Screen.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Finished Tell Plymouth To Write Out Runtime Data.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Finished Check if mainboard battery is Ok.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: check-battery.service: Deactivated successfully.
Nov 26 18:48:42 mt-dell-tumbleweed plymouthd[22514]: 00:34:22.016 ../src/main.c:2122:initialize_environment                     : source built on Nov 15 2024
Nov 26 18:48:42 mt-dell-tumbleweed plymouthd[22514]: 00:34:22.016 ../src/main.c:2048:check_logging                              : logging will be enabled!
Nov 26 18:48:42 mt-dell-tumbleweed plymouthd[22514]: 00:34:22.016 ../src/main.c:2036:check_logging                              : checking if console messages should be redirected and logged
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Starting Show Plymouth Boot Screen...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopping Show Plymouth Boot Screen...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopped Show Plymouth Boot Screen.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopping Show Plymouth Boot Screen...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopped Show Plymouth Boot Screen.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: plymouth-start.service: Deactivated successfully.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopping Tell Plymouth To Write Out Runtime Data...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopped Tell Plymouth To Write Out Runtime Data.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: plymouth-read-write.service: Deactivated successfully.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopping Hold until boot process finishes up...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopped Hold until boot process finishes up.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: plymouth-quit-wait.service: Deactivated successfully.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Starting Check if mainboard battery is Ok...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Started Discard unused filesystem blocks once a week.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopping Discard unused filesystem blocks once a week...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopped Discard unused filesystem blocks once a week.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: fstrim.timer: Deactivated successfully.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopping Forward Password Requests to Plymouth Directory Watch...
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Queuing reload/restart jobs for marked unitsā€¦
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: Reloading finished in 289 ms.
Nov 26 18:48:42 mt-dell-tumbleweed systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update the service to use a safer KillMode=, such as>
Nov 26 18:48:42 mt-dell-tumbleweed systemd-ssh-generator[22506]: ā†’ connect via 'ssh .host' locally
Nov 26 18:48:42 mt-dell-tumbleweed systemd-ssh-generator[22506]: Binding SSH to AF_UNIX socket /run/ssh-unix-local/socket.
Nov 26 18:48:41 mt-dell-tumbleweed systemd[1]: Reloading...
Nov 26 18:48:41 mt-dell-tumbleweed systemd[1]: Reload requested from client PID 22416 ('systemctl') (unit user@1000.service)...
Nov 26 18:48:37 mt-dell-tumbleweed systemd-udevd[3905]: Configuration file /etc/udev/rules.d/54-smfp_samsung.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Nov 26 18:48:22 mt-dell-tumbleweed kernel: block dm-0: the capability attribute has been deprecated.
Nov 26 18:48:15 mt-dell-tumbleweed plasmashell[5138]: KPackageStructure of KPluginMetaData(pluginId:"org.kde.merkuro.contact", fileName: "/usr/share/plasma/plasmoids/org.kde.merkuro.contact/metadata.json") does not match requested format "Plasma/Applet"
Nov 26 18:48:15 mt-dell-tumbleweed [RPM][11199]: Transaction ID 67465e3f finished: 0
Nov 26 18:48:15 mt-dell-tumbleweed [RPM][11199]: install jupyter-ipyparallel-8.8.0-1.2.noarch: success
Nov 26 18:48:15 mt-dell-tumbleweed [RPM][11199]: erase jupyter-ipyparallel-8.8.0-1.1.noarch: success
Nov 26 18:48:15 mt-dell-tumbleweed [RPM][11199]: install jupyter-ipyparallel-8.8.0-1.2.noarch: success
Nov 26 18:48:15 mt-dell-tumbleweed [RPM][11199]: erase jupyter-ipyparallel-8.8.0-1.1.noarch: success
Nov 26 18:48:15 mt-dell-tumbleweed [RPM][11199]: Transaction ID 67465e3f started
9

yes its plymouth. Trying sudo zypper in -f plymouth will do the same as you described. Is it even needed? can you just delete plymouth?

10

There seem to be a couple of different things being discussed here.

There is apparently a known issue with a delay during startup where plymouth hangs up for 30 seconds during boot. That can be mitigated, from what I understand, by removing the splash=quiet line from the kernel load line at the boot loader screen (you just have to press ā€˜eā€™ to edit the selected menu option and then remove it from the line and tell the boot to continue). Thatā€™s a temporary fix that makes no permanent change to the system.

Thatā€™s different than the issue with the posttrans script failure that JBinFla is asking about.

11

no its just plymouth got also updated today, with dracut. And reinstalling plymouth does the exact same black screen as in posttrans of dracut

12

6.11.8-1 is the version Iā€™m on as well, so that seems fine.

Looking at the posttrans script (from rpm -q --scripts dracut), itā€™s calling /usr/lib/module-init-tools/regenerate-initrd-posttrans if it exists. That script hasnā€™t been updated since September of 2024 according to the changelog, so itā€™s not likely that something got broken in the script itself.

If things seem to be running fine, then I probably wouldnā€™t worry about it for now.

13

This sounds like a different issue to me, especially the Postfix element. Probably worth starting a separate discussion.

14

So dracut is innocent here. Its just plymouth did its dirty thing with black screen while dracut was posttransing, because they both got updated in todayā€™s dup. And btw plymouth can be safely deleted, since its not in use anyway because of long boot bug

15
16

Thanks for that post, so looks like it was Plymouth as the behavior I saw was similar. I was able to switch to different ttyā€™s tho (used 1-3, 1 being default terminal, 2 is sddm and 3 was my Wayland session still running) donā€™t try others but some states they were unresponsive and mine wasnā€™t. Tho I did wait about 5 minutes ā€œhopingā€ it would finish.

I did notice this message in that thread tho:

So yeah, plymouth was restarted, causing the splash screen to force itself and inhibit a bunch of unit activations.

I wonder what unit activations I may be missing? Dunno. Tonight I hope thereā€™s more updates so Iā€™ll give it a whirl. I may try to force a reinstall of Plymouth. I did reboot several times and the splash screen seems to be working and after the workaround for my ā€œreboot hangs trying to unmount CIFS sharesā€ the reboot from typing in terminal to back at my KDE desktop is under a 30-seconds (I havenā€™t timed it thatā€™s my guess). So. All seems well!

1 Like
17

Iā€™m having exactly the same issue, except that my posttrans-script stopped at 1% (not 3%). After waiting about 1 minute and unsuccessfully trying to stop the execution of the script using ctrl+c/d, I went back to the desktop and killed zypper. I then ran ā€œzypper dupā€ again, but it said there was nothing new to install. So zypper doesnā€™t seem to be able to determine if the posttrrans script was successfully completed!(?). I then restarted and couldnā€™t find any problems. So I will not do a rollback for now!

18

Same issue here. While itā€™s hung, reboot/shutdown are blocked so I finally had to resort to kill -31 the zypper process to regain control. Is there any way to check/repair any damage that caused?

After all this, plymouth still has the 30 second hang. Plymouth should be reverted and not allowed to push yet another broken patch.

19

Facing the same issue, and reinstalling Plymouth causes it too. Is there any known fix for this?

20

Delete all plymouth named stuff?