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.
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.
I use opensuse 11.3. Tried to fsck root using the latest systemrescuecd and got a bad magic number error message. I tried the suggested alternate superblock command and got the same error message. The command I used was "fsck.ext4 /dev/sdc2". When I tried using tune2fs to force fsck at boot, I got the same error message. The system seems to be working more or less ok. What's going on and what should I do to run fsck on root?
To start with, what happened that you want to force fsck? Do you suspect some data has been damaged?
Could you post the exact error message you are receiving? Are there any relevant kernel messages when you try and mount the volume or run fsck against it?
I can't quote it but the gist of it was 'bad magic number, corrupted superblock'.
The message with tune2fs was similar except it suggested tring an alternate block. That didn't work. Same error.
The only fsck was with / which should not be mounted.
I'm trying because there have been several hard freezes in the last month and today I got an odd mysql error message with my mail program. Seemed like a good time to fsck.
The strange thing is that it's mostly working just fine.
How did you determine the alternate superblock to use ?.
fsck from a liveCD is the correct procedure - you might just have to back it up and reformat it.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
Try the boot parameter init 1. Just insert it on the kernel line in grub. Nothing will be mounted but the ramdrive. Type fsck without any device or parameters, and read the instructions! I think you want the "-p" switch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.