Vero 2 takes along time to boot, waiting for udev

Help and Support Vero 2
1

Hi,

My vero 2 needed a reboot the other day and got stuck for about 1.5 minute on waiting for udev.

I don’t know if the logs are sufficient when not enabled debug log: https://paste.osmc.tv/ufesaqihey

I think the relevant part is this:

Jun 27 14:06:29 osmc-vero2 systemd[1]: Started Rebuild Hardware Database.
Jun 27 14:06:29 osmc-vero2 systemd[1]: Starting udev Coldplug all Devices...
Jun 27 14:06:29 osmc-vero2 systemd[1]: Created slice system-lircd_helper.slice.
Jun 27 14:06:30 osmc-vero2 systemd[1]: Started udev Coldplug all Devices.
Jun 27 14:06:30 osmc-vero2 systemd[1]: Starting udev Wait for Complete Device Initialization...
Jun 27 14:06:30 osmc-vero2 systemd[1]: Reached target Sound Card.
Jun 27 14:06:30 osmc-vero2 systemd-udevd[188]: Error calling EVIOCSKEYCODE on device node     '/dev/input/event1' (scan code 0x7004a, key code 1): Invalid argument
Jun 27 14:06:30 osmc-vero2 systemd-udevd[193]: Error calling EVIOCSKEYCODE on device node     '/dev/input/event0' (scan code 0x10084, key code 180): Invalid argument
Jun 27 14:06:30 osmc-vero2 systemd-udevd[193]: Error calling EVIOCSKEYCODE on device node     '/dev/input/event0' (scan code 0xc0060, key code 179): Invalid argument
Jun 27 14:06:30 osmc-vero2 systemd[1]: Found device /dev/ttyS0.
Jun 27 14:06:30 osmc-vero2 kernel: ionvideo open
Jun 27 14:06:30 osmc-vero2 kernel: ionvideo_stop_generating!!!!
Jun 27 14:06:30 osmc-vero2 kernel: ionvideo release
Jun 27 14:07:30 osmc-vero2 systemd-udevd[179]: seq 1113 '/devices/platform/c8100580.meson-    ir/rc/rc0/lirc0' is taking a long time
Jun 27 14:08:30 osmc-vero2 systemd[1]: systemd-udev-settle.service: Main process exited,     code=exited, status=1/FAILURE
Jun 27 14:08:30 osmc-vero2 systemd[1]: Failed to start udev Wait for Complete Device Initialization.
Jun 27 14:08:30 osmc-vero2 systemd[1]: systemd-udev-settle.service: Unit entered failed state.
Jun 27 14:08:30 osmc-vero2 systemd[1]: systemd-udev-settle.service: Failed with result 'exit-code'.

I wonder if the remote dongle is failing? The remote stopped working but works after a fresh battery was inserted.

2

What devices do you have connected to the Vero?

3

Only the remote dongle that came with the device., plugged in the back USB port. Ethernet cable and all media over a smb share.

4

You could try the receiver in a different USB port. Ideally it should be in the rear port, not a side port.

Sam

5

Yes, it is situated in the rear port since I got the device. its always on so i don’t reboot very often.

6

Ok, so I removed everything and rebooted and it’s stuck on the same udev thing. It boots, but gets stuck on waiting for udev about 1.5 minute.

Logs: https://paste.osmc.tv/xujisikoje

The part that looks suspicious in the boot log:

Jun 28 11:10:05 osmc-vero2 systemd-udevd[173]: seq 1102 '/devices/platform/c8100580.meson-ir/rc/rc0/lirc0' is taking a long time
Jun 28 11:11:07 osmc-vero2 systemd[1]: systemd-udev-settle.service: Main process exited, code=exited, status=1/FAILURE
Jun 28 11:11:07 osmc-vero2 systemd[1]: Failed to start udev Wait for Complete Device Initialization.
Jun 28 11:11:07 osmc-vero2 systemd[1]: systemd-udev-settle.service: Unit entered failed state.
Jun 28 11:11:07 osmc-vero2 systemd[1]: systemd-udev-settle.service: Failed with result 'exit-code'.

So it must be something internal in the vero that’s failing @sam_nazarko

7

It might be a bug. I’ll check this shortly.

8

Any progress on this @sam_nazarko?

9

Does sudo rm /etc/modules-load.d/ir.conf solve the delayed boot?
If so – I think you need to reinstall OSMC

11

Yes it did. Any Ideas what’s wrong? file system corruption or something else? Might just replace it with my vero 4K+ that I haven’t bothered to install yet :slight_smile:

12

I’m not sure. I seem to recall you making a lot of changes to your system, so that could be a cause.

13

Nope, this is a 100% stock system from when it was new.

14

Okay. A reinstall should solve the problem, but it’s a bit of a brute force approach.