Mount problem - Bad superblock
 

Hi
I have a big problem with my second HDD on my dedicated server.
When I try to mount the HDD to be able to read my files on it, I get the following error:

In kern.log, here is the reported error:
Do you have any idea of what I could do to fix this problem and to be able to read again my data?


Thank you for your help...

The command is incorrect;
mount -t ext3 /dev/sdb3 /backup
note /backup must be a valid directory under /

That's exactly the same command/same result.
And /backup directory exists and is a valid directory.

??? The commands are very different you failed to define the parameters for mounting the device. i.e. the parameters must be specified before the device -t ext3.

If the device is not a valid ext3 file system then do;

tune2fs -j /dev/sdb3

It seems like -t ext3 being before or after the device doesn't change anything for the command to work properly...

What exactly will do the "tune2fs -j /dev/sdb3" command?
(I am afraid of loosing all my data)

tune2fs -j will convert an ext2 file system into a journalised ext3 file system.

to explain mount -t ext3;
-t ext3 =file system type ext3
if you unsure of the file system type do cfdisk /dev/sdb and it will list the partitions on the drive with their file type.

I know perfectly ext3 is the filesystem type...
The problem isn't that sdb3 is ext2 type, the problem is the following error:
What I presume means that the partition table of sdb3 is corrupted. Is it really the problem? What can I do the fix it?

EDIT:
Strange!!!! sdb3 is indeed an ext2 type O_O It should have been an ext3. What could have happened?
Is the tune2fs -j command secure to be applied?

EDIT2:
The problem is that if I mount sdb3 in ext2, there is no data at all. If I convert it in ext3, will my data be back?

So what should I do safely enough to no risk to lose my data? :)

Its telling you;
kernel: ext3: No journal on filesystem on sdb3

that's how I knew that it was probably ext2. To convert it do tune2fs -j /dev/sbd3. It does not affect the data but creates a journal. What this does is record the destination of writes every 5s. Are you certain that you have written data to this partition?

In fact the HDD partially crashed recently but was fixed. After it was fixed, I got all my data again, but since some hours now, I don't know how, I have these problems. My thought is that the table partition(the journal) has crashed, and so that the system think it is ext2, but it should be ext3...

run a scan on the unmounted disk;

e2fsck /dev/sdb6

e2fsck /dev/sdb3
e2fsck 1.37 (21-Mar-2005)
/dev/sdb3: clean, 11/19464192 files, 610802/38925495 blocks

So what I still do the tune2fs -j /dev/sbd3 command?
What do you think about my e2fsck result?

The scan indicates nothing wrong so go ahead and add the journal with tune2fs.

So the command will make my data come back? :/