Bug 113204
| Summary: | LTC5734-Problem with multiple boot entries in /etc/zipl.conf | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Mark Ver <markver> |
| Component: | s390utils | Assignee: | Phil Knirsch <pknirsch> |
| Status: | CLOSED ERRATA | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | CC: | laroche, rvokal, zaitcev |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | s390 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-11-12 04:05:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-258.html ----- Additional Comments From markver.com 2004-11-11 16:09 EDT -------
Tested this recently against "Taroon Update 4".
This issue seems to be fixed in that release.
For example:
[root@redhat1 boot]# uname -a
Linux redhat1.pdl.pok.ibm.com 2.4.21-22.EL #1 SMP Tue Oct 19 14:43:15 EDT 2004
s390 s390 s390 GNU/Linux
[root@redhat1 boot]# rpm -q s390utils
s390utils-1.2.4-5
[root@redhat1 boot]#
[root@redhat1 boot]# cat /etc/zipl.conf
[defaultboot]
default=linux
target=/boot/
[linux]
image=/boot/vmlinuz-2.4.21-22.EL
ramdisk=/boot/initrd-2.4.21-22.EL.img
parameters="root=LABEL=/"
[dumpdasd]
dumpto=/dev/dasde1
[root@redhat1 boot]#
[root@redhat1 boot]# zipl
Using config file '/etc/zipl.conf'
Building bootmap '/boot//bootmap'
Building menu 'rh-automatic-menu'
Adding #1: IPL section 'linux' (default)
Preparing boot device: dasdb (0201).
Done.
[root@redhat1 boot]#
----- Additional Comments From markver.com 2004-11-11 16:15 EDT ------- Since it seems fixed, marking bug as closed. |
The following has be reported by IBM LTC: Problem with multiple boot entries in /etc/zipl.conf Hardware Environment: Type: 2064 Model: 109 Software Environment: VM00 Control Program: z/VM 4.4.0 Kernel: 2.4.21-6.EL #1 SMP Tue Dec 9 14:42:20 EST 2003 s390 s390 s390 GNU/Linux Zipl tool package: s390utils-1.2.1-4 Steps to Reproduce: 1. Add a new section into the /etc/zipl.conf file, example: [dumpdasd] dumpto=/dev/dasdb1 2. You run the new section and it works just fine: zipl dumpdasd 3. Now you try to rerun the default section again (for example if system is having trouble starting up and you want to restore the correct bootstrap after a crash): zipl Actual Results: When trying to run the default section, after having modified zipl.conf to include the additional (dumpdasd) section, the system spits back the message: Using config file '/etc/zipl.conf' Error: Section 'dumpdasd' cannot be included in menu 'rh-automatic-menu' The strange thing is that calling the added section seems to work just fine (in my case, I could actually get a dump with the target device). It's just processing for the default section that goes berserk. The default section starts working again as soon as the added section is commented out again. Expected Results: You should be able to add other sections into the zipl.conf file, either for dump-dasd/dump-tape or other ipl sections if you have multiple kernel versions you need to deal with. Additional Informatio