np

Can confirm, once a new /boot/config/network-rules.cfg was created, everything appeared as normal! Thanks for the comments/help!

@SimonF Nope, and Nope. I assume this is what gets written to: /etc/udev/rules.d Let me see what happens if I create one manually. Thanks for the screenshot/cat, much appreciated!

I've seen this asked a couple places by can't seem to find an response/answer. I've added a new network interface to 6.10-rc2 (10G Mellanox) but I can't seem to reassign it to eth0. I see references to "Settings > Network Settings > Interface Rules" but it seems to be gone now. Is this planned to be removed for 6.10? Or just missing while 6.10 gets a polish?

I understand how unRAID and traditional raid levels work, and no, currently there is no option for selecting the RAID level. Existing solutions, OSs and full appliances, offer the ability to choose from standard levels, and some offer a superior alternative (in our case, unRAID). I believe you are correct, unRAID is a superior choice in most cases. However it seems like these choices should be something standard in a NAS, unless they will never be viable or it simply cannot be done.

I realize unRAID is an extension (ore replacement) of the standard mdadm implementation but they cannot, or should not coexist? Most related solutions take full advantage of the available raid levels. While unRAID offers something a step beyond, is leaving out existing implementations ok? I'm not really sure if there is any value, just a thought. (I don't want to stray this thread so if further discussion seems like a good idea we can move elsewhere)

In addition to multiple arrays, why not multiple raid levels to choose from?

+1 for Multiple-Array support

Oh great, I tried scanning through the posts in the 5.0 categories, sorry I missed that!

I know this only beta, so more is definately to come, but I just wanted to throw this out as a thought. I can see this space growing quite large as the web interace becomes more robust. To clean up some of the clutter can we discuss some organizational standards for the webGui directory. I can see areas for: /webGui/assets /webGui/assets/css /webGui/assets/images /webGui/assets/js /webGui/pages /webGui/plugins Then a file in the root that emhttp calls by default. I can also see a more indepth discussion on plugin organization. I realize this is fairly small compared to core functionality, so maybe we can generate some input. Let me know your thoughts.