Arch Linux User Repository

@WorMzy, it's not clear to me if you system is booting properly and you just can't see the rollback menu, or you cannot boot at all -- does the system boot when using the "btrfs" hook (official) and adding `subvol=__active` to your rootflags? you are you adding `device=/dev/sda1,device=/dev/sdb1` to your rootflags, yes? or ... ? that explicitly tells the btrfs module which devices to scan, but a `btrfs device scan` (as done by the hook) should already take care of that ... hrm, can you try using the (single/primary) UUID instead of the sdX names (should really be doing this for any FS)? you can get the primary UUID with: blkid -p -s UUID -o value /dev/sda1 ... try that without device=XXX (in rootflags), and only if it doesn't work, try *with* device=XXX. should you have good results i'll update the hook to explicitly append the device=/dev/.../UUID, and if all else fails, i suppose i'll enumerate the devices and append them instead.

No change in behaviour if: - I install core/btrfs-progs. - I move the btrfs_advanced hook to the start (well, after base) of the HOOKS array. - I remove all modules from the MODULES array (just in case). - I use an older kernel (3.3.8-1). Regenerating the initramfs at every step.

Cheers for the reply, and no worries about the delay. The hook is definitely enabled in mkinitcpio.conf, and isn't disabled in the kernel commandline. btrfs-progs-git* is installed, and lsinitcpio lists "./hooks/btrfs_advanced, ./usr/bin/btrfsck, ./usr/bin/btrfsctl, ./usr/bin/btrfs, and ./usr/lib/modules/3.4.3-1-ARCH/kernel/btrfs.ko. I had to add "device=/dev/sda1,device=/dev/sdb1" to the kernel commandline to get the RAID1 btrfs install to boot properly. Otherwise the initrd couldn't mount / due to an "incorrect filesystem/missing codepage"-type error. My /boot is on /, (as a directory, rather than a subvolume, so that syslinux and grub can still see it), but I never had a problem while I was using syslimux on non-RAID. *I will try with regular core/btrfs-progs, maybe the git package is incompatible for some reason

@WorMzy, sorry for delay ... forgot to flag email as `needs attention`. are you sure the hook is listed in your mkinitcpio.conf, and not being skipped by disablehooks=[...] on your kernel cmdline? i don't think there is an issue with RAID-for-root (not /boot of course, for now). also, make sure you have the necessary tools installed (btrfs-progs) prior to running mkinitcpio. to be clear: you are still booting properly, yes? and this behavior started immediately after switching to grub2, correct? what is the output of `lsinitcpio /boot/initramfs-linux.img | grep btrfs`?

When booting a single device btrfs system via syslinux, I got a "PRESS ANY KEY TO ACCESS BTRFS FEATURES" type message. However, I am now booting a multi-device system (raid1) via grub2, and don't see this prompt any more. Is this a problem with my grub2 config, or does the hook not support snapshot features on multi-device btrfs filesystems? If not, is this something that is planned/possible? Cheers

@skydrome, try with the latest package ... maybe that was due to the changes in mkinitcpio (working fine here ;-)

@falconindy, thanks ... i pretty much used your link verbatim, seems to work alright :-) package now depends on mkinitcpio>=0.9.0

for some reason the btrfs_advanced hook is getting run twice now

Shouldn't be difficult -- you can basically include the same exact hook as from core/btrfs-progs: http://paste.xinu.at/OTWRI/ Yes, that adds all the correct modules -- there's a hardcoded quirk to pull in crc32c{,_intel} when adding libcrc32c.