cat /proc/dasd/devices


Michael Coffin, VM Systems Programmer 
Internal Revenue Service - Room�6527 
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: James Melin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 12, 2002 2:29 PM
To: [EMAIL PROTECTED]
Subject: Re: Attempting first IPL after initial SuSE install


A thought occurs to me so I ask this... How do I tell what DEVICE
/dev/dasda is associated with?



|---------+---------------------------->
|         |           "Post, Mark K"   |
|         |           <[EMAIL PROTECTED]|
|         |           m>               |
|         |           Sent by: Linux on|
|         |           390 Port         |
|         |           <[EMAIL PROTECTED]|
|         |           IST.EDU>         |
|         |                            |
|         |                            |
|         |           03/11/2002 02:31 |
|         |           PM               |
|         |           Please respond to|
|         |           Linux on 390 Port|
|         |                            |
|---------+---------------------------->
 
>---------------------------------------------------------------------------
-----------------------------------|
  |
|
  |       To:       [EMAIL PROTECTED]
|
  |       cc:
|
  |       Subject:  Re: Attempting first IPL after initial SuSE install
|
 
>---------------------------------------------------------------------------
-----------------------------------|




Jim,

There have been some reports of problems with IPLs after initial installs,
but they were against the Red Hat GA.  What you can do is re-IPL your
installation setup, mount the root file system on /mnt (for instance), then
do a "chroot /mnt".  From there, cd to /boot, and re-run the silo command.
You should see something similar to this, which will indicate success:
Silo:o->image set to /boot/image-2.2.16-122-tape
Silo:o->ipldevice set to /dev/dasda
Silo:o->parmfile set to /boot/par
Silo:o->bootsect set to /boot/ipleckd.boot
Silo:o->Testonly flag is now 0
Silo:o->Testlevel is set to 0
Silo:o->IPL device is:'/dev/dasda '
Silo:o->bootsector is:'/boot/ipleckd.boot '...ok...
Silo:o->bootmap is:'/boot/image-2.2.16-122-tape ' ....ok...
Silo:o->Kernel image is:'/boot/ipleckd.boot ' ....ok...
Silo:o->original parameterfile is:'/boot/parm '...ok...final parameter
parm is:'/boot/parm ' ....ok...
Silo:ix 0:offset:078523 count:0c address 0x00000000
Silo:ix 1:offset:078530 count:80 address 0x0000c000
Silo:ix 2:offset:0785b0 count:80 address 0x0008c000
Silo:ix 3:offset:078630 count:6f address 0x0010c000
Silo:ix 4:offset:07a8de count:01 address 0x00008000
Silo:Bootmap is in block no:0x00001ed7

At that point, you should "exit" followed by "cd /" followed by "umount
/mnt" followed by re-trying your IPL from the SE.

Mark Post

Reply via email to