Trouble with booting system after upgrade udev=>systemd

nnihitek · 2012-06-02 21:26:36

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.

alekgr · 2012-06-03 16:05:00

Yea, I got the same issue here.
Seems to be with issue with pam and maybe with systemd.. Still troubleshooting

Last edited by alekgr (2012-06-03 16:05:19)

nnihitek · 2012-06-03 17:02:07

Downgrade udev (to 182-2) and mkinitcpio (to 0.8.8-1) fixing problem at now, but it's only workaround (ex: xorg-* also requires downgrade to working)

crab · 2012-06-03 22:28:15

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...

ataraxia · 2012-06-03 22:35:46

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)

crab · 2012-06-03 22:48:12

ataraxia wrote:

It means separate from /. So yes, you're right, you are "safe" from having to do anything with this message on your system.

Cheers ataraxia

OrangeRoot1000 · 2012-06-04 20:28:02

I am trying to get my computer updated since the udev change a few days ago.
Usually on major changes I looked at the main home page, but here I didn't.
I know we do chroot all the time with an install and such, but this is the
first time I have had to specifially call one on a box. I am getting a failure
awk, gawk [: unary guides do not exist as a file or directory. Looking inside
of bin there is nothing from mkinitcpio to point to for the link in /etc. There
happens to be nothing in there at all.
I know this fix is easy, but I have not run across anything like this myself in
my time with linux.

mkdir /mnt/arch
mount /dev/sda3 /mnt/arch/
cd /mnt/arch
mount -t proc proc proc
mount -t sysfs sys sys
mount -o bind /dev/ dev/
mount /dev/sda1 boot/
cp -L /etc/resolv.conf etc/resolv.conf

chroot . /bin/bash <<<<< this is giving me the awk, gawk etc not existent errors

source /etc/profile
exit
umount proc sys dev boot
cd ..
umount /mnt/arch
reboot

Ideas as to what I am doing wrong? I run the lts Arch linux kernel instead of
linux one.
mkinitcpio -p linux-lts says there are no config files found in the /etc
directory at all.

gk

loafer · 2012-06-04 20:45:57

The only thing missing from the Wiki is "mount -t devpts pts dev/pts/".

alekgr · 2012-06-05 00:50:42

Now after a 20 times of typing root on login getting /bin/login: error while loading shared libraries: libpam.so.0: cannot open shared file: No such file or directory INIT: ld "c1" respawing too fast: disabled for 5 minutes

ImNtReal · 2012-06-05 13:04:41

I'm not sure if this is the same issue I had, but do any of you experiencing the problem mount your / and /boot using labels to identify the partitions? If so, either the switch to systemd-tools, or the update to device mapper is causing this:

#ls /dev/disk/by-label/
\x2f  \x2fboot  swap

I'm not positive how it looked before, but prior to that upgrade, they mounted with LABEL=/ and LABEL=/boot. After, I switched to UUID, and all is well.

alphaniner · 2012-06-05 13:33:12

@ImNtReal

FWIW, I have the latest systemd and dm and use labels with no issues. Maybe it had to do with the '/' in your labels.

$ ls /dev/disk/by-label/
arch  boot  data  home  lvbucket  recover  swap1  var

alekgr · 2012-06-05 15:22:03

Yea.. I use uuid for my mounted drives

alekgr · 2012-06-05 15:24:33

Also I have system rescued and chrooted and able to see the libpam.so.0 in folder. I have a feeling maybe it something to do with initramfs

ImNtReal · 2012-06-05 15:39:26

alphaniner wrote:

@ImNtReal
FWIW, I have the latest systemd and dm and use labels with no issues. Maybe it had to do with the '/' in your labels.

I think it does. It looks like / may have changed into \x2f. Unfortunately, I can't verify that they didn't look that way prior to the upgrade. Also, I'm not positive which package would have made the change. I just wanted to offer up the tidbit in case anyone else found themselves in the same position.

gbrunoro · 2012-06-08 19:46:15

nnihitek wrote:

Downgrade udev (to 182-2) and mkinitcpio (to 0.8.8-1) fixing problem at now, but it's only workaround (ex: xorg-* also requires downgrade to working)

Had the same problem as OP here. I've already created a new boot image after to downgrading udev and mkinitcpio, but I'm still unable to boot.

nnihitek · 2012-06-08 20:21:06

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...

Thank you. This solved my problem few days ago (usr to HOOKS - i have /usr on separate partition).

gbrunoro · 2012-06-08 20:22:20

update: after downgrading a lot of packages to arbitrary lower versions, the system seems to be working with some broken libs.

mrkurtz · 2012-06-11 22:02:45

same issue here, turned out the mkinitcpio /usr hook was the culprit. not sure how many upgrades since we were required to add the /usr hook the first time, but, somehow in a very recent upgrade, the /usr hook went away. seems strange that given all the upgrades between then and now that have gone off without a problem, this recent one caused issues.

i went through and added the hook back, rebuilt the image, and everything's up and running no problem.

gabx · 2012-06-12 20:08:18

mrkurtz wrote:

same issue here, turned out the mkinitcpio /usr hook was the culprit. not sure how many upgrades since we were required to add the /usr hook the first time, but, somehow in a very recent upgrade, the /usr hook went away. seems strange that given all the upgrades between then and now that have gone off without a problem, this recent one caused issues.
i went through and added the hook back, rebuilt the image, and everything's up and running no problem.

I experienced exactly what was described in OP. I can not login anymore after a huge upgrade (15/05-12/06).
My /usr and /boot are not on same partition than /.

So I understand I must add hook and rebuilt an image. As I am far from being an expert, may you tell me how you proceed? I guess I must boot from a live cd, right? Then, what are the main steps? I dual boot with Ubuntu, can I do anything from this distro?

TY for your help.

gabx · 2012-06-13 10:23:12

after reading all the posts and trying to figure out why I couldn't login, I went to the conclusion my filesystem was not mounted. As I have /usr on a separate partition, I found too that adding "usr shutdwon" in the /etc/mkinitcpio.conf, then rebuilding the image

$mkinitcpio -p linux

when chrooting with a live CD solved my issue.

Thank you for your hints. Maybe can we mark this thread as SOLVED as it seems this workaround is a clean and working solution to this issue after upgrading to systemd for users with a separate /usr ?

Last edited by gabx (2012-06-14 20:56:46)

gbrunoro · 2012-06-14 17:07:28

indeed, updating mkinitcpio and rebuilding the boot image solved it for me too.

Arch Linux

#1 2012-06-02 21:26:36

Trouble with booting system after upgrade udev=>systemd

#2 2012-06-03 16:05:00

Re: Trouble with booting system after upgrade udev=>systemd

#3 2012-06-03 17:02:07

Re: Trouble with booting system after upgrade udev=>systemd

#4 2012-06-03 22:28:15

Re: Trouble with booting system after upgrade udev=>systemd

#5 2012-06-03 22:35:46

Re: Trouble with booting system after upgrade udev=>systemd

#6 2012-06-03 22:48:12

Re: Trouble with booting system after upgrade udev=>systemd

#7 2012-06-04 20:28:02

Re: Trouble with booting system after upgrade udev=>systemd

#8 2012-06-04 20:45:57

Re: Trouble with booting system after upgrade udev=>systemd

#9 2012-06-05 00:50:42

Re: Trouble with booting system after upgrade udev=>systemd

#10 2012-06-05 13:04:41

Re: Trouble with booting system after upgrade udev=>systemd

#11 2012-06-05 13:33:12

Re: Trouble with booting system after upgrade udev=>systemd

#12 2012-06-05 15:22:03

Re: Trouble with booting system after upgrade udev=>systemd

#13 2012-06-05 15:24:33

Re: Trouble with booting system after upgrade udev=>systemd

#14 2012-06-05 15:39:26

Re: Trouble with booting system after upgrade udev=>systemd

#15 2012-06-08 19:46:15

Re: Trouble with booting system after upgrade udev=>systemd

#16 2012-06-08 20:21:06

Re: Trouble with booting system after upgrade udev=>systemd

#17 2012-06-08 20:22:20

Re: Trouble with booting system after upgrade udev=>systemd

#18 2012-06-11 22:02:45

Re: Trouble with booting system after upgrade udev=>systemd

#19 2012-06-12 20:08:18

Re: Trouble with booting system after upgrade udev=>systemd

#20 2012-06-13 10:23:12

Re: Trouble with booting system after upgrade udev=>systemd

#21 2012-06-14 17:07:28

Re: Trouble with booting system after upgrade udev=>systemd

Board footer