After updating to baselayout2 and openrc fsck is run before lvm on boot and throws a lot of errors caused by non existing devices. Reproducible: Always Steps to Reproduce: 1. use lvm2 2. update to openrc and baselayout2 3. boot Actual Results: Failures reported by fsck Expected Results: clean boot I think, i updated all config files correctly and didn't touch the init scripts after this. If i'm not mistaken the problem is the results of a simple type in the lvm-init script. In the depend part it is: "before checkfs". Changing it to "before fsck" fixes everything.
Hi Sebastian, could you show me output of ls -l /etc/runlevels/boot please?
jf@zakath ~ $ ls -l /etc/runlevels/boot/ total 0 lrwxrwxrwx 1 root root 20 2008-04-17 17:11 bootmisc -> /etc/init.d/bootmisc lrwxrwxrwx 1 root root 23 2008-04-17 17:11 consolefont -> /etc/init.d/consolefont lrwxrwxrwx 1 root root 25 2008-04-17 17:11 device-mapper -> /etc/init.d/device-mapper lrwxrwxrwx 1 root root 16 2008-04-17 17:11 fsck -> /etc/init.d/fsck lrwxrwxrwx 1 root root 18 2007-11-05 02:45 hdparm -> /etc/init.d/hdparm lrwxrwxrwx 1 root root 20 2008-04-17 17:11 hostname -> /etc/init.d/hostname lrwxrwxrwx 1 root root 19 2008-04-17 17:11 hwclock -> /etc/init.d/hwclock lrwxrwxrwx 1 root root 19 2008-04-17 17:11 keymaps -> /etc/init.d/keymaps lrwxrwxrwx 1 root root 22 2008-04-17 17:11 localmount -> /etc/init.d/localmount lrwxrwxrwx 1 root root 15 2008-04-17 17:11 lvm -> /etc/init.d/lvm lrwxrwxrwx 1 root root 19 2008-04-17 17:11 modules -> /etc/init.d/modules lrwxrwxrwx 1 root root 16 2008-04-17 17:11 mtab -> /etc/init.d/mtab lrwxrwxrwx 1 root root 18 2007-11-05 02:45 net.lo -> /etc/init.d/net.lo lrwxrwxrwx 1 root root 18 2008-04-17 17:11 procfs -> /etc/init.d/procfs lrwxrwxrwx 1 root root 16 2008-04-17 17:11 root -> /etc/init.d/root lrwxrwxrwx 1 root root 16 2008-04-17 17:11 swap -> /etc/init.d/swap lrwxrwxrwx 1 root root 18 2008-04-17 17:11 sysctl -> /etc/init.d/sysctl lrwxrwxrwx 1 root root 24 2008-04-17 17:11 termencoding -> /etc/init.d/termencoding lrwxrwxrwx 1 root root 19 2008-04-17 17:11 urandom -> /etc/init.d/urandom I added lvm to the boot-runlevel according to the migration guide. It is run, but after fsck.
Thanks.
this issue was addressed in versions newer then the current stable. Any ~arch version contains this fix. mixing ~arch and arch is the culprit here.