cgsecurity.org

It has finished!!!
Success!
fsck has produced many many strings like that:

Free inodes count wrong for group #7308 (8192, counted=8177).
Fix? yes

Directories count wrong for group #7308 (0, counted=1).
Fix? yes

Free inodes count wrong for group #7309 (8192, counted=8190).
Fix? yes

Directories ...

A couple minutes ago I've started fsck with alternate superblock.
Waiting for results...

# fsck.ext4 /dev/sdb2 -y -f -b 32768
e2fsck 1.41.14 (22-Dec-2010)
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/sdb2 ...

I'm sorry for delay.
Here is out from fsck
for sdb2:

# fsck /dev/sdb2 -y
fsck from util-linux 2.20
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdb2
Could this be a zero-length partition?

and for sdb4:

# fsck ...

here it goes

fdisk -l /dev/sdb2

Disk /dev/sdb2: 998.1 GB, 998062948352 bytes
255 heads, 63 sectors/track, 121340 cylinders, total 1949341696 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 ...

I'm sorry for my misunderstanding.
How can I point this partition in fsck command?

/dev/sdb1 ?

I tried to run fdisk. It pointed me, that my disk has GPT partition. Does it mean?

device D-Link 320, pair WD 1Tb installed.

message from fsck
fsck.ext4 -nv -b 32768 -B 4096 /dev/sdb
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext4: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a correct ext2
filesystem. If the device ...

Yes, it was.
Unfortunately, it didn't help.
Maybe, I should pass additional parameters.
I used fsck with "-nv" parameters with/without additional "-b". I used the value for -b parameter which I got from the testdisk diagnostic message.
Tonight, I will reproduce error message from fsck and write it ...

Hi!
A few days ago one of my disks was lost. It was in dns-320 NAS (linux).
I tryed to recover filesystem using testdisk. It hasn't recovered. The filesystem is corrupt despite superblock was fine.
As I'd explored, my disk lost one sector (4096 bytes) in the Descriptors Table. Nothing more, but it ...