1humshark

Sorry for the tardiness of the reply, I have been SOOOO busy, I have not even had a chance to determine what is missing since the restore w/out disk6. I have noticed that my processor is not being fully used by this version of Unraid so updating may even bring some gains.. When I built the box I had used a AMD PhenomII x6 core. This version of Unraid only seems to use 4 cores. Thanks again for help and suggestions.

Sorry - when the data is at stake - I get all nervous nilly =) Anyway - quick question. is there a way to bring this up on the parity drive like it had never been disconnected? Is this unwise? That way the whole array could come up and function until I replaced disk6 tomorrow. Just a thought. OR is this past that point, and the only thing to do is init config and go......

OK - just to be clear. I'm attaching a pic of the array currently. To successfully start the array without disk six. Should I un-assign the device for disk 6 before performing the initconfig ?

Valium in hand. Hoping we have an out here. UnRaid v4.7 1) I realized that our server wasn't performing up to par - we've had various power issues, with storms etc. - and the battery backup that services the disk array was in alarm. 2) I pulled up the server and saw that the PARITY disk was offline, but everything else seemed to be working. I needed to copy some files from the server and it did so without complaint. 3) I have a jpeg showing the configuration that appears when i looked it up. The PARITY, & ( DISK4, DISK5, DISK6 ) all live in a small rack outside of the actual server case and have their own powersupply. ( the one in alarm ) I shut down the array and went down to check power and data connections. The external nature of this arrangement has meant that i have done this a couple times over the last few years. NOW HERE IS THE PINCH - PARITY and DISK6 share a power circuit from the powersupply, and earlier when using the array i never touched anything on DISK6. In fact theres a good chance that DISK6 hasn't been used specifically for anything in a long time. - next - made my heart sink. I replugged the power and data cables and turned the stack on. the powersupply started, went into alarm, and smoke came from the back of DISK6..... I unplugged DISK6 and started the server. Everything comes up - but the array says that the PARITY is a new disk...... and of course with DISK6 out, this thing is not going to start freely for me. Look, I don;t care about whats on DISK6. I do care about the rest of the array. HELP? Attaching a pic of the setup and the syslog syslog.txt