It just said running e2fsck on a mounted fulesystem may cause SEVERE filesystem damage. do I want to continue y/n.

Should I unmount each hda* and then remount them after the scanning is done till they are all scanned?

Evan


On Wed, 05 Nov 2003 18:03:18 +0200, Ray <[EMAIL PROTECTED]> wrote:


Use only:
fsck -t ext3 /dev/hda1

(later hda2, hda3, etc) for the begining. The program is interactive and will let you know if there are any problems
with the superblocks on the partitions. The superblocks may be OK - no need to restore them. I was suspecting the
problem with superblocks, becase you tried fsck on a wrong disk (hdc) and gave an output. Now we knw the
situation is different - you have hda, but hot hdc. One more remark. The 0 (zero) partition is never present on hard disk.
The numbers always begin with 1. So do not try to do smth. with hda0.


Ray

Evan Brown wrote:

Okay before I do the fsck thing, how would I check to make sure the superblocks are in fact damaged? I don't want to do this and then have it more screwed then before. I can list the partions thru fdisk, I would think that means that they are not hooped. does fsck have a general "check over" before I do anything crazy?

Evan


On Wed, 05 Nov 2003 17:45:27 +0200, Ray <[EMAIL PROTECTED]> wrote:


Not a problem.
Superblock backups are stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

modify the command
fsck -t ext3 -b 32768 /dev/hd??

The ext2 and ext3 are cmpatible.
Ray

Evan Brown wrote:

I have ext3 file system.

Evan Brown

On Wed, 05 Nov 2003 17:19:59 +0200, Ray <[EMAIL PROTECTED]> wrote:

If you have ext2 type damaged partition the superblok problem can be resolved by:

fsck -t ext2 -b 32768

See the details below:
-b superblock
Instead of using the normal superblock, use an alternative superblock speci�
fied by superblock. This option is normally used when the primary
superblock has been corrupted. The location of the backup superblock is
dependent on the filesystem's blocksize. For filesystems with 1k block�
sizes, a backup superblock can be found at block 8193; for filesystems with
2k blocksizes, at block 16384; and for 4k blocksizes, at block 32768.


Additional backup superblocks can be determined by using the mke2fs program
using the -n option to print out where the superblocks were created. The
-b option to mke2fs, which specifies blocksize of the filesystem must be
specified in order for the superblock locations that are printed out to be
accurate.


If an alternative superblock is specified and the filesystem is not opened
read-only, e2fsck will make sure that the primary superblock is updated
appropriately upon completion of the filesystem check.


Ray













Reply via email to