https://bugzilla.novell.com/show_bug.cgi?id=753366 https://bugzilla.novell.com/show_bug.cgi?id=753366#c13 --- Comment #13 from David Sterba <dsterba@suse.com> 2012-09-03 17:54:56 CEST --- (In reply to comment #6)
This is the correct solution to this issue: http://forums.opensuse.org/english/get-technical-help-here/install-boot-logi...
To summarize: btrfs boot script runs before mount script so module cannot be loaded from the file system. As long as your / is not btrfs, not a problem since you will get dropped into super user mode where you can load the module by hand.
The correct solution: Add btrfs module to initrd so that it is loaded into initial ramdisk.
Details are on that forum entry.
I've read through the forum post, it mentions several problems with multi-device btrfs and boot. Summary: * missing module in initrd despite btrfs feature is detected => really a bug (missing directive in mkinitrd script), already fixed, I'll check if it's actually released via maintenance update * devices not detected during boot, ie. the missing 'btrfs device scan' => unless the module is not loaded, the scan does not happen; formerly the scan step was not done at all, should be ok now there's a difference when scanning root device and non-root devices: * root: all steps need to be done from within the initrd environment (like setting up MD/DM/crypto, then scan and mount) * non-root filesystems may depend on post-initrd setup of MD/DM/crypto devices and this cannot be resolved from initrd at all => needs udev rules to detect any new blockdevice (as suggested in comment 12) I'll push out updated progs (udev rules and other progs fixes) soon. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.