search for: md127

Hello All, on a Centos5 system installed with software raid I'm getting: raid1: raid set md127 active with 2 out of 2 mirrors md:.... autorun DONE md: Autodetecting RAID arrays md: autorun..... md : autorun DONE trying to resume form /dev/md1 creating root device mounting root device mounting root filesystem ext3-fs : unable to read superblock mount : error moun...

I'm confused about which UUID to use to identify a software RAID in fstab. lsblk -fs shows: md127p1 ext4 c43af789-82aa-49e9-a8ed-acd52b1cdd58 /y --- md127 ext4 39c20575-4257-4fd7-b5c8-8a15757e9e8e --- sdb1 linux_r hostname:0 af77830e-8cfd-9012-62ce-e57105c3bf6c --- sdb --- sdc1 linux_r hostname:0 af77830e-8cfd-9012-62ce-e57105c3bf6c...

...ev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 Using this setup, I had 650 MB of disk space on /dev/md3. Now I tried to do the same thing with CentOS 7. Everything seemed to work at first, but here's what I got now: [root at nestor:~] # df -h Sys. de fichiers Taille Utilis? Dispo Uti% Mont? sur /dev/md127 226G 1,1G 213G 1% / devtmpfs 1,4G 0 1,4G 0% /dev tmpfs 1,4G 0 1,4G 0% /dev/shm tmpfs 1,4G 8,5M 1,4G 1% /run tmpfs 1,4G 0 1,4G 0% /sys/fs/cgroup /dev/md125 194M 80M 101M 45% /boot /dev/sde1...

Le 18/02/2015 09:24, Michael Volz a ?crit : > 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? [root at nestor:~] # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232,9G 0 disk ??sda1 8:1 0 3,9G 0 part ? ??md126 9:126 0 3,9G 0 r...

...:06.0: irq 42 for MSI/MSI-X virtio-pci 0000:00:06.0: irq 43 for MSI/MSI-X vdb: vdb1 tsc: Refined TSC clocksource calibration: 3392.169 MHz md: bind<vdb1> mdadm (350) used greatest stack depth: 12384 bytes left md: bind<vda2> md: raid1 personality registered for level 1 md/raid1:md127: active with 2 out of 2 mirrors created bitmap (1 pages) for device md127 md127: bitmap initialized from disk: read 1 pages, set 0 of 153 bits md127: detected capacity change from 0 to 10203693056 md127: unknown partition table systemd-cryptsetup[358]: Set cipher aes, mode xts-plain64, key si...

...:06.0: irq 42 for MSI/MSI-X virtio-pci 0000:00:06.0: irq 43 for MSI/MSI-X vdb: vdb1 tsc: Refined TSC clocksource calibration: 3392.169 MHz md: bind<vdb1> mdadm (350) used greatest stack depth: 12384 bytes left md: bind<vda2> md: raid1 personality registered for level 1 md/raid1:md127: active with 2 out of 2 mirrors created bitmap (1 pages) for device md127 md127: bitmap initialized from disk: read 1 pages, set 0 of 153 bits md127: detected capacity change from 0 to 10203693056 md127: unknown partition table systemd-cryptsetup[358]: Set cipher aes, mode xts-plain64, key si...

...8935 6359354331 sdj? ? ? ? ? ? ? 51.90? ? ? 2031.13? ? ?10684.48 1209191501 6360795559 sdi? ? ? ? ? ? ? 52.47? ? ? 2033.16? ? ?10684.48 1210399262 6360795559 sdk? ? ? ? ? ? ? 52.09? ? ? 2033.15? ? ?10684.36 1210396915 6360724971 sdl? ? ? ? ? ? ? 51.95? ? ? 2031.20? ? ?10684.36 1209235241 6360724971 md127? ? ? ? ? ?138.20? ? ? ? 74.49? ? ?64101.35? ?44348810 38161468777 avg-cpu:? %user? ?%nice %system %iowait? %steal? ?%idle ? ? ? ? ? ?8.57? ? 0.09? ? 1.33? ?26.19? ? 0.00? ?63.81 Device:? ? ? ? ? ? tps? ? kB_read/s? ? kB_wrtn/s? ? kB_read? ? kB_wrtn sda? ? ? ? ? ? ? 28.00? ? ? ?512.00? ? ? 8416.00...

On Tue, 2015-03-17 at 23:28 +0100, johan.vermeulen7 at telenet.be wrote: > > on a Centos5 system installed with software raid I'm getting: > > raid1: raid set md127 active with 2 out of 2 mirrors > > md:.... autorun DONE > > md: Autodetecting RAID arrays > > md: autorun..... > > md : autorun DONE > > trying to resume form /dev/md1 Hi Johan, Your system is assembling md127, but is apparently expecting md1. I suspect tha...

...luggish. Here's the current state of things. [root at alphamule:~] # cat /proc/mdstat Personalities : [raid1] md125 : active raid1 sdb2[1] sda2[0] 512960 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk md126 : inactive sda1[0](S) 16777216 blocks super 1.2 md127 : active raid1 sda3[0] 959323136 blocks super 1.2 [2/1] [U_] bitmap: 8/8 pages [32KB], 65536KB chunk unused devices: <none> Now how can I make my RAID array whole again? For the record, /dev/sda is intact, and /dev/sdb is the faulty disk. How can I force synchronization with /de...

