Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Wednesday 23 August 2006 21:53, Ronald Vazquez wrote:
> The thing is that as you can see on the fstab, the file system type on
> /dev/md0 is ext3 and not ext2. Would any one be so kind to give me an
> indication of what is going on here?
>
>
> Thanks,
1. Give the password for root maintenance like it says, verify that /dev/md0
exists. Does devfs use the same name or does devfsd need to make the symlink?
It is quite some time since I used devfs(d) so I don't remember the
nomenclature for md devices off the top of my head. Or perhaps some other
devfs related problem?
2. Are the md partitions marked "autoraid" as partition type in the partition
table ? If yes then the kernel can initialise the array, if not then you need
to use the mdadm tools to initialise the array at boot, that might be why the
mdadm init script is failing, because the config file is empty or invalid.
3. the failure of the mdadm script is causing the root fsck to fail for some
reason?
You might have checked some of these, I don't know that from reading your post
and I haven't read your original post just voicing the concerns I saw from
your most recent post.
hamish
--
gentoo-sparc@g.o mailing list
|
|
