[opensuse] a little help with Leap 5
I have been having a lot of trouble with upgrade, so pardon this if stupid question. I do not use LVM. When I boot the Leap 15 DVD and try to set up partitions, I get 6 rather that the usual 3 generated under 14.3. For some reason, that I can probably research on google, it sets up partition 1 as a BIOS boot partition. Not sure why this is required. But then it sets up partitions 2 and 3 as BtrFS partitions, then partition 5 as another BtrFS partition mounted as root. Then partitions for the usual swap and home file systems. Why are there 3 BtrFS partitions? The only comment I can find, all the way in Release notes:7 technical, is that there is a single subvolume for all of /var. I changed the root file system type to xfs and was able to generate the 3, (4 with BIOS boot), partition layout I am familiar with. Comments please. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 2 juni 2018 01:11:13 CEST schreef don fisher:
I have been having a lot of trouble with upgrade, so pardon this if stupid question.
I do not use LVM. When I boot the Leap 15 DVD and try to set up partitions, I get 6 rather that the usual 3 generated under 14.3. For some reason, that I can probably research on google, it sets up partition 1 as a BIOS boot partition. Not sure why this is required. But then it sets up partitions 2 and 3 as BtrFS partitions, then partition 5 as another BtrFS partition mounted as root. Then partitions for the usual swap and home file systems.
Why are there 3 BtrFS partitions? The only comment I can find, all the way in Release notes:7 technical, is that there is a single subvolume for all of /var.
I changed the root file system type to xfs and was able to generate the 3, (4 with BIOS boot), partition layout I am familiar with.
Comments please. Don Did you use the import mountpoints option? It looks like you're not performing an upgrade but rather a new install. Please provide as much info as you can gather, put the output on paste.opensuse.org
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/01/2018 05:47 PM, Knurpht @ openSUSE wrote:
Why are there 3 BtrFS partitions? The only comment I can find, all the way in Release notes:7 technical, is that there is a single subvolume for all of /var.
I changed the root file system type to xfs and was able to generate the 3, (4 with BIOS boot), partition layout I am familiar with.
Comments please. Don Did you use the import mountpoints option? It looks like you're not performing an upgrade but rather a new install. Please provide as much info as you can gather, put the output on paste.opensuse.org
It does look like it was trying to set up a new install, rather than an upgrade. That being said, there is nothing wrong with what you've selected to set up manually. Opensuse defaults to BTRFS, but you certainly don't have to accept it and setting it up in the way you are used to doing is certainly fine). (After getting corrupted and losing data twice within 6months, I've put BTRFS on my 5 year ban list, and other distros have dropped it altogether). YMMV. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen composed on 2018-06-01 18:35 (UTC-0700):
Opensuse defaults to BTRFS, but you certainly don't have to accept it and setting it up in the way you are used to doing is certainly fine).
+5
(After getting corrupted and losing data twice within 6months, I've put BTRFS on my 5 year ban list, and other distros have dropped it altogether). YMMV.
Since I first heard about it it's been on my indefinite ban list, later bolstered by other distros' absence of support. I can understand it for large organizations paying support contracts, but not for mere mortals like most who ask for help on web forums and mailing lists, and particularly not for the unique needs of multibooters. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 2 juni 2018 01:11:13 CEST schreef don fisher:
I have been having a lot of trouble with upgrade, so pardon this if stupid question.
I do not use LVM. When I boot the Leap 15 DVD and try to set up partitions, I get 6 rather that the usual 3 generated under 14.3. For some reason, that I can probably research on google, it sets up partition 1 as a BIOS boot partition. Not sure why this is required. But then it sets up partitions 2 and 3 as BtrFS partitions, then partition 5 as another BtrFS partition mounted as root. Then partitions for the usual swap and home file systems.
Why are there 3 BtrFS partitions? The only comment I can find, all the way in Release notes:7 technical, is that there is a single subvolume for all of /var.
I changed the root file system type to xfs and was able to generate the 3, (4 with BIOS boot), partition layout I am familiar with.
Comments please. Don Another thing: After reading previous threads about your issues, I think you'd be better of in forums.opensuse.org
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-02 01:11, don fisher wrote:
I have been having a lot of trouble with upgrade, so pardon this if stupid question.
So after your troubles with upgrade, you try fresh install. Understandable. Do you have a backup of your old system?
I do not use LVM. When I boot the Leap 15 DVD and try to set up partitions, I get 6 rather that the usual 3 generated under 14.3. For some reason, that I can probably research on google, it sets up partition 1 as a BIOS boot partition. Not sure why this is required.
Not always, but I think it is now always created if the disk is partitioned with GPT - probably all new disks are now using GPT. And all new computers have UEFI, which is designed to work with GPT (of course, Legacy MBR is supported). So YaST defaults to create that partition. Better do it than fail because does not exist. And better now than cry later because there is no space for it. Anyway, that partition is really tiny, about 8 MB. It doesn't matter, just let it be even if unused.
But then it sets up partitions 2 and 3 as BtrFS partitions, then partition 5 as another BtrFS partition mounted as root. Then partitions for the usual swap and home file systems.
Why are there 3 BtrFS partitions? The only comment I can find, all the way in Release notes:7 technical, is that there is a single subvolume for all of /var.
Ok, probably it is only a single btrfs partition with several subvolumes. It has to be done that way because some directories need different settings; there is not a single setting that applies fine to all directories. Things like do snapshots to this one but not to this other. And there are less now than before, because the rpm data has been moved off /var.
I changed the root file system type to xfs and was able to generate the 3, (4 with BIOS boot), partition layout I am familiar with.
"/" on XFS with no boot partition? Last time I tried that I failed, but maybe it works on GPT plus bios partition. I'll have to consider that. My personal choice is ext4 for "/", XFS for home, since many years. Before it was ext3, before it was reiserfs.
Comments please.
All good. However... you do not preserve your old /home? Or is it a new disk? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Op zaterdag 2 juni 2018 21:14:59 CEST schreef Carlos E. R.:
On 2018-06-02 01:11, don fisher wrote:
I have been having a lot of trouble with upgrade, so pardon this if stupid question.
So after your troubles with upgrade, you try fresh install. Understandable.
Do you have a backup of your old system?
I do not use LVM. When I boot the Leap 15 DVD and try to set up partitions, I get 6 rather that the usual 3 generated under 14.3. For some reason, that I can probably research on google, it sets up partition 1 as a BIOS boot partition. Not sure why this is required.
Confirmed, everything works even if it's not mounted, if one removes is the result is an unbootable system. Even though examining it shows that it has not been touched in any way.
Not always, but I think it is now always created if the disk is partitioned with GPT - probably all new disks are now using GPT. And all new computers have UEFI, which is designed to work with GPT (of course, Legacy MBR is supported). So YaST defaults to create that partition. Better do it than fail because does not exist. And better now than cry later because there is no space for it.
AFAICT I've only seen it on systems with UEFI/Secureboot enabled. That would need GPT partioned disks. I'm a firm believer in knowledge and craftmanship of the (open)SUSE devs and packagers so I leave it there, but I can understand the reasoning of users/admins that a non mounted partition is of no use, so remove it. One more reason to trust the devs/packagers and take the proposal made by the installer at least where I don't know a reason not to accept it. Sizes, data mountpoints etc are mine, these system things I leave up to the builders of the distro.
Anyway, that partition is really tiny, about 8 MB. It doesn't matter, just let it be even if unused.
But then it sets up partitions 2 and 3 as BtrFS partitions, then partition 5 as another BtrFS partition mounted as root. Then partitions for the usual swap and home file systems.
Why are there 3 BtrFS partitions? The only comment I can find, all the way in Release notes:7 technical, is that there is a single subvolume for all of /var.
Ok, probably it is only a single btrfs partition with several subvolumes. It has to be done that way because some directories need different settings; there is not a single setting that applies fine to all directories. Things like do snapshots to this one but not to this other. And there are less now than before, because the rpm data has been moved off /var.
I changed the root file system type to xfs and was able to generate the 3, (4 with BIOS boot), partition layout I am familiar with.
"/" on XFS with no boot partition? Last time I tried that I failed, but maybe it works on GPT plus bios partition. I'll have to consider that.
My personal choice is ext4 for "/", XFS for home, since many years. Before it was ext3, before it was reiserfs.
Comments please.
All good.
However... you do not preserve your old /home? Or is it a new disk?
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-02 21:39, Knurpht @ openSUSE wrote:
Op zaterdag 2 juni 2018 21:14:59 CEST schreef Carlos E. R.:
On 2018-06-02 01:11, don fisher wrote:
I have been having a lot of trouble with upgrade, so pardon this if stupid question.
So after your troubles with upgrade, you try fresh install. Understandable.
Do you have a backup of your old system?
I do not use LVM. When I boot the Leap 15 DVD and try to set up partitions, I get 6 rather that the usual 3 generated under 14.3. For some reason, that I can probably research on google, it sets up partition 1 as a BIOS boot partition. Not sure why this is required.
Confirmed, everything works even if it's not mounted, if one removes is the result is an unbootable system. Even though examining it shows that it has not been touched in any way.
Not always, but I think it is now always created if the disk is partitioned with GPT - probably all new disks are now using GPT. And all new computers have UEFI, which is designed to work with GPT (of course, Legacy MBR is supported). So YaST defaults to create that partition. Better do it than fail because does not exist. And better now than cry later because there is no space for it.
AFAICT I've only seen it on systems with UEFI/Secureboot enabled. That would need GPT partioned disks. I'm a firm believer in knowledge and craftmanship of the (open)SUSE devs and packagers so I leave it there, but I can understand the reasoning of users/admins that a non mounted partition is of no use, so remove it. One more reason to trust the devs/packagers and take the proposal made by the installer at least where I don't know a reason not to accept it. Sizes, data mountpoints etc are mine, these system things I leave up to the builders of the distro.
The partition is used by grub boot code. In words from Andrei Borzenkov: "It used to store GRUB2 MBR-gap code (as MBR gap does not exist on GPR)". "bios_boot partition contains grub2 core.img which (for btrfs on BIOS) is about 40K. Still fits into 2M space but no more into legacy 63 post-MBR sectors." "core.img is exactly *the* code that locates /boot/grub2 which contains bulk of grub2. It is effectively copy of what is written into bios_boot or other location where you chose to install grub2." (just a quick search, I know he has explained what it is needed for more than once ;-) ) Thus it is not ever needed mounted on the running system. Just used by some systems to boot. And has no filesystem, either, thus can not be mounted. It is "raw". During Beta phase it was created on some systems that did not need it. <https://lists.opensuse.org/opensuse-factory/2018-02/msg00032.html> -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Op zaterdag 2 juni 2018 22:14:55 CEST schreef Carlos E. R.:
On 2018-06-02 21:39, Knurpht @ openSUSE wrote:
Op zaterdag 2 juni 2018 21:14:59 CEST schreef Carlos E. R.:
On 2018-06-02 01:11, don fisher wrote:
I have been having a lot of trouble with upgrade, so pardon this if stupid question.
So after your troubles with upgrade, you try fresh install. Understandable.
Do you have a backup of your old system?
I do not use LVM. When I boot the Leap 15 DVD and try to set up partitions, I get 6 rather that the usual 3 generated under 14.3. For some reason, that I can probably research on google, it sets up partition 1 as a BIOS boot partition. Not sure why this is required.
Confirmed, everything works even if it's not mounted, if one removes is the result is an unbootable system. Even though examining it shows that it has not been touched in any way.
Not always, but I think it is now always created if the disk is partitioned with GPT - probably all new disks are now using GPT. And all new computers have UEFI, which is designed to work with GPT (of course, Legacy MBR is supported). So YaST defaults to create that partition. Better do it than fail because does not exist. And better now than cry later because there is no space for it.
AFAICT I've only seen it on systems with UEFI/Secureboot enabled. That would need GPT partioned disks. I'm a firm believer in knowledge and craftmanship of the (open)SUSE devs and packagers so I leave it there, but I can understand the reasoning of users/admins that a non mounted partition is of no use, so remove it. One more reason to trust the devs/packagers and take the proposal made by the installer at least where I don't know a reason not to accept it. Sizes, data mountpoints etc are mine, these system things I leave up to the builders of the distro.
The partition is used by grub boot code. In words from Andrei Borzenkov:
Thanks for elaborating. Note to self: Include "arvidjaar" in searches re. GRUB2.
"It used to store GRUB2 MBR-gap code (as MBR gap does not exist on GPR)".
"bios_boot partition contains grub2 core.img which (for btrfs on BIOS) is about 40K. Still fits into 2M space but no more into legacy 63 post-MBR sectors."
"core.img is exactly *the* code that locates /boot/grub2 which contains bulk of grub2. It is effectively copy of what is written into bios_boot or other location where you chose to install grub2."
(just a quick search, I know he has explained what it is needed for more than once ;-) )
Thus it is not ever needed mounted on the running system. Just used by some systems to boot. And has no filesystem, either, thus can not be mounted. It is "raw".
During Beta phase it was created on some systems that did not need it.
<https://lists.opensuse.org/opensuse-factory/2018-02/msg00032.html>
Summarizing: it's holding the machine's boot code which can find the system's boot loader, like MBR did on MBR partitioned disks. Correct me if that's not what it is. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-02 23:38, Knurpht @ openSUSE wrote:
Op zaterdag 2 juni 2018 22:14:55 CEST schreef Carlos E. R.:
On 2018-06-02 21:39, Knurpht @ openSUSE wrote:
Op zaterdag 2 juni 2018 21:14:59 CEST schreef Carlos E. R.:
On 2018-06-02 01:11, don fisher wrote:
I have been having a lot of trouble with upgrade, so pardon this if stupid question.
...
The partition is used by grub boot code. In words from Andrei Borzenkov:
Thanks for elaborating. Note to self: Include "arvidjaar" in searches re. GRUB2.
:-)
"It used to store GRUB2 MBR-gap code (as MBR gap does not exist on GPR)".
"bios_boot partition contains grub2 core.img which (for btrfs on BIOS) is about 40K. Still fits into 2M space but no more into legacy 63 post-MBR sectors."
"core.img is exactly *the* code that locates /boot/grub2 which contains bulk of grub2. It is effectively copy of what is written into bios_boot or other location where you chose to install grub2."
(just a quick search, I know he has explained what it is needed for more than once ;-) )
Thus it is not ever needed mounted on the running system. Just used by some systems to boot. And has no filesystem, either, thus can not be mounted. It is "raw".
During Beta phase it was created on some systems that did not need it.
<https://lists.opensuse.org/opensuse-factory/2018-02/msg00032.html>
Summarizing: it's holding the machine's boot code which can find the system's boot loader, like MBR did on MBR partitioned disks.
Correct me if that's not what it is.
Don't ask me... I got this second hand ;-) I think it is the next stage after the MBR and before grub files stored in /boot, which were previously stored in disk sectors after the MBR or PBR. Space that was not officially assigned. MBR --> core.img --> /boot/grub2/* (PBR: partition boot record) If I got this right, XFS partitions do not have this free space, and thus having root on XFS need a separate /boot partition, or Grub in the MBR. On GPT partitions there is an EFI partition and here I get lost. I think that the firmware of the computer (UEFI mode) knows enough to read the EFI partition FAT filesystem to read at least one file there, which then decides what to do. If the GPT disk is booting in legacy or BIOS mode, then there is a Protective MBR, which may have a syslinux boot code that can boot the partition marked bootable by loading that partition boot code sector. If Grub is installed in PMBR then... missing info in my knowledge. I *think* the bios part is then needed. I can't fill this gap now, and I'm also hungry, so I'll leave :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (5)
-
Carlos E. R. -
don fisher -
Felix Miata -
John Andersen -
Knurpht ＠ openSUSE