similar to: Install CentOS 6.3 to partitionable mdadm array

Hi, I've written two small howtos, and would like to contribute them to the CentOS Wiki. The first one is "How to install CentOS 5 on software partitionable mdadm RAID1", and the second one "How to repair a software mdadm RAID5 with two or more failed disks (if you know that information is still on the disks and readable)". I think that the first one should be somewhere

Environment: CentOS 6.2 amd64 (min. server install) 2 virtual hard disks of 10GB each Linux KVM Following the instructions on CentOS Wiki <http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1> I installed a min. server in Linux KVM setup (script shown below) <script> #!/bin/bash nic_mac_addr0=00:07:43:53:2b:bb kvm \ -vga std \ -m 1024 \ -cpu core2duo \ -smp 2,cores=2 \

Hi All, I am trying to create an MD device. I am using the command: /sbin/mdadm --create --a /dev/md12 --level=1 --run --raid-devices=2 /dev/sda12 /dev/sdb12 to create the device, and to dynamically create the device file if needed. What I want is the device file to be created as /dev/md12, but with the -a flag it creates it as /dev/md<first unwsed minor number>. I have tried various

Hello Since linux 2.6, the md layer has a feature called partitionable arrays. So instead of having two disks, creating an identical partition table on both and then putting those partitions in RAID 1, you take those two disks and put them in one partitionable RAID 1 array (in mdadm terms, "mdp") and create a partition table on the new RAID device. The advantages are quite clear

I have some suggested tweaks and changes to http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 1. The user should be instructed to start rescue mode with networking in order to be able to retrieve the patch for mkinitrd. 2. The command to create /etc/mdadm.conf will result in an extra line "spares=1" while the array is still syncing. Adding " | head -1 " to the

Hello folks, I am experiencing a weird problem at bootup with large RAID-6 arrays. After Googling around (a lot) I find that others are having the same issues with CentOS/RHEL/Ubuntu/whatever. In my case it's Scientific Linux-6 which should behave the same way as CentOS-6. I had the same problem with the RHEL-6 evaluation version. I'm posting this question to the SL mailing list

Hi all! I'm building up a new box and plan to use Centos 5 on it. i've got a pair of SATA 320 GB drives to make a RAID1. I'm trying to follow the "howto" on the centos wiki for making a "partitionable RAID" installation. Given that my partition scheme has a separate /boot partition, while the one in the HOWTO apparently does not, I've had to tweak the steps

Hi. The following HowTo on the CentOS Wiki: http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 valid for CentOS 5, has not been updated to CentOS 6, yet. I found it very useful during the glorious CentOS 5 days and now that I've successfully ported my RAID1 experience to CentOS 6, I'd like to share it with the Community. The title of the HowTo is currently: "How to

Hi. The following HowTo on the CentOS Wiki: http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 valid for CentOS 5, has not been updated to CentOS 6, yet. I found it very useful during the glorious CentOS 5 days and now that I've successfully ported my RAID1 experience to CentOS 6, I'd like to share it with the Community. The title of the HowTo is currently: "How to

Hi, After reading the tutorial at http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 I have the following question: What should I put instead of splashimage=(hd0,0)/grub/splash.xpm.gz and root (hd0,0) on /etc/grub.conf? Should I leave those lines untouched? If so, how would grub know where to boot from if /dev/sda fails? Or I would need to swap the drives in order to boot

On the wiki page for creating a mirrored root drive, at <https://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1>, it first tells you, in the install, to chose manual partitioning, and to leave at least 1M at the end of the drive.... and then it tells you to create the RAID 1 using /dev/sda and /dev/sdb - the *whole* raw drives. mark, currently creating a RAID 1 using just

Trying to install Centos6 on my system (it's been running C5 for years). I've got a pair of drives, so I'm trying to use RAID-1. Previously I used a procedure where each partition was part of a separate RAID device, but this time I'm trying the HOWTO from the Centos WIKI on making a partitionable RAID pair. I've been having a lot of problems, but have also been working thru

Greetings - I am preparing to order a new desktop system for work. In general the new system will be a Dell Precision T3610 with two 3 TB drives. I plan on installing CentOS 7 as a KVM host, with virtual machines for Win 7 Pro and Linux Mint. I am looking for some advice or a good how-to on configuring software raid on the two drives, then using LVM for the host and virtual machines. I

Hi! Did anyone tried this on 5.4? having a look on http://wiki.centos.org/HowTos/Install_On_Partitionable_RAID1 is would seem that that mkinitrd patch is no longer required. Can someone ack this? Thanks, Adrian -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3110 bytes Desc: S/MIME Cryptographic Signature URL:

Hi list, I'm new with UEFI and GPT. For several years I've used MBR partition table. I've installed my system on software raid1 (mdadm) using md0(sda1,sdb1) for swap, md1(sda2, sdb2) for /, md2 (sda3,sdb3) for /home. From several how-to concerning raid1 installation, I must put each partition on a different md devices. I've asked times ago if it's more correct create the

I'm using Centos 4.5 right now, and I had a RAID 5 array stop because two drives became unavailable. After adjusting the cables on several occasions and shutting down and restarting, I was able to see the drives again. This is when I snatched defeat from the jaws of victory. Please, someone with vast knowledge of how RAID 5 with mdadm works, tell me if I have any chance at all

From: Nikolay Ivanets <stenavin@gmail.com> Inspection code checks /etc/mdadm.conf to map MD device paths listed in mdadm.conf to MD device paths in the guestfs appliance. However on some operating systems (e.g. Ubuntu) mdadm.conf has alternative location: /etc/mdadm/mdadm.conf. This patch consider an alternative location of mdadm.conf as well. --- daemon/inspect_fs_unix_fstab.ml | 13

Hello all, I have run into a sticky problem with a failed device in an md array, and I asked about it on the linux raid mailing list, but since the problem may not be md-specific, I am hoping to find some insight here. (If you are on the MD list, and are seeing this twice, I humbly apologize.) The summary is that during a reshape of a raid6 on an up to date CentOS 6.3 box, one disk failed, and

md_create: mdadm: boot: mdadm: boot is not a block device. at /home/rjones/d/libguestfs/images/guest-aux/make-fedora-img.pl line 95. Looking into this, it appears the old version of mdadm shipped in Ubuntu (mdadm 2.6.7) doesn't support the notion of giving arbitrary names to devices. Thus you have to do: mdadm --create /dev/md0 [devices] We do: mdadm --create boot [devices] which it

Alessandro Baggi wrote: > Il 29/01/19 15:03, mark ha scritto: > >> I've no idea what happened, but the box I was working on last week has >> a *second* bad drive. Actually, I'm starting to wonder about that >> particulare hot-swap bay. >> >> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added /dev/sdi1... >> but see both /dev/sdh1 and