werdisturbed

Everything came up as expected since I had the correct parity drive. Thanks so much for confirming! To determine the parity drive, I slaved my largest capacity drives to a linux workstation and noted which one did not automatically mount. Since I was able to read from the others, I could assume that one should be the parity drive.

I searched but couldn't find my exact issue listed in the forum so here goes. I woke up this morning to some errors in the GUI and did as I have in the past and rebooted the server. The server never came up. I hooked up a monitor and saw "no default or ui configuration directive found". I searched for solutions to that and found it to be easier to just do a new install to USB and migrate the configuration to the new disk. This resulted in the software never fully booting to where it was pingable. I reverted to a fresh install and that boots without issue. Looking through my config (cfg) files I can see that nearly all of them are corrupted. I tried with just the minimal configurations coming over with the .key and super.dat file, was able to recover the key to the new USB (I don't trust the old one at this point) but the array configuration is still asking me to enter in the drives. Expanding further through the old flash drive data I can see that most of the files within the /config directory are corrupted. One of the text files that I know was previously readable is now displayed as "Ël$oYÿÈÓx{e}-™™JÓPJGÇ>Îä2°S®Xj)ëq§±õ«—ö„”Vúü¥¨]×0‡ó¦l‹cOk". I do NOT have a current copy of the super.dat after this last drive configuration change. I do NOT have a copy of the drive list from the Main tab of the web portal. I DO know what drive is the parity (only one parity in the array). My question is as long as I put that drive into the parity slot, does the order of the rest matter? Thanks in advance.