Unable to replace drive in software RAID-5 array (Fedora 14) - Page 4

leigh123linux · #46 2nd December 2011, 04:59 PM

Post

Code:

dumpe2fs /dev/md127 | grep -i superblock

Tamater · #47 2nd December 2011, 05:01 PM

Code:

[root@spectrum meg]# dumpe2fs /dev/md127 | grep -i superblock
dumpe2fs 1.41.12 (17-May-2010)
  Primary superblock at 0, Group descriptors at 1-350
  Backup superblock at 32768, Group descriptors at 32769-33118
  Backup superblock at 98304, Group descriptors at 98305-98654
  Backup superblock at 163840, Group descriptors at 163841-164190
  Backup superblock at 229376, Group descriptors at 229377-229726
  Backup superblock at 294912, Group descriptors at 294913-295262
  Backup superblock at 819200, Group descriptors at 819201-819550
  Backup superblock at 884736, Group descriptors at 884737-885086
  Backup superblock at 1605632, Group descriptors at 1605633-1605982
  Backup superblock at 2654208, Group descriptors at 2654209-2654558
  Backup superblock at 4096000, Group descriptors at 4096001-4096350
  Backup superblock at 7962624, Group descriptors at 7962625-7962974
  Backup superblock at 11239424, Group descriptors at 11239425-11239774
  Backup superblock at 20480000, Group descriptors at 20480001-20480350
  Backup superblock at 23887872, Group descriptors at 23887873-23888222
  Backup superblock at 71663616, Group descriptors at 71663617-71663966
  Backup superblock at 78675968, Group descriptors at 78675969-78676318
  Backup superblock at 102400000, Group descriptors at 102400001-102400350
  Backup superblock at 214990848, Group descriptors at 214990849-214991198
  Backup superblock at 512000000, Group descriptors at 512000001-512000350
  Backup superblock at 550731776, Group descriptors at 550731777-550732126
  Backup superblock at 644972544, Group descriptors at 644972545-644972894

leigh123linux · #48 2nd December 2011, 05:04 PM

Ok try

Code:

su
e2fsck -f -b 98304 /dev/md127
fsck.ext4 -v -f -y /dev/md127

Tamater · #49 2nd December 2011, 05:13 PM

should I do a -y on that e2fsck -f -b 98304 /dev/md127? It is giving me lots of confirmations...

leigh123linux · #50 2nd December 2011, 05:15 PM

Quote:

Originally Posted by Tamater

should I do a -y on that e2fsck -f -b 98304 /dev/md127? It is giving me lots of confirmations...

Yes

Tamater · #51 2nd December 2011, 05:22 PM

actually, with a -y it stops at

Quote:

Group 32767's inode bitmap at 536870912 conflicts with some other fs block.
Relocate? yes

for a long time and then does this:

Quote:

Inode 86769665 has an invalid extent node (blk 347218706, lblk 0)
Clear? yes

e2fsck: e2fsck_read_bitmaps: illegal bitmap block(s) for RAID
e2fsck: aborted

---------- Post added at 12:22 PM ---------- Previous post was at 12:16 PM ----------

running the second line....

a whole lot of

Code:

Group descriptor 44711 checksum is invalid.  FIXED.
Group descriptor 44712 checksum is invalid.  FIXED.
.....
.....

last lines:

Code:

Resize inode not valid.  Recreate? yes



Pass 1: Checking inodes, blocks, and sizes
Inode 86769665 has an invalid extent node (blk 347218706, lblk 0)
Clear? yes

fsck.ext4: e2fsck_read_bitmaps: illegal bitmap block(s) for RAID
e2fsck: aborted

leigh123linux · #52 2nd December 2011, 05:25 PM

Post

Code:

dumpe2fs /dev/md127 | grep -i "block size"

Tamater · #53 2nd December 2011, 05:46 PM

Code:

[root@spectrum meg]# dumpe2fs /dev/md127 | grep -i "block size"
dumpe2fs 1.41.12 (17-May-2010)
Block size:               4096

---------- Post added at 12:46 PM ---------- Previous post was at 12:32 PM ----------

did you just write this then delete it?

Code:

Ok I'm out of ideas, this command could be fatal



Code:
---------
su
mke2fs -S 4096 /dev/md127

leigh123linux · #54 2nd December 2011, 06:12 PM

Quote:

Originally Posted by Tamater

Code:

[root@spectrum meg]# dumpe2fs /dev/md127 | grep -i "block size"
dumpe2fs 1.41.12 (17-May-2010)
Block size:               4096

---------- Post added at 12:46 PM ---------- Previous post was at 12:32 PM ----------

did you just write this then delete it?

Code:

Ok I'm out of ideas, this command could be fatal



Code:
---------
su
mke2fs -S 4096 /dev/md127

Yes don't execute those commands.

Tamater · #55 2nd December 2011, 06:13 PM

ok....I didn't.

leigh123linux · #56 2nd December 2011, 06:45 PM

Ok try

Code:

e2fsck -C0 -p -f -v /dev/md127

Tamater · #57 2nd December 2011, 06:48 PM

Code:

[root@spectrum meg]# e2fsck -C0 -p -f -v /dev/md127
RAID: Resize inode not valid.  

RAID: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
	(i.e., without -a or -p options)

leigh123linux · #58 2nd December 2011, 06:49 PM

Ok

Code:

e2fsck -C0 -f -v /dev/md127

Tamater · #59 2nd December 2011, 06:56 PM

Code:

.....
.....
....
Group descriptor 44709 checksum is invalid.  FIXED.
Group descriptor 44710 checksum is invalid.  FIXED.
Group descriptor 44711 checksum is invalid.  FIXED.
Group descriptor 44712 checksum is invalid.  FIXED.
Resize inode not valid.  Recreate<y>? yes

Pass 1: Checking inodes, blocks, and sizes
Inode 86769665 has an invalid extent node (blk 347218706, lblk 0)              
Clear<y>? yes

e2fsck: e2fsck_read_bitmaps: illegal bitmap block(s) for RAID
e2fsck: aborted

Tamater · #60 5th December 2011, 03:27 PM

Hi Leigh,

Any more ideas?