"You'll then also need the other volumes, probably also at their prior subchannel addresses. (I/O addresses are not necessarily cast in stone, but you don't know at this point.)"
In my experience, the important address to get correct is the IPL volume. That address appears to be baked into the initrd. We use lvm here, so if all the lvm volumes are there accessible to the lpar, lvm will find them regardless of the address. You can run without swap volumes long enough to fix them. If you are lucky, then the system will come up in full muti-user mode. If not.. Then if "/" gets mounted, then you have access to commands that would be useful to fix the situation. (Just for such emergencies, we leave a specially named fstab in /etc that mounts a minimum number of filesystems. We put that fstab in place and see if the boot gets a little farther.) One of the key things if you get far enough is to see how the fstab is constructed. There are several types of mounts. Some require the volumes to have a certain address. Some might be tied to the storage controller in use. Some might require certain subchannel addresses. If you get into multi-user mode, but without a network adapter that works, then you hope that that the inittab has the entry in it that lets you access the emulated ascii terminal on the HMC. How good is the documentation concerning these systems. Did someone turn on sitar or something like it to produce documentation. Do you still have it somewhere? If so, then it should be easier to match the environment that this image is expecting. How about DR documentation? If someone saved the image, they might have also saved the recovery documentation. BTW, I am a SLES person, I don't know if Red Hat works the same way. Good luck, Ron ________________________________________ From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Richard Troth [vmcow...@gmail.com] Sent: Thursday, November 03, 2011 1:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Accessing Old Linux System After DASD Move First, let's hope these old Linux systems used EXT2 (or EXT3, which is compatible), if you need to read the content. Linux supports a wide range of filesystem types. USS will not be able to use the Linux volumes ... at all. z/OS *may* be able to read the "partitions" on the Linux volumes (usually just one per). This magic requires that Linux had been using CDL, the "compatible disk layout". The partitions should then be usable on any other Linux system: z, PC, even things like PowerMac. Other filesystem types (besides EXT2 or EXT3) will be usable by such other Linux systems, no problem. You could read the partitions (as RECFM=U datasets), copy the content (as binary) to a working Linux system (any HW) and do what we call a loop-back mount. You can probably recover all the content that way, and it would let you engage one of your Linux people to help snoop around. There is a tool for CMS to read EXT2 filesystems. Do you have VM in-house? That's for scanning. But you said you have been asked to bring them up. How did they run? (Rhetorical: you said LPAR.) Start with just one. (dunno how many Linux images you have, if LPAR then maybe only ever just one) To make it bootable, you'll need the boot vol at whatever address it was before. You'll then also need the other volumes, probably also at their prior subchannel addresses. (I/O addresses are not necessarily cast in stone, but you don't know at this point.) Once all the DASD are arranged at their prior addresses, you should be able to point-n-shoot. Other failures might not stop the boot sequence. (Like network interface missing or at a different addr.) But filesystems get usually get checked. So ... where are you at after all that? -- R; <>< Rick Troth Velocity Software http://www.velocitysoftware.com/ On Thu, Nov 3, 2011 at 13:47, Craig Pace <cp...@fruit.com> wrote: > List, > > I have been doing some reading, scanning and searching and have come to > many different answers and was wondering if someone might have some > suggestions on this item. We have an old Linux environment. I am not > sure how old it is; however, I know it is between 2 & 3 years at least. > The system (Linux on System z - LPAR Mode) was not active and had the DASD > (ECKD format) moved from one storage sub-system to another with now > different UCBs. I have been asked to look into bring up this system. Is > there any "easy" way to access the data to update the required > configuration to now point to the correct UCB addresses? At this point, > we only have z/OS LPARs running in the environment with no other Linux. I > was hoping that I might be able to do something with USS; however, he does > not know about the "formatted" filesystems that was built by Linux-390. > > > > Thanks, > > Craig Pace > Lead z/OS Systems Programmer > Fruit of the Loom, Inc.® > > Office: (270) 781-6400 ext. 4397 > Cell: (270) 991-7452 > Fax: (270) 438-4430 > E-mail: cp...@fruit.com > > One Fruit of the Loom Drive > PO Box 90015 > Bowling Green, KY 42102-9015 > > ********************************************************************** > This communication contains information which is confidential and > may also be privileged. It is for the exclusive use of the intended > recipient(s). If you are not the intended recipient(s), please note > that any distribution, copying or use of this communication or the > information in it is strictly prohibited. If you have received this > communication in error, please notify the sender immediately and > then destroy any copies of it. > ********************************************************************** > > ---------------------------------------------------------------------- > 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/
