similar to: how to replace a raid drive with mdadm

Hi all; I cross posted this to the fedora list since we use Fedora as a test bed from time to time, however given this is a production server we'll likely be running CentOS. we've just ordered a new server (http://www.spectrumservers.com/ssproducts/pc/viewPrd.asp?idcategory=26&idproduct=787) Originally I tried to simply upgrade an older server with more drive space, I

Hi all; does anyone know if the following packages are available (via yum) for CentOS 6 and if so which repo they come from? Thanks in advance... kmymoney darktable digiKam -- --------------------------------------------- Kevin Kempter - Constent State A PostgreSQL Professional Services Company www.consistentstate.com ---------------------------------------------

hi all! back in Aug several of you assisted me in solving a problem where one of my drives had dropped out of (or been kicked out of) the raid1 array. something vaguely similar appears to have happened just a few mins ago, upon rebooting after a small update. I received four emails like this, one for /dev/md0, one for /dev/md1, one for /dev/md125 and one for /dev/md126: Subject: DegradedArray

Hi All; I've downloaded the Cisco AnyConnect tar.gz file for one of our clients, when I untar it and then run the vpn_install script in the vpnclient directory I get the below error. Thanks in advance for any help... / //# ./vpn_install// //Cisco Systems VPN Client Version 4.8.02 (0030) Linux Installer// //Copyright (C) 1998-2006 Cisco Systems, Inc. All Rights Reserved.// // //By

I just upgraded my home KVM server to CentOS 6.0 CR to make use of the latest libvirt and now my RAID array with my VM storage is missing. It seems that the upgrade to mdadm-3.2.2 is the culprit. This is the output from mdadm when scanning that array, # mdadm --detail --scan ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b ARRAY /dev/md126 metadata=imsm

> On 2/24/19 9:01 PM, Jobst Schmalenbach wrote: >> I tried to delete the MDX, I removed the disks by failing them, then >> removing each array md0, md1 and md2. >> I also did >> >> dd if=/dev/zero of=/dev/sdX bs=512 seek=$(($(blockdev --getsz >> /dev/sdX)-1024)) count=1024 > > > Clearing the initial sectors doesn't do anything to clear 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

Hi All; anyone have any info on setting up a L2TP over IPSEC client vpn connection? Thanks in advance

Hi. CENTOS 7.6.1810, fresh install - use this as a base to create/upgrade new/old machines. I was trying to setup two disks as a RAID1 array, using these lines mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdc1 mdadm --create --verbose /dev/md1 --level=0 --raid-devices=2 /dev/sdb2 /dev/sdc2 mdadm --create --verbose /dev/md2 --level=0 --raid-devices=2

Hi, I have a new server HP proliant DL320 G4, with two 160 GB SATA hdds.. I have installed CentOS 4.5 with mdadm without any problem, but when I disconnect one disk the server does not boot or I received a kernel panic when booting... I have disabled the SATA embeded raid (BIOS) and nothing.. I've also download the driver from HP site HP (Embedded SATA RAID Controller Driver Diskette for Red

Hi. I''m considering an imminent switch from ext4 to btrfs and I''m hoping that someone can lend me advice before I do something unsupported. I have a software raid 6 array configured via mdadm. It was sitting at 8 x 3TB until I recently doubled that, grew the array and found that ext4 doesn''t want to resize. So, I''m looking to: 1. convert from ext4 to btrfs

While creating some arrays this evening, I noticed this line my dmesg: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction. Why is there a 200MBps limitation on the mdadm sync speed? It certainly isn't a concern for my particular systems (15k U320 SCSI) but I can imagine there are much higher end systems that actually could sync at a rate equal

The relevance of this question can be found here: http://aput.net/~jheiss/raid10/ I read the mdadm documents but I could not find a positive answer. I even read the raid10 module source but I didn't find the answer there either. Does someone here know it? Thank you!

I got the email that a drive in my 4-drive RAID10 setup failed. What are my options? Drives are WD1000FYPS (Western Digital 1 TB 3.5" SATA). mdadm.conf: # mdadm.conf written out by anaconda MAILADDR root AUTO +imsm +1.x -all ARRAY /dev/md/root level=raid10 num-devices=4 UUID=942f512e:2db8dc6c:71667abc:daf408c3 /proc/mdstat: Personalities : [raid10] md127 : active raid10 sdf1[2](F)

Hi, When installing CentOS 7, is there a way to 1. leave the GUI installer and open up a console 2. create RAID arrays manually using mdadm --create 3. get back in the GUI installer and use the freshly created /dev/mdX arrays? I tried to do this, but the installer always exits informing me that he can't create the RAID arrays (since they're already created, duh). Any suggestions?

I have a server that has 16 drives in it. They are connected to a 3ware 9650SE-16ML SATA RAID card. I have the card set to export all the drives as JBOD because I prefer Linux to do the reporting of drive and RAID health . I'm using mdadm to create a RAID6 with a hot spare. Doing this I can take the disks and put them on a completely different SATA controller/computer and still have the RAID

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

Hi, I lost my mdadm.conf (and /proc/mdadm shows nothing useful) and I'd like to mount the filesystem again. So I've booted using rescue but I was wondering if I can do a command like this safely (i.e without losing the data previously stored). mdadm -C /dev/md0 --level=raid0 --raid-devices=2 /dev/sda1 /dev/sdb1 Where of course the raid devices and the /dev/x are the correct ones

Hi, what?s the proposed way of handling mdadm in Centos 7? I did not get any notification when a disk in a RAID1 failed, and now that the configuration has changed after resolving the problem, I might be supposed to somehow update /etc/mdadm.conf. Am I not supposed to be notified by default when something goes wrong with an array? How do I update /etc/mdadm.conf? I?m used to all this working

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