HP-UX LVM Maint. Mode Post: 15919

Sponsored Content

Operating Systems HP-UX HP-UX LVM Maint. Mode Post 15919 by Perderabo on Thursday 21st of February 2002 11:28:38 AM

02-21-2002

Administrator Emeritus

Maintenance mode is intended only to enable you to rebuild the LVM data in the LIF area of boot disk after it has been damaged. It ignores the LVM data (which is in the LIF file "LABEL" ). There are two cases. Either the area after the boot area is the root filesystem or it is the /stand filesystem. In either case it must be contiguous and it must be an hfs filesystem so the boot program hpux can find the kernel. In maintenance mode, it is assumed to start after the boot area and consume the rest of the disk. But if it is /stand, a file called /stand/rootconf is read (by the kernel) and this is used to find the start of the root filesystem which is also assumed to extend to the end of the disk. This leaves them overlapping each other as well as any other logical volumes.

The result is that the kernel is running and root is mounted with nothing else. At this point you are supposed to rebuild the LVM info in the boot area. This typically involves using mkboot, vgcfgrestore, and lvlnboot. It is crucial that the disk not be synced at all. Either "reboot -n" or cycle power to exit maintenance mode.

Activating the root volume group is explicitly prohibited...doing so may corrupt it.

The kernel knew that oldroot on /dev/root was a mount point but it didn't know that oldroot on /dev/vg00/lvol3 was a mount point. That why you saw a difference.

Was /oldroot pre-existing? Even a "mkdir /oldroot" is very risky in maintenance mode. HP-UX syncs some metadata right away. That might be enough to garble the static data in your root filesystem's superblock, but I'm not sure.

Perderabo

View Public Profile for Perderabo

Find all posts by Perderabo

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Maint user cannot execute ping command

I want give rights for the maint user to execute the "ping" command. Currently root user can execute the "ping" command, but the maint user is not able to execute the command.

2. SuSE

Convet Linux OS from text mode to graphic mode

Hi All, I used to have my suse linux(VM) server in graphic mode but not anymore since morning. I cant rolback since i loose somuch work. Any idea how to it back to normal. Thanks

3. HP-UX

how to distinguish standard system mode or trust system mode

I think that if the directory /tcb exists, HP-UX is in trusted mode and the passwd data is somewhere in /tcb/files/auth. But that's all I remember. Also I think recent versions of HP-UX can have a /etc/shadow file.

4. HP-UX

How to reduce LVM to create another LVM

Hi, I'm new to HP-UX. I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3 Thanks

5. UNIX for Advanced & Expert Users

What is the difference between single line mode and multiline mode in Regular expressions?

Hi All, Can please let me know what is the difference between the single line mode and multi line mode in regular expresions? Thanks, Chidhambaram B

6. UNIX for Dummies Questions & Answers

How to convert non LVM root partition to LVM?

Hi Guys, I m using redhat 6, I have installed root partition as non-LVM . Is there any way i can convert it to LVM?

7. Solaris

DNS service is in maintenance mode. How to bring it back to online mode?

:confused: when i tried to look the status of DNS-client, it is in maintenance mode..... Please tell me how to bring it back to online mode...PLEASE TELL ME STEP BY STEP.... PLEASE... :wall:

8. HP-UX

From a C++ application how to find if a hpux host is in standard mode or trusted mode

is there a way for my C++ application to find out which mode the hpux OS is running in? standard mode or trusted mode.

9. Solaris

Maint, resyncing and last-erred notifications

Hi fellow members! I have a oracle solaris server with two internal disks, that acts as an authentication server only, and for now the server seems to be doing its job, but when typing metastat -c I get some notifications. I am not familiar with SVM, I wonder if someone can help me on this:...

LEARN ABOUT HPUX

vxdestroy_lvmroot

vxdestroy_lvmroot(1M)													     vxdestroy_lvmroot(1M)

NAME

       vxdestroy_lvmroot - remove LVM root disk and associated LVM volume group

SYNOPSIS

       vxdestroy_lvmroot [-v] [-b] lvm_root_disk

DESCRIPTION

       The  vxdestroy_lvmroot  command	tears  down  and removes the LVM volume group associated with the specified physical disk. This is done by
       removing the volumes in the volume group and then removing the volume group.

OPTIONS

       -b	 Invokes the setboot command to change the primary boot disk to the VxVM root disk from which the system was booted (if  the  pri-
		 mary  boot  disk is not already set to this disk).  The alternate boot device remains unchanged.  If the -v option is also speci-
		 fied, the settings of the primary and alternate boot devices are displayed.

       -v	 Outputs verbose messages including a timestamp that indicates major operations being performed.

ARGUMENTS

       lvm_root_disk
	    Specifies the device name of the LVM root disk that is to be destroyed, along with its entire volume group.

EXAMPLES

       This example shows the vxdestroy_lvmroot command invoked in its simpliest form:

       /etc/vx/bin/vxdestroy_lvmroot c5t1d0

       # /etc/vx/bin/vxdestroy_lvmroot -v -b c3t0d0
       Are you sure about destroying c3t0d0 (imported on VG /dev/vg02) ? YES
       vxdestroy_lvmroot 06:02: Tearing down /dev/vg02 on device c3t0d0
       vxdestroy_lvmroot 06:02:
	 Unmounting and removing any volumes associated with /dev/vg02
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol1
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol2
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol3
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol4
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol5
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol6
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol7
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol8
       vxdestroy_lvmroot 06:02: Removing Volume Group /dev/vg02
       vxdestroy_lvmroot 06:02: Removing device files in /dev/vg02
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c3t0d0
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d3
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d4
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d5
       vxdestroy_lvmroot 06:03: Current setboot values:
       vxdestroy_lvmroot 06:03: Primary:       0/0/6/0/0.0.0
       vxdestroy_lvmroot 06:03: Alternate:     0/0/1/0/0.1.0
       vxdestroy_lvmroot 06:03:
	 Making disk c0t1d0 (0/0/1/0/0.1.0) the primary boot disk
       vxdestroy_lvmroot 06:03:
	 Removal of device c3t0d0, volume group /dev/vg02 was successful

SEE ALSO

       cpio(1), dd(1), fsck(1M), setboot(1M) vxbootsetup(1M) vxcp_lvmroot(1M) vxres_lvmroot(1M)

VxVM 5.0.31.1							    24 Mar 2008 					     vxdestroy_lvmroot(1M)