Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
More information needed. What is your distro? What is your machine? Do you have a dump file in your sys logs, that may point to the reason for the crash? It appears, from your post, you have not yet followed the kernel message, about checking syslog, and dmesg. Do this, as it will give us the information we need to hunt down the reason for the crash.
I did notice an entry regarding, an illegal bitmap block in /home.
Sadly it may be that your SATA disk is broken, some how not really likely, yet.
As a last resort, you may have to do a re-install. However, this will probably not save any vital data on the disk. Sadly, again, if your inode and super blocks have been corrupted, it may be too late.
Of course, I am not a guru, simply a hobbyist user, so some one who actually has more education in the system may be of a lot more help to you.
My apologies for not responding sooner. You have the bad misfortune
of having your disk go south the day before the Kernel Summit and
Ottawa Linux Symposium started, so many of the ext2/3 hackers have
been rather busy and distracted for this past week.
It looks like your block group descriptors have gotten totally
trashed. You mentioned that your backup superblock didn't seem to
have anything useful; did you try any of the other backup superblocks?
You can find their locations by using "mke2fs -n /dev/hda1". The -n
option cause mke2fs to not actually *do* anything, but just display
what it would have displayed when it ran, which includes printing out
the backup superblock blocks. Something that might be worth doing is
to use dumpe2fs, specifying the block size and backup superblock
location, and see if any of the backup locations look sane. Checking
to see if the backup group descriptors are showing the same or
different information from the primary would also be of interest in
trying to determine what actually happened.
If you can't find any good backup group descriptors, something to try
is the -S option to mke2fs. You didn't specify how big this
filesystem was, but if you can manage to do a disk-to-disk image
backup, it would be a good idea to do this before you try mke2fs -S,
since this will overwrite the superblock and block group descriptors
with newly initialized versions. This has the potential of completely
trashing your filesystem if you don't specify *exactly* the same
arguments to mke2fs as you used when you first created the filesystem
(i.e., the blocksize, number of blocks, filesystem type if you
specified it, etc., all have to be exactly the same). Read the man
pages for more details, but as a last resort, it's certainly worth a
The crash is due to a power cut and I'm running Mandriva 2007 i586. There was no trace in the system log files. I don't think the disk itself is damaged. Furthermore, other (bootable) partitions on the same disk are doing fine. I don't wish to reinstall anything on /home or to format as I will loose my data.
Anyone else that could help me with mounting this /home partition again?