Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when opening config #29

Closed
Rekrii opened this issue Nov 25, 2018 · 2 comments
Closed

Crash when opening config #29

Rekrii opened this issue Nov 25, 2018 · 2 comments
Labels

Comments

@Rekrii
Copy link

Rekrii commented Nov 25, 2018

When I try to open a config file I get the following exception. Running from the CLI seems to work fine.

Config:
parity D:\snapraid.parity

content C:\snapraid.content
content D:\snapraid.content

data d1 E:
data d2 F:
data d3 G:\

exclude *.unrecoverable
exclude Thumbs.db
exclude $RECYCLE.BIN
exclude \System Volume Information
exclude \Program Files
exclude \Program Files (x86)
exclude \Windows\

Exception:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: Sequence contains no elements
at System.Linq.Enumerable.Max[TSource](IEnumerable`1 source)
at Elucidate.ConfigFileHelper.DoValidation()
at Elucidate.ElucidateForm.LoadConfigFile(String configFile)
at Elucidate.ElucidateForm.OpenSnapRAIDConfigToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

@hidegh
Copy link
Contributor

hidegh commented Nov 27, 2018

@Rekrii possibly relates to: #12
Use disk keyword instead of data and make it zero based d0..dN, this should make your config readable. Hope this helps.

@Rekrii
Copy link
Author

Rekrii commented Nov 28, 2018

@hidegh Thanks, spot on. I seem to have missed that thread. Using the 10.x keyword 'disk' works.

@Smurf-IV Smurf-IV added the bug label Jan 27, 2019
Smurf-IV added a commit that referenced this issue Jan 27, 2019
- Make sure old "data" tag is handled
Improve message for #33 Parity device size warning is misleading
- Not fixed cause, just making the message state why it is displayed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants