Gustaf Räntilä wrote:
> Package: yaird
> Version: 0.0.12-20
>
> yaird fails to create an initrd image for a raid5 system:
> $ sudo mkinitrd.yaird -o /boot/initrd.img-2.6.22-rc5 2.6.22-rc5
> yaird error: Could not read output for /sbin/modprobe -v -n
> --show-depends --set-version 2.6.22-rc5 raid5 (fatal)
>
> Seems to me it tries to add the kernel module "raid5" to the image,
> however, no such module exists in the kernel. Perhaps it's refering to
> raid456.
> Anyway, it's built with CONFIG_MD_RAID456=y, so it should try to load it
> as a module in the first place.
>
> Is this perhaps due to the soon 2 year old bug #337724? If so, perhaps
> yaird should bail out with an error message like; "doesn't support raid
> devices" if possible. And I raise a vote to prioritize raid support in
> yaird. After all, from what I can see, there has been a patch available
> since that bug was filed.
>
> Please tell me if I can be of further help in this issue.
Hmm - it is some while ago, but I am pretty sure that I've succesfully
used yaird with RAID5 myself. But that was with modular RAID drivers, so
perhaps that's what trigger this bug.
No, this seems unrelated to bug#337724 as that concerns dmraid - a
driver for some variants of hardware RAID.
A quick look at the yaird code seems to only explicitly attempt loading
a "raid5" module when using evms. Do you use EVMS?
Would it be possible for you to try with a kernel built with modular
RAID5? Perhaps even a plain vanilla Debian kernel?
We still should make it work using it builtin - this just to narrow down
the cause of the bug.
- Jonas
--
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
- Enden er nær: http://www.shibumi.org/eoti.htm
