Mark,
I have a 200, 201, 203, 204.  200 is /, 201 is swap, 203 is /usr and 204 is
/home.
df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/dasda1             348608     65644    264972  20% /
/dev/dasde1            1417240    884300    460948  66% /usr
/dev/dasdd1              69640       132     65916   1% /home
[root@vmlinuxg2 root]#

 cat /proc/dasd/devices
cat /proc/dasd/devices
0200(ECKD) at ( 94:  0) is dasda      : active at blocksize: 4096, 90000
blocks,
 351 MB
0201(FBA ) at ( 94:  4) is dasdb      : active at blocksize: 512, 20480
blocks,
10 MB
0202(none) at ( 94:  8) is dasdc      : unknown
0203(ECKD) at ( 94: 12) is dasdd      : active at blocksize: 4096, 18000
blocks,
 70 MB
0204(ECKD) at ( 94: 16) is dasde      : active at blocksize: 4096, 360000
blocks
, 1406 MB
[root@vmlinuxg2 root]#
cat /etc/zipl.conf
[defaultboot]
default=linux
[linux]
        target=/boot/
        image=/boot/vmlinuz-2.4.9-37
        parameters="root=/dev/dasda1  dasd=200-204,300-302,400-405"

[root@vmlinuxg2 root]#

 CP Q V DA
DASD 0190 3390 430RES R/O        107 CYL ON DASD  3662 SUBCHANNEL = 0006
DASD 0191 3390 VM365E R/O          1 CYL ON DASD  365E SUBCHANNEL = 0007
DASD 019D 3390 430RES R/O        102 CYL ON DASD  3662 SUBCHANNEL = 0005
DASD 019E 3390 430RES R/O        175 CYL ON DASD  3662 SUBCHANNEL = 0004
DASD 0200 3390 LX1026 R/W        500 CYL ON DASD  1026 SUBCHANNEL = 0008
DASD 0201 9336 (VDSK) R/W      20480 BLK ON DASD  VDSK SUBCHANNEL = 0018
DASD 0203 3390 LX1206 R/W        100 CYL ON DASD  1206 SUBCHANNEL = 0009
DASD 0204 3390 LX1206 R/W       2000 CYL ON DASD  1206 SUBCHANNEL = 000A
DASD 0300 3390 LX100B R/W       1000 CYL ON DASD  100B SUBCHANNEL = 000B
DASD 0301 3390 LX1110 R/W       1000 CYL ON DASD  1110 SUBCHANNEL = 000C
DASD 0302 3390 LX112F R/W       1000 CYL ON DASD  112F SUBCHANNEL = 000D
DASD 0400 3390 LX100B R/W       1000 CYL ON DASD  100B SUBCHANNEL = 000E
DASD 0401 3390 LX1110 R/W       1000 CYL ON DASD  1110 SUBCHANNEL = 000F
DASD 0402 3390 LX112F R/W       1000 CYL ON DASD  112F SUBCHANNEL = 0010
DASD 0403 3390 LX120A R/W       1000 CYL ON DASD  120A SUBCHANNEL = 0011
DASD 0404 3390 LX120A R/W       1000 CYL ON DASD  120A SUBCHANNEL = 0012
DASD 0405 3390 LX120A R/W       1000 CYL ON DASD  120A SUBCHANNEL = 0013
DASD 0592 3390 430W01 R/O         67 CYL ON DASD  3663 SUBCHANNEL = 0014

Thanks for any insight you may have on this.



Betsie Spann
VM Systems Programmer
----- Original Message -----
From: "Post, Mark K" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 01, 2002 5:40 PM
Subject: Re: zipl question


> Betsie,
>
> That was just a test to make sure zipl wasn't picking up parameters from
> somewhere else.  It apparently is not, so you can rename it back.
>
> I guess I'd still like to know... are you sure you are booting from the
same
> DASD volume as /boot is on?  What does a "df" command show, as well as
"cat
> /proc/dasd/devices" and what is in your /etc/zipl.conf?
>
> Mark Post
>
> -----Original Message-----
> From: Betsie Spann [mailto:betsie.spann@;oracle.com]
> Sent: Friday, November 01, 2002 6:18 PM
> To: [EMAIL PROTECTED]
> Subject: Re: zipl question
>
>
> Mark,
> I renamed /etc/zipl.conf and got an error message telling me that it could
> not access configuration file /etc/zipl.conf  and that a target directory
> was not specified on the command line or in a config file.
> I added 'noinitrd' to the parm file but it made no difference.
> Does this have anything to do with the s390-tools or s390-utils?
>
> Betsie Spann
> VM Systems Programmer
> ----- Original Message -----
> From: "Post, Mark K" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, November 01, 2002 1:22 PM
> Subject: Re: zipl question
>
>
> > Betsie,
> >
> > Try renaming /etc/zipl.conf to something else and see what happens when
> you
> > run the command.
> >
> > Also, are you booting from the same DASD volume as /boot is on?
> >
> > Mark Post
> >
> > -----Original Message-----
> > From: Betsie Spann [mailto:betsie.spann@;oracle.com]
> > Sent: Friday, November 01, 2002 3:56 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: zipl question
> >
> >
> > 'strace zipl.conf'  gave me strace: zipl.conf:  command not found
> > when I did, "strace /sbin/zipl", I got a display similar to yours.  It
> > pointed to /etc/zipl.conf and /boot/parmfile.  Both had the same "dasd="
> > string but neither matched the dasd used in the "Kernel command line"
> shown
> > at boot time or from dmesg.
> >
> > Betsie Spann
> > VM Systems Programmer
> > ----- Original Message -----
> > From: "Post, Mark K" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, November 01, 2002 12:48 PM
> > Subject: Re: zipl question
> >
> >
> > > Not at all.  It shows me what files are accessed, etc., etc.  Works
> great
> > > for the intended purpose.
> > >
> > > Mark Post
> > >
> > > -----Original Message-----
> > > From: John Summerfield [mailto:summer@;computerdatasafe.com.au]
> > > Sent: Friday, November 01, 2002 3:39 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: zipl question
> > >
> > >
> > > On Fri, 1 Nov 2002, Post, Mark K wrote:
> > >
> > > > Betsie,
> > > >
> > > > When I do an "strace zipl.conf" on my Red Hat 7.2 system, it reads
> > > > /etc/zipl.conf:
> > >
> > > I've used strace quite a bit, but I never thought tu use it
> > > just like that!
> > >
> > > I'm sure you mean something else.
> > >
> > >
> > > --
> > >
> > >
> > > Cheers
> > > John.
> > >
> > > Please, no off-list mail. You will fall foul of my spam treatment.
> > > Join the "Linux Support by Small Businesses" list at
> > > http://mail.computerdatasafe.com.au/mailman/listinfo/lssb
> > >
> >
>

Reply via email to