If there's no password at all on those disks then you'll need their z/VM
sysprogs to either (a) add the word 'ALL' to the MDISK statement of the failing
guest or (b) add LINK <failing user> xxxx yyyy RR statements to the recovery
user's directory entry.
-------- Original message --------
From: Mike Frysinger <vap...@gentoo.org>
Date: 1/30/22 20:57 (GMT+10:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] trying to recover existing install
On 30 Jan 2022 10:28, Neale Ferguson wrote:
> Get their sysprogs to add link statements (RR) to that other guest. If they
> don't have read passwords you could vmcp link guest xxxx yyyy rr.
so what i'm doing:
* "user3" is up & running like normal
* "user4" is broken
* login to "user3" and enter CMS
* run: link user4 151 152 rr
* get back what i assume is an error:
00: HCPLNM111E LGENTOO4 0151 not linked; no read password
* i tried using my login password, but i'm guessing that's diff
link user4 151 152 rr PASS=mypass
* fwiw, `query password link` says:
00: LINK PASSWORD MAY BE INCLUDED ON THE COMMAND LINE
is there a way i can set/reset this password ? or do i have to ask a
sysadmin to do this for me ?
-mike
> -------- Original message --------
> From: Mike Frysinger <vap...@gentoo.org>
> Date: 1/30/22 19:31 (GMT+10:00)
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] trying to recover existing install
>
> On 30 Jan 2022 07:21, Neale Ferguson wrote:
> > Create a new guest, install a minimal system, link to the disks of the
> > guest you wish to recover, use cio_ignore -r to make them "visible",
> > chccwdev -e to vary them online, mount them, and recover. You should be
> > able to do it r/o. If they are in an lvm then vgscan, and vgchange -ay to
> > make it usable before the mount. Just make sure your new guest has a
> > different vg name.
>
> i should clarify that i don't have a lot of privileges here, so i can't
> create a new guest. i do however have another guest on the same system.
> how would i link the disks to the other guest ?
> -mike
>
> > -------- Original message --------
> > From: Mike Frysinger <vap...@gentoo.org>
> > Date: 1/30/22 16:35 (GMT+10:00)
> > To: LINUX-390@VM.MARIST.EDU
> > Subject: [LINUX-390] trying to recover existing install
> >
> > i'm by no means an s390 expert, so i might be missing something obvious.
> >
> > we've had an install running for a couple of years. recently the rootfs
> > had some important libs deleted, so it's now unbootable. i don't want to
> > format and lose data on it. so i'm trying to boot a kernel+initrd that i
> > have locally so i can recover things.
> >
> > from the docs [1], i need to first copy those files into a DASD before
> > i can IPL or punch+IPL them. our VMs have the following DASD's:
> >
> > 00: DASD 0150 3390 MRC79A R/W 3336 CYL ON DASD C79A SUBCHANNEL = 0006
> > dasda1 /boot
> > dasda2 /usr
> > 00: DASD 0151 3390 MRC79A R/W 3338 CYL ON DASD C79A SUBCHANNEL = 0007
> > dasdb1 /
> > 00: DASD 0160 9336 (VDSK) R/W 200000 BLK ON DASD VDSK SUBCHANNEL = 000F
> > dasdc1 swap
> > 00: DASD 0190 3390 MRCA02 R/O 214 CYL ON DASD CA02 SUBCHANNEL = 000C
> > 00: DASD 0191 3390 MRC790 R/W 2 CYL ON DASD C790 SUBCHANNEL = 0008
> > dasdd
> > 00: DASD 019E 3390 MRCA02 R/O 500 CYL ON DASD CA02 SUBCHANNEL = 000D
> > 00: DASD 0200 3390 MRC79E R/W 32759 CYL ON DASD C79E SUBCHANNEL = 0005
> > dasde1 /mnt/space
> > 00: DASD 0592 3390 MRCA09 R/O 240 CYL ON DASD CA09 SUBCHANNEL = 000E
> > 00: DASD 8888 3390 MRCA05 R/O 30 CYL ON DASD CA05 SUBCHANNEL = 0004
> >
> > the only DASD i can see that i can write to from CP/CMS is 191, but it
> > is much too small to hold the kernel+initrd. these files are only a
> > few MB, but can't even fit 1 MB into 191.
> >
> > i don't want to format 150/151/200 since they have our data. i don't
> > think i can reconfigure 160 temporarily. all the rest are read-only.
> >
> > any suggestions ? if there was a way i could ftp (or send file from
> > x3270) directly into the spool, that seems ideal as i could then ipl
> > straight out of it.
> > -mike
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
