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!
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.
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.
bad magic number in super-block while trying to open /dev/xxx
encrypted ext4 partition - gpt file system - raid 5 system
is this normal on ext4 partition, should i try zfs? am near capacity, is that a possibility? this is the 3rd time i got this and fsck fixed this in the past. tia
What errors? Does your syslog say someting?
Try tune2fs -l /dev/xxx next time, just to see what's in that superblock. Apart from the magic number, do the other values make sense?
I don't think it's normal that the superblock is corrupted on any type of filesystem, even when getting full.
Couldn't find valid filesystem superblock when running tune2fs -l. syslog doesn't say anything and hasn't said anything other than to run the e2fsck. got the other values by googling.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.