Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 158232

Summary: raid devices not detected as expected
Product: Gentoo Linux Reporter: RWeber <r.weber>
Component: Current packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: VERIFIED NEEDINFO    
Severity: normal    
Priority: Low    
Version: 2006.1   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description RWeber 2006-12-15 10:23:35 UTC
Portage 2.1-r2 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r3, 2.6.18-hardened-BackEnd-Build x86_64)
=================================================================
System uname: 2.6.18-hardened-BackEnd-Build x86_64 Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz
Gentoo Base System version 1.12.1
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: [Not Present]
dev-lang/python:     2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=opteron -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /var/bind"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo"
CXXFLAGS="-march=opteron -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS=""
FEATURES="autoconfig ccache confcache distlocks fixpackages metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo"
LINGUAS="en"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 berkdb bitmap-fonts cli cracklib crypt cups dlloader dri fortran gdbm gpm hardened iconv ipv6 isdnlog libg++ ncurses nls nptl nptlonly pam pcre ppds pppd python readline reflection session snmp spl ssl tcpd truetype-fonts type1-fonts udev unicode xml xml2 xorg zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux linguas_en userland_GNU video_cards_apm video_cards_ark video_cards_ati video_cards_chips video_cards_cirrus video_cards_cyrix video_cards_dummy video_cards_fbdev video_cards_glint video_cards_i128 video_cards_i810 video_cards_mga video_cards_neomagic video_cards_nv video_cards_rendition video_cards_s3 video_cards_s3virge video_cards_savage video_cards_siliconmotion video_cards_sis video_cards_sisusb video_cards_tdfx video_cards_tga video_cards_trident video_cards_tseng video_cards_v4l video_cards_vesa video_cards_vga video_cards_via video_cards_vmware video_cards_voodoo"
Unset:  CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY


- I have created 4 Raid 1 Arrays, on 2 HDDs:
md0 -> sda1 sdb1
md1 -> sba2 sdb2
md2 -> sda3 sdb3
md3 -> sda4 sdb4

- MD2 and MD3 consist of Logical Volumes

/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
/dev/sda2              14         622     4891792+  fd  Linux raid autodetect
/dev/sda3             623        4270    29302560   fd  Linux raid autodetect
/dev/sda4            4271       10011    46114582+  fd  Linux raid autodetect

/dev/sdb1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdb2              14         622     4891792+  fd  Linux raid autodetect
/dev/sdb3             623        4270    29302560   fd  Linux raid autodetect
/dev/sdb4            4271       10011    46114582+  fd  Linux raid autodetect


mdadm.conf (also tried without 'DEVICE' entires):
DEVICE /dev/sda1 /dev/sdb1
ARRAY /dev/md0 level=raid1 num-devices=2 UID=9aec994b:2ea939b0:95fd62c1:1be9f163
DEVICE /dev/sda2 /dev/sdb2
ARRAY /dev/md1 level=raid1 num-devices=2 UID=5ef1fc27:280415f4:95c48dbd:b7003082
DEVICE /dev/sda3 /dev/sdb3
ARRAY /dev/md2 level=raid1 num-devices=2 UID=8a0463fb:3bb45a00:2d96e517:28c22bb1
DEVICE /dev/sda4 /dev/sdb4
ARRAY /dev/md3 level=raid1 num-devices=2 UID=7676d2ea:39dbae75:43124aab:7d479493

- AFTER REBOOT

cat /proc/mdstat
md1 : active raid1 sdb2[1] sda2[0]
      4891712 blocks [2/2] [UU]
      
md2 : active raid1 sdb3[1] sda3[0]
      29302464 blocks [2/2] [UU]
      
md4 : active raid1 sdb4[1] sda4[2](F)
      46114496 blocks [2/1] [_U]
      
md0 : active raid1 sdb1[1] sda1[0]
      104320 blocks [2/2] [UU]

