I think this is your problem:
Kernel command line: root=/dev/ram0 ro

It's telling the system that your root file system is on your ram disk,
which essentially has some device driver modules, and that's about it.  I
think you need to IPL your installation system, mount your DASD volumes,
chroot to the root file system, update your zipl parameters, re-make the
initrd, and re-run zipl, then reboot.


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Eric
Sammons
Sent: Wednesday, June 30, 2004 1:55 PM
To: [EMAIL PROTECTED]
Subject: Re: Trouble booting a new guest


Here it is again, a fresh build with
0300    ext2    /boot
0301    ext3    /
0302    ext3    /var
0303    ext3    /home
Ready; T=0.01/0.02 13:50:31
ipl 300 clear
hwc low level driver: can write messages
hwc low level driver: can not read state change notifications hwc low level
driver: can receive signal quiesce hwc low level driver: can read commands
hwc low level driver: can read priority commands Linux version
2.4.19-3suse-SMP ([EMAIL PROTECTED]) (gcc version 3.2) #1 SMP Wed Nov 6  22:34:43
UTC 2002 We are running under VM (31 bit mode) This machine has an IEEE fpu
On node 0 totalpages: 131072
zone(0): 131072 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Building zonelist for node : 0
Kernel command line: root=/dev/ram0 ro
Highest subchannel number detected (hex) : 0023
Calibrating delay loop... 627.50 BogoMIPS
Memory: 513944k/524288k available (1706k kernel code, 0k reserved, 396k
data, 56 k init)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)     ,
Inode cache hash table entries: 32768 (order: 6, 262144 bytes) Mount-cache
hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table
entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries:
131072 (order: 7, 524288 bytes)
debug: Initialization complete
POSIX conformance testing by UNIFIX
Detected 1 CPU's
Boot cpu address  0
cpu 0 phys_idx=0 vers=FF ident=0F11AA machine=2064 unused=0000
migration_task 0 on cpu=0 init_mach : starting machine check handler Linux
NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket mach_handler : ready mach_handler : waiting
for wakeup Starting kswapd kinoded started
VFS: Diskquotas version dquot_6.5.0 initialized
aio_setup: num_physpages = 32768
aio_setup: sizeof(struct page) = 44
pty: 256 Unix98 ptys configured     ,
RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
loop: loaded (max 16 devices)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
debug: cio_msg: new level 6
debug: cio_trace: new level 6
debug: cio_crw: new level 6
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 32Kbytes
TCP: Hash tables configured (established 65536 bind 65536) Linux IP
multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 644k freed
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 14k freed
#

Thoughts?



===============================

Eric Sammons, RHCE
(804)697-3925
eric.sammons at frit.frb.org
FRIT - Unix Systems

===============================

"First you guess.  Don't laugh, this is the most important step.  then you
compute the consequences.  Compare the consequences to experience.  If it
disagrees with experience, the guess is wrong.  In that simple statement is
the key to science.  It doesn't matter how beautiful your guess is or how
smart you are or what your name is.  If it disagrees with experience, It's
wrong.  That's all there is to it."  -- Richard Feynman





"Little, Chris" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
06/30/2004 01:11 PM
Please respond to Linux on 390 Port


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        Re: Trouble booting a new guest

Doesn't look like everything was installed.  Are you sure it completed
successfully?

