Re: Anyone know how to fix this problem?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Paul wrote:
Hi,

A partition on one of my hard drives has decided that blocks 0, 1 and 2
are no-go areas. I can mount the drive manually by using mount -t ext3
-o sb=131073 /dev/hdg2 /web.

If I run e2fsck on the drive, I always get the following output

/dev/hdg2 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #116 (32255, counted=32253).
Fix? yes

Free blocks count wrong for group #178 (32252, counted=32251).
Fix? yes

Free blocks count wrong for group #209 (6856, counted=6790).
Fix? yes

Free blocks count wrong for group #210 (16220, counted=16282).
Fix? yes

Free blocks count wrong for group #229 (32208, counted=31551).
Fix? yes

Free blocks count wrong (8301757, counted=8301093).
Fix? yes

Free inodes count wrong for group #116 (16352, counted=16350).
Fix? yes

Directories count wrong for group #116 (0, counted=1).
Fix? yes

Free inodes count wrong for group #229 (16331, counted=16201).
Fix? yes

Directories count wrong for group #229 (7, counted=19).
Fix? yes

Free inodes count wrong (4293267, counted=4293135).
Fix? yes


/dev/hdg2: ***** FILE SYSTEM WAS MODIFIED ***** /dev/hdg2: 7441/4300576 files (1.6% non-contiguous), 294123/8595216 blocks Error writing block 1 (Attempt to write block from filesystem resulted in short write). Ignore error? yes

It doesn't matter how many times I run e2fsck or fsck.ext3, I always get
the above.

badblocks -n doesn't help either.

The superblock is intact (as I can mount it), but I am unable to
automount the drive on boot.

No, the primary superblock is bad as you must specify one of the alternatives in your mount command.

Anyone know how to get around this?

Use "dumpe2fs -b >/tmp/badblocks" to get a list of the bad blocks in /tmp/badblocks. Edit that file and add an entry for block 1, then run "badblocks -i /tmp/badblocks" to mark the block as bad.

All of this is buried in the manpage for badblocks.  Read carefully.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens@xxxxxxxxxxxxxxx -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-         "If you can't fix it...duct tape it!"  - Tim Allen         -
----------------------------------------------------------------------


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux