RE: Installation Question
Steve,
Thanks.
>If I remember right,
>there is an initial screen which displays all the DASD devices it
>recognizes.
Unfortunately the list is empty (recognizes none) and then prompts me to enter an address, which, of course fails.
Thanks again, ..............Larry
-----Original Message-----
From: Stephen Powell [mailto:zlinuxman@wowway.com]
Sent: Wednesday, December 23, 2009 11:41 AM
To: debian-s390@lists.debian.org
Subject: RE: Installation Question
On 2009-12-23, Larry Martin wrote:
> It appears that Debian does not think the disks are usable because
> they are "reachable" from another partition.
> When I did the IOCDS for our machine I actually had the two volumes
> for Linux reachable from four LPARs. One of the four is linux, one
> is inactive, one has the volumes offline, and the last one is a
> coupling facility LPAR.
> Does anyone have an IOCDS that shows 3390's properly defined for Debian?
> Or any other suggestions? The disks are definitely reachable from the
> LPAR into which I am loading Linux.
> Thanks, .........Larry
Larry,
I'm not sure what you mean by "reachable". Do you mean shared? Here
are some excerpts from our IOCP statements for a z890 (2086) with an IBM
DS6800 1750-511 RAID box for our DASD, which is attached to the host via
four FICON chpids. The RAID box defines 512 devices: 6100-61FF and
6300-63FF. 6100-6112 and 6300-6312 (38 devices) are emulated 3390-9
devices. The rest are 3390-3 devices. None of these devices support
PVA. These are IOCP statements generated by HCD/HCM running under z/OS,
which are slightly different in format from the native IOCP format. But
you'll get the idea.
----------
TITLE 'SYS1.IODF01 - 2006-10-10 12:08:22 '
*
ID NAME=DOLC01,UNIT=2086,MODEL=A04,MODE=LPAR,LEVEL=H040331, *
SCR='DOLC01 06-10-1012:08:22SYS*
1 IODF01 '
RESOURCE PARTITION=((CSS(0),(MVSPROD,1),(MVSTECH,3),(MVSTEST,2*
),(ZOSPROD,4),(ZVMPROD,5))),MAXDEV=((CSS(0),64512)), *
DESCL=('MVS PRODUCTION LPAR',' ','MVS TES*
T LPAR',' ',' '),USAGE=(OS,OS,OS,OS,OS)
.
.
.
CHPID PATH=(CSS(0),20),SHARED, *
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=120
CHPID PATH=(CSS(0),21),SHARED, *
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=121
.
.
.
CHPID PATH=(CSS(0),30),SHARED, *
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=130
CHPID PATH=(CSS(0),31),SHARED, *
PARTITION=((MVSPROD,MVSTECH,MVSTEST,ZOSPROD,ZVMPROD),(=)*
),DESC='IBM DS6800 DASD',TYPE=FC,PCHID=131
.
.
.
CNTLUNIT CUNUMBR=6100,PATH=((CSS(0),20,30,21,31)), *
UNITADD=((00,256)),SHARED=N,CUADD=1,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 Control Unit',UNIT=1750
IODEVICE ADDRESS=(6100,256),UNITADD=00,CUNUMBR=(6100),STADET=Y*
,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 mod-9 && mod-3s',UNIT=3390
CNTLUNIT CUNUMBR=6300,PATH=((CSS(0),21,31,20,30)), *
UNITADD=((00,256)),SHARED=N,CUADD=3,SERIAL='13-AFALA', *
DESC='DS6800 1750-511 Control Unit',UNIT=1750
IODEVICE ADDRESS=(6300,256),UNITADD=00,CUNUMBR=(6300),STADET=Y*
,SERIAL='13-AFALA',
DESC='DS6800 1750-511 mod-9 && mod-3s',UNIT=3390
----------
The above IOCP definitions use the ESCON Multi-Image Facility (EMIF)
to allow the DASD devices to be shared by all LPARs. (EMIF works for
FICON as well as ESCON.)
If a normal mainframe operating system, such as z/OS or z/VM, can "see"
the DASD, then Linux should be able to "see" it too. If not, then you're
probably doing something wrong in the installation. If I remember right,
there is an initial screen which displays all the DASD devices it
recognizes. You have to explicitly select all the devices you are going
to use on that screen, though some of them may be pre-selected. Then
there is another screen later on where you can create partitions,
assign mount points, etc. If you don't select the devices on the first
screen, they won't be available on the second screen.
Also, keep in mind that (a) the Debian installer supports only CKD DASD
devices and (b) the Debian installer supports only the cdl format
(compatible disk layout). You said that your devices were 3390s, which
are CKD devices; so that should be OK.
I do all of my Linux installs in a virtual machine under z/VM, not natively
in an LPAR as you are attempting to do; so I don't really know how much
more help I can be if you are running into an LPAR-environment-specific
problem.
Regards,
Steve
--
To UNSUBSCRIBE, email to debian-s390-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
This E-mail and any of its attachments may contain Prince George’s County Government or Prince George's County 7th Judicial Circuit Court proprietary information, which is privileged and confidential. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
Reply to: