January 20, 20251 yr Community Expert Go to Tools - New Config, Retain All, Apply Assign new disk as Disk1, check BOTH Parity Valid and Maintenance Mode checkboxes, Start array Post new diagnostics
January 20, 20251 yr Community Expert Stop array, unassign disk1, start array in normal (not Maintenance) mode Post new diagnostics
January 20, 20251 yr Community Expert Unfortunately, emulated disk1 is unmountable as you should be able to see in Main - Array Devices. We will have to see if it can be repaired. Check filesystem on emulated disk1 (not on the physical unassigned disk). Be sure to use the webUI to do the check, easy to get it wrong if you try to do it at the command line. Post the output
January 20, 20251 yr Author I don't see the option. Do I need to change the file system type manually for this option to become available?
January 20, 20251 yr Community Expert yes, maybe that's why it was unmountable. After you change it go back to Array Devices and see if that fixed it. Maybe we won't have to do check filesystem.
January 20, 20251 yr Community Expert That looks hopeful. Do it again without -n. If it asks for it, use -L. Post the output
January 20, 20251 yr Community Expert Looks like they changed the webUI in v7, it didn't have that Fix button before. Try it and see.
January 20, 20251 yr Author She is still loading.. opened another tab and a Googleplex of a log with info like this -
January 20, 20251 yr Community Expert That doesn't look so good, but we will just have to let it finish and see what we get.
January 20, 20251 yr Author At the bottom, it says this, with "File System Corruption Fixed" at the end -
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.