Ok, forget my comment for this issue.
After leaving the system alone for a couple of minutes it had been started and it seems that the padlock issue wasn't the cause because after looking at syslog I saw that this message occurs everytime when booting but doesn't cause a delay.
It rather seems to be a problem with ntp synching:
...
Jun 12 23:20:24 pc NetworkManager[987]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 12 23:20:31 pc kernel: [ 198.670027] eth0: no IPv6 routers present
Jun 12 23:20:32 pc ntpdate[1254]: adjust time server 91.189.94.4 offset -0.406334 sec
Jun 12 23:25:30 pc kernel: [ 497.243444] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jun 12 23:25:30 pc kernel: [ 497.244409] SGI XFS Quota Management subsystem
...
I'm really surprised that time server adjusting interrupts the whole boot process, but that's another issue...
Ok, forget my comment for this issue.
After leaving the system alone for a couple of minutes it had been started and it seems that the padlock issue wasn't the cause because after looking at syslog I saw that this message occurs everytime when booting but doesn't cause a delay.
It rather seems to be a problem with ntp synching:
... 987]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 12 23:20:24 pc NetworkManager[
Jun 12 23:20:31 pc kernel: [ 198.670027] eth0: no IPv6 routers present
Jun 12 23:20:32 pc ntpdate[1254]: adjust time server 91.189.94.4 offset -0.406334 sec
Jun 12 23:25:30 pc kernel: [ 497.243444] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jun 12 23:25:30 pc kernel: [ 497.244409] SGI XFS Quota Management subsystem
...
I'm really surprised that time server adjusting interrupts the whole boot process, but that's another issue...