LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 11-16-2011, 08:39 AM   #1
illuminate0
LQ Newbie
 
Registered: Nov 2011
Location: United States
Posts: 2

Rep: Reputation: Disabled
group descriptors corrupted!


Hi all, new user here. I did my due diligence and tried to find the answer prior to posting and have tried a few things but I am still broken. My situation: I have a storage device hooked up to a Ubuntu server via iSCSI. I had it all talking nicely and up and running about 2 weeks ago. Now the device will no longer mount.

Code:
root@Backup:~# mount /backups2
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
The log..
Code:
root@Backup:~# dmesg | tail
[   39.995906] sd 2:0:0:1: [sdb] 18556198912 512-byte logical blocks: (9.50 TB/8.64 TiB)
[   39.998644] sd 2:0:0:1: [sdb] Write Protect is off
[   39.998654] sd 2:0:0:1: [sdb] Mode Sense: 97 00 00 08
[   40.000292] sd 2:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   40.003415]  sdb: sda1
[   40.018085] sd 2:0:0:0: [sda] Attached SCSI disk
[   40.026415]  unknown partition table
[   40.030556] sd 2:0:0:1: [sdb] Attached SCSI disk
[ 5715.244441] EXT4-fs (sda1): ext4_check_descriptors: Checksum for group 0 failed (51749!=0)
[ 5715.244453] EXT4-fs (sda1): group descriptors corrupted!
Code:
root@Backup:/# fdisk -ul /dev/sda1

Disk /dev/sda1: 9000.7 GB, 9000731017216 bytes
255 heads, 63 sectors/track, 1094276 cylinders, total 17579552768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sda1 doesn't contain a valid partition table
Did some research and found this link and tried the following:

Code:
root@Backup:~# fsck /dev/sda1
fsck from util-linux-ng 2.17.2
e2fsck 1.41.11 (14-Mar-2010)
fsck.ext4: Group descriptors look bad... trying backup blocks...
fsck.ext4: Bad magic number in super-block when using the backup blocks
fsck.ext4: going back to original superblock
fsck.ext4: Device or resource busy while trying to open /dev/sda1
Filesystem mounted or opened exclusively by another program?

root@Backup:~# mke2fs -n /dev/sda1
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
549363712 inodes, 2197444096 blocks
109872204 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
67061 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
        102400000, 214990848, 512000000, 550731776, 644972544, 1934917632

root@Backup:~# e2fsck -b 1605632 /dev/sda1
/dev/sda1 contains a file system with errors, check forced.
Resize inode not valid.  Recreate<y>? yes

Pass 1: Checking inodes, blocks, and sizes
yyyInode 425 has a extra size (65535) which is invalid
Fix<y>? yes

Inode 426 is in use, but has dtime set.  Fix<y>? yes

Inode 426 has a extra size (18635) which is invalid
Fix<y>? yes

Inode 426 has compression flag set on filesystem without compression support.  Clear<y>? yes

Inode 426, i_size is 6414028916418760925, should be 0.  Fix<y>? yes

Inode 426, i_blocks is 6779278794416, should be 0.  Fix<y>? yes

Inode 427 is in use, but has dtime set.  Fix<y>? yes

Inode 427 has a extra size (42746) which is invalid
Fix<y>? yes

Inode 428 is in use, but has dtime set.  Fix<y>? yes

Inode 428 has imagic flag set.  Clear<y>? yes

Inode 428 has a extra size (11520) which is invalid
Fix<y>? yes

Inode 429 is in use, but has dtime set.  Fix<y>?
The above errors just went on and on.. Can anyone guide me in the next steps? I can provide more information as needed, please help!

Last edited by illuminate0; 11-16-2011 at 08:43 AM.
 
Old 11-16-2011, 05:52 PM   #2
chrism01
Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Centos 6.5, Centos 5.10
Posts: 16,280

Rep: Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032Reputation: 2032
If you've re-created the FS and then fsck complains, could be a dying disk. Try this tool for analysis http://linux.die.net/man/8/smartctl
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Block bitmap for group 416 not in group (block 0) + group descriptors corrupted? quanta Linux - Server 1 12-08-2010 10:40 AM
EXT3-fs: group descriptors corrupted! secretlydead Linux - Hardware 1 01-31-2010 08:34 AM
EXT3-fs:group descriptors corrupted! (GNU/RH9) jjlune Linux - General 13 04-16-2006 04:38 PM
EXT3-fs: group descriptors corrupted dadriver Linux - Hardware 2 02-04-2006 03:16 AM
EXt3-fs:group descriptors corrupted. anjanesh Fedora 0 11-15-2004 12:26 AM


All times are GMT -5. The time now is 12:59 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration