2013. szeptember 4. 15:33 napon Roger Oberholtzer <roger@opq.se> írta:
On an openSUSE 12.3 system, I have started getting the following:
This is an automatically generated mail message from mdadm running on acme
A DegradedArray event had been detected on md device /dev/md127.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [raid1] md127 : active raid1 sdf1[0] 1953513280 blocks super 1.0 [2/1] [U_] bitmap: 15/15 pages [60KB], 65536KB chunk
md1 : active raid1 sde1[1] sdd1[0] 1953513280 blocks super 1.0 [2/2] [UU] bitmap: 0/15 pages [0KB], 65536KB chunk
md0 : active raid1 sdc1[1] sdb1[0] 1953513280 blocks super 1.0 [2/2] [UU] bitmap: 0/15 pages [0KB], 65536KB chunk
md2 : active raid1 sdg1[1] 1953513280 blocks super 1.0 [2/1] [_U] bitmap: 15/15 pages [60KB], 65536KB chunk
unused devices: <none>
This is comprised of a number of SATA 3 disks. It seems that the complaint is for sdf1. How can I get more details about the nature of the problem? It is a new software raid1 setup I am not yet using.
It is hard to tell what the problem is. Look at your /etc/mdadm.donf file. It list the arrays ant belonging disks should be configured. Also look at dmesg and/or var/log/messages and search for "md:" lines. It also seems that your have problem with md2 raid1 array as well. Most likely the arrays have become degraded due to a non-clean shutdown. If you see messages in dmesg like: Aug 2 18:01:30 linux kernel: [ 16.152421] md: md0 stopped. Aug 2 18:01:30 linux kernel: [ 16.153198] md: bind<sdc3> Aug 2 18:01:30 linux kernel: [ 16.153313] md: bind<sdb3> Aug 2 18:01:30 linux kernel: [ 16.153323] md: kicking non-fresh sdc3 from array! Aug 2 18:01:30 linux kernel: [ 16.153326] md: unbind<sdc3> Aug 2 18:01:30 linux kernel: [ 16.164094] md: export_rdev(sdc3) Aug 2 18:01:30 linux kernel: [ 16.165335] md/raid1:md0: active with 1 out of 2 mirrors Aug 2 18:01:30 linux kernel: [ 16.165434] created bitmap (1 pages) for device md0 Aug 2 18:01:30 linux kernel: [ 16.165533] md0: bitmap initialized from disk: read 1/1 pages, set 166 of 324 bits Aug 2 18:01:30 linux kernel: [ 16.185522] md0: detected capacity change from 0 to 21731115008 Aug 2 18:01:30 linux kernel: [ 16.193240] md0: unknown partition table Search for 'kicking'. In such a case you can easily fix the array by adding back the missing device to the array. In the above case the command would be: # madm /dev/md0 --add /dev/sdc3 You have to adjust array name and device name. In /proc/mdstat you can check that the array is synchronized and its progress. By the way the linux RAID wiki site is here: https://raid.wiki.kernel.org/index.php/Linux_Raid Unfortunately the site is very badly organized, it is hard to find or locate information on specific cases. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org