diizzyy:

We should probably try bumping mdadm first if possible before fixing out rather old version.

diizzyy:

lede-project/source#996
Please test if that helps

kisgezenguz:

thank you for the feedback
do you have a binary for ppc or armv5tel?
I don't have configured build host currently.

chunkeey:

Well, I bet the kernel is missing CONFIG_DIRECT_IO.

You probably want to avoid this issue by compiling mdadm into the image. The mdadm package automatically requests the required CONFIG_KERNEL_DIRECT_IO in LEDE's build configuration (which will select CONFIG_DIRECT_IO for the Kernel).

Edit: Formatting.

diizzyy:

Good point, it's not enabled in stock builds.

kisgezenguz:

Hi diizzyy, Christian,

thank you for the input.
I set up a Virtual box and compiled the mdadm 4.0, but is not help.
I think also Christian hint will solve this problem,
my question is only: Hot to request to add the CONFIG_KERNEL_DIRECT_IO to the stable release?

root@Netgear:~# /tmp/mdadm -V
mdadm - v4.0 - 2017-01-09

root@Netgear:~# /tmp/mdadm --create --verbose /dev/md1 --level=1 --raid-devices=2 /dev/sdb1 /dev/sdd1
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: partition table exists on /dev/sdd1
mdadm: partition table exists on /dev/sdd1 but will be lost or
meaningless after creating array
mdadm: size set to 982464K
Continue creating array? (y/n) y
mdadm: unexpected failure opening /dev/md1

diizzyy:

Did you install the firmware which was generated when you built mdadm?

chunkeey:

Hello Szabo,

If you want to run a quick test, I've uploaded one of my sysupgrade images at: https://github.com/chunkeey/apm82181-lede/releases/tag/2017-03-25

I've included the mdadm package ( + a bunch of other stuff).
As a result, CONFIG_KERNEL_DIRECT_IO is enabled. so I expect
mdadm to work (The arrays might get autoassembled. At least
they for me. so check /proc/mdstat.

As for pushing the option to stable releases. I think the major
blocker are the low-mem and low-flash devices... They simply
can't afford any more stuff that isn't absolutely necessary.
Sadly this means, that you'll need to create your own system
images in the forsee-able future, if you want the feature.
Unless of course, you want to bring this topic on attention on
the Mailing-List of Forum.

I hope this helps. If it does, please consider closing the
report for now.

Thanks,
Christian

diizzyy:

Is that using 4.0 or the older one?

chunkeey:

@diizzyy

I've included both version. the version with mdadm 4.0 is prefixed with mdadm4-...
As for "mdadm: unexpected failure opening /dev/md1". It will still happen with 4.0
if the kernel doesn't have CONFIG_DIRECT_IO set. :-/

diizzyy:

@christian
Ahh, cool.

@Szabo
Please test 4.0 first, would be nice if we could have something a bit fresher code-wise in the tree. :-)

kisgezenguz:

Hi,

@diizzyy
Thank you but, I did not find any firmware after build mdadm 4.0.
Where is located?

@christian
Thank you for the image but I could not test, because I am on duty and could not risk to brick my router. But I could test on my GoFlex Net
I know the most device have limited memory and flash but I think the GoflexNet and also the WNDR4700 have enough.

I close this report, but let open the GoflexNet report to, please input there.