Well, I tried "init 3", but it didn't work so well. Here's what was
displayed:
init 3
INIT: Switching to runlevel: 3
INIT: Sending processes the TERM signal
Boot logging started on /dev/ttyS0(/dev/console) at Thu Jan 25 15:52:46
2007
Master Resource Control: previous runlevel: *, switching to runlevel: 3
/etc/init.d/rc*.d/: more than one link for service coldplug
/etc/init.d/rc*.d/: more than one link for service random
/etc/init.d/rc*.d/: more than one link for service network
/etc/init.d/rc*.d/: more than one link for service syslog
/etc/init.d/rc*.d/: more than one link for service nmb
/etc/init.d/rc*.d/: more than one link for service portmap
/etc/init.d/rc*.d/: more than one link for service resmgr
/etc/init.d/rc*.d/: more than one link for service postfix
/etc/init.d/rc*.d/: more than one link for service nfsboot
/etc/init.d/rc*.d/: more than one link for service cups
/etc/init.d/rc*.d/: more than one link for service fbset
/etc/init.d/rc*.d/: more than one link for service sshd
/etc/init.d/rc*.d/: more than one link for service smb
/etc/init.d/rc*.d/: more than one link for service cron
/etc/init.d/rc*.d/: more than one link for service hwscan
/etc/init.d/rc*.d/: more than one link for service smbfs
Shutting down service xdm..done
No available keymaps for machine s390x found
Master Resource Control: runlevel 3 has been reached
Failed services in runlevel 3: Ý80C Ý10Dkbd
Welcome to SUSE LINUX Enterprise Server 9 (s390x) - Kernel
2.6.5-7.244-s390x (ttyS0).
I haven't updated zipl.conf followed by the mkinitrd & zipl commands yet -
that was what I was hoping to do if I got networking up and could logon via
SSH.
I took a look under the directory /etc/init.d/ and see a bash script called
"network", also discovered there is an rcnetwork command. I tried both of
these with start, restart and reload, but it only seems to start a minimal
network service - no IP connectivity. Am I getting close? Any other ideas?
Jim Moling
|---------+-------------------------------->
| | "Edmund R. MacKenty" |
| | <[EMAIL PROTECTED]|
| | ftware.com> |
| | Sent by: Linux on 390|
| | Port |
| | <[EMAIL PROTECTED]|
| | EDU> |
| | |
| | |
| | 01/25/2007 03:45 PM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|---------+-------------------------------->
>------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc: (bcc: James Moling/IR/FMS)
|
| Subject: Re: Lost an LVM under SLES9 64-bit ...
|
>------------------------------------------------------------------------------------------------------------|
On Thursday 25 January 2007 15:33, Jim Moling wrote:
>That's easy - I didn't think of it (it's to easy) AND I don't know how,
but
>it sure sounds like a great idea.
>I have to admit I've been relying on Yast alot so far (which I can't use
at
>this point) as my repertoire of Linux commands is pretty weak (like almost
>nonexistent?) ...
>So if you can give me a hint as to how I would go about doing that - I
>assume there are line command(s) for this ...?
>Note that I am still in "maint" mode, and I don't know exactly how limited
>that is, i.e. is there anything that I might be missing that would prevent
>networking from starting?
>Of course, I suppose I will find that out as soon as I try it - nothing
>beats trial by fire, eh?
By "maint" mode, I assume you mean the superuser "repair shell" that the
IPL
put you into when things came up without the LVM. The system is in
single-user mode, which just means that it has not run all the usual
boot-time initialization scripts to support multiple users. Or the
network.
>From single-user mode, you can tell Linux to change to multi-user mode with
network enabled with the command: "init 3". That moves you from run-level
1
(single-user) to run-level 3 (multi-user with network). You will see the
output of various initialization scripts on your console as it goes and
does
that. It might terminate the shell on your console, so you might have to
do
a Linux login again there.
Alternatively, you could just exit that single-user shell, and Linux should
attempt a reboot. Because you have done your mkinitrd and zipl now, it
should come up cleanly, mount and check your LVM filesystems, and
automatically go to run-level 3 for you.
It's probably overkill, but I would halt Linux, logoff the guest, logon the
guest again and IPL Linux; just to make sure that everything is set up
properly for the next time your guest gets logged off.
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software, Inc.
Newton, MA USA
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
