Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
We have a Sun X4270 with 16 disks. I am having an odd problem where raid devices are not being ignored by LVM and raid devices are geting hosed after reboots.
This system is running kernel 2.6.18-220.127.116.11.2.el5. (64-bit)
/dev/sda is the system disk and is cold-mirrored to /dev/sdf. The remaining devices are being used to create a 14-device raid5 device - /dev/md0.
Each of the disks to be used in the raid device are partitioned as so:
Disk /dev/sdb: 36472 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdb1 0+ 36471 36472- 292961308+ fd Linux raid autodetect
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
The problem is that you're using partition ID fd for your RAID partitions and you're loading device mapper at boot. Device mapper and md volumes are two very different things.
Seeing partitions with ID fd, device mapper will look for LVM metadata on your volumes. Of course, you're not actually using device mapper/LVM, so this cannot possibly work. Unfortunately, it seems device mapper finds something that resembles LVM metadata and tries to set up LVM volumes accordingly.
Possible solutions: Don't use partition ID fd and/or don't load the device mapper kernel modules at boot (or at all).