On 12/02/2010 03:51 AM, Bern VK2KAD wrote:
I then managed to make progress using the URL install method and ftp - after
successfully logging on to the ftp server things started to happen. So far so
good.
Alas, suddenly it all evaporated into a puff of smoke - the following is a
snip from the log.
Can anyone explain why the install decided to shutdown -
02:44:43,403 INFO : transferring
ftp://b...@20.250.180.52/RHEL6/images/install.img
02:45:24,353 INFO : mounted loopback device /mnt/runtime on /dev/loop0 as
/tmp/install.img
02:45:24,354 INFO : got stage2 at url
ftp://b...@20.250.180.52/RHEL6/images/install.img
02:45:24,354 INFO : reset repo= parameter to ftp://b...@20.250.180.52/RHEL6
02:45:26,682 INFO : Loading SELinux policy
02:45:42,692 INFO : getting ready to spawn shell now
02:45:42,697 INFO : not spawning a shell
02:45:54,461 INFO : Running anaconda script /usr/bin/anaconda
Apparently, the installer made progress into phase 3
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-guimode-s390.html.
Did you see any TUI/GUI parts of this phase 3?
If so, during which of the wizard screens did the installer bail out?
Maybe enabling debug output will show some hints on the console. Could
you please add "loglevel=debug ignore_loglevel"
[https://bugzilla.redhat.com/show_bug.cgi?id=603136#c1] to your parm
file (NOT conf file) and post the entire console log from IPL to shutdown?
about to exec shutdown
disabling swap...
unmounting filesystems...
/mnt/runtime done
disabling /dev/loop0 LOOP_CLR_FD failed: 16
/proc done
/dev/pts done
/sys done
/selinux done
waiting for mdraid sets to become clean...
Error: mdadm exited with status: 127
sending termination signals...done
sending kill signals...done
halting system
This is just the default follow-on procedure in case anaconda bails out.
There is an anaconda boot option "nokill" to prevent this default
shutdown. Unfortunately, it currently does not work on s390. It would be
very helpful to fetch the logs from the volatile /tmp to see where the
installer bailed out. In case you need or would like to do that, the
following patch would need to be applied to sbin/init inside initrd.img:
commit ea22912b014c64ca8732305b36d4463c33f438e9
Author: Steffen Maier <ma...@linux.vnet.ibm.com>
Date: Mon Jun 7 03:08:23 2010 +0200
Support "nokill" boot option for shutdown in linuxrc.s390
diff --git a/loader/linuxrc.s390 b/loader/linuxrc.s390
index 2a4104a..c0a6331 100644
--- a/loader/linuxrc.s390
+++ b/loader/linuxrc.s390
@@ -103,10 +103,17 @@ function checkipv4()
return $?
}
+function getKillPolicy()
+{
+ if grep -q nokill /proc/cmdline; then
+ echo "--nokill"
+ fi
+}
+
function doshutdown()
{
echo $"about to exec shutdown"
- exec /sbin/shutdown
+ exec /sbin/shutdown $(getKillPolicy)
exit 0
}
@@ -123,7 +130,7 @@ function doreboot()
fi
echo $"about to exec shutdown -r"
- exec /sbin/shutdown -r
+ exec /sbin/shutdown -r $(getKillPolicy)
exit 0
}
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
