The next idea is checking the VGDA, it might just be corrupted.
If this is the case, you might have to repair the VGDA data, which is not an easy task (and without danger neither).
There is an (undocumented! so use at your own risk) command "readvgda". If used on a good copy it will show you the complete VG layout, including LVs, their PP mappings, etc.. I suggest you read also the LVM redbook to understand the concepts behind the following actions. CAUTION: these actions have the potential to harm your data, carefully examine all the steps, save everything you do and only proceed when feeling comfortable!
You need a "/etc/filesystems" too, because you do not get the mount points from the VGDA.
Now construct map files for each LV from the VGDA info. Then export the VG and recreate it on the original PVs and with the original PP size, then recreate each LV usin the constructed map file on its original place:
(I was supposing jfs here, change the commands accordingly if you use jfs2.)
Now restore the "/etc/filesystems" but DO NOT MOUNT yet!
For each filesystem update the LVCB with the log and label information:
NOW run "fsck" over each FS - WITHOUT the "-y"! If "fsck" complains about not being able to read the superblock the respective LV was not recreated correctly and you have to start over. If the jfslog LV was not recreated correctly, then "fsck" will not be able to replay the log and you will probably lose some data, so better double- and triple-check your mappings before you answer "yes" to any of "fsck" questions if it should correct anything.
Note, that if a filesystem was online at the time of the crash fsck might find some (unrecoverable) errors because of corrupted inode-lists. The only thing you can do is to fix this, but it will probably make you lose data. (Serves you right if you have no working backup.)
Re-run "fsck" until there are no errors any more to correct, then mount FSes. If any errors were fixed you should check "lost+found" for the remains of orphaned files/blocks. You might be able to regain some of the lost data from there.
I am managing a linux cluster which has been build on Platform Cluster Manager PCM 1.2.1) from IBM Platform Computing. Unfortunately somebody deteled data files of postgresql from /var/lib directory. I somehow managed to start the postmaster service again, but all the administrative commands of... (2 Replies)
Is there a way to find the volume group name after assigning hdisk to the machine for importing it ?
importvg -y <find_the_name_from_the_unknown_disk_> hdiskX
Code tags and no hijacking. You should be aware of that ;) (3 Replies)
I don't know if I am asking this correctly, but I have a hard drive with some bad sectors and it appears that some of the data is corrupt. I am having allot of trouble copying the data to a new drive. The issue is not in copying files, but that the new drive to which files are copied is not acting... (17 Replies)
Hallo Friends,
I have application X running on hpux 11.11 and oracle 9i release 2. I recently had a hardware failure on disk /dev/dsk/c2t0d0
Below is the systemlog file :
root@a7dmc:/var/adm/syslog > /opt/resmon/bin/resdata -R 155713541 -r /storage/events/enclosures/gazemon/0_1_1_0.0.0... (11 Replies)
Hi
How to check if a vg is exported from an LPAR using exportvg?
Is there a command or place where we can see the list of the vg's exported from the LPAR ?
Because if i run the command to varyonvg i get the below error :
root@cbspsrc02 #varyonvg old_rootvg
0516-082 varyonvg: Unable to... (7 Replies)
Hello,
On Aix 5.3, during importvg, the varyonvg fails:
importvg -y vgtest hdisk20
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
When i use manually the command varyonvg -u -b -t vgtest to force, the vg can... (3 Replies)
Hmm, how to ask this without sounding too malicious...
How might one go about causing a disk corruption in OS X specifically or via the command line in UNIX in general?
Doesnt matter the severity of the problem, I just want to scare the person a little, then fix the problem for them.
Any... (1 Reply)