| 1 |
On Thursday, 1 August 2019 20:29:08 BST Jack wrote: |
| 2 |
> On 2019.08.01 09:59, Helmut Jarausch wrote: |
| 3 |
> > Hi, |
| 4 |
> > since the upgrade from systemd-242-r6 to systemd-243_rc1 I cannot |
| 5 |
> > mount my (external) USB drive any more. |
| 6 |
> > I get |
| 7 |
> > kernel: sd 10:0:0:0: [sde] Assuming drive cache: write through |
| 8 |
> > kernel: sde: sde1 sde2 sde3 sde4 sde5 sde6 sde7 |
| 9 |
> > kernel: systemd-udevd[480887]: |
| 10 |
> > Assertion 'key' failed at |
| 11 |
> > src/libsystemd/sd-device/device-private.c:34, |
| 12 |
> > function device_add_property(). Aborting. |
| 13 |
> > |
| 14 |
> > The strange thing is, I don't use systemd on start-up (I'm using |
| 15 |
> > openrc) but I have systemd installed here. |
| 16 |
> > This configuration has been working for a very long time. |
| 17 |
> > |
| 18 |
> > Many thanks for a hint, |
| 19 |
> > Helmut |
| 20 |
> |
| 21 |
> Helmut, |
| 22 |
> |
| 23 |
> You say you don't use systemd on start-up, but is any of it running |
| 24 |
> when you get this error? If you aren't using it at start-up, I wonder |
| 25 |
> what the implcations are of having it installed - where might it have |
| 26 |
> insinuated itself, so it gets called instead of something else you |
| 27 |
> might have expected. |
| 28 |
> |
| 29 |
> Next time you get the error, can you do "ps auxf" to see if you can |
| 30 |
> tell what processes called systemd-udevd? |
| 31 |
> |
| 32 |
> Jack |
| 33 |
|
| 34 |
Could it be the systemd upgrade you refer to interfered with any udev rules |
| 35 |
you had set up to deal with your external drive, or in any case changes in |
| 36 |
udev rules are no longer agreeable with your external device? |
| 37 |
|
| 38 |
-- |
| 39 |
Regards, |
| 40 |
|
| 41 |
Mick |
Archives