James,
Partition checks are a normal part of the system's boot cycle - it lists
all the partitions it sees on your system. It looks like it sees no
partitions on your dasdb device, though, which is a cause for alarm, unless
the IPL just stopped before it could list /dev/dasdb1. I'd be grasping at
straws to guess at what this might have to do with your IPL halting in
mid-stream.
I'm not running SuSE.
I have to wonder what happened to the partition table on dasdb, though,
provided that the IPL just didn't stop there by chance. Is it possible you
ran zipl against the device (dasdb) and not against a partition on that
device (dasdb1)? Maybe that might explain it? dasdb1 is supposed to be your
root disk ... whenever I've been in situations where the kernel couldn't
mount the root device for any reason, it's complained very clearly and
loudly about that very fact. This IPL freeze is odd.
I don't know of any layout requirements (CDL/LDL) on the swap DASD.
--Jim--
James S. Tison
Senior Software Engineer
TPF Laboratory / Architecture
IBM Corporation
+1 203 486-2835 (voice/fax)
[EMAIL PROTECTED]
James Melin
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
epin.mn.us> cc:
Sent by: Linux on Subject: Re: ZIPL - confused and dazed
390 Port
<[EMAIL PROTECTED]
ST.EDU>
01/24/2003 03:19
PM
Please respond to
Linux on 390 Port
I rolled the dice and did an IPL. I got activity, and stuff, so YaST now
apparently writes the IPL record correctly. But I get the following thing
that halts the IPL.
Partition Check:
dasda:VOL1/ L40D1C : dasda dasda1
dasdb:VOl1/ L40D18: dasdb
The Kernel command line looked like this:
dasd=0d1c,0d18,0d1a,0d19,0d1d,0d1b,0d1e,0d1f root = /dev/dasdb1 noinitrd
0d1c is the swap volume and I had it formatted in CDL layout as well as the
others. 0D18-0D1B are mod 9 devices, while 0d1c-0d1f are custom volumes of
approximately 1 gig. I used 0d1d I believe as /tmp, 0d1a as /var, 0d19 as
/opt and 0d1b as /usr I think - not that this is probably relevant.
Of course, yast re-arranges things so that swap is always dasda.
Thing is, should swap be in CDL format? it allowed me to set it as swap in
fdasd. So what is a Partition check and how does one fix it?
|---------+---------------------------->
| | "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.
