We figured it out. Didn't run fdasd after the dasdfmt command. Jason
-----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 14, 2002 2:53 PM To: [EMAIL PROTECTED] Subject: Re: SuSe Install dasd problem Jason, I would say that there is a bug in the YaST code to display the number of blocks. Have you tried to proceed anyway, to see what happens? Mark Post -----Original Message----- From: Galecki, Jason [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 14, 2002 2:18 PM To: [EMAIL PROTECTED] Subject: SuSe Install dasd problem We have z/VM running with dasd assigned to a "guest" (SuSe 2.4.7). This is our first install during our companies trial period. The problem we are having is when I run the command below: SuSE Instsys ZSUSE001:/etc # cat /proc/dasd/devices 0200(ECKD) at ( 94: 0) is dasda:active at blocksize: 4096, 597240 blocks, 2332 MB 0201(ECKD) at ( 94: 4) is dasdb:active at blocksize: 4096, 36000 blocks, 140 MB This is good, but when I run Yast, I then go to the create swap screen, it shows the Blocks for each disk at 0. In the instructions we have it always shows the blocks as the number, i.e. 597240 blocks, like on page 60 of the Installing SuSe on s390 manual we have. Does anyone have any thought as to why this may not be seen correctly by Yast? I did do the dasdfmt -f /dev/dasda -b 4096, and also didn't do the format, which we were going to let SuSe do it. Jason
