/usr only contains the lib64 directory.
-- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Justin Payne > Sent: Monday, April 14, 2008 3:28 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > Do you see lvm in /usr/sbin? > > ~Justin > > Kelly F. Hickel wrote: > > Brad, > > I don't have any of those commands. What I've done is to to a > > load from CDRom on the HMC and point it at a downloaded mirror of the > > s390x centos repo. Is there some other rescue mode that is more > useful > > than what I have???? > > > > The contents of /sbin on this ramdisk are: > > -/bin/sh-3.00# ls /sbin > > [ dasdfmt hexdump mktemp rmmod > touch > > ash date hostname modprobe route tr > > awk dd id more rpm2cpio > > traceroute > > basename deallocvt ifconfig mount sed true > > bash df in.telnetd msh sh tty > > bunzip2 dirname init mv shutdown > umount > > busybox dmesg insmod nc sleep > uname > > bzcat du install openvt sort uniq > > cat echo ip passwd sshd > unzip > > chgrp egrep kill pidof strings > uptime > > chmod env killall ping stty > usleep > > chown expr ln pivot_root swapoff vi > > chroot false load_policy poweroff swapon wc > > chvt fgrep loader ps sync wget > > clear find login pwd tail > which > > cmp free ls rdate tar > whoami > > cmsfscat grep lsmod readlink tee > xargs > > cmsfslst gunzip makedevs reboot telnet > xauth > > cp gzip md5sum reset test > xinetd > > cpio halt mkdir rm time yes > > cut head mknod rmdir top zcat > > > > And that's all that I have to work with... > > > > -- > > > > Kelly F. Hickel > > Senior Product Architect > > MQSoftware, Inc. > > 952-345-8677 Office > > 952-345-8721 Fax > > [EMAIL PROTECTED] > > www.mqsoftware.com > > SEE BUSINESS WORK > > > > > > > >> -----Original Message----- > >> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf > Of > >> Brad Hinson > >> Sent: Monday, April 14, 2008 3:05 PM > >> To: LINUX-390@VM.MARIST.EDU > >> Subject: Re: CentOS 4.4 kernel panic on boot s390x > >> > >> When inside the rescue environment, run 'lvm'. This is an LVM > "shell" > >> with all the commands you need (pvcreate, vgscan, etc). At the very > >> least, you can run: > >> > >> lvm > >> vgscan > >> vgchange -a y > >> > >> to activate the LVM. The vgscan creates the /dev nodes, so you > don't > >> need to do that manually. After you exit the LVM shell, you can > >> manually mount /dev/<vg_name>/<lv_name> to /mnt/<where_ever>. > >> > >> The kernel panic is most likely because your root file system can't > be > >> found. This could be due to the logical volume for "/" having > >> problems, > >> or zipl not finding it correctly. Double check that /etc/zipl.conf > >> > > has > > > >> the correct root= entry, i.e. > >> > >> "root=/dev/<your_vg_name>/<your_lv_name>" > >> > >> for the root file system. And for good measure, you may want to run > >> 'zipl' again from the rescue environment after 'chroot'ing to the > >> mounted root fs, just to make sure the MBR is in sync with > zipl.conf. > >> > >> -Brad > >> > >> On Mon, 2008-04-14 at 14:36 -0500, Kelly F. Hickel wrote: > >> > >>> So, I've got this zlinux LPAR on a z9BC, and it's been running > >>> > > CentOS > > > >>> 4.4 for a year or so, and recently it failed to reboot after an > IPL. > >>> > >>> It lists all the dasd, then says "Activating logical volumes" then > >>> panics with "Kernel panic - not syncing: Attempted to kill init!". > >>> > >>> I've been able to boot from the initrd 4.4 images (thanks all!) but > >>> > >> the > >> > >>> tools that I'd expect to see (pvscan, fdisk) aren't there. Looking > >>> > >> in > >> > >>> /proc/dasd/devices shows that the devices are all there and online. > >>> > >> I'm > >> > >>> even tried created the /dev nodes and mounting /dev/dasda1 (that > >>> > >> should > >> > >>> be where /boot is, right?) with no luck. > >>> > >>> I've googled and found a few cookbooks on getting back up after a > >>> > >> device > >> > >>> or kernel change, but I can't get to the point where I can mount > the > >>> volume. > >>> > >>> Any ideas what to try next? > >>> > >>> > >>> -- > >>> > >>> Kelly F. Hickel > >>> Senior Product Architect > >>> MQSoftware, Inc. > >>> 952-345-8677 Office > >>> 952-345-8721 Fax > >>> [EMAIL PROTECTED] > >>> www.mqsoftware.com > >>> SEE BUSINESS WORK > >>> > >>> > >>> > > --------------------------------------------------------------------- > > > >> - > >> > >>> 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 > >>> > >> -- > >> Brad Hinson <[EMAIL PROTECTED]> > >> Sr. Support Engineer Lead, System z > >> Red Hat, Inc. > >> (919) 754-4198 > >> > >> -------------------------------------------------------------------- > -- > >> 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
