On 31 Jan 2022 16:18, Mark Post wrote: > On 1/30/22 01:34, Mike Frysinger wrote: > > 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. > > If you have the kernel and initrd on an FTP server somewhere in your > network, then you might want to try defining a temporary DASD volume, or > a VDISK > > For example: > #cp define t3390 300 200 > or > #cp define vfb-512 300 200000 > > The first command will give you about 140MB of space to work with. The > second command about 195MB. That should be more than enough to hold the > files you need. It could be that your z/VM systems programmer hasn't > defined either TDISK or VDISK space to be used. If not, then ask them to > do so.
the first one failed: 00: CP DEFINE T3390 300 200 00: HCPLNM091E DASD 0300 not defined; temp space not available the second one worked: 00: CP DEFINE VFB-512 300 200000 00: DASD 0300 DEFINED > The CMS FTP client lives on your 592 disk, so you'll need to access that > before trying to download the files. yeah, i was able to ftp files in already, i just ran out of space. that said, i talked to our admin, and they were fine with increasing our normal boot disk. but this temp disk approach is good info, thanks. -mike ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
signature.asc
Description: PGP signature
