Hans-Joachim Picht
2005-Mar-22 20:43 UTC
ext2fs_read_bb_inode: Invalid argument && Can't read an block bitmap
Hello,
sorry if the question was asked a couple of times before but I couldn't
find any useful hinds to this problem using google and the listman
search-engine of the archive of this list.
Somehow the ext3 filesystem on one of my machines died an after a reboot
grub wouldn't come up again.
What I did so far:
fsck -y /dev/hda4
fsck 1.35 (28-Feb-2004)
e2fsck 1.35 (28-Feb-2004)
Group descriptors look bad... trying backup blocks...
Block bitmap for group 0 is not in group. (block 2553887680)
Relocate? yes
Inode bitmap for group 0 is not in group. (block 16777216)
Relocate? yes
Inode table for group 0 is not in group. (block 2238581760)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate? yes
[ more like this ]
Block bitmap for group 127 is not in group. (block 0)
Relocate? yes
Inode bitmap for group 127 is not in group. (block 0)
Relocate? yes
Inode table for group 127 is not in group. (block 0)
WARNING: SEVERE DATA LOSS POSSIBLE.
Relocate? yes
fsck.ext2: e2fsck_read_bitmaps: illegal bitmap block(s) for /dev/hda4
dd if=/dev/hda of=/dev/sda conv=noerror,sync
dumpe2fs /dev/sda4
dumpe2fs 1.35 (28-Feb-2004)
ext2fs_read_bb_inode: Invalid argument
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: a300ff1d-5cf0-4d8a-9336-ae39bc64ed95
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype sparse_super large_file
Default mount options: (none)
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 7274496
Block count: 14542841
Reserved block count: 727142
Free blocks: 1454431
Free inodes: 4906461
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Last mount time: Thu Mar 17 09:17:22 2005
Last write time: Tue Mar 22 18:11:10 2005
Mount count: 35
Maximum mount count: 100
Last checked: Thu Mar 3 09:12:04 2005
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
First orphan inode: 775060
Journal backup: inode blocks
Group 0: (Blocks 0-32767)
Primary superblock at 0, Group descriptors at 1-4
Block bitmap at 2553887680, Inode bitmap at 16777216 (+16777216)
Inode table at 2238581760-2238582271
5376 free blocks, 4096 free inodes, 0 directories
Group 1: (Blocks 32768-65535)
Backup superblock at 32768, Group descriptors at 32769-32772
Block bitmap at 0, Inode bitmap at 822088960 (+822056192)
Inode table at 33554432-33554943 (+33521664)
20480 free blocks, 6016 free inodes, 0 directories
Group 2: (Blocks 65536-98303)
Block bitmap at 33554432 (+33488896), Inode bitmap at 2789758720
Inode table at 33554432-33554943 (+33488896)
[...]
Group 443: (Blocks 14516224-14542840)
Block bitmap at 14516224 (+0), Inode bitmap at 14516225 (+1)
Inode table at 14516231-14516742 (+7)
20485 free blocks, 16165 free inodes, 0 directories
dumpe2fs: /dev/sda4: error reading bitmaps: Can't read an block bitmap
dumpe2fs -b /dev/sda4
dumpe2fs 1.35 (28-Feb-2004)
ext2fs_read_bb_inode: Invalid argument
Any hinds what to do?
With best regards,
Hans-Joachim Picht
--
Picht Consulting http://www.picht.org
Hans-Joachim Picht hans at picht.org
Eichgaertenallee 88 Tel. +49 (0)641 41 600
35394 Giessen, Germany Fax. +49 (0)641 41 300
Hans-Joachim Picht
2005-Mar-23 22:12 UTC
ext2fs_read_bb_inode: Invalid argument && Can't read an block bitmap
On Tue, Mar 22, 2005 at 09:43:25PM +0100, Hans-Joachim Picht wrote: Hello, even if I reply to my own posting, I presuaded fsck to produce some probaly more helpful output which might help to find someone who gives an advice how to fix this> sorry if the question was asked a couple of times before but I couldn't > find any useful hinds to this problem using google and the listman > search-engine of the archive of this list. > > Somehow the ext3 filesystem on one of my machines died an after a reboot > grub wouldn't come up again. > > What I did so far:fsck -n /dev/hda4 resulted in fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004) Group descriptors look bad... trying backup blocks... Block bitmap for group 0 is not in group. (block 2553887680) Relocate? no Inode bitmap for group 0 is not in group. (block 16777216) Relocate? no Inode table for group 0 is not in group. (block 2238581760) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? no [...] Block bitmap for group 127 is not in group. (block 0) Relocate? no Inode bitmap for group 127 is not in group. (block 0) Relocate? no Inode table for group 127 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? no /dev/hda4 was not cleanly unmounted, check forced. Error reading block 2238581760 (Invalid argument). Ignore error? no fsck.ext3: Invalid argument while reading bad blocks inode This doesn't bode well, but we'll try to go on... Pass 1: Checking inodes, blocks, and sizes Illegal block number passed to ext2fs_test_block_bitmap #2238581760 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #2238581760 for in-use block map Illegal block number passed to ext2fs_test_block_bitmap #2238581761 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #2238581761 for in-use block map Illegal block number passed to ext2fs_test_block_bitmap #2238581762 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #2238581762 for in-use block map Illegal block number passed to ext2fs_test_block_bitmap #2238581763 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #2238581763 for in-use block map [...] Illegal block number passed to ext2fs_test_block_bitmap #167772670 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #167772670 for in-use block map Illegal block number passed to ext2fs_test_block_bitmap #167772671 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #167772671 for in-use block map Illegal block number passed to ext2fs_test_block_bitmap #33554432 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #33554432 for in-use block map Illegal block number passed to ext2fs_test_block_bitmap #2892119552 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #2892119552 for in-use block map Error reading block 2238581760 (Invalid argument) while doing inode scan. Ignore error? no Error reading block 2238581760 (Invalid argument) while doing inode scan. Ignore error? no Error while scanning inodes (0): Can't read next inode e2fsck: aborted With best regards, Hans-Joachim Picht -- Picht Consulting http://www.picht.org Hans-Joachim Picht hans at picht.org Eichgaertenallee 88 Tel. +49 (0)641 41 600 35394 Giessen, Germany Fax. +49 (0)641 41 300
Apparently Analagous Threads
- [jonathan.picht@web.de: Bug#133557: flac: --fast and --best switches (as in gzip and bzip2) would be nice]
- recovery system
- The computer hangs while booting the kernel
- [jonathan.picht@web.de: Bug#133557: flac: --fast and --best switches (as in gzip and bzip2) would be nice]
- Seriously corrupt ext3 root filesystem - help?