It's been quite a while since I did an actual SLES9 installation. But, I seem to recall that you need to run dasdfmt and fdasd "outside" of YaST before trying to get it to use the DASD on a system.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Stuart Sent: Tuesday, November 07, 2006 5:16 PM To: [email protected] Subject: SLES 9 Install Assistance - Missing DASD Good afternoon, I am new to this list, but I am hoping someone can help solve my problem, or give me some pointers. I am trying to install SLES 9 SP 3 into an LPAR (no VM) on a 9672-RA6 (G5 System). I can boot successfully from the CD in the HMC, and can configure the OSA card, and load the Install System from a FTP Server. Once that has loaded, I am able to ssh -X into the System, and sign on a root using the 'install' password. And then successfully start yast. The problem is that in yast, after selecting the Configure DASD, and after the install system says that it is analyzing the system, probing the disk controller, etc., it indicates there are no DASD available on the system. If I cancel out of the DASD Configuration, the install system goes through its system analysis, probing of disk controllers, etc. again, and messages are issued to the HMC Integrated Console that appear to me to indicate that the install system *has* communicated with the disk controllers. These messages include throughput in MB/Sec for several different configurations, and the final selection. However, when trying to go back through yast to configure/partition the DASD, it still indicates there are no DASD volumes available. DASD are 16 volumes of 3390-3 (ECKD) running on a 9393-T82 RAMAC Virtual Array. The 9393 is Escon attached to the 9672, and there are 8 Escon paths available. The 16 volumes were isolated to this LPAR via IOCP. I have verified that the 16 volumes are *not* available to the other 4 LPARs on the system. However, I have not yet been able to verify that the 16 volumes *are* available to the Linux LPAR, although they should be. Short of deactivating the LPAR, reactivating in S/390 mode, and using Stand Alone Utilities, I have not yet found a way to verify the DASD. I have been working with a pre-sales engineer from Novell, and I have him, stumped, too. We have tried various flavors of the insmod command, with various dasd option, with no results. Updated the boot-time parm file with a DASD= parameter, but it also failed. I am stumped. Any suggestions gratefully received. TIA, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA ---------------------------------------------------------------------- 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
