similar to: Problem with RAID following update

Hello all, In the process of building a new VM box to replace several individual CentOS servers, I've had the "interesting" experience of running both CentOS-5.5 and RHEL-6 (eval copy) as I build out the hardware based on a Supermicro motherboard. A couple of observations regarding RAID-6: - RAID-6 arrays created on RHEL-6 don't seem backward compatible with CentOS-5.5.

> 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

Ok, this is the case: I've got two raid-5 arrays with software raid, both with three disks. Setup: md0 has hdb2, hdd1 and sda1 md1 has hdb5, hdd3 and sda3 Tonight, the system lost power due to a power spike. The result was a reboot where it attempted to fix the raid, but it didn't exactly work. I have now booted a live CD and using utilities there. It seems the checksum value is

You didn't answer all of the questions I asked, but I'll answer as best I can with the information you gave. On 01/25/2017 04:47 AM, mark wrote: > > Made an md RAID 0 on the raw disks - /dev/sda /dev/sdb. No partitions, > nothing. OK, so right off the bat we have to note that this is not a configuration supported by Red Hat. It is possible to set such a system up, but it

On Wed, January 25, 2017 9:51 am, m.roth at 5-cent.us wrote: > Let me see if I can, um, reboot this thread.... > > I made a RAID 1 of two raw disks, /dev/sda and /dev/sdb, *not* /dev/sdax > /dev/sdbx. Then I installed CentOS 7 on the RAID, with /boot, /, and swap > being partitions on the RAID. My problem is that grub2-install absolutely > and resolutely refuses to install on

Hi I have setup software RAID two years ago using FC3 using the graphical installer (RAID1). In the mean time I installed CENTOS4.5 and everything is running fine. At least that was my perception. It now turns out that raid is not working and that LVS just finds 4 partitions from four disks and that's it.: /dev/sda2 VolGroup00 lvm2 a- 94.88G 0 /dev/sdb1 VolGroup00 lvm2 a-

Since your actually forming the raid on dom-0 and not inside of the guest, there is absolutely no need to load md and associated modules in the guest at all. The guest will just see the volume group you are exporting as a regular sata drive the same size as the vg being exported. I''m guessing the second drive is for swap? Hope this helps Best, -Tim On Mon, 2006-10-23 at 16:36 +1000,

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 Folks, I've inherited an old RH7 system that I'd like to upgrade to CentOS6.1 by means of wiping it clean and doing a fresh install. However, the system has a software raid setup that I wish to keep untouched as it has data on that I must keep. Or at the very least, TRY to keep. If all else fails, then so be it and I'll just recreate the thing. I do plan on backing up

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

On Mon, Feb 9, 2015 at 5:16 PM, Niki Kovacs <info at microlinux.fr> wrote: > 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

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

On Wed, Feb 18, 2015 at 9:25 PM, John R Pierce <pierce at hogranch.com> wrote: > disks -> partition(s) -> mdraid devices -> PVs -> VG -> LV -> file system. > phew. You might be a candidate for LVM integrated raid. It uses the md kernel code on the backend, but it's all LVM tools to create, manage and monitor. The raid level is defined per LV, instead of all

Hi Niki, md127 apparently only uses 81.95GB per disk. Maybe one of the partitions has the wrong size. What's the output of lsblk? Regards Michael ----- Urspr?ngliche Mail ----- Von: "Niki Kovacs" <info at microlinux.fr> An: "CentOS mailing list" <CentOS at centos.org> Gesendet: Mittwoch, 18. Februar 2015 08:09:13 Betreff: [CentOS] CentOS 7: software RAID 5

Hi, The entire OS I am using is running on software RAID-1. Before killing the power of the UPS, I issue: /sbin/mdadm --readonly $RAIDDEV on all the RAID devices I have. This, however, does not seem to be enough, and when i power the system back on, the RAID arrays are not clean, and a long syncing starts. A last step is missing; something like marking the arrays that they are clean. I see this

On Tue, January 24, 2017 1:10 pm, m.roth at 5-cent.us wrote: > Gordon Messmer wrote: >> On 01/24/2017 08:33 AM, m.roth at 5-cent.us wrote: >>> I'm building a new box, and I want three partitions - /boot, /, and >>> swap, on*one* RAID 1, not three separate partitions. Other than >>> <alt-f2> mdadm...,*is* there any way in the graphical installer

I have 4 ST2000DL003-9VT166 (2Tbyte) disks in a RAID 5 array. Because of the size I built them as a GPT partitioned disk. They were originally built on a CentOS 5.x machine but more recently plugged into a CentOS 6.2 machine where they were detected just fine e.g. % parted /dev/sdj print Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdj: 2000GB Sector size (logical/physical): 512B/512B

Sorry for breaking the threading, as I only get the daily digest. My comments (interspersed) begin with the **. Message: 41 Date: Tue, 16 Sep 2014 18:38:02 -0400 From: SilverTip257 <silvertip257 at gmail.com> To: CentOS mailing list <centos at centos.org> Subject: Re: [CentOS] Advice on CentOS 7, software raid 1, lvm, 3 TB disks Message-ID:

On 23/11/2020 17:16, Ralf Prengel wrote: > Backup!!!!!!!! > > Von meinem iPhone gesendet You do have a recent backup available anyway, haven't you? That is: Even without planning to replace disks. And testing such strategies/sequences using loopback devices is definitely a good idea to get used to the machinery... On a side note: I have had a fair number of drives die on me

I just replaced two md-raided (RAID1) disks with bigger ones and decided to check out how far I get with them when I put them in another machine. The kernel boots and then panics when it wants to mount the root filesystem on the disk. md: Autodetecting RAID arrays md: autorun md: autorun DONE < not sure if this means it was successful or failed, I rather think it failed because it