I went ahead and started playing with ED until I got zipl.conf properly
updated, then ran mkinitrd & zipl, did a reboot and everything came back up
OK. Whew!
I am still going to work on setting up a rescue system procedure that I can
use as a fallback in the future.
Thanks a bunch for everyone's help!
Jim Moling
James Moling
To: Linux on 390 Port
<[email protected]>
01/25/2007 05:24 cc:
PM Subject: Re: Lost an LVM under
SLES9 64-bit ...(Document link: Jim Moling)
Hmm - doesn't look good, here's the response that I got:
ifup eth0
eth0
ERROR: No configuration found for eth0
Jim Moling
"Post, Mark K"
<[EMAIL PROTECTED] To:
[email protected]
m> cc: (bcc: James
Moling/IR/FMS)
Sent by: Linux on Subject: Re: Lost an LVM under
SLES9 64-bit ...
390 Port
<[EMAIL PROTECTED]
IST.EDU>
01/25/2007 04:40
PM
Please respond to
Linux on 390 Port
Next try doing an "ifup eth0" if using QDIO. "ifup hsi0" for HiperSockets.
ctc0 for CTCs, etc.
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jim
Moling
Sent: Thursday, January 25, 2007 4:23 PM
To: [email protected]
Subject: Re: Lost an LVM under SLES9 64-bit ...
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
----------------------------------------------------------------------
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
