Rescue software RAID system

Lennart Sorensen lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Mon Feb 3 20:29:31 UTC 2014


On Mon, Feb 03, 2014 at 11:50:29AM -0500, William Muriithi wrote:
> This eventually worked. I have now been able to bring up one of the RAID
> device up fully. This is md0 which is RAID1. I have struggled with md2
> though which is a RAID5 device. Here is how it looks.
> 
> mdadm --query --detail /dev/md2
> 
> /dev/md2: Version : 1.2 Creation Time : Thu Dec 13 11:04:35 2012 Raid Level
> : raid5 Used Dev Size : -1 Raid Devices : 3 Total Devices : 2 Persistence :
> Superblock is persistent
> 
> Update Time : Thu Nov 21 09:20:07 2013 State : active, degraded, Not
> Started Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare
> Devices : 0
> 
> Layout : left-symmetric Chunk Size : 512K
> 
> Name : gfs1.jamar.com:2 (local to host gfs1.jamar.com) UUID :
> 0202547e:d9a3bd67:fdeaf168: a780aa38 Events : 6292
> 
> Number Major Minor RaidDevice State 0 0 0 0 removed 1 8 18 1 active sync
> /dev/sdb2 3 8 34 2 active sync /dev/sdc2
> 
> mdadm --add /dev/md2 /dev/sda2 mdadm: add new device failed for /dev/sda2
> as 4: Invalid argument

mdadm --manage /dev/md2 --add /dev/sda2

-- 
Len Sorensen
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list