[yast-devel] detected a file system next to a partition table on the device /dev/md4; &
1 http://fm.no-ip.com/SS/Suse/YaST/yast2md4error.png Is this a real error, or a bug that either exists or I should file? http://fm.no-ip.com/Tmp/SUSE/Factory/gb250L08x2.txt has possibly relevant data I collected, much of which I don't believe needs to stay in the list archive. http://fm.no-ip.com/Tmp/SUSE/Factory/y2l-201908.xz is /var/log/YaST2/y2log. http://fm.no-ip.com/Tmp/SUSE/Factory/y2l-201908.tgz has control/ and storage/. When I chose to continue, no more messages appeared. 2 The reason I opened bootloader in the first place was a search for a correspondence to /etc/default/grub's GRUB_DISABLE_SUBMENU= which seems to be absent. Need I report a B.O.O. bug asking that this be added? Has this wish been made already? I tried searching, but it's reliably returning either document contains no data, or simply timing out "Secure Connection Failed...The page you are trying to view cannot be shown because the authenticity of the received data could not be verified". -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, Aug 28, 2019 at 03:32:05PM -0400, Felix Miata wrote:
1 http://fm.no-ip.com/SS/Suse/YaST/yast2md4error.png
Is this a real error, or a bug that either exists or I should file?
md4 contains the signatures of an ext4 filesystem and of an
MS-DOS partition table. You can check this with blkid, parted and
wipefs or other tools. YaST simple reports this strange setup.
Regards,
Arvin
--
Arvin Schnell,
Arvin Schnell composed on 2019-08-28 20:24 (UTC):
On Wed, Aug 28, 2019 at 03:32:05PM -0400, Felix Miata wrote:
Is this a real error, or a bug that either exists or I should file?
md4 contains the signatures of an ext4 filesystem and of an MS-DOS partition table. You can check this with blkid, parted and wipefs or other tools. YaST simple reports this strange setup.
The system has two MBR disks, one GPT disk. It has 6 md devices comprised from 12 partitions on the two MBR disks. All 6 md devices have EXT4 filesystems on them, as do most partitions on all three "disks" not comprising md devices. It was booted from the GPT disk. The "unexpected condition" reported by the popup I sort of grok, though I'm unsure why Grub is on each of md4's partitions but not on others with root filesystems (sda[9,10,11] & sdb[9,10,11]). Those MBR disks were transplanted from a different PC. The GPT SSD was all there was when the PC was placed in service. Grub's presence on sda12 and sdb12 are the result of me putting it there using the Grub Legacy shell at installation of 42.3 (IIRC). Why did the presence of Grub (Legacy) on /dev/sda12 and /dev/sdb12 (comprising /dev/md4) cause the "next to a partition table" report by the popup? What significance could "next to a partition table" even be? Grub on MBR code block and the blocks following sector 0 are historically quite common (and normal), if not remaining so. And it's normal on partitions with EXT4 filesystems directly on them rather than on partitions comprising RAID devices (e.g. how I select alternate kernels on most installations, via chainloading from master bootloader). -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
V Wed, 28 Aug 2019 15:32:05 -0400
Felix Miata
2 The reason I opened bootloader in the first place was a search for a correspondence to /etc/default/grub's
GRUB_DISABLE_SUBMENU=
which seems to be absent. Need I report a B.O.O. bug asking that this be added? Has this wish been made already? I tried searching, but it's reliably returning either document contains no data, or simply timing out "Secure Connection Failed...The page you are trying to view cannot be shown because the authenticity of the received data could not be verified".
Hi Felix, this option is not present in yast2-bootloader (but if it is there, it should be kept). What is your use case for it? We need it to decice if it is something to offer all users or if it is specialized "expert" option for very specific use case. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Josef Reidinger composed on 2019-08-29 09:06 (UTC+0200):
Wed, 28 Aug 2019 15:32:05 -0400 Felix Miata composed:
2 The reason I opened bootloader in the first place was a search for a correspondence to /etc/default/grub's
GRUB_DISABLE_SUBMENU=
which seems to be absent. Need I report a B.O.O. bug asking that this be added? Has this wish been made already? I tried searching, but it's reliably returning either document contains no data, or simply timing out "Secure Connection Failed...The page you are trying to view cannot be shown because the authenticity of the received data could not be verified".
Hi Felix, this option is not present in yast2-bootloader (but if it is there, it should be kept). What is your use case for it? We need it to decice if it is something to offer all users or if it is specialized "expert" option for very specific use case.
https://www.linuxquestions.org/questions/fedora-installation-39/multiboot-de... is the thread that lead here, a "triple" boot UEFI installation with Debian and Fedora, where installing openSUSE after Debian and Fedora resulted in an openSUSE Grub in which the only apparent choices found by the poster were openSUSE Leap 15.1 and Advanced options, in part I expect because the "Probe Foreign OS" box was not checked. I'm not familiar with any specific details of what is expected with that box checked, because I never use it. I make my own menus with either menu.lst (MBR installations), or custom.cfg (UEFI installations) via /etc/grub.d/06_custom (copied from 40_custom). The use case is a desire to suggest when possibly appropriate that a nominally enlightened or unenlightened multibooter switch his boot menu from multiscreen configuration to single, and be able to do it with openSUSE's flagship tool YaST2 instead of via the shell. Maybe it's a good idea to offer the option any time more than one or two other operating system(s) have been first installed, if not always? Personally I find all multipage Grub menu configurations obnoxious. They strongly remind me of Windows' little bitty windows with select lists that expose only two or three selections at a time on a screen that has ample space for many times that number in a window nominally taller. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
V Thu, 29 Aug 2019 03:38:13 -0400
Felix Miata
Josef Reidinger composed on 2019-08-29 09:06 (UTC+0200):
Wed, 28 Aug 2019 15:32:05 -0400 Felix Miata composed:
2 The reason I opened bootloader in the first place was a search for a correspondence to /etc/default/grub's
GRUB_DISABLE_SUBMENU=
which seems to be absent. Need I report a B.O.O. bug asking that this be added? Has this wish been made already? I tried searching, but it's reliably returning either document contains no data, or simply timing out "Secure Connection Failed...The page you are trying to view cannot be shown because the authenticity of the received data could not be verified".
Hi Felix, this option is not present in yast2-bootloader (but if it is there, it should be kept). What is your use case for it? We need it to decice if it is something to offer all users or if it is specialized "expert" option for very specific use case.
https://www.linuxquestions.org/questions/fedora-installation-39/multiboot-de... is the thread that lead here, a "triple" boot UEFI installation with Debian and Fedora, where installing openSUSE after Debian and Fedora resulted in an openSUSE Grub in which the only apparent choices found by the poster were openSUSE Leap 15.1 and Advanced options, in part I expect because the "Probe Foreign OS" box was not checked. I'm not familiar with any specific details of what is expected with that box checked, because I never use it. I make my own menus with either menu.lst (MBR installations), or custom.cfg (UEFI installations) via /etc/grub.d/06_custom (copied from 40_custom).
Yep, that looks like not checked Probe Foreign OS. In Advanced options are only specific options related to given kernel. All other OS are directly in top level menu and can boot directly from it. I have it even on my own machine. But it should be enabled by default on opensuse.
The use case is a desire to suggest when possibly appropriate that a nominally enlightened or unenlightened multibooter switch his boot menu from multiscreen configuration to single, and be able to do it with openSUSE's flagship tool YaST2 instead of via the shell.
Maybe it's a good idea to offer the option any time more than one or two other operating system(s) have been first installed, if not always?
That is problem. How to find it? Reason why probe foreign os is optional is that it is very time consuming to inspect partitions.
Personally I find all multipage Grub menu configurations obnoxious. They strongly remind me of Windows' little bitty windows with select lists that expose only two or three selections at a time on a screen that has ample space for many times that number in a window nominally taller.
In fact that submenus is mainly to boot specific kernel or btrfs snapshot. For other OSes it should not be used. So goal is to not confuse users and easily allow him to select the latest and greatest kernel. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
Arvin Schnell -
Felix Miata -
Josef Reidinger