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