Attention with the update today for grub2. I installed it an hour ago and the system is completely broken. I cannot login and the OS complains that the system volume is not found. When trying to mount the LVM volume with a KDE life CD (12.1) it refuses with error 3016 (probably your password is wrong) - but I tried and the password is right. So it appears that the issue is with encryption. Any suggestion to understand what is wrong?
To make it more clear:
Without doubt you mean the update that is in the Update repo for grub2.
Thus the warning is not to run YaST > Software > Online update, or zypper patch (or an equivalent from PackageManager) without further knowledge about this phenomenon.
Yes sorry. I have the face blue and red and was a bit “emotionally challenged”. It is exactly as you said.
At start up grub goes up to the moment when the LUKS password for the LVM partition should be asked. Then it runs over and over again: cannot find system volume, registering, this may take a while. It is then a loop that takes forever.
By using a live CD with 12.1 on it (this is what I have under my hands) I can access the disc boot and its content. I can see the correct partition setup, with /boot and the LVM partition seen as encrypted.
When I try to mount with the partitioner tool in yast it tells me “unable to register password error -3016”. So, I checked but the password is right.
I tried to mount on the command line but:
linux:~ # cryptsetup luksOpen /dev/sda2
cryptsetup: luksOpen: requires <device> <name> as arguments
This answer I do not understand at all. because:
linux:~ # fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000d7e9
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 321535 159744 83 Linux
/dev/sda2 321536 976773119 488225792 8e Linux LVM
Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0003de95
Device Boot Start End Blocks Id System
/dev/sdb1 16065 488392064 244188000 83 Linux
linux:~ #
To be clear: the laptop has one only disk (sda) with default LUKS encrypted partitioning.
It sits on an ultrabase with another HDD inside (sdb) that was not mounted at the accident, nor was it mounted ever before on this system.
So /dev/sda2 IS to all extend the right name. But mount /dev/sda1 /temp is done without problem. So it allows me to see /boot.
O.K., going offline now because I am boiled. I am now as far as I can open with luksOpen but I do get the following error when I try to mount
Failure occurred during following action:
Mounting /dev/sda2 to /local
System error code was: -3003
/bin/mount -t auto ‘/dev/mapper/cr_sda2’ ‘/local’:
mount: unknown filesystem type ‘LVM2_member’
Continue despite the error?
Should I continue and trying to mount? What is wrong now? The volume opens apparently correctly (also in the command line there is no O.K. on the luksOpen command and no slot indication, that may tell something is wrong.
On 2013-01-14 23:46, stakanov wrote:
>
> I tried to mount on the command line but:
>
> Code:
> --------------------
> linux:~ # cryptsetup luksOpen /dev/sda2
> cryptsetup: luksOpen: requires <device> <name> as arguments
>
> --------------------
>
> This answer I do not understand at all. because:
It is clear enough. The manual says you have to do:
cryptsetup luksOpen device name
You are giving the device, but not the name. You miss one argument. The
name is arbitrary.
–
Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)
On 2013-01-15 00:26, stakanov wrote:
>> /bin/mount -t auto ‘/dev/mapper/cr_sda2’ ‘/local’:
>> mount: unknown filesystem type ‘LVM2_member’
>> Continue despite the error?
You can not mount an LVM like that. ‘/dev/mapper/cr_sda2’ is the
container, you have to give the devices inside. Don’t ask me, i don’t
use LVM myself. Suggest you read on how LVM works.
–
Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)
The first step would be to run
pvs --all
after setting up crypto container to check whether some PVs are found at all.
Well I tried. Gives:
linux:~ # sudo cryptsetup luksOpen /dev/sda2 LVM
Enter passphrase for /dev/sda2:
linux:~ # pvs --all
PV VG Fmt Attr PSize PFree
/dev/dm-0 system lvm2 a- 465.61g 0
/dev/ram0 -- 0 0
/dev/ram1 -- 0 0
/dev/ram10 -- 0 0
/dev/ram11 -- 0 0
/dev/ram12 -- 0 0
/dev/ram13 -- 0 0
/dev/ram14 -- 0 0
/dev/ram15 -- 0 0
/dev/ram2 -- 0 0
/dev/ram3 -- 0 0
/dev/ram4 -- 0 0
/dev/ram5 -- 0 0
/dev/ram6 -- 0 0
/dev/ram7 -- 0 0
/dev/ram8 -- 0 0
/dev/ram9 -- 0 0
/dev/root -- 0 0
/dev/sda1 -- 0 0
/dev/sda2 -- 0 0
/dev/sdb1 -- 0 0
Please note that this is the first time of my life that I am rescuing an LVM. It is also the first time I am having this kind of problem with LUKS. So I am NOT familiar with ANY procedure. I am also quite stressed because of my data. So when I do an error that is “clear enough” for me it might not be and so please…be patient. (@anvidiaar - the last sentence is not directed to you or your post but a general - and stressed - comment.)
P.S. that is the default setup with one change, so the names are LVM for an extended partition in which there are /swap /root /usr/lib/kvm and /home. So there are 4 partitions in the LVM.
updt: tried also:
linux:~ # vgscan --mknodes
Reading all physical volumes. This may take a while...
Found volume group "system" using metadata type lvm2
changed to a more serious life-disk.
So:
root@PartedMagic:~# pvs -o +uuid
PV VG Fmt Attr PSize PFree PV UUID
/dev/mapper/LVM system lvm2 a-- 465.61g 0 epRApx-adiG-Ji4K-N5DD-Twwh-HAzc-J5iA7e
everything seems to be there? Not complaining on anything.
root@PartedMagic:~# lvs -o +devices
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert Devices
KVM system -wi------ 49.61g /dev/mapper/LVM(0)
home system -wi------ 358.00g /dev/mapper/LVM(12699)
root system -wi------ 50.00g /dev/mapper/LVM(104347)
swap system -wi------ 8.00g /dev/mapper/LVM(117147)
Looks even better. So where is the problem??
root@PartedMagic:~# vgchange -a y system
4 logical volume(s) in volume group "system" now active
O.K.
BTW I am not a genious, I am following this](http://mbroz.fedorapeople.org/talks/LinuxAlt2009_2/lvmrecovery.pdf) document.
root@PartedMagic:~# mount /dev/system/home /home
Works! and I am able to access my data. So, since I will not use my data, is there a way to achieve this during boot and to find out what is wrong?
Thanks for all suggestion.
And since for me it was a lucky chance to find the how-to. For all in the same situation, do not forget to re-emit the pvs --all command once you are at the last point, so it will show you all your partitions inside the LVM system container and you can then mount them to your convenience. Still my system… is broken. Still…:’(
It is very unlikely related to GRUB2 update. I suspect that at some point in the past you installed some update that rebuilt initrd, but did not reboot immediately. Now after updating GRUB2 you rebooted and hit issue with initrd.
Low hanging fruit would be to rebuild initrd. Something like
mkdir /tmp/sysroot
mount /dev/system/root /tmp/sysroot
mount /dev/sda1 /tmp/sysroot/boot
mount -o bind /sys /tmp/sysroot/sys
mount -o bind /dev /tmp/sysroot/dev
mount -o bind /proc /tmp/sysroot/proc
chroot /tmp/sysroot
mkinitrd
If it does not work, more close examination of initrd content is required.
Just saw this post: https://forums.opensuse.org/english/get-technical-help-here/install-boot-login/482323-failes-boot-up-after-upgrade.html Do you see similar errors when booting?
On 2013-01-15 08:46, stakanov wrote:
> Please note that this is the first time of my life that I am rescuing
> an LVM. It is also the first time I am having this kind of problem with
> LUKS. So I am NOT familiar with ANY procedure. I am also quite stressed
> because of my data. So when I do an error that is “clear enough” for me
> it might not be and so please…be patient. (@anvidiaar - the last
> sentence is not directed to you or your post but a general - and
> stressed - comment.)
I understand perfectly.
Your situation is the exact reason why I never install LVM, it is harder
to recover. I do not know how to recover an LVM, so I do not use it.
Just go slowly, read the error messages carefully… and drink a
tranquilizing tissanna 
–
Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)
No, I did not get any of these. Only that “the “system” folder cannot be found. Registering, this may take a while.” Then it loops.
The update coming in this night AFAIR was a) grub2 b) udev c) some unrelated stuff. So if there was any update “pending” it is the one of udev not compatible with grub2. The machine has a very low uptime, it is a laptop, so every day it is booted several times.
Low hanging fruit would be to rebuild initrd.
(O.T. I really loved that expression, you teach me some, thank you. )
Question: is there a backup of the last initrd? If yes would it be convenient to rename it to avoid it to be erased by the process? I filed a bug for this, so in case it would be fair to gather all the available info for anybody else going through this (which is likely, it is a very much “default install”, so I would expect some more people being “blessed”).
So to be clear, only the four updates/patches of yesterday where installed after the last reboot. Nothing should be pending.
LOL, you would not belief how hands can shake. At least data can be safe and the procedure indicated does allow other persons in my situation to recover the data. Why they never wanted to support real partition encryption via LUKS as it was in 10.3 and 11.1 (at the time by handwork) I will never understand. Maybe some commercial interest… boh. Thanks for the tisana thing. I should try a “salvia divinorum” trip LOL.
Oh! 
This is perfect example of
- importance to provide full information
- why one should not jump to conclusion without full understanding of what’s going on
GRUB2 is unrelated to your problem. But udev can easily screw device detection.
c) some unrelated stuff.
How can you claim it?
I do not want to sound rude, but if you really knew which stuff is related and which is not, you did not need to ask for help here in the first place.
Question: is there a backup of the last initrd?
Your last initrd should be still in /boot. Or may be the problem is that you do not have any initrd; can happen. Mount /boot and check.
I filed a bug for this
And bug number is …?
On 2013-01-15 11:16, stakanov wrote:
>
> LOL, you would not belief how hands can shake.
I can… This laptop home partition broke last week, it has now over 280
bad sectors and growing. I noticed in time by the merest chance of doing
a ‘SMART’ long test. In time because I could dd_rescue it, I only lost
two movies that I have backup of.
It took me a whole night to order the replacement disk and do a backup
(I banged on the table at least once, amid some gross language that
nobody heard). Now I’m waiting for that replacement to arrive today via
UPS, and its getting on my nerves.
> At least data can be
> safe and the procedure indicated does allow other persons in my
> situation to recover the data. Why they never wanted to support real
> partition encryption via LUKS as it was in 10.3 and 11.1 (at the time by
> handwork) I will never understand. Maybe some commercial interest…
> boh. Thanks for the tisana thing. I should try a “salvia divinorum”
> trip LOL.
They thought that doing it via LVM was easier, I guess. Other people
managed to do it without, manually, and get the system to ask for the
passphrase only once. The procedure is written somewhere in the security
mail list. Dunno if it will work with systemd, though.
I don’t use whole system encription, only some data. It is easier to
maintain.
–
Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)
@ arvidjaar:
Bug 798471
Why do I say “unrelated”: concerning other applications of the userspace, not realted to the boot process in any kind.
Information:
you see, I am coming here to seek for help but I provided to fellows up to now at least the process on how to come to ones data in such case and a link for a pertinent document. It is not that I am not searching. Recall that I am on a life CD with no other PC available and have to “try” but everytime of course I have to reset the life system and mount by the same procedure all volumes on reboot.
If you wish to have a more stringent info on what updates have been done, you could indicate (if you know it) if there is a listing of the updates coming out in the update-repo so I can tell you the last four of them exactly. I am not knowledgeable of such a list and normally I look in yast - updatehistory (but this o course in my situation is not available. Of course I looked up openSUSE Mailinglist Archive: opensuse-updates but yesterday is still not on it. As the system was fully patched, the last 4 patches are the ones in question.
If have already mounted /boot as /mnt/recover1. So the directory listing is as follows:
root@PartedMagic:~# cd /mnt/recover1
root@PartedMagic:/mnt/recover1# ls -lt
total 30685
drwx------ 2 999 users 1024 Jan 14 23:00 pulse-f28lbQ3uO3xG
drwx------ 2 999 users 1024 Jan 14 23:00 ksocket-linux
drwx------ 2 root root 1024 Jan 14 23:00 ksocket-root
drwx------ 2 root root 1024 Jan 14 23:00 pulse-9K88eMlGn7Cc
drwx------ 3 999 users 1024 Jan 14 23:00 kde-linux
drwx------ 2 999 users 1024 Jan 14 22:59 orbit-linux
drwx------ 2 root root 1024 Jan 14 21:43 kde-root
drwx------ 2 root root 1024 Jan 14 21:36 orbit-root
drwx------ 2 root root 1024 Jan 14 21:24 YaST2-06322-bWV3A5
drwxr-xr-x 6 root root 1024 Jan 14 19:34 grub2
lrwxrwxrwx 1 root root 26 Jan 14 19:34 initrd -> initrd-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 17328492 Jan 14 19:34 initrd-3.4.11-2.16-desktop
lrwxrwxrwx 1 root root 27 Dec 31 01:51 vmlinuz -> vmlinuz-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 581632 Dec 31 01:49 message
-rw------- 1 root root 512 Dec 30 23:45 backup_mbr
lrwxrwxrwx 1 root root 1 Dec 30 23:34 boot -> .
drwxr-xr-x 2 root root 1024 Dec 30 23:34 grub
drwx------ 2 root root 12288 Dec 30 23:31 lost+found
-rw-r--r-- 1 root root 222379 Oct 4 22:51 symvers-3.4.11-2.16-desktop.gz
-rw-r--r-- 1 root root 520 Oct 4 22:51 sysctl.conf-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 5719500 Oct 4 22:50 vmlinux-3.4.11-2.16-desktop.gz
-rw-r--r-- 1 root root 4919280 Oct 4 22:30 vmlinuz-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 2487319 Oct 4 22:30 System.map-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 131351 Oct 4 20:56 config-3.4.11-2.16-desktop
-rw-r--r-- 1 root root 1236 Jul 15 2012 boot.readme
FYI: the system broke at 19:34. The other timestamps I think are due to the fact that I continuously tried to boot it (without success), when I did start up later it was already in the current state.
Hope this info helps.
P.S. well, you did sound quite rude, but you are doing me a favor so I will not complain.
@Carlos: at least I can assure that SMART test is fine on the disc. The disc has no physical problem.
On 2013-01-15 12:56, stakanov wrote:
> If you wish to have a more stringent info on what updates have been
> done, you could indicate (if you know it) if there is a listing of the
> updates coming out in the update-repo so I can tell you the last four of
> them exactly. I am not knowledgeable of such a list and normally I look
> in yast - updatehistory (but this o course in my situation is not
> available. Of course I looked up 'openSUSE Mailinglist Archive:
If you can mount the lvm partition that holds /root, the history file is
in “…/var/log/zypp/history”.
–
Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)
wow, thank you, I can.
2013-01-14 20:33:43|install|grub2|2.00-1.23.1|x86_64||repo-update|9c02e4b780e0b55c3b95bff6ebdd53e8e6c94e7497b9aeeb93b133444e3174e8
# 2013-01-14 20:34:24 udev-182-4.29.1.x86_64.rpm installed ok
# Additional rpm output:
# Scanning scripts ...
# Resolve dependencies ...
# Install symlinks in /lib/mkinitrd/setup ...
# Install symlinks in /lib/mkinitrd/boot ...
#
# Kernel image: /boot/vmlinuz-3.4.11-2.16-desktop
# Initrd image: /boot/initrd-3.4.11-2.16-desktop
# KMS drivers: i915
# Root device: /dev/system/root (mounted on / as ext4)
# Resume device: /dev/system/swap
# modprobe: Module hid_generic not found.
# WARNING: no dependencies for kernel module 'hid-generic' found.
# Kernel Modules: thermal_sys thermal processor fan dm-mod dm-snapshot dm-crypt scsi_dh scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj linear
# Features: acpi dm kms plymouth block usb lvm2 resume.userspace resume.kernel
# Scanning scripts ...
# Resolve dependencies ...
# Install symlinks in /lib/mkinitrd/setup ...
# Install symlinks in /lib/mkinitrd/boot ...
#
# Kernel image: /boot/vmlinuz-3.4.11-2.16-desktop
# Initrd image: /boot/initrd-3.4.11-2.16-desktop
# KMS drivers: i915
# Root device: /dev/system/root (mounted on / as ext4)
# Resume device: /dev/system/swap
# modprobe: Module hid_generic not found.
# WARNING: no dependencies for kernel module 'hid-generic' found.
# Kernel Modules: thermal_sys thermal processor fan dm-mod dm-snapshot dm-crypt scsi_dh scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj linear
# Features: acpi dm kms plymouth block usb lvm2 resume.userspace resume.kernel
#
2013-01-14 20:34:24|install|udev|182-4.29.1|x86_64||repo-update|13f171050543879068cf8cbf2d6bda5ba5dec91d7844a8954a45eaacb7f7cdda
2013-01-14 20:34:25|install|libudev0-32bit|182-4.29.1|x86_64||repo-update|fea154733888175ed17066a59780260e9f0f36c70e6d2c4f9848df1ebb2ac8a8
2013-01-14 20:34:31|install|ruby19|1.9.3.p194-3.8.1|x86_64||repo-update|ce45a7de884424756b04cb31762341fd7db2c495a98701be82050123d9f0aa76
2013-01-14 20:34:31|install|xorg-x11-Xvnc|7.6_1.12.3-1.21.1|x86_64||repo-update|8b754a2f1322c73be0c3943e1466dfb35d522b09fd30e4f9a9547c08916940e5
2013-01-14 20:34:32|install|libudev0|182-4.29.1|x86_64||repo-update|ef408792ba130b37ce642d975c69f657362d11d0e175bdbf8b8ac59a6bd61d7c
# 2013-01-14 20:34:33 xorg-x11-server-7.6_1.12.3-1.21.1.x86_64.rpm installed ok
# Additional rpm output:
# Updating /etc/sysconfig/displaymanager...
# /usr/bin/Xorg: cannot verify root:root 0755 - not listed in /etc/permissions
#
2013-01-14 20:34:33|install|xorg-x11-server|7.6_1.12.3-1.21.1|x86_64||repo-update|9e1b864c9b5c87e7aefbb727d7c7fa0eeab4471ea798a5679d3c4e461cbed3ba
2013-01-14 20:34:34|install|libgudev-1_0-0|182-4.29.1|x86_64||repo-update|324064204c91774de86a5e81ceebabfba976c7c49eb4306e15f04118d9acf05e
2013-01-14 20:37:09|install|libvlccore5|2.0.5-101.10|x86_64|root@linux-ayey.site|packman.inode.at-suse|27b1054ffe3db67bdcf8bd26231083cf2b15de4d361c56556032598748934500
2013-01-14 20:37:14|install|k3b|2.0.2-15.87|x86_64|root@linux-ayey.site|packman.inode.at-suse|4c02d39321af1dd96f9f8a5e7b46c036988eb78088ddf20fb631c7aa54c33ec6
2013-01-14 20:37:14|install|libavutil52|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|4c8db059a2548625205342da917af2f3eec70d220fc0c56dc80b033e327238f3
2013-01-14 20:37:15|install|libavcodec54|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|6d5d8cee0945712e2f34f7d02b193cf42496edaec5b42e9d9485d694d8b0f2e2
2013-01-14 20:37:15|install|libavresample1|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|8d09a418c5bb3f42dba15b72f1aee6ef9186840f6724089eb0a03fb2584712dd
2013-01-14 20:37:15|install|libswscale2|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|e54e803b9935e8bfdf6fd3f8d2315a7d7a19b4554042da462b1f3b40c38bfa3f
2013-01-14 20:37:16|install|libpostproc52|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|84fbae0f6aa9b06ee13fd974110df116e93d3a38706babaf0491972c3311ae9f
2013-01-14 20:37:16|install|libswresample0|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|cef22a4a9f38983581890431cc5169ac3c3de977343bd008bf59c0bf8337391a
2013-01-14 20:37:16|install|libavfilter3|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|4c3d97341f62908fe2d338aec44a8980eb75aa2fe978719507345330a779c525
2013-01-14 20:37:17|install|libavformat54|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|5a821111c3faca6b837ad5784e81161edb15116d3befb87a2969c6308aae6d1c
2013-01-14 20:37:17|install|k3b-codecs|2.0.2-15.87|x86_64|root@linux-ayey.site|packman.inode.at-suse|c8091f2941388c81bfcca34cb49c8b5c63911f63088e9ad3d72433ee830eee54
2013-01-14 20:37:17|install|libavdevice54|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|397c2a1f5e2649e78f6f091030976e0624b9868db4ef4e3759114fefdb89b688
2013-01-14 20:37:22|install|vlc-noX|2.0.5-101.10|x86_64|root@linux-ayey.site|packman.inode.at-suse|ef3a1f5cb9853388b12ce18be20307c44aaf738122cc90f91c381c4d8a8e45ce
2013-01-14 20:37:23|install|ffmpeg|1.1-2.1|x86_64|root@linux-ayey.site|packman.inode.at-suse|4135388e6446480cb7ac40877c18dd0c3bc5e7bac4d18e779f3a95d1da644fd6
2013-01-14 20:37:24|install|ffmpeg2theora|0.29-1.37|x86_64|root@linux-ayey.site|packman.inode.at-suse|6aa644800ed95dd9dde03bcc2718221dcc81a9ff303da6739708b6092f79c727
2013-01-14 20:37:24|install|libvlc5|2.0.5-101.10|x86_64|root@linux-ayey.site|packman.inode.at-suse|cb20bb5590c365707e2ae67a9cc1691a9d6bf442c54e58d652afe17f86597d9f
2013-01-14 20:37:24|install|vlc-qt|2.0.5-101.10|x86_64|root@linux-ayey.site|packman.inode.at-suse|fe0b5ea2a93bc029073833495580e226f13f27f131bd7923300935fc36c7eac6
2013-01-14 20:37:25|install|vlc|2.0.5-101.10|x86_64|root@linux-ayey.site|packman.inode.at-suse|858b4fefb939f99e4b32147f40b3697213cf6c4b7b7f06ad69029ed57e4efcd3
2013-01-14 20:37:25|install|vlc-aout-pulse|2.0.5-101.10|x86_64|root@linux-ayey.site|packman.inode.at-suse|09db8594308611ffa0b0bd4c50099068110e68f9f2c69ed110be7b473cf5a810
O.K. I was apparently wrong on the time I did the update and I did also packman-updates before shutting down. This is the complete log.
I am seeing only one warning: WARNING: no dependencies for kernel module ‘hid-generic’ found (should be my keyboard).
But this should not be the problem right? Anybody sees any other problem? All seems all right. So the culprit might be the bunch of three udev updates? But they gave no error.
@Carlos: do you have also a handy solution for getting hold of the exact message while the boot procedure loops? I would have to be in boot because the logfiles are not accessible when it happens of course.