after setting up the devices (i.e. partitioning) and in case of mkraid creating a correct /etc/raidtab the actual creating of the raid device /dev/md0 fails with an error like: could not create /dev/md0, so such device. mdadm returns a similar error. tried to use MKDEVICE /dev/md0 without success. however, booting from a amd64-livcd-2004.1 creating the devices works. the bad thing is i can't use a 2004.1 livcd to setup a nforce4 mainboard, so i'm not doing anything until this can be solved. Reproducible: Always Steps to Reproduce: 1. boot with amd64-livecd-2005.0 and kernel option doataraid 2. partition disks and create /etc/raidtab or just use mdadm 3. Actual Results: cannot create /dev/md0, no such device. Expected Results: /dev/md0 has been created and i'm able to start the raiddevice this is a similar system (but one i could boot with the livcd-2004.1) - so, this is not from the nforce4 box. Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-ck4 x86_64) ================================================================= System uname: 2.6.11-ck4 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Apr 6 2005, 18:31:44)] ccache version 2.3 [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.14 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-mtune=k8 -Os -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /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 /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mtune=k8 -Os -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox strict" GENTOO_MIRRORS="http://gentoo.mirror.solnet.ch http://mirror.switch.ch/gentoo http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mir.zyrianes.net/gentoo/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://gentoo.math.bme.hu http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://ftp.iasi.roedu.net/mirrors/gentoo.org/ ftp://ftp.iasi.roedu.net/pub/mirrors/gentoo.org/" LC_ALL="en_US" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://10.10.10.1/gentoo-portage" USE="amd64 X acpi alsa berkdb bitmap-fonts cdr crypt curl dvd dvdread esd fam flac font-server fortran gcj gif gpm imagemagick imap imlib java jp2 jpeg junit kde libwww locales lzw lzw-tiff maildir mp3 ncurses nls nptl ogg opengl oss pam perl png python qt readline sasl ssl symlink tcpd tetex tiff truetype truetype-fonts type1-fonts usb userlocales xine xml2 xmms xpm xrandr xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LDFLAGS, LINGUAS
i tried an amd64-livecd-2004.3 too, same result - not working.
Did you do modprobe raid1 or whatever RAID variant you are trying to create?
i did modprobe md, but no, no RAID variant.
You need to MAKEDEV md, as documented both in the release notes and the Handbook. It is a limitation of how udev does things and can't be fixed, as udev only builds device nodes for devices that are present. Since you do not yet have a RAID, it isn't present. It is a bit annoying, but well documented.
thanks for the replies. i had issues with udev (like /dev/console or /dev/null not being created), so, i'm used to it. but i do rtfm and just searched both the amd64 (http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?style=printable&full=1) and x86 doc (http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?style=printable&full=1) (as i must admit i don't read them carefully anymore ;-)) but have not found any hint about that MAKEDEV command. i just booted my raided amd64 system and modprobed the raid variant. /dev/md* are not yet created. how should i use MAKEDEV and where are the release notes and the hint in the documentation?
*bump*
http://www.gentoo.org/proj/en/releng/release/2005.0/amd64-release-notes.xml Also, don't bump bugs. Not only is it rude, but it tends to piss people off. I didn't answer you because I figured you would be abe to look around for it and find it yourself.
this might be a language problem - i thought bump means: "please help me, i'm still interested in the subject but simply can't solve the problem". anyway, i stated above that i've been looking around and haven't found anything useful about that issue. further i don't understand why release notes are not on the mirrors in the correspondig folder of the release files. why a seperate/special server? either way, thanks for your answer. but it does not work at all. i just grapped the original error upon "mkraid /dev/md0 /dev/sda1 /dev/sdb1": "cannot determine md version: no MD device file in /dev". "MAKEDEV /dev/md0" returns: "/sbin/MAKEDEV: don't know how to make /dev/md0". i guess i have to reopen the bug.
Did you READ the release notes? It says, and I quote, "Manually create the device nodes using MAKEDEV md". Nowhere did it say anything about MAKEDEV /dev/md0. As for the "bump"... This is a bug report, not a web forum. Bugs do not just disappear. Posting a bump says to us "Hey... I'm more important than anything you might be working on, so I'm going to post a worthless post to the bug just to get your attention, since there's no way this bug could possibly be on your list of things to look at."
i appreciate the work you guys put in gentoo. but so do i. i don't get why i get pissed at if i open a bug. if you're an active member of the forum you'll read once in a while that one should open a bug instead of posting in the forums. so, i used bump, explained why and acknowlegded your hint of not using it. now, i'd really like to know why this "certain tone" is necessary. you're right, i was thinking instead of just typing the command. so, it is my fault and not a bug. considering this issue after leaning back i'd say: well, did you READ my bug report? i explained exactly what i did in the first post. you pointed me into the right directions - but with your knowledge i bet you knew from the beginning what the mistake was. so instead of saying: "turn right, your tail is just behing you" you could have explicitly say: don't turn, just grab your tail, i.e. don't use "MAKEDEV /dev/md0" but "MAKEDEV md" and the issue what have been solved right away. now i remember that i read that hint either in the forums or in the release notes - where the heck would i've else known about MAKEDEV?
