Mark, thanks. Taking the CMS RESERVE out did the trick. Now since I am a novice, my intentions are to have a /boot partition, a /, and put everything else in a LVM group. Can you point me in the right direction as to how to do this?
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Post, Mark K Sent: Thursday, February 17, 2005 12:05 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Slackware S390 formatting dasd If you CMS format and reserve them, the DIAG driver picks them up (or FBA if you load that first), not the ECKD driver. Leave off the reserve step, and they'll get picked up by the ECKD driver. The "detected" bit looks a lot to me like the insmod abend problem I described earlier. Spool your console and look through it carefully. I'll bet you find something in it. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Imholte, John (Cincinnati, OH) Sent: Thursday, February 17, 2005 11:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Slackware S390 formatting dasd This is what I receive now... cat /proc/dasd/devices cat /proc/dasd/devices 0151(DIAG) at ( 94: 0) is dasda : active at blocksize: 4096, 18000 blocks, 70 MB 0152(ECKD) at ( 94: 4) is dasdb : detected 0153(DIAG) at ( 94: 8) is dasdc : active at blocksize: 4096, 400500 blocks , 1564 MB 0154(ECKD) at ( 94: 12) is dasdd : detected 0155(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 400500 blocks , 1564 MB 0140(FBA ) at ( 94: 20) is dasdf : active at blocksize: 512, 144000 blocks, 70 MB Am I wrong in assuming that they all should be active and not DIAG? I did a CPVOL format, CMS format, CMS reserve, is this correct? BTW: Mark I tried the new initrd.gz that you posted and it worked fine, thanks. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Imholte, John (Cincinnati, OH) Sent: Thursday, February 17, 2005 10:03 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Slackware S390 formatting dasd I am in the process of trying what Michael suggested. >From all indications this should work.. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Post, Mark K Sent: Thursday, February 17, 2005 9:58 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Slackware S390 formatting dasd John, One of the annoying little(?) bugs that pops up on a regular occasion is that when the installation system is loading the DASD driver, insmod takes an error and dies midway through. It usually gets reported as being rmmod.old and not insmod, though. Usually, just rebooting again (or again or again) gets you past it. The fact that simply retrying works always annoys (and worries) me, but I haven't been able to figure out why it happens. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Imholte, John (Cincinnati, OH) Sent: Thursday, February 17, 2005 9:26 AM To: LINUX-390@VM.MARIST.EDU Subject: Slackware S390 formatting dasd I am using the command dasdfmt -b 4096 -y -f /dev/dasda to attempt to format the DASD. I have 151-155 3390 disk attached as MDISK. 151 is 100 cylinders to be used as the /boot. The other 4 are mod2 MDISK 152 3390 0001 2225. I get several error messages when attempting this, but the really odd thing is that the last DASD is OK and I can format it and partition it also. So what's the difference? Well I had Suse 8 installed once on them except for DASDE, 155. I have tried everything except doing a ICKDSF CP format. Is this what is needed? dasdfmt -b 4096 -y -f /dev/dasda " dasdfmt: Unable to open device /dev/dasda: No such device" dasdfmt -b 4096 -y -f /dev/dasdb" dasdfmt: Unsupported disk type" /dev/dasdb is not an ECKD disk!" Sincerely, John Imholte Unisource Worldwide 513-752-1660 ext. 222 - - - - - Work 513-368-3682 - - - - - - - - - - - Cell 513-943-2755 - - - - - - - - - - - FAX Personal Email: unwind at fuse.net Work Email: imholj01 at unisourcelink.com ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
