Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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:
Quote:
mount /dev/sdb3 /backup -t ext3
mount: wrong fs type, bad option, bad superblock on /dev/sdb3,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
In kern.log, here is the reported error:
Quote:
kernel: ext3: No journal on filesystem on sdb3
Do you have any idea of what I could do to fix this problem and to be able to read again my data?
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;
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:
Quote:
kernel: ext3: No journal on filesystem on sdb3
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?
Last edited by stratogratte; 03-24-2006 at 12:57 PM.
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...
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...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.