How to repair my lvm volume?

boast · 2012-05-21 03:22:01

I have

# e2fsck -f /dev/media/media 
e2fsck 1.42.2 (27-Mar-2012)
Superblock has an invalid journal (inode 8).
Clear<y>? yes
*** ext3 journal has been deleted - filesystem is now ext2 only ***

The filesystem size (according to the superblock) is 1232118784 blocks
The physical size of the device is 1220943872 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? no
Pass 1: Checking inodes, blocks, and sizes
Group 16623's block bitmap (544702464) is bad.  Relocate<y>? yes
Group 16623's inode bitmap (544702465) is bad.  Relocate<y>? yes

Group 16624's block bitmap (544735232) is bad.  Relocate<y>? yes
Group 16624's inode bitmap (544735233) is bad.  Relocate<y>? yes
Group 16625's block bitmap (544768000) is bad.  Relocate<y>? yes
Group 16625's inode bitmap (544768001) is bad.  Relocate<y>? yes
Group 16626's block bitmap (544800768) is bad.  Relocate<y>? 

..............

Error writing block 1220968637 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Error writing block 1220968638 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Error writing block 1220968639 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Error writing block 1220968640 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Error writing block 1220968641 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Error writing block 1220968634 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Error writing block 1220968635 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Error writing block 1220968636 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes
Error reading block 1220968642 (Invalid argument) while getting next inode from scan.  Ignore error<y>? yes

I couldn't figure out what it said at the end since I had to leave a weight on the enter key to go through all the errors and it overflowed the output. But the other 3 times I've run it, it was something about multiple blocks for one inode and unable to move the inode or something, and then e2fsck aborts.

I had done "e2fsck -cc" and that was a good 3+ days spent which didn't fix it either.

and the setup im dealing with:

Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
81 heads, 63 sectors/track, 382818 cylinders, total 1953525168 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: 0xd8295a24

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048  1953525167   976761560   8e  Linux LVM

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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: 0x49f8bd43

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1              63  1953520064   976760001   8e  Linux LVM

Disk /dev/mapper/media-media: 5001.0 GB, 5000986099712 bytes
255 heads, 63 sectors/track, 608001 cylinders, total 9767550976 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Last edited by boast (2012-05-21 03:29:34)

tomk · 2012-05-21 06:09:08

No idea about your issue, but...

boast wrote:

I had to leave a weight on the enter key to go through all the errors

e2fsck has a -y option for that.

boast · 2012-05-21 12:44:07

tomk wrote:

No idea about your issue, but...
boast wrote:
I had to leave a weight on the enter key to go through all the errors
e2fsck has a -y option for that.

yeah, but the first question asks if you'd like to abort with a default of yes. Unless theres a way to do "no for the first one and yes for the rest" lol

tomk · 2012-05-21 15:10:13

?... never seen that, and I've been using it for years.

Anyway, not relevant here, just thought I'd mention it.

boast · 2012-05-23 00:46:44

finally got to the end of one fsck

Error writing block 1232109568 (Invalid argument) while reading inode and block bitmaps.  Ignore error<y>? yes
Error reading block 1232109569 (Invalid argument) while reading inode and block bitmaps.  Ignore error<y>? yes
Force rewrite<y>? yes
(There are 1 inodes containing multiply-claimed blocks.)
File ... (inode #77003937, mod time Sun Jul  9 12:44:01 1989) 
  has 15 multiply-claimed block(s), shared with 1 file(s):
        <filesystem metadata>
Clone multiply-claimed blocks<y>? yes
Error writing block 1232109569 (Invalid argument).  Ignore error<y>? yes
Recreate journal<y>? yes
Creating journal (32768 blocks): 
 Done.
*** journal has been re-created - filesystem is now ext3 again ***
e2fsck: aborted
/dev/media/media: ***** FILE SYSTEM WAS MODIFIED *****
/dev/media/media: ********** WARNING: Filesystem still has errors **********

edit: I consider it gone forever now. Googled and tried everything I found with no luck. Using photorec now to recover what I can.

Last edited by boast (2012-05-24 21:52:39)

nelsontk · 2017-03-18 22:33:21

For anyone with this issue now, typing a capital A will answer yes to all.

Trilby · 2017-03-18 23:10:58

Given that this was 5 years ago, I doubt they are still waiting for an answer.

Please do not necrobump old threads.

Closed.

Arch Linux

#1 2012-05-21 03:22:01

How to repair my lvm volume?

#2 2012-05-21 06:09:08

Re: How to repair my lvm volume?

#3 2012-05-21 12:44:07

Re: How to repair my lvm volume?

#4 2012-05-21 15:10:13

Re: How to repair my lvm volume?

#5 2012-05-23 00:46:44

Re: How to repair my lvm volume?

#6 2017-03-18 22:33:21

Re: How to repair my lvm volume?

#7 2017-03-18 23:10:58

Re: How to repair my lvm volume?

Board footer