Hello.
The zipl.conf do not take the parameter as disk. You should give the
parameter as dasd=302 instead of disk=302. You zipl.conf should look
like the following if your dasd module is kernel inbuilt.
[defaultboot]
default=linux
target=/boot/
[linux]
image=/boot/vmlinuz-2.6.9-55.EL
ramdisk=/boot/initrd-2.6.9-55.EL.img
parameters="root=LABEL=/ dasd=302"
In redhat the dasd module is a loadable module. do you have to put the
dasd reference in /etc/modprobe.conf as following
options dasd_mod dasd=<root-dasd>,302
and build initrd in /boot again and run zipl -V to activate the dasd.
This should work.
On Wed, 2007-07-18 at 10:00 -0500, John White wrote:
> The following is the contents of our /etc/zipl.conf.
>
> [EMAIL PROTECTED] network-scripts]# cat /etc/zipl.conf
> [defaultboot]
> default=linux
> target=/boot/
> [linux]
> image=/boot/vmlinuz-2.6.9-55.EL
> ramdisk=/boot/initrd-2.6.9-55.EL.img
> parameters="root=LABEL=/"
>
> According to (http://www.linuxvm.com/vdskdoit.html) We're supposed to
> add the disk to the Linux Boot Parameter file, 'i.e. disk=302' in our
> case. I added it as, "parameters="root=LABEL=/ disk=302" and it did not
> make a difference. When I do a listing of /dev/dasd* there does not
> show a corresponding device to run a 'mkswap' or 'mke2fs' command
> against.
>
> The 302 disk is CMS FORMAT'ted.
>
> John
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Rick Troth
> Sent: Wednesday, July 18, 2007 5:37 AM
> To: [email protected]
> Subject: Re: RedHat ES 4 using VDISK
>
> On Wed, 18 Jul 2007, Srinivasa R Chamarthy wrote:
> > Can you let me know what is your /etc/zipl.conf ? And also let me know
>
> > if you are using a CMS formatted disk. If it is a CMS formatted disk
> > then you can not put swap to it. and also give me the output for
> > lsdasd. It would help me in debugging.
>
> Not exactly.
>
> Just for clarification,
> CMS FORMAT does two things: low-level format (akin to 'dasdfmt') and
> high-level format (akin to 'mke2fs'). If the disk is FBA or VDSK then
> CMS FORMAT silently skips the low-level formatting operation.
>
> In general, FBA and VDSK should be usable immediately without CMS
> FORMAT (and without 'dasdfmt'). You can simply 'mkswap'
> or 'mke2fs' and use the whole disk. If you need partitioning, the story
> changes. And if you use 'dasdfmt -l cdl' the waters get even murkier
> w/r/t using "the whole disk".
>
> But the low-level half of the CMS FORMAT operation is essential prior to
> using CKD disks, unless one runs 'dasdfmt' in Linux.
>
> *** summary ***
>
> CKD or ECKD -- require low-level formatting
>
> FBA, VDSK, SAN -- do not require low-level formatting
>
> CMS FORMAT -- performs low-level and high-level formatting
>
> 'mkswap' -- performs high-level formatting for swap space and
> can be run even if the disk was CMS FORMATted
>
> 'mke2fs' -- performs high-level formatting for a filesystem and
> can be run even if the disk was CMS FORMATted
>
> Partitioning schemes may throw-off the latter two.
>
> -- 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 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
