Yeah, that was my though also. I just redid those steps with somebody who is a bit familiar with Linux looking over my shoulder. Same results, volume 210 does not come online. I can however use the chccwdev to bring 210 online after the boot.
Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -----Original Message----- From: Stephen Frazier [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2008 1:18 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Having trouble adding a volume The symptoms you describe leads me to believe that you left out a step on the second server. Look at /etc/modprobe.conf on the SECOND server. If it has what you think it should, run mkinitrd on the SECOND server. Then run zipl on the SECOND server. Then reboot. I expect that you will find the problem fixed. Bauer, Bobby (NIH/CIT) [E] wrote: > I'm sure this is a rookie mistake (we are zVM and zLinux rookies). I'm > trying to add a little space to a logical volume on 2 test servers. > Redhat 5.1 running under zVM. I'm using the "z/VM and Linux on IBM > System z: The Virtualization Cookbook for RHEL 5" as my guided. I was > able to extend the logical volume on test server #1 but I can't bring > the volume online to test server #2. I have the following for both > servers, volume 210 was added to each: > > /etc/modprobe.conf: > alias eth0 qeth > options dasd_mod dasd=200-201,210 > > > I run mkinitrd and zipl and reboot. > > On server #1 lsdasd shows: > 0.0.0200(ECKD) at ( 94: 0) is dasda : active at blocksize 4096, > 600840 blocks, 2347 MB > 0.0.0201(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096, > 600840 blocks, 2347 MB > 0.0.0210(ECKD) at ( 94: 8) is dasdc : active at blocksize 4096, > 270000 blocks, 1054 MB > and a vmcp q dasd shows: > DASD 0200 3390 LNX006 R/W 3338 CYL ON DASD 0304 SUBCHANNEL = 0002 > DASD 0201 3390 LNX007 R/W 3338 CYL ON DASD 0604 SUBCHANNEL = 0003 > DASD 0210 3390 LNX008 R/W 1500 CYL ON DASD 0778 SUBCHANNEL = 0004 > > > On server #2 after mkinitrd, zipl and reboot I see: > 0.0.0200(ECKD) at ( 94: 0) is dasda : active at blocksize 4096, > 600840 blocks, 2347 MB > 0.0.0201(ECKD) at ( 94: 4) is dasdb : active at blocksize 4096, > 600840 blocks, 2347 MB > and a vmcp q dasd shows: > DASD 0200 3390 LNX009 R/W 3338 CYL ON DASD 0886 SUBCHANNEL = 0002 > DASD 0201 3390 LNX010 R/W 3338 CYL ON DASD 0326 SUBCHANNEL = 0003 > DASD 0210 3390 LNX008 R/W 1500 CYL ON DASD 0778 SUBCHANNEL = 0004 > > > I don't think the fact that dasd 210 has the same name and dasd number. > Each is defined under VM as different parts of the disk. > > From USER DIRECT, server #1 has > MDISK 210 3390 1 1500 LNX008 MR > > And server #2 has > MDISK 210 3390 1501 1500 LNX008 MR > > I'm at a loss and not sure where to look next. Any suggestions would be > appreciated > > Thanks > > Bobby Bauer > Center for Information Technology > National Institutes of Health > Bethesda, MD 20892-5628 > 301-594-7474 > > > > > ---------------------------------------------------------------------- > 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 -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us ---------------------------------------------------------------------- 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 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
