Recovering from super block errors

If you receive one of the following errors from the
problem may be a corrupted superblock:
fsck or mount commands, the

fsck: Not an AIX3 file system
fsck: Not an AIXV3 file system
fsck: Not an AIX4 file system
fsck: Not an AIXV4 file system
fsck: Not a recognized file system type
mount: invalid argument
The problem can be resolved by restoring the backup of the superblock over the
primary superblock using one of the following commands:

dd count=1 bs=4k skip=31 seek=1 if=/dev/lv00 of=/dev/lv00
Once the restoration process is completed, check the integrity of the file system

Comments

Post a Comment

Popular posts from this blog

Installing and configuring the storage agent (AIX)

The storage agent must be installed on a client system that has connections to storage resources on the SAN. Before beginning this procedure: Verify that your system meets the hardware and software requirements. Be sure that you have the information recorded in the configuration-information work sheets. Close all existing Tivoli® Storage Manager products prior to installing the storage agent. Installation will stop if an active Tivoli Storage Manager process is detected. If this occurs, close all active Tivoli Storage Manager products and retry installing the storage agent. The storage agent honors the Tivoli Storage Manager server environment variables DSMSERV_CONFIG. The instructions in this section are shown using the Software Management and Installation Tool (SMIT). You can also use the Install and Update Software Manager (installm). To reduce workload and processing time and to optimize LAN-free performance, do not install the storage agent and the Tivoli Storag
Read more

Breaking mirrors on an existing mksysb

To restore a mksysb without mirroring. the following procedure can be used NOTE: Access to another AIX system and an AIX formatted diskette is required to perform this procedure.  All references to the tape device in the next section are as rmt0. On another AIX system, place the mksysb tape in the tape drive. Change the block size of the tape drive to 512 by running: chdev -l rmt0 -a block_size=512   Create a temporary directory in /tmp called newdata .   mkdir /tmp/newdata Change to the /tmp/newdata directory. Enter:   cd /tmp/newdata    Make sure that the tape is rewound. Enter: tctl -f /dev/rmt0 rewind    Restore the image.data file from the second image of the mksysb tape. Enter: restore -s2 -xqvf /dev/rmt0.1 ./image.data    Edit the /tmp/newdata/image.data file and make changes to each of the lv_data stanzas as in
Read more

Move a file system to another volume group

How to move FS to anotherVG UNMOUNT fs Copy the source logical volume to the desired volume group with the cplv command. For example, where myvg is the new volume group and mylv is the name of the user's logical volume, enter:        cplv -v myvg mylv This will return the name of the new logical volume, such as lv00. 2- To make a new JFS log, enter the following command, where myvg is the name of the new volume group, enter:        mklv -t jfslog  myvg 1 To make a new JFS2 log, enter:      mklv -t jfs2log  myvg 1 ** This new logical volume will need to be formatted with the logform command in order to function properly as either a JFS or JFS2 log. For example:        logform /dev/loglv00 Answer yes to destroy. 3-Change the filesystem to reference a log device that exists in the new volume group and the new logical volume with the chfs command. For example, where myfilesystem is the name of the user's filesystem, enter:        chfs -a dev=/dev/lv00 -a log=/dev/loglv00 /myf
Read more