RAID Creation Fails Every Time With Failed to Execute Command On New Installation

TechnoDadLife · Dec 18th 2018

Quote from flmaxey

@votdev :
@tkaiser has a legitimate point - most SBC users won't visit the forum looking for information on what not to do. The assumption would be, if it's possible to create a RAID array, it's OK.

However, there's a middle ground. Rather than stop the RAID creation process, a WARNING dialog could be popped up much like the box for deleting a shared folder. Something to the effect;

Using RAID on (certain) SBC's is not supported and comes with the risk of data loss. Continue?

Much like "delete" warnings, the above is fair notice before performing an operation that's known to be risky. This would be a service to unsuspecting users, while allowing hobbyists to do as they please.

Regards

Display More

I still think this is a good idea (Even a post just about arm and raspberry pi) from the prospective that I can point people to this information from YouTube.

macom · Dec 18th 2018

And a hint in the notes at the download page on sourceforge.

tkaiser · Dec 18th 2018

Quote from macom

a hint in the notes at the download page on sourceforge

This will be as useless as a warning dialog. Users will ignore this since they are told since a decade that the totally useless RAID-1 mode would provide data safety and/or data security (while it's only the try to provide data availability). Simply google for 'data safety raid 1' and you get the idea.

This whole 'mislead people to believe RAID-1 would provide data safety' is substantial part of the marketing efforts of SOHO NAS vendors, and media outlets spread this nonsense also since a decade.

All that helps is disabled RAID functionality on platforms where it will only cause harm (data loss and/or corruption). That applies to almost all the SBC platforms unfortunately.

ryecoaaron · Dec 18th 2018

Quote from tkaiser

All that helps is disabled RAID functionality on platforms where it will only cause harm (data loss and/or corruption). That applies to almost all the SBC platforms unfortunately.

Anything we do to disable raid would be reverted by an OMV upgrade since Volker does not want to make the raid plugin a separate plugin.

votdev · Dec 18th 2018

I think the best will be that devices connected via USB are not displayed in the RAID creation dialog anymore. This is very easy to implement.

ryecoaaron · Dec 18th 2018

Quote from votdev

I think the best will be that devices connected via USB are not displayed in the RAID creation dialog anymore. This is very easy to implement.

I like this idea but we might need a note mentioning this on the form. Otherwise, people will wonder why their drives don't show up. And for the people who insist on doing the wrong thing, they can still create an array from the command line.

crashtest · Dec 18th 2018

Quote from votdev

I think the best will be that devices connected via USB are not displayed in the RAID creation dialog anymore. This is very easy to implement.

This would handle the entire issue completely since, if the problem is distilled down to the actual cause, it's RAID+USB. This applies to X64 platforms as well.

Quote from ryecoaaron

I like this idea but we might need a note mentioning this on the form. Otherwise, people will wonder why their drives don't show up. And for the people who insist on doing the wrong thing, they can still create an array from the command line.

And this also allows flexibility for the hobbyist/enthusiast to do as they please. However, since RAID over USB won't be "click of a mouse button" easy, the majority won't do it.

I believe it would be easier to explain why RAID over USB is no longer supported in the GUI, then it is to tell a user (after the fact) that their data is most likely gone.

votdev · Dec 19th 2018

PR is ready for review: https://github.com/openmediavault/openmediavault/pull/239

votdev · Dec 22nd 2018

I've improved the RAID creation dialog a little bit. Please review PR https://github.com/openmediavault/openmediavault/pull/243.

crashtest · Dec 22nd 2018

I like your original idea better; filter USB devices so they don't even show up in the create dialog. If it's not available and easy for a beginner, chances are, they won't do it. (Or even become aware that it can be done.) RAID through USB is just bad news.

But, I'm OK with going back to a create dialog warning. A threshold warning, in this case, is a very good thing.

RAID Creation Fails Every Time With Failed to Execute Command On New Installation

Participate now!

Tags