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.
it is a newly installed Gentoo Linux and seems not successful
i got the following message while booting:
* checking all filesystems...
fsck.ext2 : No such file or directory while trying to open /dev/BOOT
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem(and not swap or ufs or something else). than the superblock is corrupt and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>.
* Fsck could not correct all errors, manual repair needed [!! ]
what can i do to fix this problem? and what is superblock?
As a brand new Gentoo installation, i'd guess that you've not updated /etc/fstab correctly, as /dev/BOOT is a default entry there, and if you'd edited that yourself you'd be asking your question in a different way so i'd say nip back to the install doc at gentoo.org and find the part about fstab editing. if you are unsure how you've partitioned your system, run "fdisk -l" and that should tell you what you'd need.
I am using mandrake linux 9.2 and ebery thing was working fine but I resized a partition through WINDOWS XP (that partition was of FAT filesystem). But on next boot GRUB was corrupted, I reinstalled it and boot LINUX but it gave me exactly the same errors?
I have tried
e2fsck -b 8193 /dev/hda9
but it told that it can't open /dev/hda9 due to corrupted superblock and ........
What should I do now? please help me as I am unable to boot LINUX now.
My root partition is /dav/hda7
SWAP partition is /dev/hda8
/usr partition is /dev/hda9
and it is affected.
my experience is that windows and windows tools do messy things with foreign partition.
Sometimes their not even nice to there own flavor of formats.
My recomondation is to never resize a fat or ntfs partition in windows. there are linux tools which do the job just a liittte better. ( at least for ntfs, as much as i know )
its possible that windows has screwd up your partition table. You might wanna compare with the one you've had bevore.
ohh you didnt save the partiton table? too bad.
you could trie some repair tools, but their doomed to fail.
And if thats your /usr partition its not worth it anyways. ( if some files wont be recovered or named wrongly your system will be screwed up anyways )
my tip to you is.
reinstall. its most probably the fastest and the most clean solution
Yeah it was may big mistake that I hadn't save my partition table. Now it was very great system, I managed and mintained it very well and installed a lot of updates and packages from net, so now I want to recover it on any expense, pplease tell me about it.
Today I ran several commands including e2fsck, debugfs and mke2fs, one of them gave me the location of alternates superblock, and they were 32768, 98304 and 163840, I tried as
e2fsck -b 32768 /dev/hda9
it checked it and I recieved a message that filesystem was modified, I then ran fsck but it again gave me the previous error message that superblock is corrupted. I now ran with 98304 and it again did preety well stuffs including making and fixing group, inode errors, the system remained busy for almost 3 minutes but on running fsck it worked and said that filesystem is good, I rebooted but again gave the same errors but this time the fsck was looking for /dev/hda11 and the considerable thing is that my HDD doesn't contain /dev/hda11, instead on /dev/hda7 and /dev/hda9 it said that every thing is OK. WHat can I do now that the fsck doesn't look for hda11 instaed of hda9?
Any way thanks for ur reply.
what do ou mean? they all fail? or nothing even tries to start? do you get a login?
also please do not hijack threads. when you have a problem, start new, well written thread in the approriate forum. your problem has nothing in common with the original one, other than the word "superblock"
The first message I got is the fail message of activating swap after that it mounts my /usr partition but after that I recieve a long list of fail messages in front of many services, and after that I got login but only in console, the X server doesn't start. I think that I did wrong wrong by updating superblock because I just had to update my /etc/fstab and change the root device from /dev/hda11 to /dev/hda10 but now what should I do?
I am thinking of starting new thread but I found that in searching google so I posted here otherwise I was going to post a new one.
Thank U very much.