> -----Original Message-----
> From: Eric Sammons [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 30, 2004 11:54 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Trouble booting a new guest
>
>
> The guest never gets to run level 2.  None of the commands are
> available. Because ls and other commands are not available I use echo
> *, from / that
> returns:
> bin dev lib linuxrc
>
> Thanks!
> ===============================
>
> Eric Sammons, RHCE
> (804)697-3925
> eric.sammons at frit.frb.org
> FRIT - Unix Systems
>
> ===============================
>
> "First you guess.  Don't laugh, this is the most important step.  then
> you compute the consequences.  Compare the consequences to
> experience.  If it
> disagrees with experience, the guess is wrong.  In that
> simple statement
> is the key to science.  It doesn't matter how beautiful your
> guess is or
> how smart you are or what your name is.  If it disagrees with
> experience,
> It's wrong.  That's all there is to it."  -- Richard Feynman
>
>
>
>
>
> Ranga Nathan <[EMAIL PROTECTED]>
> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 06/30/2004 11:52
> AM Please respond to Linux on 390 Port
>
>
>         To:     [EMAIL PROTECTED]
>         cc:
>         Subject:        Re: Trouble booting a new guest
>
> Hmm. Normally I would see some info about interface binding to eth0
> which will give you an IP. Looks like you can log in as root. Can you
> type 'login root'? or somehow get to run '/sbin/ifconfig eth0'? Or can
> you manually perform 'init 3'?
> __________________________________________
> Ranga Nathan / CSG
> Systems Programmer - Specialist; Technical Services;
> BAX Global Inc. Irvine-California
> Tel: 714-442-7591   Fax: 714-442-2840
>
>
>
>
>
> Eric Sammons <[EMAIL PROTECTED]>
>
> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 06/30/2004 08:37
> AM Please respond to Linux on 390 Port
>
>         To:     [EMAIL PROTECTED]
>         cc:
>         Subject:        Re: Trouble booting a new guest
>
>
> The system never gets to runlevel 3.  In fact I believe it fails to
> get to runlevel 2.  You will notice I have root prompt, Never got a
> login prompt
> and never got to the point where services start-up.
>
> Thanks!
>
> ===============================
>
> Eric Sammons, RHCE
> (804)697-3925
> eric.sammons at frit.frb.org
> FRIT - Unix Systems
>
> ===============================
>
> "First you guess.  Don't laugh, this is the most important step.  then
> you compute the consequences.  Compare the consequences to
> experience.  If it
> disagrees with experience, the guess is wrong.  In that
> simple statement
> is the key to science.  It doesn't matter how beautiful your
> guess is or
> how smart you are or what your name is.  If it disagrees with
> experience,
> It's wrong.  That's all there is to it."  -- Richard Feynman
>
>
>
>
>
> "Post, Mark K" <[EMAIL PROTECTED]>
> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 06/30/2004 11:00
> AM Please respond to Linux on 390 Port
>
>
>         To:     [EMAIL PROTECTED]
>         cc:
>         Subject:        Re: Trouble booting a new guest
>
> That all looks like normal startup messages to me.  What is your
> problem, exactly?
>
>
> Mark Post
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Eric Sammons
> Sent: Wednesday, June 30, 2004 10:03 AM
> To: [EMAIL PROTECTED]
> Subject: Trouble booting a new guest
>
>
> I have installed a new guest, I am using NFS as my install medium and
> not that it should matter, I am using a Red Hat Linux Intel
> system as my NFS
> server.  The system seems to build just fine; however, when I
> execute the
> ipl 300 clear I get the following:
>
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer-cache hash
> table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table
> entries:
> 131072 (order: 7, 524288 bytes)
> debug: Initialization complete
> POSIX conformance testing by UNIFIX
> Detected 1 CPU's
> Boot cpu address  0
> cpu 0 phys_idx=0 vers=FF ident=0F11AA machine=2064 unused=0000
> migration_task 0 on cpu=0 init_mach : starting machine check
> handler Linux
> NET4.0 for Linux 2.4 Based upon Swansea University Computer Society
> NET3.039
> Initializing RT netlink socket mach_handler : ready
> mach_handler : waiting
> for wakeup Starting kswapd kinoded started
> VFS: Diskquotas version dquot_6.5.0 initialized
> aio_setup: num_physpages = 32768
> aio_setup: sizeof(struct page) = 44
> pty: 256 Unix98 ptys configured
> RAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
> loop: loaded (max 16 devices)
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> debug: cio_msg: new level 6
> debug: cio_trace: new level 6
> debug: cio_crw: new level 6
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 2048 buckets, 32Kbytes
> TCP: Hash tables configured (established 65536 bind 65536) Linux IP
> multicast router 0.06 plus PIM-SM
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 644k freed
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 14k freed
> #
>
>
> I have two disks and two filesystems:
>
> 0300            =>      /dev/dasdf1     =>      /boot   => ext3
> 0301            =>      /dev/dasdg1     =>      /       => ext3
>
> I can not figure out what is going on or if something is missing etc.
> . .
>
> Thoughts - Help?
>
> Thanks!
> ===============================
>
> Eric Sammons, RHCE
> eric.sammons at frit.frb.org
>
> ===============================
>
> "First you guess.  Don't laugh, this is the most important step.  then
> you compute the consequences.  Compare the consequences to
> experience.  If it
> disagrees with experience, the guess is wrong.  In that
> simple statement
> is
> the key to science.  It doesn't matter how beautiful your
> guess is or how
> smart you are or what your name is.  If it disagrees with
> experience, It's
> wrong.  That's all there is to it."  -- Richard Feynman
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email
to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to