Quote Originally Posted by Robotbeat
I've had many "system corrupted" errors, but have never lost data on the open-e systems. It is incredibly annoying that it happens (and open-e probably should switch to a filesystem like JFFS2 which is designed to be used on flash), but you just swap out the module or boot from a CD and your data is still there, safe and sound.

There's also the option of installing open-e dss (atlanta i.e. build 3511 or later) on any hard disk or RAID volume slice. I actually still like the ability to easily swap out modules, even though the stupid things keep failing. I've been looking at some USB thumb drives that use both wear-leveling and single-level cells. They're about $30 online.
This is kind of disconcerting to hear about system corruption just as I was in the middle of testing my Open-e for deployment in the next month or so.

What would be the procedure to combat this in the event it should happen?
What steps would I take to recover from something horrible like this happening?

I'm testing V6 so not sure if its different then V5, but I am using the square USB dom I had gotten with DSS V5 and overwrote it with V6. I would assume in the future I could re-run the V6 installer and overwrite the DOM and the restore my saved config settings? The disk configs are stored on the arrays themselves, correct?

Our Datacenter recently had a UPS go out so this kind of power outage is possible and I'd like to be prepared.

Thanks!