-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: unable to write to pipe (Broken pipe) #2628
Comments
Same. Version:
|
Can you please try dracut-git arch package (instead of te dracut arch package) as that is closer to the state of upstream ? |
i am also having this same issue. i tried with darcut-git but same result |
Hi :-) Could it be that this has nothing to do with dracut itself but with pacman/libalpm? |
Describe the bug
When updating the System with
pacman -Syu
oryay
sometimes you'd get "error: unable to write to pipe (Broken pipe)". I can't make sense of it and don't know what's causing it though i saw this popping up in the EndeavourOS Forums a few times and also experienced it on Arch. Running dracut again right after will not bring up the error again. It shouldn't be a space Error since i have 1GB Space for /efi and only one Kernel/Fallback installed. For example my current drive looks like/dev/nvme1n1p1 999M 101M 898M 11% /efi
Distribution used
have seen this on both Arch and EndeouverOS and on different systems (one is an Intel/NV system the other a Pure AMD System)
Dracut version
059-5
Init system
Systemd
To Reproduce
just update the system using for example yay or pacman -Syu (today is a good day. To do so when using EndeavourOS happend on both my Systems)
Expected behavior
shouldn't happen
Additional context
It'S actually not clear what's the cause of it. It could be visible only since it happens right after creating the Initrd
the Error will look like
in case it helps these were the packages that got upgrades
The text was updated successfully, but these errors were encountered: