LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   Block bitmap for group 416 not in group (block 0) + group descriptors corrupted? (https://www.linuxquestions.org/questions/linux-server-73/block-bitmap-for-group-416-not-in-group-block-0-group-descriptors-corrupted-849067/)

quanta 12-08-2010 10:26 AM

Block bitmap for group 416 not in group (block 0) + group descriptors corrupted?
 
Hi,

Because the provider change the UPS, our server must be shutdown. But I got the problem when the server startup:
Quote:

fsck.ext4: No such file or directory while trying to open /dev/sdc1
as you can see from the above, sdc1 doesn't exist in /dev.
/etc/fstab:
Code:

/dev/sdc1 /data ext4 defaults 0 0
Try to use parted to get the partition info:
Code:

Model: Adaptec xx (scsi)
Disk /dev/sdc: 5991GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size    File system  Flags
 1      0.00kB  5991GB  5991GB  ext3

Code:

(parted) check 1                                                         
Warning: File system has errors!  You should run e2fsck.                 
Ignore/Cancel? I
Error: File system has an incompatible feature enabled.

Follow this guide, I try to mount manually (also tried with ext4):
Code:

losetup /dev/loop0 /dev/sdc -o $((0*512))
mount /dev/loop0 /mnt/sdc1

but the system hangs at mount command and the /var/log/messages displays the below error:
Quote:

Dec 8 18:07:12 xx kernel: EXT3-fs error (device loop0): ext3_check_descriptors: Block bitmap for group 416 not in group (block 0)!
Dec 8 18:07:12 xx kernel: EXT3-fs: group descriptors corrupted!
After that, the server seems to be hang and auto restart. It take me 15 to 20 minutes to ssh again.

Related info:
Code:

# tune2fs -l /dev/sdc
tune2fs 1.39 (29-May-2006)
Filesystem volume name:  <none>
Last mounted on:          <not available>
Filesystem UUID:          ac12e26a-6007-4070-9df8-d6c71af16ef5
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal resize_inode dir_index filetype sparse_super large_file
Default mount options:    (none)
Filesystem state:        clean with errors
Errors behavior:          Continue
Filesystem OS type:      Linux
Inode count:              731381760
Block count:              1462763520
Reserved block count:    73138176
Free blocks:              1173216062
Free inodes:              368151971
First block:              0
Block size:              4096
Fragment size:            4096
Reserved GDT blocks:      675
Blocks per group:        32768
Fragments per group:      32768
Inodes per group:        16384
Inode blocks per group:  512
Filesystem created:      Mon Aug  2 11:26:40 2010
Last mount time:          Mon Aug  2 11:40:53 2010
Last write time:          Wed Dec  8 18:21:08 2010
Mount count:              1
Maximum mount count:      21
Last checked:            Mon Aug  2 11:26:40 2010
Check interval:          15552000 (6 months)
Next check after:        Sat Jan 29 11:26:40 2011
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:                  128
Journal inode:            8
Default directory hash:  tea
Directory Hash Seed:      a7202c00-1faa-46a1-a083-b8fa53be3c6f
Journal backup:          inode blocks

Code:

# sfdisk -sl /dev/sdc
5851054080

Disk /dev/sdc: 728422 cylinders, 255 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
 /dev/sdc: unrecognized partition table type
No partitions found

Code:

# e2fsck -fDC0 /dev/sdc
e2fsck 1.39 (29-May-2006)
Group descriptors look bad... trying backup blocks...
Superblock has an invalid ext3 journal (inode 8).
Clear<y>? no

e2fsck: Illegal inode number while checking ext3 journal for /dev/sdc

Tomorrow morning, I will go to the data center to see what messages come out from the kernel (I guess the kernel was crash) when I try to mount manually. But I want to raise the matter here to know whether anyone has ever been in this situation.

The surprising thing from the other server which has same function is we have an entry in /etc/fstab, mount the whole disk instead of the partition:
Code:

# grep sdc /etc/mtab
/dev/sdc /data ext4 rw 0 0

I have never seen that before. Can someone give me some info about that?
Code:

# parted /dev/sdc
GNU Parted 1.8.1
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print                                                           

Model: Adaptec vcdata (scsi)
Disk /dev/sdc: 2999GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number  Start  End    Size    File system  Flags
 1      0.00kB  2999GB  2999GB  ext3


stress_junkie 12-08-2010 10:40 AM

Do you have a backup of the data that was on that partition? If so then just recreate the partition, format it, and restore from backup.

If you don't have a backup then I would use dd to make an image of that entire disk before I messed with it. You can make an image into a file on another disk. Naturally the disk that holds the image file will have to have more free space than the entire source disk's capacity.
Code:

dd if=/dev/sdc of=/mnt/bigdisk/image.dd bs=4096 conv=notrunc,noerror
Again, naturally this example assumes that there is a big disk with lots of free space mounted at /mnt/bigdisk.

Let us know if my first suggestion is available to you. If it is then the problem may be solved, unless you have a hardware problem. Hopefully this was caused by a one time anomaly due to the installation of the new power supply.


All times are GMT -5. The time now is 09:50 AM.