Hide Forgot
Description of problem: When /boot is a logical volume and non-C (or non-english) locale is used then zipl fails with an error. [root@devel2 ~]# zipl Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper /boot/ Error: Could not determine partition start for dasda1 Error: Script could not determine target parameters Version-Release number of selected component (if applicable): s390utils-1.8.2-36.el6.s390x How reproducible: 100% Steps to Reproduce: 1. zipl Actual results: [root@devel2 ~]# zipl Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper /boot/ Error: Could not determine partition start for dasda1 Error: Script could not determine target parameters Expected results: [root@devel2 ~]# LANG=C zipl Using config file '/etc/zipl.conf' Run /lib/s390-tools/zipl_helper.device-mapper /boot/ Building bootmap in '/boot/' Building menu 'rh-automatic-menu' Adding #1: IPL section 'linux-2.6.32-131.0.15.el6.s390x' (default) Preparing boot device: dasda. Done.
Created attachment 517826 [details] run helper script in C locale
My locale is "cs_CZ.UTF-8" and the tool with translated output is blockdev.
Created attachment 519007 [details] s390-tools-rhel6-zipl_helper_locale.patch ------- Comment on attachment From brueckner.ibm.com 2011-08-19 06:31 EDT------- Description: zipl: localized scripting output leads to errors Symptom: zipl is terminated with an error: "Script could not determine target parameters" Problem: zipl uses zipl_helper.device-mapper to print zipl parameters for device mapper devices. This script parses the output of other programs that might have a locale dependent output. If so, the script is unable to parse the output. Solution: Setup and use a standard locale to avoid localized scripting output.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1525.html