You are not logged in.
Pages: 1
I have recently upgraded (``pacman -Syu'' ) my netbook. It's a massive upgrade since I hadn't done that for a while. After reboot however, fsck.ext4 complained it could't resolve the disk label since my root partition is on a LVM logical partition, it turned out udev failed to make appropriate devices nodes for LVM logical partitions.
In rescue mode, running ```vgmknodes && mount -a'' will have everything back again, but that's not a solution in the long run.
Offline
I had the same problem with my laptop running LVM & LUKS. As I update often so I found the offending package was the new version of sysvinit. sysvinit-2.88-2 seems to work for me.
Offline
As I update often so I found the offending package was the new version of sysvinit.
Can you check this again please? I do not see how the relevant change can cause that.
Offline
jakobm, maybe its something with my setup but I tried again with the new sysvinit and confirmed it broke my boot. Like the first poster my volume group is not even a device in /dev. I get the message
/etc/rc.sysinit: line 15: mountpoint: command not found
Offline
well apparently its some known bug in pacman.. performing a "sudo pacman -S sysvinit; sudo pacman -S util-linux" fixed the problem of the missing mountpoint command
Offline
well apparently its some known bug in pacman.. performing a "sudo pacman -S sysvinit; sudo pacman -S util-linux" fixed the problem of the missing mountpoint command
That solved my problem too, thanks!
Offline
Tip: change the subject line of the first post to SOLVED for others to find later in their searches. That or you risk the wrath of some random admin.
Offline
Pages: 1