mdadm --detail --scan :
ARRAY /dev/md0 level=raid1 num-devices=2 UID=9aec994b:2ea939b0:95fd62c1:1be9f163
ARRAY /dev/md4 level=raid1 num-devices=2 UID=7676d2ea:39dbae75:43124aab:7d479493
ARRAY /dev/md2 level=raid1 num-devices=2 UID=8a0463fb:3bb45a00:2d96e517:28c22bb1
ARRAY /dev/md1 level=raid1 num-devices=2 UID=5ef1fc27:280415f4:95c48dbd:b7003082

ls -l /dev/md
total 0
brw-rw---- 1 root disk 9, 0 Dec 15 17:50 0
brw-rw---- 1 root disk 9, 1 Dec 15 17:50 1
brw-rw---- 1 root disk 9, 2 Dec 15 17:50 2
brw-rw---- 1 root disk 9, 3 Dec 15 17:50 3
brw-rw---- 1 root disk 9, 4 Dec 15 17:50 4

dmesg
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdb4 ...
md:  adding sdb4 ...
md: sdb3 has different UUID to sdb4
md: sdb2 has different UUID to sdb4
md: sdb1 has different UUID to sdb4
md:  adding sda4 ...
md: sda3 has different UUID to sdb4
md: sda2 has different UUID to sdb4
md: sda1 has different UUID to sdb4
md: created md4
md: bind<sda4>
md: bind<sdb4>
md: running: <sdb4><sda4>
raid1: raid set md4 active with 2 out of 2 mirrors
md: considering sdb3 ...
md:  adding sdb3 ...
md: sdb2 has different UUID to sdb3
md: sdb1 has different UUID to sdb3
md:  adding sda3 ...
md: sda2 has different UUID to sdb3
md: sda1 has different UUID to sdb3
md: created md2
md: bind<sda3>
md: bind<sdb3>
md: running: <sdb3><sda3>
raid1: raid set md2 active with 2 out of 2 mirrors
md: considering sdb2 ...
md:  adding sdb2 ...
md: sdb1 has different UUID to sdb2
md:  adding sda2 ...
md: sda1 has different UUID to sdb2
md: created md1
md: bind<sda2>
md: bind<sdb2>
md: running: <sdb2><sda2>
raid1: raid set md1 active with 2 out of 2 mirrors
md: considering sdb1 ...
md:  adding sdb1 ...
md:  adding sda1 ...
md: created md0
md: bind<sda1>
md: bind<sdb1>
md: running: <sdb1><sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
Comment 1 SpanKY gentoo-dev 2006-12-15 21:54:59 UTC
i cant read your mind ... you didnt really say what the problem is, you just show a bunch of raid stuff on your machine
Comment 2 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2006-12-15 22:04:43 UTC
the output shows that before the reboot, there are md[0-3]
but afterwards there are md[0-2,4] (no md3).

I'd wager that 'md3' has a wrong minor number. examine /dev/sda4 with mdadm -E and see what persistant minor there is.
Comment 3 SpanKY gentoo-dev 2006-12-15 22:25:19 UTC
got ya ... not a userspace bug
Comment 4 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2006-12-15 22:57:44 UTC
vapier: no i meant that it's probably a human-error.
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2006-12-16 01:24:39 UTC
See comment #2.
Comment 6 RWeber 2006-12-18 01:29:53 UTC
Sorry for the 'hidden' problem description.
Exactly, md4 should actually be md3.

I did a mdadm -E on all drives now. Here is the result:

#      Major    Minor
0       8        1        0      active sync   /dev/sda1
0       8        2        0      active sync   /dev/sda2
0       8        3        0      active sync   /dev/sda3
0       8        4        0      active sync   /dev/sda4


The funny thing is, that md0-2 are build as expected. I did the Raid creation on the same way for all nodes (md0 to md3).

Comment 7 Jakub Moc (RETIRED) gentoo-dev 2006-12-18 01:42:23 UTC
What exactly did you reopen this bug for? Check the node for sdb4 which is faulty:

<snip>
md4 : active raid1 sdb4[1] sda4[2](F)
      46114496 blocks [2/1] [_U]
</snip>
Comment 8 RWeber 2006-12-18 01:51:42 UTC
you where right.
I found preferred minor is set wrong for sda4.

Thanks!