Re: fsck does not fix the drive In article <ed3bf47c.0408222127.359f340c@posting.google.com >, levw <lev.weissman@creo.com> wrote:
> If you have a dirty superblock error message during mount or fsck
> -you might try to do "fsck". If this does not work try the following
> (This procedure does not promise 100% success).
> USE this procedure ONLY as a last resort if fsck fails !!!!!
> (The following example relates to a bad filesystem in slv2.0)
> Copy the secondary superblock to the primary superblock. An example
> command and output follows:
> dd count=1 bs=4k skip=31 seek=1 if=/dev/slv2.0 of=/dev/slv2.0
> dd: 1+0 records in.
> dd: 1+0 records out.
>
> Then we'll run fsck on this filesystem to ensure it's back.
The original poster seems to have a dying hard drive with multiple
unrecoverable bad blocks.
He would be better advised to replace that drive immediately using
normal procedures then do a restore from backup or to re-mirror upon the
replacement drive.
If he has no usable backups, and if he has at least AIX 4.1, an easier
(and equivalent) way of copying the secondary superblock is to use:
# fsck -p /dev/nfs2lv1
-p will copy and then use the secondary superblock if the primary is
corrupt.
-Dan |