DebianThis forum is for the discussion of Debian Linux.
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.
I've looked all over and don't understand it. You configure the VM with x amount of disk space and that should be transparent to the O.S. (Debian 6.0) if it's local or remote RAID storage. If you have a RAID controller, it should present the storage as one solid disk and then you can carve it up as you feel fit.
I've tried RHEL 6, Arch Linux, Ubuntu Server 10.10, Slackware, & Gentoo and Debian is the only one with this problem. It's flooding my logs to the point that I can't even run this as a O.S. I also reinstalled 3 times.
I don't know if there are any negative implementations to disabling this service or why Debian even elected to install / use this to begin with. Anyone know? Obviously I'm running this on a server with a hardware RAID controller from Dell (PERC 5i) so there is no need to run software RAID or 'mdadm'.
I may be missing something, but mpt-statusd deals with hardware raid. If you are getting message from your raid them perhaps the raid pair is either being rebuilt or needs to be? mdadm deals with software raid. I think at least some of the Dell Hardware Raid products use LSI chips or boards and that is what mpt-statusd is looking at.
I know that on our server I had to manually during bootup force the LSI card to start the rebuild of our array. It continued to do so through a series of reboots until the job was done. I got an email saying it was in "non-optimal status" and then one that said it was fixed. Hope this helps.