I think I have a telling message now, on why the IPL halted.
After I got the partition check messages:
Partition Check:
dasda:VOL1/ L40D1C : dasda dasda1
dasdb:VOl1/ L40D18: dasdb
After a while, this shows up.
<7> dasd_erp(3990): /dev/dasdb(94:4),0d18@0x2f6:
Perform logging requested
Then it hangs.
I can certainly go back through a dasdfmt/fdasd process and re-install to
see if I missed anything but I'd rather not....
|---------+---------------------------->
| | "Post, Mark K" |
| | <[EMAIL PROTECTED]|
| | m> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 01/24/2003 01:41 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: ZIPL - confused and dazed
|
>------------------------------------------------------------------------------------------------------------------------------|
James,
Not sure if the install did it or not. Theoretically, you should be able
to
just issue the zipl command (with no parameters) to make sure.
Mark Post
-----Original Message-----
From: James Melin [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 9:07 AM
To: [EMAIL PROTECTED]
Subject: Re: ZIPL - confused and dazed
I found what appears to be my new root volume at /mnt/. Apparantly YaST has
already built a zipl.conf file for me? Does this mean that YaST also
handled the IPL record? The zipl.conf file contains the correct dasd
devices. I see it still keeps the annoying behaviour of rearranging things
so that dasda1 is your swap volume.
I just want to make sure that the ipl record has been written. If so, I
will attempt to IPL the new system.
|---------+---------------------------->
| | "Post, Mark K" |
| | <[EMAIL PROTECTED]|
| | m> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 01/23/2003 03:52 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>
---------------------------------------------------------------------------
---------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: ZIPL - confused and dazed
|
>
---------------------------------------------------------------------------
---------------------------------------------------|
James,
The /boot directory can be on any physical disk on your system. That then
becomes the device number you IPL from. A lot of people have it in their
root file system, which by default will wind up on /dev/dasdb1 on a SuSE
system. The "df" command will show you all your currently mounted file
systems. "/" should be at the top.
Mark Post
-----Original Message-----
From: James Melin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 4:31 PM
To: [EMAIL PROTECTED]
Subject: ZIPL - confused and dazed
I have my system built. all that remains is for me to run zipl and I should
be able to build it.
I don't know where /boot is supposed to be . I cannot seem to locate my
root volume even though cat /proc/dasd/devices indicates the volume is
available.
don't I need to be able to run zipl from the root volume of the new file
system I just installed? What should I really put in /etc/zipl.conf?
I'm basically staring a tthe 2-3 pages of the SuSE manual and going 'this
assumes I know more than I do'
I wouldn't normalyl give up so soon and ask this fairly benign question but
we're doing a power-on reset on sunday. So I have tomorrow to get this
thing to IPL-able or start over and re-install monday.
