| View previous topic :: View next topic |
| Author |
Message |
ElAngelo
Joined: 10 Aug 2005
Posts: 77
|
 Posted: Tue Aug 22, 2006 7:40 am Post subject: /dev/md0 is not being created |
 |
|
Hi,
I'm experimenting a bit with software raid on my box here...
ATM all added partitions are on the same physical disk just for testing (i'm planning to have a raid5 with 4 or 5 200GB sata drives if this experiments works well...
All seem to be working well... I have tried recovering and stuff like that...
With the exception of one single thing... At boot the /dev/mdX (X going from 0 to 9) is not created...
while in 50-udev.rules :
| Code: |
$ grep md /etc/udev/rules.d/50-udev.rules
# md block devices
KERNEL=="md[0-9]*", NAME="md/%n", SYMLINK+="%k", GROUP="disk"
|
and i do have md support in the kernel :
| Code: |
│ │[*] Multiple devices driver support (RAID and LVM) │ │
│ │<M> RAID support │ │
│ │<M> RAID-4/RAID-5 mode │ │
│ │[*] Support adding drives to a raid-5 array (experimental) │ │
│ │<M> Device mapper support │ │
|
| Code: | $ dmesg | grep md
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
|
Of course i could solve this with a "mknod /dev/md0 b 9 0" in my bootmisc but that doesn't look like a good sollution. IMHO udev should take take of the creation of the /dev's...
Any suggestions? |
|
| Back to top |
|
 |
pcanavan
Joined: 28 Aug 2006
Posts: 1
|
| Posted: Mon Aug 28, 2006 5:52 pm Post subject: Similar troubles on Gentoo |
|
|
I'm not quite sure what's causing it yet, but I've just started to see the same problem on my Athlon64 box running 64-bit Gentoo. It was previously working fine, so it's a regression issue, rather than that uDev is just "still broken with RAID". Looking at what's been installed when, I think uDev 087 is in the clear (installed in early May) but I've upgraded both my kernel and init scripts since it was last working.
Out of interest, which kernel are you running? I'm on 2.6.17 (+ Gentoo patches), and it was certainly working on 2.6.16 (+ other Gentoo patches...) with my old set of "base" init scripts. I've got all my init scripts under version control, but haven't looked at them yet. To be honest I reboot the box so infrequently that I've not done much about it at all.
Philip. |
|
| Back to top |
|
|
ElAngelo
Joined: 10 Aug 2005
Posts: 77
|
| Posted: Tue Aug 29, 2006 9:31 am Post subject: |
|
|
| 2.6.17.11 vanilla |
|
| Back to top |
|
|
kalou
Joined: 09 Oct 2006
Posts: 1
|
| Posted: Mon Oct 09, 2006 5:59 am Post subject: |
|
|
Hello,
just to let you know, same problem with udev and /dev/md* here;
- udev version: udev-071-0.FC4.3
- kernel 2.6.17.4-1.2139_FC4 (patched with via vt8251)
- Centos 4.4
[root@raidy src]# grep md/ /etc/udev/rules.d/*
/etc/udev/rules.d/50-udev.rules:KERNEL=="md[0-9]*", NAME="md/%n", SYMLINK+="%k", GROUP="disk"
Don't know how to fix this yet.
Tried to mknod /dev/md2 (it's 0+1 from md0 and md1), but at each reboot,
it has desapeared  |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Profile
Log in to check your private messages
Log in
