[DLSLUG-Discuss] raid woes on a server I was trying to upgrade to FC6
Python
e-mail addresses are not shown in archives
Sat Jan 27 15:56:01 EST 2007
The main root (/) partition is /dev/md0. It is raid-1 (mirrored config)
running on a single drive. The FC6 boot process was unable to recognize
the raid config. (/dev/md1 is the swap and appears to be OK.)
The /dev/sda5 drive is shown as a spare. I am unable to get it back in
as an active part of the raid device. A reboot changed the mdstat file
to show that the device was in recovery mode and would need an hour to
finish. An hour later, I was back where I had started with /dev/sda5
installed as a spare. The mdadm --examine pronounces it clean, so I
assume the drive is really OK. The mdadm man page does not provide an
explicit command to move a drive from spare to active. As near as I can
tell that should be automatic.
mdadm /dev/md0 --add /dev/sda5
mdadm: hot add failed for /dev/sda5: Invalid argument
Running fail, remove, add seems to work, but leaves me back where I
started with /dev/sda5 as a spare drive.
mdadm /dev/md0 --fail /dev/sda5 --remove /dev/sda5 --add /dev/sda5
mdadm: set /dev/sda5 faulty in /dev/md0
mdadm: hot removed /dev/sda5
mdadm: hot added /dev/sda5
I am enclosing an awful lot of junk so I understand that many will not
have time to wade through this. I am hoping that I am just missing
something fairly simple.
cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdb1[1] sda3[0]
2232960 blocks [2/2] [UU]
md0 : active raid1 sdb2[1] sda5[2]
153854400 blocks [2/1] [_U]
unused devices: <none>
mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.01
Creation Time : Wed Jun 29 07:16:05 2005
Raid Level : raid1
Array Size : 153854400 (146.73 GiB 157.55 GB)
Device Size : 153854400 (146.73 GiB 157.55 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sat Jan 27 15:42:04 2007
State : clean, degraded
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1
Number Major Minor RaidDevice State
0 0 0 -1 removed
1 8 18 1 active sync /dev/sdb2
2 8 5 0 spare /dev/sda5
UUID : ad4cd055:143e016a:fe221f00:b00d167f
Events : 0.31673576
mdadm --examine /dev/sda5
/dev/sda5:
Magic : a92b4efc
Version : 00.90.00
UUID : ad4cd055:143e016a:fe221f00:b00d167f
Creation Time : Wed Jun 29 07:16:05 2005
Raid Level : raid1
Device Size : 153854400 (146.73 GiB 157.55 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Sat Jan 27 15:21:25 2007
State : clean
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1
Checksum : ae55c2b7 - correct
Events : 0.31672680
Number Major Minor RaidDevice State
this 2 8 5 2 spare /dev/sda5
0 0 0 0 0 removed
1 1 8 18 1 active sync /dev/sdb2
2 2 8 5 2 spare /dev/sda5
mdadm --examine /dev/sdb2
/dev/sdb2:
Magic : a92b4efc
Version : 00.90.00
UUID : ad4cd055:143e016a:fe221f00:b00d167f
Creation Time : Wed Jun 29 07:16:05 2005
Raid Level : raid1
Device Size : 153854400 (146.73 GiB 157.55 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Sat Jan 27 15:22:27 2007
State : clean
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1
Checksum : ae55c34c - correct
Events : 0.31672716
Number Major Minor RaidDevice State
this 1 8 18 1 active sync /dev/sdb2
0 0 0 0 0 removed
1 1 8 18 1 active sync /dev/sdb2
2 2 8 5 0 spare /dev/sda5
cat /etc/mdadm.conf (created by using mdadm --detail --scan)
MAILADDR root
DEVICE /dev/sda5 /dev/sdb2 /dev/sda3 /dev/sdb1
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=d3f9bd15:d527f433:891cbe54:9d56a5d6
devices=/dev/sda3,/dev/sdb1
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=ad4cd055:143e016a:fe221f00:b00d167f
devices=/dev/sdb2,/dev/sda5
These are the boot messages
Jan 27 14:20:06 newemail kernel: md: raid1 personality registered as nr 3
Jan 27 14:20:06 newemail kernel: md: Autodetecting RAID arrays.
Jan 27 14:20:06 newemail kernel: md: autorun ...
Jan 27 14:20:06 newemail kernel: md: considering sdb2 ...
Jan 27 14:20:06 newemail kernel: md: adding sdb2 ...
Jan 27 14:20:06 newemail kernel: md: sdb1 has different UUID to sdb2
Jan 27 14:20:06 newemail kernel: md: adding sda5 ...
Jan 27 14:20:06 newemail kernel: md: sda3 has different UUID to sdb2
Jan 27 14:20:06 newemail kernel: md: created md0
Jan 27 14:20:06 newemail kernel: md: bind<sda5>
Jan 27 14:20:06 newemail kernel: md: bind<sdb2>
Jan 27 14:20:06 newemail kernel: md: running: <sdb2><sda5>
Jan 27 14:20:06 newemail kernel: raid1: raid set md0 active with 1 out of 2 mirrors
Jan 27 14:20:06 newemail kernel: md: considering sdb1 ...
Jan 27 14:20:06 newemail kernel: RAID1 conf printout:
Jan 27 14:20:06 newemail kernel: --- wd:1 rd:2
Jan 27 14:20:06 newemail kernel: disk 0, wo:1, o:1, dev:sda5
Jan 27 14:20:06 newemail kernel: disk 1, wo:0, o:1, dev:sdb2
Jan 27 14:20:06 newemail kernel: md: adding sdb1 ...
Jan 27 14:20:06 newemail kernel: md: adding sda3 ...
Jan 27 14:20:06 newemail kernel: ..<6>md: syncing RAID array md0
Jan 27 14:20:06 newemail kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Jan 27 14:20:06 newemail kernel: md: using maximum available idle IO bandwith (but not more than 200000 KB/sec) for reconstruction.
Jan 27 14:20:06 newemail kernel: md: using 128k window, over a total of 153854400 blocks.
Jan 27 14:20:06 newemail kernel: md: created md1
Jan 27 14:20:06 newemail kernel: md: bind<sda3>
Jan 27 14:20:06 newemail kernel: md: bind<sdb1>
Jan 27 14:20:06 newemail kernel: md: running: <sdb1><sda3>
Jan 27 14:20:06 newemail kernel: raid1: raid set md1 active with 2 out of 2 mirrors
Jan 27 14:20:06 newemail kernel: md: ... autorun DONE.
Jan 27 14:20:06 newemail kernel: md: Autodetecting RAID arrays.
Jan 27 14:20:06 newemail kernel: md: autorun ...
Jan 27 14:20:06 newemail kernel: md: ... autorun DONE.
--
Lloyd Kvam
Venix Corp
More information about the DLSLUG-Discuss
mailing list