James, At a guess, it looks as though you did a CMS format and RESERVE on those two minidisks. Correct? If so, that's one possible explanation for the difference. I don't think that will cause you any problems, but it might. I had some bad experiences with the earlier 2.4 DIAG drivers when playing with V-disks and swap disks. Try redoing the CMS formatting, but don't RESERVE it and see if that helps.
As Jim points out, PAV-enabled volumes won't work as _boot_ volumes. You'll need to turn that off for whatever minidisk you'll be booting from (usually your root file system disk). Mark Post -----Original Message----- From: James Peddycord [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 2:45 PM To: [EMAIL PROTECTED] Subject: Problem: DIAG vs ECKD - Yast hangs OOPS! My previous post had no subject. I apologize, and here goes again. I am running into a problem trying to install SLES7 from scratch. After I boot the ramdisk system, I am able to log on via SSH and do the insmod, then when I do yast it hangs directly after I choose 'English' for the language. My system is a 2064 1C8 IFL running z/VM 4.3. My DASD is a Hitachi 9980V running in 2105 mode with HPAV enabled. As I log on to the instance and do the insmod command, here is what I see in my SSH session: SuSE Instsys GSLP02A:/root # insmod dasd dasd=200,201 Using /lib/modules/2.4.7-SuSE-SMP/kernel/drivers/s390/block/dasd.o On the VM console I see: dasd:initializing... dasd:Registered successfully to major no 94 dasd:initialization finished dasd(diag):DIAG discipline initializing dasd(diag):/dev/dasda (0200): capacity (4kB blks): 108000kB dasd(diag):/dev/dasdb (0201): capacity (4kB blks): 1080000kB Partition check: dasda:<6>dasd(fba):FBA discipline initializing dasd(fba):We are interested in: Dev 9336/00 @ CU 6310/00 dasd(fba):We are interested in: Dev 3370/00 @ CU 3880/00 dasd(eckd):ECKD discipline initializing dasd(eckd):We are interested in: CU 3880/00 dasd(eckd):We are interested in: CU 3990/00 dasd(eckd):We are interested in: CU 2105/00 dasd(eckd):We are interested in: CU 9343/00 CMS1/ LNXSWP(MDSK): dasda dasda1 dasdb:CMS1/ LNX201(MDSK): dasdb dasdb1 I do a "cat /proc/dasd/devices": 0200(DIAG) at ( 94: 0) is dasda:active at blocksize: 4096, 27000 blocks, 105 MB 0201(DIAG) at ( 94: 4) is dasdb:active at blocksize: 4096, 270000 blocks, 1054 MB On my running systems, when I do a "cat /proc/dasd/devices", I see: 0200(ECKD) at ( 94: 0) is dasda:active at blocksize: 4096, 27000 blocks, 105 MB 0201(ECKD) at ( 94: 4) is dasdb:active at blocksize: 4096, 270000 blocks, 1054 MB Anyone have any idea whay the ramdisk install system is using DIAG instead of ECKD? Thanks in advance! Jim
