On Thu, Feb 14, 2019 at 6:39 PM Vincent Danjean <vdanj...@debian.org> wrote:
> Package: udev > Version: 240-5 > Severity: serious > Justification: render the system unbootable > > Hi, > > After a major upgrade to unstable (the system was not upgraded > during a few months) and after a reboot, udevd refuse to start. This leads > to > LVs (of LVM) to not appear in /dev (but the LV where the root FS is > stored). I > was offered to type the root password to go to an emergency shell. > > Trying to restart the systemd-udevd service failed. > Looking to log with journalctl give me very few info: > févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager... > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process > exited, code=killed, status=31/SYS > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with > result 'signal'. > févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device > Manager. > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no > hold-off time (RestartSec=0), scheduli > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled > restart job, restart counter is at 1. > févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager. > févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager... > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process > exited, code=killed, status=31/SYS > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with > result 'signal'. > févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device > Manager. > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no > hold-off time (RestartSec=0), scheduli > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled > restart job, restart counter is at 2. > févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager. > févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager... > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process > exited, code=killed, status=31/SYS > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with > result 'signal'. > févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device > Manager. > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no > hold-off time (RestartSec=0), scheduli > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled > restart job, restart counter is at 3. > févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager. > févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager... > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process > exited, code=killed, status=31/SYS > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with > result 'signal'. > févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device > Manager. > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no > hold-off time (RestartSec=0), scheduli > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled > restart job, restart counter is at 4. > févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager. > févr. 14 14:13:46 eyak systemd[1]: Starting udev Kernel Device Manager... > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Main process > exited, code=killed, status=31/SYS > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with > result 'signal'. > févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device > Manager. > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Service has no > hold-off time (RestartSec=0), scheduli > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Scheduled > restart job, restart counter is at 5. > févr. 14 14:13:46 eyak systemd[1]: Stopped udev Kernel Device Manager. > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Start request > repeated too quickly. > févr. 14 14:13:46 eyak systemd[1]: systemd-udevd.service: Failed with > result 'signal'. > févr. 14 14:13:46 eyak systemd[1]: Failed to start udev Kernel Device > Manager. > > Then, I looked at the service file and tried to manually start > systemd-udevd. It seems to work. So, I stopped it and > comment-out most of systemd features in the service file. In > /lib/systemd/system/systemd-udevd.service I have now: > #PrivateMounts=yes > #MemoryDenyWriteExecute=yes > #RestrictRealtime=yes > #RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 > #SystemCallArchitectures=native > #LockPersonality=yes > #IPAddressDeny=any > > It worked (systemd-udevd started with systemctl and also after > a reboot) > > I did not try to find the specific feature that was problematic > as I quickly needed the computer for (long) production. If you need > more info or tests, I should be able to reboot the system in a few > days. > > Regards, > Vincent > > -- Package-specific info: > > -- System Information: > Debian Release: buster/sid > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, > 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, armel, mipsel > Is udev by any chance i386 instead of amd64? -- Saludos, Felipe Sateler
