OK, I got it !! Thank you all guys. This is the fix to this problem ===============================
I had defined the VM Directory minidisks using decimal notation (...8, 9, 10, 11, etc.) instead of hexadecimal (...8, 9, A, B...). And in zipl.conf I used the range 503-563 but zipl expected an hexadecimal notation, so there were missing ranges (50A-50F, etc.) So the problem has two possible solutions: - Either modify the VM directory using correlative hexadecimal addresses for the minidisks (this is the fastest and easiest way) - or modify zipl.conf like this: 503-509,510-519,520-529,530-539,540-549,550-559,560-563 (which certainly isn't so fast and rather unconfortable). I hope this may help if any of you faces this problem in the future. Again thanks a lot for your inspiration. :-) Saludos, Best Regards José R. Barón Dpto. Sistemas CALCULO S. A. Tel. 91 330 86 44 e-mail: [EMAIL PROTECTED] -----Mensaje original----- De: Spann, Elizebeth (Betsie) [mailto:[EMAIL PROTECTED] Enviado el: jueves, 11 de enero de 2007 19:08 Para: José Raúl Barón Rodriguez Asunto: RE: LVM filesystem definition / creation problem Minidisk addresses 50a-50f are missing. You must have defined ..508, 509, 510 instead of ...508, 509, 50a, etc. Betsie -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jose Raul Baron Sent: Thursday, January 11, 2007 10:04 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM filesystem definition / creation problem What I have seen to my surprise is that there are kind of "leaps" in /proc/dasd/devices. Allow me explain it: cat /proc/dasd/devices cat /proc/dasd/devices 0.0.0150(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 60066 0 blocks, 2346 MB 0.0.0151(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 60066 0 blocks, 2346 MB 0.0.0503(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 60066 0 blocks, 2346 MB 0.0.0504(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 60066 0 blocks, 2346 MB 0.0.0505(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 60066 0 blocks, 2346 MB 0.0.0506(ECKD) at ( 94: 20) is dasdf : active at blocksize: 4096, 60066 0 blocks, 2346 MB 0.0.0507(ECKD) at ( 94: 24) is dasdg : active at blocksize: 4096, 60066 0 blocks, 2346 MB 0.0.0508(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 60066 0 blocks, 2346 MB 0.0.0509(ECKD) at ( 94: 32) is dasdi : active at blocksize: 4096, 60066 0 blocks, 2346 MB (there are no dasdj......dasdo now. There were before but not any longer) 0.0.0510(ECKD) at ( 94: 60) is dasdp : active at blocksize: 4096, 60066 0 blocks, 2346 MB Saludos, José R. Barón Dpto. Sistemas CALCULO S. A. Tel. 91 330 86 44 e-mail: [EMAIL PROTECTED] -----Mensaje original----- De: Linux on 390 Port [mailto:[EMAIL PROTECTED] En nombre de Post, Mark K Enviado el: jueves, 11 de enero de 2007 18:59 Para: LINUX-390@VM.MARIST.EDU Asunto: Re: LVM filesystem definition / creation problem Check /proc/dasd/devices to see if they're listed there. If they're not, then you'll probably need to look at your initrd to see if they're listed there, and fix it if they're not. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jose Raul Baron Sent: Thursday, January 11, 2007 12:54 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM filesystem definition / creation problem First of all thank you all for your quick answers. I will try to answer your questions now: - I used yast2 to activate the dasd. It worked fine. - This is exactly what I changed in /etc/zipl.conf: (added 503-563 dasd interval) parameters = "dasd=150-151,503-563 root=/dev/dasdb1 selinux=0 TERM=dumb elevator=cfq" - Yes, I ran zipl after modifying zipl.conf - pvscan ran cleanly before re-ipling the system. - all the filesystems were mounted correctly before re-ipling. Saludos / BRGDS José R. Barón Dpto. Sistemas CALCULO S. A. Tel. 91 330 86 44 e-mail: [EMAIL PROTECTED] ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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