You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
btrfs
- Thread starter peters
- Start date
Ryan247Zook
Member
Yes, you can boot Linux using the Btrfs file system, as modern GRUB2 supports it well. However, using EasyBCD to load a Linux system from a Btrfs partition is often problematic. EasyBCD's NeoGRUB component is typically based on older GRUB versions that lack robust Btrfs support. While you could request a Btrfs module for NeoGRUB, it's a significant development effort for the EasyBCD creators. For reliable dual-booting mycenturahealth with Windows, it's usually better to let the Linux distribution install its own GRUB2, which can then manage both operating systems, or if using EasyBCD, ensure your Linux installation has a separate /boot partition formatted with a more traditional filesystem like Ext4.
Thank you very much for your explanations. Surely using GRUB2 from a Linux installation is the easiest way to load almost any OS.
In my situation, I am experimenting with 3 Linux systems installed in 3 different configurations - openSUSE on ext4, Manjaro on btrfs (both single partition) and Fedora on ext4 (boot partition) and btrfs (root partition), working in parallel with Win 10 as the primary system boot source.
The first two allow for the boot loader to be installed on their system partition, and they can be set up with EasyBCD GRUB (legacy) option where Windows BCD uses the Linux VBR (Volume/Partition Boot Record) to start Linux GRUB2. Amazingly, Manjaro despite using btrfs loads fine.
There is a problem with using the same arrangement for Fedora. It seems that a separate ext4 boot partition would make it easy, but it fails with an error message that 'component cannot be found'.
The problem may come from Fedora structure where the boot partition is stored as / and then mounted by grub.cfg as /boot/ for loading the system, although I don't know enough about GRUB2 to say whether this suggestion makes sense.
However, I can still load Fedora through a modified entry in ANG0 using EasyBCD (GRUB2) option, explicitly referencing Core.img on its boot partition (it just needs to referenced as /grub2/i386-pc/Core.img rather than /boot/grub2/i386-pc/Core.img).
It would be nice to have it working the same way as for other distros, but I am not sure how to approach troubleshooting in this case.
P.S. Is there a way of muting NeoGRUB startup messages? Apparently this can be done for GRUB4DOS by changing one internal parameter.
In my situation, I am experimenting with 3 Linux systems installed in 3 different configurations - openSUSE on ext4, Manjaro on btrfs (both single partition) and Fedora on ext4 (boot partition) and btrfs (root partition), working in parallel with Win 10 as the primary system boot source.
The first two allow for the boot loader to be installed on their system partition, and they can be set up with EasyBCD GRUB (legacy) option where Windows BCD uses the Linux VBR (Volume/Partition Boot Record) to start Linux GRUB2. Amazingly, Manjaro despite using btrfs loads fine.
There is a problem with using the same arrangement for Fedora. It seems that a separate ext4 boot partition would make it easy, but it fails with an error message that 'component cannot be found'.
The problem may come from Fedora structure where the boot partition is stored as / and then mounted by grub.cfg as /boot/ for loading the system, although I don't know enough about GRUB2 to say whether this suggestion makes sense.
However, I can still load Fedora through a modified entry in ANG0 using EasyBCD (GRUB2) option, explicitly referencing Core.img on its boot partition (it just needs to referenced as /grub2/i386-pc/Core.img rather than /boot/grub2/i386-pc/Core.img).
It would be nice to have it working the same way as for other distros, but I am not sure how to approach troubleshooting in this case.
P.S. Is there a way of muting NeoGRUB startup messages? Apparently this can be done for GRUB4DOS by changing one internal parameter.