...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 was marked as such in the array, but is not allowing me to remove it: # mdadm /dev/md127 --fail /dev/sdg mdadm: set /dev/sdg faulty in /dev/md127 # mdadm /dev/md127 --remove /dev/sdg mdadm: hot remove failed for /dev/sdg: Device or resource busy And in dmesg, I get an error like so: md: cannot remove active disk sdg from md127 ... More details, including mdadm -D output and other di...

...858.19 0.74 27.30 36.96 27.22 7.55 20.58 sdi 0.03 0.53 0.22 27.13 0.03 11.40 856.04 1.60 58.50 27.43 58.75 5.21 14.24 sdl 0.02 0.56 0.15 27.11 0.03 11.40 858.27 1.12 41.09 27.89 41.16 5.00 13.63 md127 0.00 0.00 2.53 161.84 0.36 68.39 856.56 0.00 0.00 0.00 0.00 0.00 0.00 avg-cpu: %user %nice %system %iowait %steal %idle 13.11 0.00 1.82 1.07 0.00 84.01 Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avg...

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

On 2016-05-25 19:13, Kelly Lesperance wrote: > Hdparm didn?t get far: > > [root at r1k1 ~] # hdparm -tT /dev/sda > > /dev/sda: > Timing cached reads: Alarm clock > [root at r1k1 ~] # Hi Kelly, Try running 'iostat -xdmc 1'. Look for a single drive that has substantially greater await than ~10msec. If all the drives except one are taking 6-8msec, but one is very

...-pci 0000:00:06.0: irq 43 for MSI/MSI-X > vdb: vdb1 > tsc: Refined TSC clocksource calibration: 3392.169 MHz > md: bind<vdb1> > mdadm (350) used greatest stack depth: 12384 bytes left > md: bind<vda2> > md: raid1 personality registered for level 1 > md/raid1:md127: active with 2 out of 2 mirrors > created bitmap (1 pages) for device md127 > md127: bitmap initialized from disk: read 1 pages, set 0 of 153 bits > md127: detected capacity change from 0 to 10203693056 > md127: unknown partition table > systemd-cryptsetup[358]: Set cipher aes,...

...0.74 27.30 36.96 27.22 7.55 20.58 >sdi 0.03 0.53 0.22 27.13 0.03 11.40 856.04 1.60 58.50 27.43 58.75 5.21 14.24 >sdl 0.02 0.56 0.15 27.11 0.03 11.40 858.27 1.12 41.09 27.89 41.16 5.00 13.63 >md127 0.00 0.00 2.53 161.84 0.36 68.39 856.56 0.00 0.00 0.00 0.00 0.00 0.00 > >avg-cpu: %user %nice %system %iowait %steal %idle > 13.11 0.00 1.82 1.07 0.00 84.01 > >Device: rrqm/s wrqm/s r/s w/s...

.... 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) sdg1[3] sde1[1] sdd1[0] 1949480960 blocks super 1.2 512K chunks 2 near-copies [4/3] [UU_U] bitmap: 15/15 pages [60KB], 65536KB chunk smartctl reports this for sdf: 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 1 198 Offline...

...; [root at alphamule:~] # cat /proc/mdstat > Personalities : [raid1] > md125 : active raid1 sdb2[1] sda2[0] > 512960 blocks super 1.0 [2/2] [UU] > bitmap: 0/1 pages [0KB], 65536KB chunk > > md126 : inactive sda1[0](S) > 16777216 blocks super 1.2 > > md127 : active raid1 sda3[0] > 959323136 blocks super 1.2 [2/1] [U_] > bitmap: 8/8 pages [32KB], 65536KB chunk > > unused devices: <none> > > Now how can I make my RAID array whole again? For the record, /dev/sda > is intact, and /dev/sdb is the faulty disk. How...

...d drive. I know how to mount the drive, and have done so on another system to confirm that the information I want is there. My question is this: What is going to happen when I try to mount a drive that the system thinks is part of an existing array? To put it another way:? I had two drives in md127.? I removed one (call it drive1), and replaced it with a new drive.? Some files were accidentally deleted from md127, so now I want to connect drive1 back to the same machine and mount it as a separate array from md127 so I can copy the files from drive1 back to md127.? What do I need to do to...

...s +} +trap cleanup INT QUIT TERM EXIT + +guestfish <<EOF +# Add 2 empty disks +sparse $disk1 100M +sparse $disk2 100M +run + +# Create a raid1 based on the 2 disks +md-create test "/dev/sda /dev/sdb" level:raid1 + +# Create volume group and logical volume on md device +pvcreate /dev/md127 +vgcreate vg0 /dev/md127 +lvcreate-free lv0 vg0 100 +EOF + +# Ensure list-md-devices now returns the newly created md device +output=$( +guestfish --format=raw -a $disk1 --format=raw -a $disk2 <<EOF +run +list-md-devices +lvs +EOF +) + +expected="/dev/md127 +/dev/vg0/lv0" + +if [ &q...