[Bug 1230345] New: s390-tools zipl : Error: Unsupported SCSI disk layout when multipath device
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Bug ID: 1230345 Summary: s390-tools zipl : Error: Unsupported SCSI disk layout when multipath device Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs@suse.de Reporter: ro@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- this same setup has worked for many years and in all of code 15 zipl version from: # rpm -q s390-tools s390-tools-2.34.0-1.1.s390x topmost changelog entry: * Mon Aug 26 2024 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> * Applied a patch to fix Rust compilation errors (bsc#1229461) - s390-tools-2.34-Fix-Rust-compilation-errors.patch - Fix: s390-tools: Rust compilation errors (s390_pv_core), build fails with "error: unnecessary qualification" * Added BuildRequieres in the .spec file - perl-Bootloader >= 0.4.15 setup: /dev/mapper/3600507630bffd2160000000000002000 4120288 347688 3562888 9% /boot2 s390zl21:~ # multipath -ll 3600507630bffd2160000000000002000 dm-1 IBM,2107900 size=4.0G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 0:0:2:1073758240 sdb 8:16 active ready running `- 1:0:1:1073758240 sdh 8:112 active ready running s390zl21:~ # cat /boot2/zipl.conf [defaultboot] defaultmenu = menu [KIWI_SLES15_20240909] image = /boot2/kernel-kiwi-20240909 target = /boot2/zipl ramdisk = /boot2/initrd-kiwi-20240909.xz parameters = "hvc_iucv=8 TERM=dumb switch_amode console=sclp_line0 console=ttyS0 bond_mode=1 kiwiservertype=http kiwiimage=workers/test-s390x-kvm/image-current.xz kiwidebug=1 kiwikernelmodule=scsi_dh_alua ELOG_EXCEPTION=/dev/sclp_line0 ELOG_BOOTSHELL=/dev/ttysclp0 cio_ignore=all,!ipldev,!condev,!f900,!fa00,!fc00,!f100-f123,!f200-f223 crashkernel=64M-:32M net.ifnames=0 sysctl.vm.allocate_pgste=1 transparent_hugepage=never" ... :menu default = 1 prompt = 1 target = /boot2/zipl timeout = 10 1 = KIWI_SLES15_20240909 dropping multipath it works again, but it really should keep working with the device on a multipath map. s390zl21:~ # umount /boot2 s390zl21:~ # multipathd -k multipathd> del map 3600507630bffd2160000000000002000 ok s390zl21:~ # mount /dev/sdb /boot2 s390zl21:~ # zipl -c /boot2/zipl.conf Using config file '/boot2/zipl.conf' (from command line) Building bootmap in '/boot2/zipl' Building menu 'menu' Adding #1: IPL section 'KIWI_SLES15_20240909' (default) Adding #2: IPL section 'KIWI_SLES15_20240903' Adding #3: IPL section 'KIWI_SLES15_20240808' Preparing boot device for LD-IPL: sdb. Done. s390zl21:~ # umount /boot2 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |nikolay.gueorguiev@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c1 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com --- Comment #1 from Thomas Blume <thomas.blume@suse.com> --- Just tried a plain tumbleweed installation on s390 zvm multipathed device. That worked: --> 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Using config file '/boot/zipl/config' (from command line) 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Building bootmap in '/boot/zipl' 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Building menu 'menu' 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Adding #1: IPL section 'grub2' (default) 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Adding #2: IPL section 'skip-grub2' 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Adding #3: IPL section 'grub2-mem1G' 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Run /lib/s390-tools/zipl_helper.device-mapper 253:20 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Preparing boot device for LD-IPL: dm-1. 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Standard output: Done. 2024-09-11 14:35:44 <3> install(3196) [Ruby] lib/cheetah.rb(log_stream_line):211 Error output: Installation beendet. Keine Fehler aufgetreten. 2024-09-11 14:35:44 <1> install(3196) [Ruby] lib/cheetah.rb(record_status):183 Status: 0 --< Maybe there is something missing in the kiwi image? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nikolay.gueorguiev@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c2 --- Comment #2 from Ruediger Oertel <ro@suse.com> --- well, this worked with the same IBS/OBS worker images all the time. reducing to 1 entry, running with "-V": s390zl21:/ # zipl -V -c /boot2/zipl.conf.min Looking for components in '/lib/s390-tools' Using config file '/boot2/zipl.conf.min' (from command line) Secure boot support: yes Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Target device information Device..........................: fe:01 *) Partition.......................: fe:01 Device name.....................: dm-1 Device driver name..............: device-mapper Type............................: disk partition Disk layout.....................: SCSI disk layout *) Geometry - start................: 0 *) File system block size..........: 4096 Physical block size.............: 512 *) Device size in physical blocks..: 8388608 *) Data provided by script. Building bootmap in '/boot2/zipl' Building menu 'menu' Adding #1: IPL section 'KIWI_SLES15_20240909' (default) initial ramdisk...: /boot2/initrd-kiwi-20240909.xz kernel image......: /boot2/kernel-kiwi-20240909 Run /lib/s390-tools/zipl_helper.device-mapper 254:1 kernel parmline...: 'hvc_iucv=8 TERM=dumb switch_amode console=sclp_line0 console=ttyS0 bond_mode=1 kiwiservertype=http kiwiimage=workers/test-s390x-kvm/image-current.xz kiwidebug=1 kiwikernelmodule=scsi_dh_alua ELOG_EXCEPTION=/dev/sclp_line0 ELOG_BOOTSHELL=/dev/ttysclp0 cio_ignore=all,!ipldev,!condev,!f900,!fa00,!fc00,!f100-f123,!f200-f223 crashkernel=64M-:32M net.ifnames=0 sysctl.vm.allocate_pgste=1 transparent_hugepage=never' Run /lib/s390-tools/zipl_helper.device-mapper 254:1 component address: heap area.......: 0x00002000-0x00005fff stack area......: 0x0000f000-0x0000ffff internal loader.: 0x0000a000-0x0000dfff parameters......: 0x00009000-0x000091ff kernel image....: 0x00010000-0x00a06fff parmline........: 0x00a08000-0x00a081ff initial ramdisk.: 0x00a20000-0x0714fdff environment blk.: 0x00a18000-0x00a18fff zIPL environment block content: Preparing boot device for LD-IPL: dm-1. Error: Unsupported SCSI disk layout end of strace: 3460311 write(3, "zSeries bootmap file\ncreated by "..., 512) = 512 3460311 lseek(3, 49664, SEEK_SET) = 49664 3460311 write(1, " component address:\n", 21) = 21 3460311 write(1, " heap area.......: 0x00002000"..., 44) = 44 3460311 write(1, " stack area......: 0x0000f000"..., 44) = 44 3460311 write(1, " internal loader.: 0x0000a000"..., 44) = 44 3460311 write(1, " parameters......: 0x00009000"..., 44) = 44 3460311 write(1, " kernel image....: 0x00010000"..., 44) = 44 3460311 write(1, " parmline........: 0x00a08000"..., 44) = 44 3460311 write(1, " initial ramdisk.: 0x00a20000"..., 44) = 44 3460311 write(1, " environment blk.: 0x00a18000"..., 44) = 44 3460311 lseek(3, 0, SEEK_CUR) = 49664 3460311 write(3, "zIPL\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) = 512 3460311 fstatfs64(3, 88, {f_type=EXT2_SUPER_MAGIC, f_bsize=4096, f_blocks=1030072, f_bfree=943135, f_bavail=890707, f_files=262144, f_ffree=262115, f_fsid={val=[0xb175a6e9, 0x95ddf447]}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 3460311 ioctl(3, FS_IOC_FIEMAP, {fm_start=49664, fm_length=4096, fm_flags=FIEMAP_FLAG_SYNC, fm_extent_count=1} => {fm_flags=FIEMAP_FLAG_SYNC, fm_mapped_extents=1, ...}) = 0 3460311 write(1, "zIPL environment block content:\n", 32) = 32 3460311 lseek(3, 0, SEEK_CUR) = 50176 3460311 write(3, "zIPL\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0040\t\2\0\0\0\0\0\0\0"..., 512) = 512 3460311 fstatfs64(3, 88, {f_type=EXT2_SUPER_MAGIC, f_bsize=4096, f_blocks=1030072, f_bfree=943135, f_bavail=890707, f_files=262144, f_ffree=262115, f_fsid={val=[0xb175a6e9, 0x95ddf447]}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 3460311 ioctl(3, FS_IOC_FIEMAP, {fm_start=50176, fm_length=4096, fm_flags=FIEMAP_FLAG_SYNC, fm_extent_count=1} => {fm_flags=FIEMAP_FLAG_SYNC, fm_mapped_extents=1, ...}) = 0 3460311 write(1, "Preparing boot device for LD-IPL"..., 40) = 40 3460311 openat(AT_FDCWD, "/dev/zipl0000", O_RDWR) = 4 3460311 ioctl(4, BLKFLSBUF) = 0 3460311 lseek(4, 0, SEEK_SET) = 0 3460311 read(4, "zIPL\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\200\10\2\0\0\0\0\0\0\0"..., 512) = 512 3460311 fsync(4) = 0 3460311 close(4) = 0 3460311 close(3) = 0 3460311 unlink("/boot2/zipl/bootmap_temp.XoknWX") = 0 3460311 unlink("/dev/zipl0000") = 0 3460311 write(2, "Error: Unsupported SCSI disk lay"..., 36) = 36 3460311 exit_group(1) = ? 3460311 +++ exited with 1 +++ -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c3 --- Comment #3 from Ruediger Oertel <ro@suse.com> --- without multipath the "-V" ends with: zIPL environment block content: Preparing boot device for LD-IPL: sdb. Detected plain SCSI partition. Writing SCSI master boot record. Syncing disks... Done. and the strace ends with: 3467985 write(1, " initial ramdisk.: 0x00a20000"..., 44) = 44 3467985 write(1, " environment blk.: 0x00a18000"..., 44) = 44 3467985 lseek(3, 0, SEEK_CUR) = 49664 3467985 write(3, "zIPL\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) = 512 3467985 fstatfs64(3, 88, {f_type=EXT2_SUPER_MAGIC, f_bsize=4096, f_blocks=1030072, f_bfree=943156, f_bavail=890728, f_files=262144, f_ffree=262115, f_fsid={val=[0xb175a6e9, 0x95ddf447]}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 3467985 ioctl(3, FS_IOC_FIEMAP, {fm_start=49664, fm_length=4096, fm_flags=FIEMAP_FLAG_SYNC, fm_extent_count=1} => {fm_flags=FIEMAP_FLAG_SYNC, fm_mapped_extents=1, ...}) = 0 3467985 write(1, "zIPL environment block content:\n", 32) = 32 3467985 lseek(3, 0, SEEK_CUR) = 50176 3467985 write(3, "zIPL\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0x@a\2\0\0\0\0\0\0\0"..., 512) = 512 3467985 fstatfs64(3, 88, {f_type=EXT2_SUPER_MAGIC, f_bsize=4096, f_blocks=1030072, f_bfree=943156, f_bavail=890728, f_files=262144, f_ffree=262115, f_fsid={val=[0xb175a6e9, 0x95ddf447]}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0 3467985 ioctl(3, FS_IOC_FIEMAP, {fm_start=50176, fm_length=4096, fm_flags=FIEMAP_FLAG_SYNC, fm_extent_count=1} => {fm_flags=FIEMAP_FLAG_SYNC, fm_mapped_extents=1, ...}) = 0 3467985 write(1, "Preparing boot device for LD-IPL"..., 39) = 39 3467985 openat(AT_FDCWD, "/dev/zipl0000", O_RDWR) = 4 3467985 ioctl(4, BLKFLSBUF) = 0 3467985 lseek(4, 0, SEEK_SET) = 0 3467985 read(4, "zIPL\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0x`\2\2\0\0\0\0\0\0\0"..., 512) = 512 3467985 write(1, "Detected plain SCSI partition.\n", 31) = 31 3467985 write(1, "Writing SCSI master boot record."..., 33) = 33 3467985 lseek(4, 0, SEEK_SET) = 0 3467985 write(4, "zIPL\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0x@b\2\0\0\0\0\0\0\0"..., 512) = 512 3467985 fsync(4) = 0 3467985 close(4) = 0 3467985 openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = 4 3467985 fstat(4, {st_mode=S_IFREG|0644, st_size=114, ...}) = 0 3467985 fstat(4, {st_mode=S_IFREG|0644, st_size=114, ...}) = 0 3467985 read(4, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 114 3467985 lseek(4, -60, SEEK_CUR) = 54 3467985 read(4, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 60 3467985 close(4) = 0 3467985 socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4 3467985 connect(4, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0 3467985 send(4, "<14>Sep 11 16:23:44 zipl: Boot l"..., 60, MSG_NOSIGNAL) = 60 3467985 rename("/boot2/zipl/bootmap_temp.PbIcra", "/boot2/zipl/bootmap") = 0 3467985 close(3) = 0 3467985 unlink("/dev/zipl0000") = 0 3467985 write(1, "Syncing disks...\n", 17) = 17 3467985 sync() = 0 3467985 write(1, "Done.\n", 6) = 6 3467985 exit_group(0) = ? 3467985 +++ exited with 0 +++ -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c4 --- Comment #4 from Ruediger Oertel <ro@suse.com> --- broken case: 3460311 openat(AT_FDCWD, "/dev/zipl0000", O_RDWR) = 4 3460311 ioctl(4, BLKFLSBUF) = 0 3460311 lseek(4, 0, SEEK_SET) = 0 3460311 read(4, "zIPL\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\200\10\2\0\0\0\0\0\0\0"..., 512) = 512 working case: 3467985 openat(AT_FDCWD, "/dev/zipl0000", O_RDWR) = 4 3467985 ioctl(4, BLKFLSBUF) = 0 3467985 lseek(4, 0, SEEK_SET) = 0 3467985 read(4, "zIPL\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0x`\2\2\0\0\0\0\0\0\0"..., 512) = 512 checking /dev/sdb vs /dev/mapper/3600507630bffd2160000000000002000 in both cases same output: s390zl21:~ # dd if=/dev/sda of=test1 bs=256 count=1 1+0 records in 1+0 records out 256 bytes copied, 5.3152e-05 s, 4.8 MB/s s390zl21:~ # xxd test1 00000000: 7a49 504c 0000 0001 0000 0000 0000 0000 zIPL............ 00000010: 0000 0000 0078 4062 0200 0000 0000 0000 .....x@b........ 00000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................ -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c5 --- Comment #5 from Ruediger Oertel <ro@suse.com> --- multipath/broken: s390zl21:~ # grep mknod bla.multipath 3480780 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0xfe, 0x1)) = 0 3480782 mknodat(AT_FDCWD, "/dev/zipl-dm-temp-00", S_IFBLK|000, makedev(0x8, 0x10)) = 0 3480780 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0xfe, 0x1)) = 0 3480780 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0xfe, 0x1)) = -1 EEXIST (File exists) 3480780 mknodat(AT_FDCWD, "/dev/zipl0001", S_IFBLK|0700, makedev(0xfe, 0x1)) = 0 3480789 mknodat(AT_FDCWD, "/dev/zipl-dm-temp-00", S_IFBLK|000, makedev(0x8, 0x10)) = 0 3480780 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0xfe, 0x1)) = -1 EEXIST (File exists) 3480780 mknodat(AT_FDCWD, "/dev/zipl0001", S_IFBLK|0700, makedev(0xfe, 0x1)) = 0 3480823 mknodat(AT_FDCWD, "/dev/zipl-dm-temp-00", S_IFBLK|000, makedev(0x8, 0x10)) = 0 sdb/working: ^[[As390zl21:~ # grep mknod bla.sdb 3482680 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0x8, 0x10)) = 0 3482680 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0x8, 0x10)) = 0 3482680 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0x8, 0x10)) = -1 EEXIST (File exists) 3482680 mknodat(AT_FDCWD, "/dev/zipl0001", S_IFBLK|0700, makedev(0x8, 0x10)) = 0 3482680 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0x8, 0x10)) = -1 EEXIST (File exists) 3482680 mknodat(AT_FDCWD, "/dev/zipl0001", S_IFBLK|0700, makedev(0x8, 0x10)) = 0 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c6 --- Comment #6 from Ruediger Oertel <ro@suse.com> --- s390zl21:~ # df -hT /boot2 Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/3600507630bffd2160000000000002000 ext2 4.0G 340M 3.4G 9% /boot2 vs s390zl21:~ # df -hT /boot2 Filesystem Type Size Used Avail Use% Mounted on /dev/sdb ext2 4.0G 340M 3.4G 9% /boot2 I really do not understand the difference. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c7 --- Comment #7 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Ruediger Oertel from comment #6)
s390zl21:~ # df -hT /boot2 Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/3600507630bffd2160000000000002000 ext2 4.0G 340M 3.4G 9% /boot2
vs
s390zl21:~ # df -hT /boot2 Filesystem Type Size Used Avail Use% Mounted on /dev/sdb ext2 4.0G 340M 3.4G 9% /boot2
I really do not understand the difference.
Rudi, could you attach the full strace of the non-working case? I'd like to compare it with my testsetup. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c8 --- Comment #8 from Ruediger Oertel <ro@suse.com> --- Created attachment 877286 --> https://bugzilla.suse.com/attachment.cgi?id=877286&action=edit strace on multipath -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c9 --- Comment #9 from Ruediger Oertel <ro@suse.com> --- Created attachment 877287 --> https://bugzilla.suse.com/attachment.cgi?id=877287&action=edit strace without multipath -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c10 --- Comment #10 from Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> --- zipl/include/install.h * * * /* Determine SCSI disk layout from the specified BOOTBLOCK. */ static inline enum scsi_layout get_scsi_layout(unsigned char *bootblock) { if ((bootblock[510] == 0x55) && (bootblock[511] == 0xaa)) return scsi_layout_pcbios; else if ((bootblock[508] == 0xda) && (bootblock[509] == 0xbe)) return scsi_layout_sun; else if ((bootblock[0] == 0x0b) && (bootblock[1] == 0xe5) && (bootblock[2] == 0xa9) && (bootblock[3] == 0x41)) return scsi_layout_sgi; return scsi_layout_unknown; } * * * /* Types of SCSI disk layouts */ enum scsi_layout { scsi_layout_pcbios, scsi_layout_sun, scsi_layout_sgi, scsi_layout_unknown }; * * * zipl/src/install.c * * * /* Create an IPL master boot record data structure for SCSI MBRs in memory * at location BUFFER. TABLE contains a pointer to the program table. INFO * provides information about the disk. */ static int update_scsi_mbr(void* bootblock, disk_blockptr_t* table, struct disk_info* info, disk_blockptr_t* scsi_dump_sb_blockptr) { struct scsi_mbr *mbr; struct scsi_dump_param param; void* buffer; switch (get_scsi_layout(bootblock)) { case scsi_layout_pcbios: if (verbose) printf("Detected SCSI PCBIOS disk layout.\n"); buffer = bootblock; break; case scsi_layout_sun: case scsi_layout_sgi: error_reason("Unsupported SCSI disk layout"); return -1; default: if (info->partnum) { error_reason("Unsupported SCSI disk layout"); return -1; } else { if (verbose) printf ("Detected plain SCSI partition.\n"); buffer=bootblock; } } mbr = (struct scsi_mbr *) buffer; memset(buffer, 0, sizeof(struct scsi_mbr)); memcpy(&mbr->magic, ZIPL_MAGIC, ZIPL_MAGIC_SIZE); mbr->version_id = DISK_LAYOUT_ID; bootmap_store_blockptr(&mbr->program_table_pointer, table, info, 0 /* this argument is ignored for scsi */); if (scsi_dump_sb_blockptr && scsi_dump_sb_blockptr->linear.block != 0) { /* Write dump boot_info */ param.block = scsi_dump_sb_blockptr->linear.block * scsi_dump_sb_blockptr->linear.size; boot_get_dump_info(&mbr->boot_info, BOOT_INFO_DEV_TYPE_SCSI, ¶m); } return 0; } -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c11 --- Comment #11 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Nikolay Gueorguiev from comment #10)
default: if (info->partnum) { error_reason("Unsupported SCSI disk layout"); return -1;
Hm, that looks like zipl fails if it detects the disk layout on a partition instead of a disk device. Usually, I can see the multipath disk device as /dev/dm-0 on my testmachines and subsequent dm-X numbers as the partitions on this device. e.g. my strace shows: --> [pid 68581] newfstatat(AT_FDCWD, "/dev/dm-0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0xfe, 0), ...}, 0) = 0 --< In the failing multipath zipl setup strace, I cannot find any dm-0, but dm-1 instead: --> 3480829 newfstatat(AT_FDCWD, "/dev/dm-1", {st_mode=S_IFBLK|0660, st_rdev=makedev(0xfe, 0x1), ...}, 0) = 0 --< However, if you have more than one multipath device attached, dm-1 could be valid for a disk device, so not sure if my suspect holds. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c12 --- Comment #12 from Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> --- I did a brand new installation of Tumbleweed on LPAR with mutipath. I didn't have issues. What I should look for? * * * monizp02:~ # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20240908" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240908" PRETTY_NAME="openSUSE Tumbleweed" * * * monizp02:~ # multipath -ll 3600507630bffd216000000000000204c dm-2 IBM,2107900 size=30G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 0:0:2:1078738976 sdf 8:80 active ready running `- 1:0:2:1078738976 sdh 8:112 active ready running 3600507630bffd216000000000000204d dm-10 IBM,2107900 size=30G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 0:0:2:1078804512 sdg 8:96 active ready running `- 1:0:2:1078804512 sdi 8:128 active ready running * * * monizp02:~ # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/3600507638081855cd8000000000000a3-part2 30G 2.0G 28G 7% / devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs 3.1G 384K 3.1G 1% /run tmpfs 7.7G 0 7.7G 0% /tmp tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-udev-load-credentials.service tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysctl.service tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysusers.service tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev.service /dev/mapper/3600507638081855cd8000000000000a3-part2 30G 2.0G 28G 7% /.snapshots /dev/mapper/3600507638081855cd8000000000000a3-part2 30G 2.0G 28G 7% /boot/grub2/s390x-emu /dev/mapper/3600507638081855cd8000000000000a3-part2 30G 2.0G 28G 7% /opt /dev/mapper/3600507638081855cd8000000000000a3-part2 30G 2.0G 28G 7% /root /dev/mapper/3600507638081855cd8000000000000a3-part2 30G 2.0G 28G 7% /srv /dev/mapper/3600507638081855cd8000000000000a3-part2 30G 2.0G 28G 7% /usr/local /dev/mapper/3600507638081855cd8000000000000a3-part1 280M 30M 235M 12% /boot/zipl /dev/mapper/3600507630bffd216000000000000204c-part1 30G 620M 30G 3% /home /dev/mapper/3600507638081855cd8000000000000a4-part1 30G 731M 30G 3% /var tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup.service tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-vconsole-setup.service tmpfs 1.0M 0 1.0M 0% /run/credentials/serial-getty@sclp_line0.service tmpfs 1.0M 0 1.0M 0% /run/credentials/serial-getty@ttysclp0.service tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs 1.6G 4.0K 1.6G 1% /run/user/1000 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c13 --- Comment #13 from Ruediger Oertel <ro@suse.com> --- not sure if this helps: s390zl21:~ # l /dev/mapper/ total 0 drwxr-xr-x 2 root root 260 Sep 11 16:50 ./ drwxr-xr-x 14 root root 5660 Sep 12 16:47 ../ lrwxrwxrwx 1 root root 7 Sep 11 16:50 3600507630bffd2160000000000002000 -> ../dm-1 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002100 -> ../dm-2 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002100-part1 -> ../dm-5 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002100-part2 -> ../dm-6 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002100-part3 -> ../dm-7 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002101 -> ../dm-3 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002104 -> ../dm-4 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002104-part1 -> ../dm-9 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507638081855cd80000000000002a -> ../dm-0 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600a0980383041622f2455736d434a76 -> ../dm-8 crw------- 1 root root 10, 236 Sep 9 16:28 control s390zl21:~ # dmsetup table 3600507630bffd2160000000000002000: 0 8388608 multipath 1 queue_if_no_path 1 alua 1 1 service-time 0 2 2 8:16 1 1 8:112 1 1 3600507630bffd2160000000000002100: 0 20971520 multipath 1 queue_if_no_path 1 alua 1 1 service-time 0 2 2 8:32 1 1 8:128 1 1 3600507630bffd2160000000000002100-part1: 0 5117952 linear 254:2 2048 3600507630bffd2160000000000002100-part2: 0 13305856 linear 254:2 5120000 3600507630bffd2160000000000002100-part3: 0 2543616 linear 254:2 18425856 3600507630bffd2160000000000002101: 0 1073741824 multipath 1 queue_if_no_path 1 alua 1 1 service-time 0 2 2 8:48 1 1 8:144 1 1 3600507630bffd2160000000000002104: 0 209715200 multipath 1 queue_if_no_path 1 alua 1 1 service-time 0 2 2 8:64 1 1 8:160 1 1 3600507630bffd2160000000000002104-part1: 0 209713152 linear 254:4 2048 3600507638081855cd80000000000002a: 0 8388608 multipath 1 queue_if_no_path 1 alua 2 1 service-time 0 1 2 8:176 1 1 service-time 0 1 2 8:0 1 1 3600a0980383041622f2455736d434a76: 0 8388608 multipath 3 queue_if_no_path pg_init_retries 50 1 alua 2 1 service-time 0 2 2 8:80 1 1 8:192 1 1 service-time 0 2 2 8:96 1 1 8:208 1 1 and grepping mknod from the strace runs: s390zl21:~ # grep mknod bla.multipath 3480780 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0xfe, 0x1)) = 0 3480782 mknodat(AT_FDCWD, "/dev/zipl-dm-temp-00", S_IFBLK|000, makedev(0x8, 0x10)) = 0 3480780 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0xfe, 0x1)) = 0 3480780 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0xfe, 0x1)) = -1 EEXIST (File exists) 3480780 mknodat(AT_FDCWD, "/dev/zipl0001", S_IFBLK|0700, makedev(0xfe, 0x1)) = 0 3480789 mknodat(AT_FDCWD, "/dev/zipl-dm-temp-00", S_IFBLK|000, makedev(0x8, 0x10)) = 0 3480780 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0xfe, 0x1)) = -1 EEXIST (File exists) 3480780 mknodat(AT_FDCWD, "/dev/zipl0001", S_IFBLK|0700, makedev(0xfe, 0x1)) = 0 3480823 mknodat(AT_FDCWD, "/dev/zipl-dm-temp-00", S_IFBLK|000, makedev(0x8, 0x10)) = 0 s390zl21:~ # grep mknod bla.sdb 3482680 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0x8, 0x10)) = 0 3482680 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0x8, 0x10)) = 0 3482680 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0x8, 0x10)) = -1 EEXIST (File exists) 3482680 mknodat(AT_FDCWD, "/dev/zipl0001", S_IFBLK|0700, makedev(0x8, 0x10)) = 0 3482680 mknodat(AT_FDCWD, "/dev/zipl0000", S_IFBLK|0700, makedev(0x8, 0x10)) = -1 EEXIST (File exists) 3482680 mknodat(AT_FDCWD, "/dev/zipl0001", S_IFBLK|0700, makedev(0x8, 0x10)) = 0 0xfe,0x1 = 254,1 = dm-1 0x08,0x10 = 8,16 = sdb -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c14 --- Comment #14 from Ruediger Oertel <ro@suse.com> --- s390zl21:~ # cat /etc/multipath.conf defaults { path_grouping_policy multibus path_checker tur polling_interval 15 no_path_retry queue checker_timeout 60 path_selector "service-time 0" find_multipaths smart } devices { device { vendor "IBM" product "2107900" path_grouping_policy group_by_prio prio alua } } -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c15 --- Comment #15 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Ruediger Oertel from comment #13)
not sure if this helps:
s390zl21:~ # l /dev/mapper/ total 0
Ah, it seems it had wrong assumptions about your disk layout. It seems that your zipl config (normally mounted at /boot/zipl) resides on a separate device and not as usual on a partition on the system root device. Therefore zipl assumes the ipl device is 3600507630bffd2160000000000002000
3600507630bffd2160000000000002000 -> ../dm-1 lrwxrwxrwx 1 root root 7 Sep 9 16:26
It looks like system root rather resides on:
3600507630bffd2160000000000002100 -> ../dm-2 lrwxrwxrwx 1 root root 7 Sep 9 16:26
because there are the partitions:
3600507630bffd2160000000000002100-part1 -> ../dm-5 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002100-part2 -> ../dm-6 lrwxrwxrwx 1 root root 7 Sep 9 16:26 3600507630bffd2160000000000002100-part3 -> ../dm-7
Rudi can you confirm that? I never did an installation with /boot/zipl on a separate disk. Maybe doing so can reproduce the issue. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c16 --- Comment #16 from Ruediger Oertel <ro@suse.com> --- no, I think I wrote it somewhere above. the boot disk is
3600507630bffd2160000000000002000 -> ../dm-1
and it has no partitions at all, it is a separate LUN shared between many LPARs that all boot off this disk. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c17 --- Comment #17 from Ruediger Oertel <ro@suse.com> --- (that disk is normally not mounted at all and I only mount it to add a new kernel/initrd pair and update zipl): ssh $TARG "mkdir -p /boot2 ; mount /dev/mapper/3600507630bffd2160000000000002000 /boot2" scp $ENVI/kernel $TARG:/boot2/kernel-kiwi-$DAT scp $ENVI/initrd.xz $TARG:/boot2/initrd-kiwi-$DAT.xz ssh $TARG "sed -i -e 's@workers/[^/]*/@workers/$ENVI/@' /boot2/zipl.entry" ssh $TARG "/boot2/gen_zipl_conf ; umount /boot2" and /boot2/gen_zipl_conf generates the config and calls zipl: ... cat /boot2/zipl.head /boot2/zipl.entries /boot2/zipl.bottom /boot2/zipl.menu > /boot2/zipl.conf zipl -c /boot2/zipl.conf -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Marcela Maslanova <marcela.maslanova@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marcela.maslanova@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Miroslav Franc <miroslav.franc@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |miroslav.franc@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c18 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |CONFIRMED --- Comment #18 from Thomas Blume <thomas.blume@suse.com> --- I could reproduce the issue with /boot/zipl on a separate device. In that case the partitioner in the installer already shows a warning: --> The system might not be able to boot: Missing device for /boot/zipl with size equal or bigger than 100 MiB and filesystem ext2, ext3, ext4, xfs Do you want to continue? --< continuing the installation results in a fatal error at grub installation: --> Execution of command "[["/usr/sbin/grub2-install", "--target=s390x-emu", "--force", "--skip-fs-probe"]]" failed. Exit code: 1 Error output: Installing for s390x-emu platform. /usr/sbin/grub2-install: warning: no hints available for your platform. Expect reduced performance. Error: Unsupported SCSI disk layout /sbin/zipl: Failed /usr/sbin/grub2-install: error: `grub2-zipl-setup' failed. --< Nikolay, according to https://www.ibm.com/docs/en/linux-on-systems?topic=ldabd-using-base-paramete... having /boot/zipl on a separate disk is supported. So, that installation should work. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugproxy@us.ibm.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marcus.kraft1@ibm.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tstaudt@de.ibm.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c19 --- Comment #19 from Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> --- Hello @IBM, Could you please review this bugzilla? Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c20 --- Comment #20 from Thomas Staudt <tstaudt@de.ibm.com> --- I'll mirror it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 LTC BugProxy <bugproxy@us.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.linux.ibm. | |com/show_bug.cgi?id=209005 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c21 --- Comment #21 from LTC BugProxy <bugproxy@us.ibm.com> --- ------- Comment From Eduard.Shishkin@ibm.com 2024-09-13 18:37 EDT------- Hello, Thank you for the report. The problem is caused by massive changes in zipl(8) tool, specifically by this commit: https://github.com/ibm-s390-linux/s390-tools/commit/76aaf3d4a8c41185a7e0be99... which is required to resolve old issues and to implement new features. Unfortunately, the problem is not always reproducible and its appearance depends on many factors. This why it did hit the distro bypassing our internal CI-environment. The fixup is still in our internal development branch. We'll think on how to release it ASAP. Thanks, Eduard. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c22 --- Comment #22 from LTC BugProxy <bugproxy@us.ibm.com> --- ------- Comment From Jan.Hoeppner@de.ibm.com 2024-09-16 07:43 EDT------- Hi Suse, the fix for this issue is available upstream: https://github.com/ibm-s390-linux/s390-tools/commit/d6b702d5791b47f735960ad1... You may apply the fix and verify that it solves the issue at hand. The fix will be part of the upcoming s390-tools release v2.35.0 which is scheduled for CW40. As of now, it's likely that this release will also be the base for SLES15 SP7. You can either wait for the release or integrate the fix mentioned above manually. There is no other release planned before that. If you need anything else from us, please let us know. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c23 --- Comment #23 from Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> --- https://build.opensuse.org/request/show/1201422 The patch has been applied. Waiting for acceptance. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c25 --- Comment #25 from Ruediger Oertel <ro@suse.com> --- confirmed. patch works for me: before: Unsupported SCSI disk layout when multipath device updated: s390zl21:~ # rpm -q --changelog s390-tools | head * Mon Sep 16 2024 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> * Applied patches (bsc#1230345) - zipl/src: add basic support for multiple target base disks - s390-tools-01-zipl-src-add-basic-support-for-multiple-target-base-disks.patch - s390-tools-02-zipl-src-add-basic-support-for-multiple-target-base-disks.patch now: s390zl21:~ # /boot2/gen_zipl_conf Using config file '/boot2/zipl.conf' (from command line) Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Building bootmap in '/boot2/zipl' Building menu 'menu' Adding #1: IPL section 'KIWI_SLES15_20240919' (default) Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Adding #2: IPL section 'KIWI_SLES15_20240912' Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Adding #3: IPL section 'KIWI_SLES15_20240909' Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Run /lib/s390-tools/zipl_helper.device-mapper 254:1 Preparing boot device for LD-IPL: dm-1. Done. thank you! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230345 https://bugzilla.suse.com/show_bug.cgi?id=1230345#c26 Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #26 from Nikolay Gueorguiev <nikolay.gueorguiev@suse.com> --- Patches applied. Confirmation that they work. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com