udev 238-5 upgrade from 2018-06-27-raspbian-stretch-lite image

Bug #1779563 reported by Michael on 2018-07-01
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Raspbian
Undecided
Unassigned

Bug Description

Hi,

I upgrade straight away from stretch (using 2018-06-27-raspbian-stretch-lite image on a Raspberry Pi 3) and the issue popped-up, I get no log on what is wrong with udev, just:

 systemctl status systemd-udevd.service
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-07-01 11:24:00 CEST; 2min 48s ago
     Docs: man:systemd-udevd.service(8)
           man:udev(7)
  Process: 5732 ExecStart=/lib/systemd/systemd-udevd (code=exited, status=127)
 Main PID: 5732 (code=exited, status=127)

so aptitude failed with:

sudo aptitude upgrade
Résolution des dépendances…
Les paquets partiellement installés suivants seront configurés :
  bluez plymouth udev
Aucun paquet ne va être installé, mis à jour ou enlevé.
0 paquets mis à jour, 0 nouvellement installés, 0 à enlever et 1 non mis à jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 0 o seront utilisés.
Paramétrage de udev (238-5) ...
Job for systemd-udevd.service failed because the control process exited with error code.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor preset: enabled)
   Active: activating (start) since Sun 2018-07-01 11:30:11 CEST; 39ms ago
     Docs: man:systemd-udevd.service(8)
           man:udev(7)
 Main PID: 5810 (systemd-udevd)
   CGroup: /system.slice/systemd-udevd.service
           └─5810 [systemd-udevd]
dpkg: erreur de traitement du paquet udev (--configure) :
 installed udev package post-installation script subprocess returned error exit status 1
dpkg: des problèmes de dépendances empêchent la configuration de bluez :
 bluez dépend de udev ; cependant :
 Le paquet udev n'est pas encore configuré.

dpkg: erreur de traitement du paquet bluez (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de plymouth :
 plymouth dépend de udev (>= 232-8~) ; cependant :
 Le paquet udev n'est pas encore configuré.

dpkg: erreur de traitement du paquet plymouth (--configure) :
 problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
 udev
 bluez
 plymouth
E: Sub-process /usr/bin/dpkg returned an error code (1)
Paramétrage de udev (238-5) ...
Job for systemd-udevd.service failed because the control process exited with error code.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor preset: enabled)
   Active: activating (start) since Sun 2018-07-01 11:30:16 CEST; 27ms ago
     Docs: man:systemd-udevd.service(8)
           man:udev(7)
 Main PID: 5871 (systemd-udevd)
   CGroup: /system.slice/systemd-udevd.service
           └─5871 [systemd-udevd]
dpkg: erreur de traitement du paquet udev (--configure) :
 installed udev package post-installation script subprocess returned error exit status 1
dpkg: des problèmes de dépendances empêchent la configuration de bluez :
 bluez dépend de udev ; cependant :
 Le paquet udev n'est pas encore configuré.

dpkg: erreur de traitement du paquet bluez (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de plymouth :
 plymouth dépend de udev (>= 232-8~) ; cependant :
 Le paquet udev n'est pas encore configuré.

dpkg: erreur de traitement du paquet plymouth (--configure) :
 problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
 udev
 bluez
 plymouth

Debian close (and closed) issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902185

Michael Biebl's fix (see link just above) cannot be used as these config doesn't exists at all in this version.
udev failed to start but give no useful info on what's wrong. System then just doesn't boot (tried before), systemd is already the latest available on testing.

Looks like no one get into it or are unable to spot the actual guilty as I get nothing related to this issue on Internet.

Steps:
- install Raspbian image given above on a sdcard,
- create ssh file,
- put sdcard on the Pi, boot
- change 'stretch' to 'testing' on etc/apt/sources.list
- do sudo aptitude update,
- then sudo aptitude upgrade

dom96 (dom96) wrote :

Same issue here. I wanted to grab just one package from Buster but adding the sources.list for it meant that I upgraded to it by accident too :(

Carlos Bouzón García (bougar) wrote :

I have fixed the issue purging the "raspi-copies-and-fills" package. More detailed information about this fix can be found here: https://raspberrypi.stackexchange.com/questions/72594/failed-to-start-udev-kernel-device-manager

Maybe a more viable solution would be to compile the last version of the https://github.com/bavison/arm-mem repository to see if the problem is fixed correctly as suggested in the last answer of the provided stackexchange topic.

Carlos Bouzón García (bougar) wrote :

I can confirm the last version of the https://github.com/bavison/arm-mem repository is working properly.
The steps that I have followed:
1. Purge "raspi-copies-and-fills" package
2. Clone https://github.com/bavison/arm-mem repository using "git" tool
3. 'make' command to compile from source
4. 'cp libarmmem-v7l.so /usr/lib/arm-linux-gnueabihf/libarmmem.so'
5. 'echo "/usr/lib/arm-linux-gnueabihf/libarmmem.so" >> /etc/ld.so.preload'
Maybe is not the best solution but is working at the moment. It would be nice an update of the "raspi-copies-and-fills" package.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers