Trouble with booting system after upgrade udev= systemd

Question

Hi everybody,
I have been trouble with my system since last upgrade (udev => systemd)
My issue is something like this: https://bbs.archlinux.org/viewtopic.php?pid=1106157 but advice from this discussion doesn't work.
When system booting, *immediately* (very fast, too fast) display login screen after start parsing hook [udev]
Of course, i can't login - type username and i have redraw screen again on all /dev/tty* - i have no chance to type password.
Many invalid logins suspend init for 5 minutes and allow me see display error due stop redraw screen - libpam.so.0 cannot find.
I suspect that, partitions aren't mount (this fast login screen doesn't have even hostname). I have a 4 discs, with many partitions - mounting
this take a some time (+- 5 secs).
In rescuecd, i can mount all partitions and chroot. In chroot all works fine - /bin/login (i was checked authorization on all users),
paths and pams are ok. Of course i try ,,default rescue trick'': `pacman -Suy linux udev mkinitcpio` and 'mkinitcpio -p linux' on rescuecd
but nothing it's changed after reboot. I checking grub config, and unpack and check initramfs-linux.img - all ok.
In my mkinitcpio.conf ofcourse i have MODULES="ext3" (for my filesystems).
Please help.

Answer 1

crab wrote:
This may or may not be related... but I saw this message just now during an upgrade:
(121/168) upgrading mkinitcpio [###################] 100%
==> If your /usr is on a separate partition, you must add the "usr" hook
to /etc/mkinitcpio.conf and regenerate your images before rebooting
And am wondering what the message means by if /usr is on a separate partition - separate partition to what?  /boot? / ?
I have my /usr partition in the same partition as /  (but /boot is in a different partition)
Logic tells me I'm safe (haven't rebooted yet), as / is "master", and anything else is a separate partition, and I have /usr on the same partition as /.
Do you guys have separate /usr and/or /boot partitions?  As stated in first sentence this may not be related, but looks important...
It means separate from /. So yes, you're right, you are "safe" from having to do anything with this message on your system.
And to the other people on this thread: make sure you do have all your packages uniformly updated, including any pam-related AUR or ABS-build packages. libpam and the pam module directory (.../lib/security) were moved from /lib to /usr/lib a little while back, so make sure that anything that cares about where these may be have been updated so they aren't confused by this move.
Last edited by ataraxia (2012-06-03 22:40:22)