Ron, I only included this: INITRD_MODULES="jbd ext3 dasd_diag_mod"
The other two appear by default through some other config. Dasd_diag_mod loads first according to the console log, but dasd_fba_mod loads just before it creates the swap disks. Maybe I'll try specifying all the drivers. I'm trying to minimize the number and extent of config changes, since I want the Linux images to stay as 'plain vanilla' as possible to reduce future headaches for myself or whoever ends up working on them. Log extract: Creating devices 09:20:24 Loading dasd_mod Loading dasd_diag_mod Loading dasd_eckd_mod dasd(eckd): 0.0.0103: 3390/0C(CU:3990/01) Cyl:10016 Head:15 Sec:224 dasd(eckd): 0.0.0103: (4kB blks): 7211520kB at 48kB/trk compatible disk layout dasdd:VOL1/ 0X0109: 09:20:24 dasdd1 dasdd2 dasd(eckd): 0.0.0100: 3390/0C(CU:3990/01) Cyl:6677 Head:15 Sec:224 dasd(eckd): 0.0.0100: (4kB blks): 4807440kB at 48kB/trk compatible disk layout dasda:VOL1/ 0X0108: dasda1 09:20:24 dasd(eckd): 0.0.0101: 3390/0C(CU:3990/01) Cyl:3338 Head:15 Sec:224 dasd(eckd): 0.0.0101: (4kB blks): 2403360kB at 48kB/trk compatible disk layout dasdb:VOL1/ 0X0101: dasdb1 dasd(eckd): 0.0.0104: 3390/0C(CU:3990/01) Cyl:20 Head:15 Sec:224 dasd(eckd): 0.0.0104: (4kB blks): 14400kB at 48kB/trk compatible disk layout dasde:VOL1/ 0X0104: dasde1 09:20:24 dasd(eckd): 0.0.0102: 3390/0C(CU:3990/01) Cyl:1669 Head:15 Sec:224 dasd(eckd): 0.0.0102: (4kB blks): 1201680kB at 48kB/trk compatible disk layout dasdc:VOL1/ 0X0102: dasdc1 Loading dasd_fba_mod 09:20:24 dasd(fba): 0.0.0105: 9336/10(CU:6310/80) 122MB at(512 B/blk) dasdf:CMS1/ LXSWAP(MDSK): dasdf1 dasd(fba): 0.0.0106: 9336/10(CU:6310/80) 244MB at(512 B/blk) dasdg:CMS1/ LXSWAP(MDSK): dasdg1 dasd(fba): 0.0.0107: 9336/10(CU:6310/80) 366MB at(512 B/blk) dasdh:CMS1/ LXSWAP(MDSK): dasdh1 I'll also try to reactivate the vdisk with the diag option, once I track down the commands for that. Ray -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Ron Foster at Baldor-IS Sent: Wednesday, July 29, 2009 11:15 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Dasd_diag_mod question Ray, When you include dasd_diag_mod in the kernel configuration, did you put the dasd drivers in the correct order? Ours is: INITRD_MODULES="reiserfs dm_mod dasd_diag_mod dasd_eckd_mod dasd_fba_mod" If dasd_fba_mod is first, then the vdisk will always be detected at bootup as fba. Once upon a time, it was also necessary to include the diag information in zipl.conf. dasd=0100,0102-0105,106-107(diag) This was set up some time ago. Since we have gone to SLES10 SP2, I have not tried booting one of our vdisk systems without the diag parameter. Ron ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
