You are right on target. This got rid of that message.
Thanks,
Ken
Richard Fish wrote:
> If either of these sounds right, you should be able to remove the
> "raid" entry from RC_VOLUME_ORDER in /etc/conf.d/rc.
--
gentoo-user@gentoo.org mailing list
On 7/18/06, Andreas Claesson <[EMAIL PROTECTED]> wrote:
I believe the reason for this is that your partitions are of type 'fd'
When they have that id they are automagically found and started by the
kernel, and therefor there are nothing for mdadm to do.
But this is just a guess.
That would be m
On 7/19/06, Kenton Groombridge <[EMAIL PROTECTED]> wrote:
Jarry wrote:
> I have noticed following message in /var/log/boot
> (but I see them too early during boot-up):
> ...
> * Remounting root filesystem read/write ... [ ok ]
> * Setting hostname to obelix ... [ ok ]
> * Starting
Jarry wrote:
> I have noticed following message in /var/log/boot
> (but I see them too early during boot-up):
> ...
> * Remounting root filesystem read/write ... [ ok ]
> * Setting hostname to obelix ... [ ok ]
> * Starting up RAID devices (mdadm) ...
> mdadm: No arrays found in con
> I have noticed following message in /var/log/boot
> (but I see them too early during boot-up):
> ...
> * Remounting root filesystem read/write ... [ ok ]
> * Setting hostname to obelix ... [ ok ]
> * Starting up RAID devices (mdadm) ...
> mdadm: No arrays found in config file
Hi,
I have noticed following message in /var/log/boot
(but I see them too early during boot-up):
...
* Remounting root filesystem read/write ... [ ok ]
* Setting hostname to obelix ... [ ok ]
* Starting up RAID devices (mdadm) ...
mdadm: No arrays found in config file [ !!
6 matches
Mail list logo