Well, this is what I finally tried:

SuSE Instsys linuxlpar:/root # ls
SuSE Instsys linuxlpar:/root # rmmod dasd
rmmod: module dasd is not loaded
SuSE Instsys linuxlpar:/root # insmod dasd dasd=4c0
Using /lib/modules/2.2.16/block/dasd.o
SuSE Instsys linuxlpar:/root # dasdfmt -n 4c0 -b 4096

Now my session just sits there doing nothing for hours !!!

I guess this is progress ??
Ken Dreger




At 04:17 PM 2/1/2002, Post, Mark K wrote:
>Actually, there is help: dasdfmt -help
>Try doing the dasdfmt this way:
>dasdfmt -b 4096 -n 04c0
>
>Hint: the order of the parameters is important.
>
>The other way to do it would be:
>dasdfmt -b 4096 -f /dev/dasda
>dasdfmt -b 4096 -f /dev/dasdb
>etc.
>
>The way to check to make sure your DASD devices were recognized properly is
>to do this:
>cat /proc/dasd/devices
>
>You should see something like this:
>010F(ECKD) at (94:0) is   dasda:active  at blocksize: 4096, 57600 blocks,
>225 MB
>0100(ECKD) at (94:4) is   dasdb:active  at blocksize: 4096, 13500 blocks, 52
>MB
>0106(ECKD) at (94:8) is   dasdc:active  at blocksize: 4096, 270000 blocks,
>1054 MB
>0107(ECKD) at (94:12) is   dasdd:active  at blocksize: 4096, 360000 blocks,
>1406 MB
>
>Mark Post
>
>-----Original Message-----
>From: Ken Dreger: Dr. "D" [mailto:[EMAIL PROTECTED]]
>Sent: Friday, February 01, 2002 7:02 PM
>To: [EMAIL PROTECTED]
>Subject: Re: SUSE install on a OS/390 LPAR
>
>
>Here is what shows up:
>
>SuSE Instsys linuxlpar:/root # insmod dasd probeonly
>Using /lib/modules/2.2.16/block/dasd.o
>insmod: a module named dasd already exists
>SuSE Instsys linuxlpar:/root # rmmod dasd
>SuSE Instsys linuxlpar:/root # insmod dasd dasd=4c0-4c4
>Using /lib/modules/2.2.16/block/dasd.o
>SuSE Instsys linuxlpar:/root #
>
>so I also tried this:
>SuSE Instsys linuxlpar:/root # insmod dasd probeonly
>Using /lib/modules/2.2.16/block/dasd.o
>insmod: a module named dasd already exists
>SuSE Instsys linuxlpar:/root # rmmod dasd
>
>SuSE Instsys linuxlpar:/root # insmod dasd dasd=4c0-4c4
>Using /lib/modules/2.2.16/block/dasd.o
>
>   Then I tried this:
>
>SuSE Instsys linuxlpar:/root # rmmod dasd
>SuSE Instsys linuxlpar:/root # insmod dasd dasd=04c0-04c4
>Using /lib/modules/2.2.16/block/dasd.o
>SuSE Instsys linuxlpar:/root #
>
>
>    Then I tried this...:
>
>SuSE Instsys linuxlpar:/root # insmod dasd
>probeonly
>Using
>/lib/modules/2.2.16/block/dasd.o
>insmod: a module named dasd already
>exists
>SuSE Instsys linuxlpar:/root # rmmod
>dasd
>
>SuSE Instsys linuxlpar:/root # insmod dasd
>dasd=4c0-4c4
>Using /lib/modules/2.2.16/block/dasd.o
>
>Then this one:...
>
>SuSE Instsys linuxlpar:/root # rmmod
>dasd
>SuSE Instsys linuxlpar:/root # insmod dasd
>dasd=04c0-04c4
>Using
>/lib/modules/2.2.16/block/dasd.o
>SuSE Instsys linuxlpar:/root # dasdfmt -n 04c0 -b
>4096
>dasdfmt: failed to find device in the /proc filesystem (are you sure to
>have th)
>SuSE Instsys linuxlpar:/root
>#
>
>Then this one....:
>SuSE Instsys linuxlpar:/root # rmmod
>dasd
>SuSE Instsys linuxlpar:/root # insmod dasd
>dasd=4c0-4c0
>Using
>/lib/modules/2.2.16/block/dasd.o
>SuSE Instsys linuxlpar:/root # dasdfmt -n 4c0 -b
>4096
>dasdfmt: failed to find device in the /proc filesystem (are you sure to
>have th)
>SuSE Instsys linuxlpar:/root
>#
>
>There is no help on the dasdfmt command and it is NOT in my UNIX command
>book I have.
>Any other ideas ????
>thanks
>Ken
>
>
>
>
>At 03:21 PM 2/1/2002, you wrote:
> >What happens with this sequence:
> >insmod dasd probeonly
> >rmmod dasd
> >insmod dasd dasd=4c0-4c4
> >
> > > -----Original Message-----
> > > SuSE Instsys linuxlpar:/root # insmod dasd probeonly
> > > Using /lib/modules/2.2.16/block/dasd.o
> > > SuSE Instsys linuxlpar:/root # insmod dasd 04c0-04c4
> > > Using /lib/modules/2.2.16/block/dasd.o
> > > insmod: a module named dasd already exists
> > > Then I issue the following command:
> > > SuSE Instsys linuxlpar:/root # dasdfmt -n 04c0-04c4 -b 4096
> > > dasdfmt: device number is in invalid format

Reply via email to