For BtrFS experts

[marco07]

I just installed openSUSE Leap 42.2 and its boot loader (Grub) on an extended test partition sdb12 (25gig). The installer automatically formatted this partition btrfs (i did not see a choice to select formating type) and picked another free partition sdb11 (45gig) formatted as xfs with some files on it. It also created a few small (<5gig) partitions TMPfs (). I have no idea what these are, nor know much about btrfs file system.
Any how, my problem is that when I updated grub2 my boot loader on Ubuntu 16.04 (sdb10), it does not list the newly created bootable partitions. My googling ended up with the result that grub2 can not detect btrfs partition. However, on a trial, I used chain loader entries in 40_custom and was able to boot leap 42.2. But after a few times rebooting it due to configuration needs, grub2 now complains that "no such partition available." I used sdb12 not partition code no. in chainloader.
Is there any other way to make grub2 to handle this? Or any ideas at all?
Thanks!

[vinnywright]

no expert , although I do use it , but the people @hear that are good with BTRFS will need to see at least your

sudo parted -l

and the chainloader you put in 40_custom

please enclose in code tags ,,,,,the "#" in the text editing bar in the top of the "reply window"

VINNY

[marco07]

no expert , although I do use it , but the people @hear that are good with BTRFS will need to see at least your

sudo parted -l

and the chainloader you put in 40_custom

please enclose in code tags ,,,,,the "#" in the text editing bar in the top of the "reply window"

VINNY

Thanks Vinny! To be honest, after posting here and fiddling around more with th leap installation, I lost my patient with that and deleted all those partitions created by the leap installer and got rid of it. Bottom line, I gave up on Leap.
Thanks again!

[vinnywright]

Thanks Vinny! To be honest, after posting here and fiddling around more with th leap installation, I lost my patient with that and deleted all those partitions created by the leap installer and got rid of it. Bottom line, I gave up on Leap.
Thanks again!

LOL ,,,,,OK then ,,,,,,,,,,but for further info hear is my chainloader in /etc/grub.d/40_custom

menuentry "Netrunner" {
insmod gzio
insmod part_gpt
insmod part_gpt
insmod btrfs
[COLOR=#ff0000]set root='(hd1,gpt1)'[/COLOR]
configfile /@/boot/grub/grub.cfg
}

grub see's hard drives as the part in red hear ,,,,,, hd0 would be the first HD as seen by the BIOS or UEFI so /sda ,,,hd1 /sdb and so on ,,,,,,gpt1 is the partition on /sdb but instead of starting with 0 the partition part starts at 1 ,,,,,,,,,,so hd1,gpt1 is /sdb1

and you are corect that grubs OS prober will not pick up an install to btrfs ,,,,,,,,,this chainloader in /etc/grub.d/40_custom is in my 14.04 install but is not the install that controls "grub on boot" so if I want to boot it I half to go to 14.04's grub then boot it ... yes I am lazy.

VINNY

[marco07]

LOL ,,,,,OK then ,,,,,,,,,,but for further info hear is my chainloader in /etc/grub.d/40_custom

menuentry "Netrunner" {
insmod gzio
insmod part_gpt
insmod part_gpt
insmod btrfs
[COLOR=#ff0000]set root='(hd1,gpt1)'[/COLOR]
configfile /@/boot/grub/grub.cfg
}

grub see's hard drives as the part in red hear ,,,,,, hd0 would be the first HD as seen by the BIOS or UEFI so /sda ,,,hd1 /sdb and so on ,,,,,,gpt1 is the partition on /sdb but instead of starting with 0 the partition part starts at 1 ,,,,,,,,,,so hd1,gpt1 is /sdb1

and you are corect that grubs OS prober will not pick up an install to btrfs ,,,,,,,,,this chainloader in /etc/grub.d/40_custom is in my 14.04 install but is not the install that controls "grub on boot" so if I want to boot it I half to go to 14.04's grub then boot it ... yes I am lazy.

VINNY

My chain loader was simply:
#menuentry "openSUSE Leap 42.2 on sbd12" {
# set root=(hd1,12)
# chainloader +1
#}

I left it on 40_costum by commenting lines out.

As I said this worked for a number of times (perhaps 3-4) rebooting and booted leap up correctly. But all of a sudden on next reboot it complained "no such partition..."
Then I got tired not only of this but configuration of leap itself, the reason for continuous need to reboot which caused grub failure. That is when I gave up. for me nothing beats our own K(ubuntu).

[vinnywright]

for me nothing beats our own k(ubuntu).

vinny

[GreyGeek]

vinny

Exactly! openSUSE defaults to btrfs. And, it makes volumes out of each of the root based directories. Some like that approach, but when I played with Leap I found that I liked the way KUbuntu did it better: two subvolumes, @/ and @/home. A lot simpler and more flexible, believe it or not.

Here are some links to discussions on btrfs:

https://www.kubuntuforums.net/showth...ighlight=btrfs
https://www.kubuntuforums.net/showth...ighlight=btrfs
https://www.kubuntuforums.net/showth...ighlight=btrfs
https://www.kubuntuforums.net/showth...ighlight=btrfs
https://www.kubuntuforums.net/showth...ighlight=btrfs
https://www.kubuntuforums.net/showth...ighlight=btrfs
https://www.kubuntuforums.net/showth...ighlight=btrfs
https://www.kubuntuforums.net/showth...ighlight=btrfs

[#]BTRFS[/#]