Boot time - udisks2 PolicyKit timeout

Technical Support
, , ,
1

Hi there,

i am using a Apalis IMX8QM 4GB WB IT and Torizon Core 5.3 for a small Docker application.
I was trying to reduce boot time when i stumbled over the udisks2.service which takes up to about 25 seconds.

systemd-analyze blame | head
29.102s plymouth-quit-wait.service
25.523s udisks2.service
10.429s NetworkManager-wait-online.service
3.913s docker.service
1.316s dev-disk-by\x2dlabel-otaroot.device
1.303s plymouth-quit.service
1.008s systemd-logind.service
832ms systemd-networkd.service
780ms systemd-resolved.service
624ms systemd-journald.service

A closer look revealed a timeout on polkit.

systemctl -l status udisks2
● udisks2.service - Disk Manager
Loaded: loaded (/usr/lib/systemd/system/udisks2.service; disabled; vendor preset: disabled)
Active: active (running) since Thu 1970-01-01 00:00:32 UTC; 3min 20s ago
Docs: man:udisks(8)
Main PID: 697 (udisksd)
Tasks: 5 (limit: 3206)
Memory: 13.0M
CGroup: /system.slice/udisks2.service
└─697 /usr/libexec/udisks2/udisksd

Jan 01 00:00:06 apalis-imx8-06875081 systemd[1]: Starting Disk Manager…
Jan 01 00:00:06 apalis-imx8-06875081 udisksd[697]: udisks daemon version 2.9.0 starting
Jan 01 00:00:31 apalis-imx8-06875081 udisksd[697]: Error initializing polkit authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Jan 01 00:00:32 apalis-imx8-06875081 systemd[1]: Started Disk Manager.
Jan 01 00:00:32 apalis-imx8-06875081 udisksd[697]: Acquired the name org.freedesktop.UDisks2 on the system message bus

Is there a easy way to get rid of this error? Or at least to set the Timeout to a lower time?
Thanks for the help.

2

Greetings @Vinc2021,

Before I comment more in-depth I would like to give a suggestion first. You stated you are on TorizonCore 5.3. May I suggest you try out 5.4 first. We made many changes and optimizations that reduced overall boot time between 5.3 and 5.4.

I would ask you to evaluate the boot time in 5.4 first before we discuss any further here. For further user optimizations to boot time we also have an article here: TorizonCore Boot Time Optimization | Toradex Developer Center

Though this article is only relevant starting with version 5.4 forwards.

Best Regards,
Jeremias

3

Greetings @jeremias.tx ,

i finally hat time to test the Torizon 5.4.
Torizon 5.4 seems to work fine.
No timeouts of udisks2 and others.

systemd-analyze blame | head
5.703s plymouth-quit-wait.service
3.937s docker.service
2.054s dev-disk-by\x2dlabel-otaroot.device
1.796s plymouth-quit.service
1.580s systemd-logind.service
814ms systemd-networkd.service
791ms systemd-udevd.service
552ms systemd-udev-trigger.service
525ms udisks2.service
463ms systemd-resolved.service

The application is now running at about 20 Sec after Power Up, with is good enough for us.
Thx for the Tip.

Best Wishes.

4

Glad to hear Torizon 5.4 was sufficient for your needs!