similar to: hard drive failing in linux raid

Backup!!!!!!!! Von meinem iPhone gesendet > Am 23.11.2020 um 17:10 schrieb centos at niob.at: > > ?On 23/11/2020 16:49, Frank Bures wrote: >> On 11/23/20 10:46 AM, Simon Matter wrote: >>>> Hi, >>>> >>>> I want to replace my hard drives based SW RAID-1 with SSD's. >>>> >>>> What would be the recommended procedure?

On 11/23/20 10:46 AM, Simon Matter wrote: >> Hi, >> >> I want to replace my hard drives based SW RAID-1 with SSD's. >> >> What would be the recommended procedure? Can I just remove one drive, >> replace with SSD and rebuild, then repeat with the other drive? > > I suggest to "mdadm --fail" one drive, then "mdadm --remove" it.

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 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

On 23/11/2020 16:49, Frank Bures wrote: > On 11/23/20 10:46 AM, Simon Matter wrote: >>> Hi, >>> >>> I want to replace my hard drives based SW RAID-1 with SSD's. >>> >>> What would be the recommended procedure?? Can I just remove one drive, >>> replace with SSD and rebuild, then repeat with the other drive? >> >> I suggest to

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

Hi, I'm on kernel 2.14.13-ac8 running Redhat 7.1. I've successfully converted all my file system to ext3 and is working fine for a couple of weeks. However, I did a silly thing when I e2fsck (version 1.23) an ext3 /home partiction without umounting it. Now, I believe my partiton super-block is corrupted and the system wasn't able to mount /home. I tried as suggested to do a e2fsck -b

I'am running CentOS 4.3 on an (Intel) with one SATA disk (/dev/sda). The output of fdisk -l: Disk /dev/sda: 81.9 GB, 81964302336 bytes 255 heads, 63 sectors/track, 9964 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 19 152586 83 Linux /dev/sda2 20 2569

We're just using Linux software RAID for the first time - RAID1, and the other day, a drive failed. We have a clone machine to play with, so it's not that critical, but.... I partitioned a replacement drive. On the clone, I marked the RAID partitions on /dev/sda failed, and remove, and pulled the drive. After several iterations, I waited a minute or two, until all messages had stopped,

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?

Hi I have a degraded array /dev/md2 ===================================================================== $ mdadm -D /dev/md2 /dev/md2: Version : 00.90.01 Creation Time : Thu Oct 6 20:31:57 2005 Raid Level : raid5 Array Size : 221953536 (211.67 GiB 227.28 GB) Device Size : 110976768 (105.84 GiB 113.64 GB) Raid Devices : 3 Total Devices : 2 Preferred Minor : 2

Hi, This is my current config: /dev/md0 -> 200 MB -> sda1 + sdd1 -> /boot /dev/md1 -> 36 GB -> sda2 + sdd2 -> form VolGroup00 with md2 /dev/md2 -> 18 GB -> sdb1 + sde1 -> form VolGroup00 with md1 sda,sdd -> 36 GB 10k SCSI HDDs sdb,sde -> 18 GB 10k SCSI HDDs I have added 2 36 GB 10K SCSI drives in it, they are detected as sdc and sdf. What should I do if I

In article <20190225050144.GA5984 at button.barrett.com.au>, Jobst Schmalenbach <jobst at barrett.com.au> wrote: > 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

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

I thought I'd test replacing a failed drive in a 4 drive raid 10 array on a CentOS 5.2 box before it goes online and before a drive really fails. I 'mdadm failed, removed', powered off, replaced drive, partitioned with sfdisk -d /dev/sda | sfdisk /dev/sdb, and finally 'mdadm add'ed'. Everything seems fine until I try to create a snapshot lv. (Creating a snapshot lv

> 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

Hello, i recently installed Centos 5 on a new server with a single scsii disk. After the installation, i added 2 additional disks that were once the components of a raid0 array on another server. I get some errors and am unable to start the array the following is an extract from dmesg output: md: Autodetecting RAID arrays. md: could not open unknown-block(8,17). md: could not open

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

Hi , currently i have 2 raid devices /dev/md0 and /dev/md1 , i have added 2 new disks, fdisked , created 2 primary partitions with type fd (linux raid autodetect) Now i want to create raid from them root at vmhost1 ~]# mdadm --create --verbose /dev/md2 --level=1 /dev/sdc1 /dev/sdd1 mdadm: error opening /dev/md2: No such file or directory will return that error, what shouldi do? Thanks!

Hello, I''m doing one emergencial migrate for one very old machine, because we will have one IMPLOSION (!!!) very close from here, and I''m thinking that this old IDE disk will not survive... :-/ [root@registro-2 /root]# df -h Filesystem Size Used Avail Use% Mounted on /dev/ida/c0d0p2 3.8G 2.3G 1.4G 62% / /dev/ida/c0d0p8 26G 20G 4.4G 82% /data