Prev Next

SUMMARY Trying to rcover disk from crashed system

Jay Duncan -- Thu, 3 Feb 2000 21:56:21 +0100 (MET)

Well, I received a few responses that were fairly similar but the one that gave
me the best hint was from "Donald Bodle".  Thanks to everyone who responded. His
response and the original question are at the end of this email.  Here's what I
ended up doing:

# cd /dev
# mkdir vg01
# cd vg01
# mknod group c 64 0x010000
# rm /etc/lvmtab
# vgscan
Creating "/etc/lvmtab".
vgscan: Couldn't access the list of physical volumes for volume group
"/dev/vg00".
vgscan: Couldn't access the list of physical volumes for volume group
"/dev/vg01".
Physical Volume "/dev/dsk/c0t2d0" contains no LVM information

Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c2t6d0

# vgimport -p -v /dev/vg01 /dev/dsk/c2t6d0
Beginning the import process on Volume Group "/dev/vg01".
Logical volume "/dev/vg01/lvol1" has been successfully created
with lv number 1.
Volume group "/dev/vg01" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating
the volume group.

# vgimport -v /dev/vg01 /dev/dsk/c2t6d0
Beginning the import process on Volume Group "/dev/vg01".
Logical volume "/dev/vg01/lvol1" has been successfully created
with lv number 1.
Volume group "/dev/vg01" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating
the volume group.

# vgchange -a y /dev/vg01
Activated volume group
Volume group "/dev/vg01" has been successfully changed.

# vgscan
vgscan: The physical volume "/dev/dsk/c2t5d0" is already recorded in the
"/etc/lvmtab" file.
vgscan: The physical volume "/dev/dsk/c2t6d0" is already recorded in the
"/etc/lvmtab" file.
Physical Volume "/dev/dsk/c0t2d0" contains no LVM information

# cd /etc

# vi fstab

# System /etc/fstab file.  Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / hfs defaults 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /opt hfs defaults 0 2
/dev/vg00/lvol5 /tmp hfs defaults 0 2
/dev/vg00/lvol6 /usr hfs defaults 0 2
/dev/vg00/lvol7 /var hfs defaults 0 2
/dev/vg01/lvol1 /home hfs defaults 0 2  # ***ADDED THIS LINE***
/dev/dsk/c0t2d0 /cdrom cdfs ro,suid 0 0

# mount /home
vxfs mount: /dev/vg01/lvol1 is corrupted. needs checking (NOTE vxfs!!!)

# vi fstab
# System /etc/fstab file.  Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / hfs defaults 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /opt hfs defaults 0 2
/dev/vg00/lvol5 /tmp hfs defaults 0 2
/dev/vg00/lvol6 /usr hfs defaults 0 2
/dev/vg00/lvol7 /var hfs defaults 0 2
/dev/vg01/lvol1 /home vxfs defaults 0 2     # ***CHANGED TO "vxfs"***
/dev/dsk/c0t2d0 /cdrom cdfs ro,suid 0 0

# mount /home
vxfs mount: /dev/vg01/lvol1 is corrupted. needs checking
# fsck /dev/vg01/lvol1
log replay in progress
replay complete - marking super-block as CLEAN
# mount /home
# cd /home/ftp/dist

# ll
total 688
-r--r--r--   1 root       sys            643 Jan  6 21:31
CHECK_TOTAL_DISK_SPACE.sh
-r--r--r--   1 root       sys         184320 Jan  9 16:08 EVERYTHING.tar
-r--r--r--   1 root       sys            334 Jan  6 21:53 FTP_Script.sh

Yes!!!  Everthing is Back!!!!!

____________________Reply Separator____________________
Subject:    RE: [HPADM] Trying to rcover disk from crashed system 
Author: "Bodle  Donald E" <donald_bodle@reyrey.com>
Date:       2/3/00 11:45 AM

You need to know the /dev/dsk device file for the disk (you can get it from
ioscan -fnC disk).
Then try
vgimport -p -v /dev/vg01 /dev/dsk/"device file"
See what errors you get ( -p is for preview).  If it looks okay, then repeat
the vgimport command without the -p.  Then do the vgchange and the mount.

As I recall, an fsck on a raw device (/dev/dsk/whatever) will error out on a
disk that's been LVM'ed.  You have to do the fsck on the logical volume,
which of course you can't do right now until its imported....

the -s option is only if you're sharing the device in a cluster, I believe.
You need the first form in the man pages.
I think you can also try the import option in sam under volume groups.  It
scans the "unused" physical disks for evidence of LVM information.

Note, I've just been back into HPs for a few weeks now after about three
years away.


> -----Original Message-----
> From: Jay Duncan [SMTP:jduncan@dellabs.com]
> Sent: Thursday, February 03, 2000 11:05 AM
> To:   hpux-admin@dutchworks.nl
> Subject:  [HPADM] Trying to rcover disk from crashed system
> 
> I have a disk that was the second disk in a crashed system (735 10.20).
> vg00
> crashed and this is vg01. 
> 
> I'm trying to mount this disk on another system to get at the data. 
> 
>      mkdir /dev/vg01
>      mknod /dev/vg01/group c 64 0x010000
>      vgimport -s -m mapfile /dev/vg01
>      vgchange -a y /dev/vg01
>      mount -a
> 
> The problem is I don't have a "mapfile".  From what I read in the man
> pages a
> mapfile is created when you do a vgexport.  So, it imports the vg and
> makes it
> active but it doesn't mount the file system that was on it.  When you look
> at
> the lvol on it it says "unused".  When I try to do this all in sam and
> finally
> mount the file system by "Not creating a new file system" and mounting the
> old
> filesystem, it says the file system is not HFS so I try'd vxfs (I don't no
> what
> it is) and it tells me there is an error in the superblock and says to
> fsck it. 
> I do fsck and it wants the location of an alternat superblock, which I
> don't
> know....   Help!
> 
> TIA
> -jay
>     
> 
> 
> 
> --
>              ---> Please post QUESTIONS and SUMMARIES only!! <---
>         To subscribe/unsubscribe to this list, contact
> majordomo@dutchworks.nl
>        Name: hpux-admin@dutchworks.nl     Owner:
> owner-hpux-admin@dutchworks.nl
>  
>  Archives:  ftp.dutchworks.nl:/pub/digests/hpux-admin       (FTP, browse
> only)
>             http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse &
> search)



--
             ---> Please post QUESTIONS and SUMMARIES only!! <---
        To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
       Name: hpux-admin@dutchworks.nl     Owner: owner-hpux-admin@dutchworks.nl
 
 Archives:  ftp.dutchworks.nl:/pub/digests/hpux-admin       (FTP, browse only)
            http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse & search)