Yes, you will have to go thru the installation process UNTIL it asks you about ssh.
Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Thu, Dec 16, 2010 at 8:25 PM, Melancon, Ruddy <melanc...@dot.state.al.us>wrote: > I have restore the disk to a pre-LVM image. This image knows nothing about > 208-213. I have commented these volumes out in the 'user direct' file. > > I tried this but it takes me to the install menu, not Yast or an option to > select ssh. > > Ruddy > > -----Original Message----- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > Mauro Souza > Sent: Thursday, December 16, 2010 3:40 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: ipl problem > > When you (or someone else) installed the first primordial Linux image, the > installation kernel and initrd was used. > In most shops, there's an exec somewhere named SLES10 EXEC or RHEL5 EXEC or > something like that. > > Log on your dead penguim, and issue those commands: > > #CP IPL CMS > ACC (NOPROF > > That will bring you to a bare CMS, and it's all we need. Ask about where > the > IPL execs for the installation are, you will need them. > > Assuming the execs and initrd/kernel images are on the disk 200 on LINUXOP > (as is in my place), issue this: > > LINK LINUXOP 200 1200 RR > ACC 1200 Z > SLES11SP1 (if the exec is called SLES11SP1. If not, check with a FLIST * > EXEC Z). > > This will bring up the installation mode. Proceed as usual, to the point > where Yast asks you to choose what kind of terminal you want to use. Select > SSH. > > Fire up your ssh client, connect to the now undead penguim, and run this: > > chccwdev -e 202-213 > vgscan > vgchange -ay > > From now, you will have your disks and LVM activated. I don't know if you > put / and /boot on the LVM or not. Let's continue as if you did: > > mkdir /tmp/root > mount /dev/mapper/vg-name/lv-name /mnt/root > mount -o bind /dev /tmp/root/dev > mount -o bind /sys /tmp/root/sys > mount -t proc none /tmp/root/proc > chroot /tmp/root > cd /boot > mkinitrd > zipl > exit > cd / > umount /tmp/root/* (easier than issue a lot of umounts) > shutdown -h now > > From now, you have re-created the boot record and all the structures needed > to boot. Try to boot from your dasd again. > > Ask anything you need. > > Mauro > http://mauro.limeiratem.com - registered Linux User: 294521 > Scripture is both history, and a love letter from God. > > > On Thu, Dec 16, 2010 at 7:19 PM, Melancon, Ruddy > <melanc...@dot.state.al.us>wrote: > > > Where do I get instructions on doing this?? > > > > Ruddy > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > Mark > > Post > > Sent: Thursday, December 16, 2010 2:48 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: ipl problem > > > > >>> On 12/16/2010 at 02:59 PM, "Melancon, Ruddy" < > > melanc...@dot.state.al.us> wrote: > > > > > 00: IPL 202 CLEAR > > > 00: zIPL v1.8.0-44.22.5 interactive boot menu > > > 00: > > > 00: 0. default (SLES11_SP1) > > > 00: > > > 00: 1. SLES11_SP1 > > > 00: 2. FailsafeV1 > > > 00: 3. ipl > > > 00: > > > 00: Note: VM users please use '#cp vi vmsg <number> > <kernel-parameters>' > > > 00: > > > 00: Please choose (default will boot in 10 seconds): > > > 00: Booting default (SLES11_SP1)... > > > 00: HCPGIR450W CP entered; disabled wait PSW 000A0000 00000102 > > > > Not sure how this came about, but I think your solution is to boot from > the > > VM reader using the installation kernel/initrd, activate your DASD, mount > > your root file system (and /boot if that is separate) and re-run zipl. > > > > > > Mark Post > > > > ---------------------------------------------------------------------- > > 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/ > > > > ---------------------------------------------------------------------- > > 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/ > > > > ---------------------------------------------------------------------- > 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/ > > ---------------------------------------------------------------------- > 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/ > ---------------------------------------------------------------------- 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/
