After the upgrade to baselayout-1.11.12 {-r1} I have these messages concerning my soft RAID during boot (just after modules loading): *Starting up RAID devices (raidtools) /dev/md0: Invalid argument /dev/md1: Invalid argument /dev/md2: Invalid argument /dev/md3: Invalid argument *Starting up RAID devices (mdadm) mdadm: No arrays found in config files Reproducible: Always Steps to Reproduce: 1.Upgrade baselayout from 1.11.11-r3 to 1.11.12-r1 2.Reboot 3. Actual Results: Strange messages concerning my soft RAID during boot. Anyway, I can boot, and RAID is up and running. I have 3 RAID0 and 1 RAID1. I downgraded to 1.11.11-r3, and these messages disapeared. (I have the same messages with 1.11.12 and 1.11.12-r1). I've had a look in old log files, and I am pretty sure that these messages are related to the 1.11.12 upgrade of baselayout. Expected Results: Boot smoothly. emerge info Portage 2.0.51.22 (default-linux/amd64/2005.0, gcc-3.4.3-20050110, glibc-2.3.5-r0, 2.6.11-gentoo x86_64) ================================================================= System uname: 2.6.11-gentoo x86_64 AMD Athlon(tm) 64 Processor 3500+ Gentoo Base System version 1.6.11 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.8 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r9 sys-devel/libtool: 1.5.18 virtual/os-headers: 2.6.11 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildsyspkg candy distlocks sandbox strict" GENTOO_MIRRORS="ftp://ftp.proxad.net/mirrors/ftp.gentoo.org/ http://mirror.switch.ch/ftp/mirror/gentoo/ ftp://mirror.switch.ch/ftp/mirror/gentoo/" LANG="fr_FR.utf8" LC_ALL="fr_FR.utf8" LINGUAS="fr en_GB" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aalib acpi alsa apache2 avi bash-completion berkdb bitmap-fonts bonobo cdr chroot crypt curl dba dvd dvdr dvdread eds esd fam flac font-server fortran gd gdbm gif gstreamer gtk gtk2 gtkhtml guile hal ieee1394 imagemagick imlib ipv6 jabber java jp2 jpeg junit kdeenablefinal libwww lm_sensors lzw lzw-tiff mad matroska mikmod motif mp3 mpeg msn mysql ncurses nls nowin nptl nptlonly nvidia ogg opengl oss pam perl php png python readline real ruby samba sdl slang spell ssl svg tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts unicode usb userlocales vorbis wmf xine xml xml2 xmms xpm xrandr xv xvid zlib linguas_fr linguas_en_GB userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS cheers
it's because baselayout-1.11.12 just runs `raidstart -a` and lets the raidtools handle the rest of the details could you please post your /etc/raidtab file ?
here you are: /etc/raidtab raiddev /dev/md0 raid-level 0 nr-raid-disks 2 persistent-superblock 1 chunk-size 32 device /dev/sda5 raid-disk 0 device /dev/sdb5 raid-disk 1 raiddev /dev/md1 raid-level 1 nr-raid-disks 2 persistent-superblock 1 chunk-size 32 device /dev/sda7 raid-disk 0 device /dev/sdb7 raid-disk 1 raiddev /dev/md2 raid-level 0 nr-raid-disks 2 persistent-superblock 1 chunk-size 32 device /dev/sda2 raid-disk 0 device /dev/sdb2 raid-disk 1 raiddev /dev/md3 raid-level 0 nr-raid-disks 2 persistent-superblock 1 chunk-size 32 device /dev/sda3 raid-disk 0 device /dev/sdb3 raid-disk 1
A workaround is to compile your raid functionality directly into the kernel (not as modules) and use Raid-autodetect as the partition type. The raid arrays will be automatically started at boot by the kernel.
(In reply to comment #3) RAID support is already directly into the kernel (my / is RAID0 ): grep -i RAID /usr/src/linux/.config <snip> CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y <snip> And the partition type is already "raid autodetect". For instance: fdisk -l Disque /dev/sdb: 120.0 Go, 120034123776 octets 255 t
(In reply to comment #3) RAID support is already directly into the kernel (my / is RAID0 ): grep -i RAID /usr/src/linux/.config <snip> CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y <snip> And the partition type is already "raid autodetect". For instance: fdisk -l Disque /dev/sdb: 120.0 Go, 120034123776 octets 255 têtes, 63 secteurs/piste, 14593 cylindres Unités = cylindres de 16065 * 512 = 8225280 octets Périphérique Amorce Début Fin Blocs Id Système /dev/sdb2 9 1225 9775552+ fd Linux raid autodetect /dev/sdb3 1226 3710 19960762+ fd Linux raid autodetect <snip> cheers
which is prob why you're getting those errors raidtools isnt good at handling arrays that have been already started
could you sync up in a bit and try emerging raidtools-1.00.3-r5 ? it is marked with KEYWORDS=-* so you'll have to `emerge <path to ebuild>/raidtools-1.00.3-r5.ebuild` then reboot and see if any error messages are posted
unmasked -r5
I'm late, wasn't available these last days. emerging raidtools-1.00.3-r5 solved it. thanks.
