too slow udisks2.service at boot #1033
Replies: 5 comments 4 replies
-
This should be almost instant, however in case of a complex storage setup or sleeping drives this may take a while. Please provide |
Beta Was this translation helpful? Give feedback.
-
I see you have two rotational HDDs and two CD-ROM drives. UDisks does some probing on startup, possibly spinning the drives up (HDDs when sleeping or CD-ROM media). Also, there are some filesystem tools called and SMART update. All this is doing some I/O and the drives may be simply too busy. Nine seconds startup time would suggest that, it's nothing unexpected. Can you also post |
Beta Was this translation helpful? Give feedback.
-
Have a look at here: https://wiki.ubuntu.com/Kernel/Reference/IOSchedulers It's just a performance tip that might improve your performance. UDisks 2.10.0 will improve things a little as we try to limit the filesystem tools execution in some cases. |
Beta Was this translation helpful? Give feedback.
-
FYI, UDisks 2.10.0 has just been released and carries a couple fixes that might help in your case. Make sure you have util-linux-2.39 that brought some improvements used by UDisks. |
Beta Was this translation helpful? Give feedback.
-
Hi Tomás, |
Beta Was this translation helpful? Give feedback.
-
Hi All,
I am writing about my Ubuntu 22.04 system. I have the following:
kernel: org.freedesktop.UDisks2
CPU: laci@Sanyika:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 43 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 12
On-line CPU(s) list: 0-11
Vendor ID: AuthenticAMD
Model name: AMD Ryzen 5 2600 Six-Core Processor
HDD: /dev/sda, 750.16 GB, SAMSUNG HD753LJ, /dev/sdb, 500.11 GB, SAMSUNG HD502IJ
(a bit old models, but I don't know where is the latest driver for them)
I am in the middle of accelerating my PC and it seems the the slowest part.
graphical.target @19.667s
└─udisks2.service @10.771s +8.895s
└─basic.target @9.585s
└─sockets.target @9.584s
└─uuidd.socket @9.584s
└─sysinit.target @9.501s
└─systemd-timesyncd.service @8.722s +778ms
└─systemd-tmpfiles-setup.service @7.179s +1.304s
└─systemd-journal-flush.service @4.321s +2.856s
└─systemd-remount-fs.service @4.075s +244ms
└─systemd-fsck-root.service @584542y 2w 2d 20h 1min 48.366s +89ms
└─systemd-fsckd.socket @3.974s
└─system.slice
└─-.slice
Can you please provide me with information on what are the alternatives to speed up? (service configuration change, driver uplift, . . . etc)
Thank you for your help.
L.
Beta Was this translation helpful? Give feedback.
All reactions