Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39407 - Systemd breaks boot after new update due to disk dependencies not satisfied
Attached to Project:
Arch Linux
Opened by Andrea (Melkor) - Friday, 14 March 2014, 09:51 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Friday, 14 March 2014, 17:49 GMT
Opened by Andrea (Melkor) - Friday, 14 March 2014, 09:51 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Friday, 14 March 2014, 17:49 GMT
|
DetailsDescription:Systemd update doesnt recognize disks
After having updated to the new systemd version, I am unable to boot as the boot process gets stuck at "A start job is running for..." followed by all the devices in my fstab. I never experienced this issue before, and downgrading to the old systemd fixes the problem. I am currently in recovery mode and navigating from lynx, which doesn't allow me to upload the files, so I will append them here http://sprunge.us/XWde http://sprunge.us/PhbF http://sprunge.us/LcdR http://sprunge.us/hFWM http://sprunge.us/jjPT http://sprunge.us/ZKHT http://sprunge.us/cZcL Thank you in advance! Additional info:none * package version(s)210-3 * config and/or log files etc. Journalctl fstab udevadm Steps to reproduce:Update to systemd 210-3 Boot |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Friday, 14 March 2014, 17:49 GMT
Reason for closing: Not a bug
Friday, 14 March 2014, 17:49 GMT
Reason for closing: Not a bug
1) the journal of the boot, with udev in debug logging mode
2) my fstab
3-4-5-6) udevadm info -p for some of the affected devices
7) dmesg|tail after mounting the same devices.
as you can see, the nodes are created nonetheless, and I am able to mount them without any problem. This is what is strange.
> Boot
What do I do when this succeeds? What else did you upgrade with systemd? What about 211?