![](https://seccdn.libravatar.org/avatar/8df291265238395e793d45e1e572336d.jpg?s=120&d=mm&r=g)
On Wed, 4 Sep 2013 17:10:50 Roger Oberholtzer wrote:
On Wednesday, September 04, 2013 03:48:00 PM Philippe Andersson wrote:
mdadm -Q -D /dev/md127
Sadly, I am none the wiser:
# mdadm -v -Q -D /dev/md127
/dev/md127: Version : 1.0 Creation Time : Mon Apr 8 14:06:44 2013 Raid Level : raid1 Array Size : 1953513280 (1863.02 GiB 2000.40 GB) Used Dev Size : 1953513280 (1863.02 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Wed Sep 4 17:09:16 2013 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0
Name : acme.pacific:2 UUID : c6b77f62:9e280889:353ed7d7:9c8686d1 Events : 84030
Number Major Minor RaidDevice State 0 8 81 0 active sync /dev/sdf1 1 0 0 1 removed
This last line tells you the answer. ^^^^ /dev/md127 has only one active member - /dev/sdf1. Whatever else the system thinks was part of that array has been "removed" from the array, therefore it is reported as running in degraded mode. It could be, though, that /dev/sdf1 used to be part of one of your other arrays and for some reason is now detected as separate (but still having the Linux-RAID partition type). Did you document what partitions you used when first assembling the raid array(s)? -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org