similar to: adding raid1 to running system

I'm playing with software RAID and LVM in some virtual machines and I've run into an issue that I can't find a good answer to in the docs. I have the following RAID setup: md0: sda1 and sdb1, RAID 1. This is /boot md1: sda2 and sdb2, RAID 1. This is a PV for LVM. VolGroup00, this is the volume group and md1 is the only PV in it. LogVol00 is swap LogVol01 is / LogVol02 is /home

Hi, I'm currently experimenting with software RAID1 on a spare PC with two 40 GB hard disks. Normally, on a desktop PC with only one hard disk, I have a very simple partitioning scheme like this : /dev/hda1 80 MB /boot ext2 /dev/hda2 1 GB swap /dev/hda3 39 GB / ext3 Here's what I'd like to do. Partition a second hard disk (say, /dev/hdb) with three

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

Hello, I have two disks sda and sdb. One of the was broken so I have changed the broken disk with a working one. I started the server in rescue mode, and created the partional table, and added all the partitions to the software raid. *I have added the partitions to the RAID, and reboot.* # mdadm /dev/md0 --add /dev/sdb1 # mdadm /dev/md1 --add /dev/sdb2 # mdadm /dev/md2 --add /dev/sdb3 # mdadm

Hi All, I'm currently trying to install centos 5.4 x86-64bit on a raid 1, so if one the 2 disks fails the server will still be available. i installed grub on /dev/sda using the advanced grub configuration option during the install. after the install is done i boot in linux rescue mode , chroot the filesystem and copy grub to both drives using: grub>root (hd0,0) grub>setup (hd0)

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 all. I have a Dell SC440 running Centos 4.4. It has two 500GB disks in a RAID1 array using linux software raid (md1 is / and md0 is /boot). Recently the root file system was remounted read-only for some reason. The logs don't show anything unusual, presumably the file system was read-only before anythng was logged. Running dmesg showed this error repeated many times: EXT3-fs error (device

Guys, The other day while working on my old workstation it get frozen and after reboot I lost almost all data unexpectedly. I have a RAID1 configuration with LVM. 2 IDE HDDs. md0 .. store /boot (100MB) -------------------------- /dev/hda2 /dev/hdd1 md1 .. store / (26GB) /dev/hda3 /dev/hdd2 The only info that still rest in was that, that I restore after the fresh install. It seems that the

I am running software RAID1 on a somewhat critical server. Today I noticed one drive is giving errors. Good thing I had RAID. I planned on upgrading this server in next month or so. Just wandering if there was an easy way to fix this to avoid rushing the upgrade? Having a single drive is slowing down reads as well, I think. Thanks. Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb

Guys, The other day while working on my old workstation it got frozen and after reboot I lost almost all data unexpectedly. I have a RAID1 configuration with LVM. 2 IDE HDDs. md0 .. store /boot (100MB) -------------------------- /dev/hda2 /dev/hdd1 md1 .. store / (26GB) -------------------------- /dev/hda3 /dev/hdd2 The only info that still rest in was that, that I restore after the fresh

System is CentOS 6 all up to date, previously had two drives in MD RAID configuration. md0: sda1/sdb1, 20 GB, OS / Partition md1: sda2/sdb2, 1 TB, data mounted as /home Installed kmod ZFS via yum, reboot, zpool works fine. Backed up the /home data 2x, then stopped the sd[ab]2 partition with: mdadm --stop /dev/md1; mdadm --zero-superblock /dev/sd[ab]1; Removed /home in /etc/fstab. Used

I have a system that is RAID -1 configured as /dev/md0 is /dev/hda1 /dev/hdb1 /dev/md1 is /dev/hdb3 /dev/hdb3 it seems as though /dev/hda has failed.... I have another disk (identical model) that I can replace hda with. I know about the commands fdisk to repartion and raidhotadd /dev/md0 /dev/hda1 and raidhotadd /dev/md1 /dev/hda3 (to be ran after the system boots). BUT... how do I now get

it seems like I keep running into a wall. The present raid array...well let me do an fdisk -l: ---------------------------------------- Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux

Hi > Continuing this thread, and focusing on RAID1. > > I got an HPE Proliant gen10+ that has hardware RAID support.? (can turn > it off if I want). What exact model of RAID controller is this? If it's a S100i SR Gen10 then it's not hardware RAID at all. > > I am planning two groupings of RAID1 (it has 4 bays). > > There is also an internal USB boot port. >

I am trying to convert an existing IDE one-disk system to RAID1 using the general strategy found here: http://lists.centos.org/pipermail/centos/2005-March/003813.html But I am stuck on one thing - when I went to create the second md device with mdadm, # mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/hdb2 missing mdadm: error opening /dev/md1: No such file or directory And indeed,

I have a CentOS 4.2 system that was set up VERY quickly following the demise of its former life as a CentOS 3 server - you don't want the full story, but it had to be done quickly to get a company up and working following a slight disaster involving an electrician, a portable appliance safety tester and a pulled power cable - anyway, here's where I am at... Everything is running fine but

I just installed CentOS 5.4 64 bit release on a 1.9ghz CPU with 8gB of RAM. It has 2 Western Digital 1.5TB SATA2 drives in RAID1. [root at server ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/md2 1.4T 1.4G 1.3T 1% / /dev/md0 99M 19M 76M 20% /boot tmpfs 4.0G 0 4.0G 0% /dev/shm [root at server ~]# Its barebones

Hi! Whew, I have googled around a lot w/this but can't quite seem to come up w/the right answer. This system works beautifully w/nothing wrong w/it. But my goal is to be able to test the raid system by just unplugging hda to mimic a faulty drive and have it just carry on and boot from hdc. md0 = hda1/hdc1 /boot (primary boot partitions on both drives) md1 = hda2/hdc2 / is it possible to

> In article <6566355.ijNRhnPfCt at tesla.schoolpathways.com>, > Benjamin Smith <lists at benjamindsmith.com> wrote: >> System is CentOS 6 all up to date, previously had two drives in MD RAID >> configuration. >> >> md0: sda1/sdb1, 20 GB, OS / Partition >> md1: sda2/sdb2, 1 TB, data mounted as /home >> >> Installed kmod ZFS via yum,

> 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