Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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'm trying to install SLES 11.1 on an intel atom (intel D510M0 Motherboard).
During the install, SLES automatically configures two md containers, /dev/md127 (intel matrix storage manager container as far as I can tell), and /dev/md126 (6 drive raid 0 array).
I have only a single intel x25M in the system, however, so I'm not sure where its picking up the 6 drive raid 0 array from. Since /dev/sda is a part of md126, I cannot partition or install on /dev/sda, and obviously I can't install on the non fucntional raid array specified in /dev/md126.
I've attempted to remove /dev/md127 and /dev/md126 by using ctrl-alt-F2 to get into a shell and running mdadm --stop /dev/md127 and running mdadm --remove /dev/md127 (same procedure for md126). Unfortunatly as soon as I ctrl-alt-f7 toreturn to the GUI installer, the md devices return. I'm not sure what automated processes is creating the raid arrays, and there is no config file for md for me to edit that I can find on the system.
Any thoughts out there on what to do stop the creation of md126 and md127 or some how shut down the process that is readding them?
Distribution: pclos2016, Slack14.1 Deb Jessie, + 50+ other Linux OS, for test only.
Recommended : Prepare the partitions, before the Suse install.
Use e.g. the "Gparted Livecd", which also is the best choice for the
partitioning. You will need one partition " / " and a swap.
( And may be a " /home ".)
A) Installation Settings : Please click "Partitioning"
B) Choose : Custom partitioning.
C) Expert Partitioner :
Highlight the partition, you want to use, and click it.
C-1) Expert Partitioner : Hit the "Edit" button.
D) Tick : "Format Partition" ( And choose filesystem.)
... And tick : 'Mount partition/Mount point' and set " / ".
That's it. And you can hit "Finish", "Accept", etc.
I have tried using knoppix to boot and then using fdisk and mk2fs to create the partions on the disk. That works great, but when I boot off of the SLES 11.1 DVD, it creates md126 / 127 automatically and does not give me the option to directly access sda1, as sda1 is already a member of the raid set md126. I have also tried the boot option raid=noautodetect, but that has no effect on the creation of md126 / md127 either.
I'll see if I can grab some screen shots, but that can be a bit tricky given the fact that I'm installing the OS.
I'm also exploring using autoyast to just create the partitions via a autoyast xml file. That may allow me to bypass the auto creation of the raid array as well.