Pretty bizarre.  Glad it's going better now.

Mark Post

-----Original Message-----
From: Hall, Jammie [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 17, 2002 10:13 AM
To: [EMAIL PROTECTED]
Subject: Re: format dasd install suse


After doing some checking at the console yesterday and today (no errors
reported), I started another telnet session this am, checked using 'top'
command and dasdfmt showed up as PID 112 but was not using any CPU. I
then went to my previous telnet session that started the dasdfmt and hit
enter three times. I then went back to the 'top' session and what do you
know PID 112 was getting 94.7% CPU and was running. Very baffling. It is
still going strong. Thanks for your input. I'll be back with more
questions I know.
J-me



                -----Original Message-----
                From:   Post, Mark K
                Sent:   Thursday, January 17, 2002 8:59 AM
                To:     [EMAIL PROTECTED]
                Subject:             Re: format dasd install suse

                Except he's not running under VM, so that's out.  What
bothers me is that he
                says he has a command prompt waiting for him, #:, but
apparently dasdfmt
                didn't output any messages.

                Jammie, you should be able to use the HMC to see what
kind of I/O is going
                on in that LPAR.  If the dasdfmt is still running (and I
agree with Mike
                that it should have ended a long time ago) then you
should be seeing a _lot_
                of activity on that channel(s).  If you're not seeing
that, then try issuing
                _any_ command, such as "ls" or "ps -ax" and see if
anything comes back.

                Mark Post

                -----Original Message-----
                From: Coffin Michael C [mailto:[EMAIL PROTECTED]]
                Sent: Thursday, January 17, 2002 9:40 AM
                To: [EMAIL PROTECTED]
                Subject: Re: format dasd install suse


                Even if you're only getting the left over cycles in your
LPAR, that 2Gig
                format should have finished a long time ago (probably
less than an hour to
                format that disk).  Go to the virtual machine console
for your Linux390
                machine and see if there are any errors being reported.
If you are running
                disconnected, spool your console and close it so that
you can see any errors
                (suggest you keep the console open until your system is
built, some messages
                will only appear on the system console and the telnet
session running YaST
                will show you nothing).

                Michael Coffin, VM Systems Programmer
                Internal Revenue Service - Room 6030
                1111 Constitution Avenue, N.W.
                Washington, D.C.  20224

                Voice: (202) 927-4188   FAX:  (202) 622-6726
                [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>



                -----Original Message-----
                From: Hall, Jammie [mailto:[EMAIL PROTECTED]]
                Sent: Thursday, January 17, 2002 9:24 AM
                To: [EMAIL PROTECTED]
                Subject: format dasd install suse


                New to Linux s/390. Installing SuSE 7.3. I have
downloaded the proper
                files tapeipl.img, parmfile, initrd and put on tape. I
have started the
                boot from tape process and finally got to the format
DASD step. I have
                2GB DASD to format and it has been running since 11:30
1/16. Taking
                5-10% CPU. CPU 2003-135 allocated 1CPU and 48 mb to this
LPAR. How will
                this format process last? Is there a way I can tell
what, if anything,
                is going on from the console? I have a #: so I know I
can enter a
                command. Just not sure what command.

Reply via email to