The 03.02.24 at 11:23, Paul Uiterlinden wrote:
On Saturday 22 February 2003 22:46, Carlos E. R. wrote:
No, no, you misunderstood me: I can mount my raid, that is no problem :-)
The thing is that I'm curious why the kernel tries to mount it very early on the boot process, but it fails. A bit later, initrd is read, the root partition (reiserfs) is mounted, and then the raid is successfully mounted, maybe after reading /etc/fstab (this last detail I'm not sure).
But this means the system is trying twice; I was trying to optimize the process, and understand why it is happening.
That's why I asked what your RAID1 partition contains (boot, root?). My boot partition is non-RAID. I was guessing this would be the difference (it's just guessing).
Ahh. No, my root partition is plain reiser, and /boot is ext2, both non raid, on /dev/hdb. I only have an extra 3 Gb partition as raid, to experiment with :-)
But now you mention that the system is trying twice: looking carefully to the output of dmesg, I see the same. Only thing is: the first time it succeeds, the second time it says "md: array md0 already exists!" (see below for complete output).
Interesting... Ah, but yours are scsi disks, it seems. Maybe there is a difference there :-?
My RAID stuff is all modularized (/usr/src/linux/.config):
# # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set # CONFIG_MD_MULTIPATH is not set CONFIG_BLK_DEV_LVM=m
Hmmm, "all modularized"? Not quite: CONFIG_BLK_DEV_MD can be set to "m" as well. I wonder what happens if I do that. As soon as I've done that, I'll let you know.
Mine is very similar: CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID5=m CONFIG_MD_MULTIPATH=m CONFIG_BLK_DEV_LVM=m -- Cheers, Carlos Robinson