Bauer, Bobby (NIH/CIT) [E] wrote:
Hey, this is getting to be fun. I've gotten into rescue mode as described in
the manual Brad referenced below and was able to follow the script but it
doesn't tell me how to finish.
An 'lvm vgscan' found VolGroup00
The 'lvm vgchange -a y' found the 11 volumes and activated VolGroup00
I was able to mount all file systems under /mnt/sysimage/*
Now what, the chapter ends?
Now that everything's mounted, you can troubleshoot the original
problem. If you're being dropped to a repair prompt on normal boot,
here are some things to check:
- verify all entries in /mnt/sysimage/etc/fstab, but specifically /usr
entry.
- check /etc/modprobe.conf, dasd= parameter. Especially if any disks
have been added/removed/changed recently.
- there could be an initrd problem (perhaps the lvm module isn't being
loaded?) You can regenerate the initrd with chroot /mnt/sysimage;
mkinitrd -v /boot/initrd...img <kernel_version>
- if you make any changes to modprobe.conf or the initrd, chroot
/mnt/sysimage, then run zipl. This is good to do anyway, just in case
something is out of sync.
- unmount /usr and run e2fsck /dev/<volumegroup>/<usr_lv> to check the
filesystem. This is always a good thing to check, but in your case it's
probably not the problem. If there was a filesystem problem, it
wouldn't have mounted under rescue mode either.
-Brad
Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Brad
Hinson
Sent: Tuesday, February 17, 2009 5:49 PM
To: [email protected]
Subject: Re: Broken logical volume group
Mark Post wrote:
On 2/17/2009 at 1:17 PM, "Bauer, Bobby (NIH/CIT) [E]" <[email protected]>
wrote:
Looks like this is going to be ugly. We booted on of our servers and the
logical volume was corrupted and I got dropped down to the Repair Filesystem
prompt. One big problem is /usr is empty so none of the logical volume
commands are availably.
They're not in /sbin? Are you getting to the point that the root file system is mounted,
or are you still in the initrd? I.e., is your root file system an LV, or not? If it's
an LV, then you'll need to reboot from your installation kernel and initrd, or whatever
other rescue system Red Hat provides. And then for all future builds, remember to not
have "/" be an LV.
Mark Post
Hi Bobby,
fyi, rescue mode is documented in the RHEL 5.2 Redbook, in section 13.4.2:
http://www.redbooks.ibm.com/abstracts/sg247492.html
Rescue mode has all commands necessary to bring the LVM online and fix it.
There are pluses and minuses to "/" on LVM. Bit of a holy war at
times.. one of the minuses cited is administration through rescue mode.
It is, however, fully documented in the above link.
-Brad
----------------------------------------------------------------------
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
www.redhat.com/z
----------------------------------------------------------------------
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
--
Brad Hinson <[email protected]>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
----------------------------------------------------------------------
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
