Bad root block 0

["Roland Häder" <webmaster@autoinstaller.de>]

Hello,

I have created an image on this way:

dd if=/dev/urandom of=image.file bs=1k count=98288

And I have latest 3.6.11 ReiserFS tools. So I setup the loop-back device:

losetup -e rc6 /dev/loop3 image.file

RC6 need a keysize. I use 256 Bits and entered a password.

I created a ReiserFS on it: mkreiserfs /dev/loop3

This happens all yesterday.

I never used any resizer tools and I did not run reiserfschk while it was mounted. Also my box did not crash while it was mounted.

Today I setup the loop-back device on same way (and same password!) again and try to mount it:

$: mount /dev/loop3 /mnt
mount: Not a directory
$:

Well, /mnt *is* definely a directory...

When I do a reiserfschk --rebuild-tree I got this:

Replaying journal..
0 transactions replayed
###########
reiserfsck --rebuild-tree started at Sun Sep  7 14:22:00 2003
###########
 
Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 8211 blocks marked used
Skipping 8211 blocks (super block, journal, bitmaps) 0 blocks will be read
 
Could not find a hash in use. Using "r5"
        "r5" hash is selected
Flushing..finished
        Read blocks (but not data blocks) 0
                Leaves among those 0
                Objectids found 2
 
Pass 1 (will try to insert 0 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished
 
Flushing..finished
        0 leaves read
                0 inserted
####### Pass 2 #######
Flushing..finished
 
 
No reiserfs metadata found. ... ... ...

And debugreiserfs -d /dev/loop3 shows me this:

debugreiserfs 3.6.11 (2003 www.namesys.com)
 
 
Filesystem state: consistency is not checked after last mounting
 
Reiserfs super block in block 16 on 0x703 of format 3.6 with standard journal
Count of blocks on the device: 24492
Number of bitmaps: 1
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 24492
Root block: 0
Filesystem is cleanly umounted
Tree height: 65535
Hash function used to sort names: "r5"
Objectid map size 2, max 972
Journal parameters:
        Device [0x0]
        Magic [0x9cdd049]
        Size 8193 blocks (including 1 for journal header) (first block 18)
        Max transaction length 1024 blocks
        Max batch size 900 blocks
        Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0xfa02:
        FATAL corruptions exist.
sb_version: 2
inode generation number: 0
UUID: 7691903f-ec2b-4c06-9cf2-eaa545c7db77
LABEL: Haspa-Banking
Set flags in SB:
        ATTRIBUTES CLEAN
65534 expected, 0 found in 0
Block 0 contains unformatted data
print_disk_tree: bad block type (level=0, nr_items=0, free_space=0 rdkey)
File system uses 0 internal + 0 leaves + 0 unformatted nodes = 0 blocks

So, how can I safely fix the image? Or restore needed data (like my Online Banking Keyfile)

Chears,
  Roland Häder