On 04/13/2015 11:49 AM, de Wet, Albertus H wrote: > I installed Redhat(R7.1) and SUSE(R12.0) onto to different DASD's in LPAR > mode. > I can IPL from these volumes and access the systems. This is in LPAR mode > (Not z/VM)
Level set. Good. So we know that works. > I want to install another Redhat image to a few DASD 3390-3 devices > (better selection of applications) - but I cannot get new DASD devices online, > from either REDHAT or SUSE. Are you working with the (new) DASD in a prior LPAR or in the new LPAR? (Forgive me, some of below leads me to ask.) > I tried chccwdev -e 0.0.newdev > I get "Device 0.0.newdev not found" > > I tried dasd_configure 0.0.newdev > I get "No device 0.0.newdev" What I don't follow is: are you running 'chccwdev' and 'dasd_configure' from an existing Linux LPAR or from the new one? (ie: using the installation shell. Dracut below suggests this, which is fine.) I would recommend formatting the new DASD from a fully operational Linux (LPAR or virtual). Get the 'dasdfmt' part out of the way. This is from personal experience. Mark and Danny and others will chime in with more details about how to get it working with only the installation shell. If you're going to install a new system, you would then bring them online to the target LPAR. You might need to explicitly bring them offline from the first LPAR. (Personally, I'm used to shared disks, on any HW. But there are risks and challenges.) > How do I add any new DASD device to a LINUX distribution, running in LPAR > mode? You need to get them online (chccwdev). If you want to use them on that LPAR, then you need to get them configured (dasd_config), and be sure they "stick" (historically 'mkinitrd' followed by 'zipl'). For SUSE, 'yast' is your safest route for getting the new disks to come online after reboot. > I want to format a few devices so that I can install Redhat again, but when I > specify the 'unformatted device' 0.0.newdev, I get an I/O error and end up in > a Dracut# prompt. It may help to have something cloneable. For native (LPAR) Linux, you would run stand-alone DDR to copy the system disk. 'dasdfmt' followed by 'fdasd' will perform the CDL magic needed, but you cannot (last I tried) 'dd' such a disk (like you can with other Unix/Linux, or like you could when S/390 was LDL). Then be sure to change essential configuration (IP address at least). It certainly helps, if you go the cloning route, to have things at the same I/O addresses (disk, OSA). (Of course, the IP address will change.) I'm a little suspicious about either your IOCDS (for either LPAR) or device contention (are these disks visible elsewhere?). In any case, you clearly got through the installation once. So don't give up hope. This *will* work. -- R; <>< ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
