Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

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.

Had a raid 50 set up last week on a new server and it seemed to work. I set it up from a pair of 3 disk raid 5 arrays and put a JFS filesystem on it. So far all good. I even put data on it (that I'd like to keep!).

Today when I booted up the machine (possibly the first reboot since I put data on the raid) I found that i could not mount /dev/md2. I get:

mount: wrong fs type, bad option, bad superblock on /dev/md2,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

I did actually reboot once (i remember not being silly enough not to test this) while some data was on it and that was fine. When I boot up, md0 and md1 are autodetected and start, but md2 does not - but i can simply do a mdadm --assemble /dev/md2 /dev/md[01] and then mount /dev/md2 and it was working. But now it starts and will not mount.

Does anyone have any ideas? Why would a JFS filesystem not mount? I can only assume that something weird is going on in the underlying raid which has corrupted the filesystem? No data has been written to the disks between it working and not working, so in theory the FS is still intact.